Nothing is overwritten
Every movement is added to the history. A quantity that changed has a reason, a person and a timestamp attached to it, permanently.
Why DKayMRP exists
We read what manufacturers say about the systems they are stuck with. Then we built the opposite.
Before writing any of it we went through the places manufacturers complain honestly about the software they already have. Every complaint that kept coming up became a rule for how this one works.
01Research, not testimonials
Their words about the systems they are living with.
These are complaints manufacturers make in public about other people's software. They are not reviews of DKayMRP, and we will not dress them up as any.
What they say
“These systems are built for accountants, not for the people on the floor.”
What we did about it
The screens the floor uses came first, and accounting comes last. Every task is designed around the person holding the scanner, not the person closing the books.
What they say
“If logging a movement takes too many clicks, people will find a way around it.”
What we did about it
Recording a movement is one short form with the obvious answers already filled in and fields a barcode scanner can drive. If it is slower than the paper it replaces, it has already failed.
What they say
“They tried to roll out everything at once and we all went back to Excel.”
What we did about it
The modules stand on their own. Start with inventory, run it for a season, and add manufacturing when you are ready, not because a contract says this is the month.
What they say
“Software will not fix a process that is already broken on paper.”
What we did about it
Completely agree, so we do not pretend otherwise. We start by walking how stock actually moves through your building, then fit the software to that, not the other way round.
What they say
“The one engineer who built our custom system left, and now nobody can touch it.”
What we did about it
The reason every rule in this system is written down next to the code is that bus factor is the single thing buyers are right to fear about bespoke software. Your data is yours and exportable, and nothing here is a black box you cannot leave.
What they say
“The schedule says eight hundred hours are available. Reality is six hundred and fifty.”
What we did about it
So the planner does not get to overrule your supervisor. Dates come from constraints you set and stay adjustable by the person who can actually see the floor, because a schedule nobody believes is a schedule nobody follows.
02How it is built
Four rules we hold ourselves to.
The floor comes first
If a task takes more clicks than the paper it replaces, it gets redesigned. Operators route around friction, and a system they route around is worse than no system.
Guide, do not block
Hard stops halt production and infuriate everyone. Where data is wrong we surface it in front of someone who can fix it rather than locking the line.
Modules stand alone
Each one is useful by itself and better with the others. Adoption is a sequence you choose, not a switch we flip.
03Scope, stated plainly
The things we will not build.
Scope creep is the named killer of manufacturing software rollouts. The fastest way to avoid it is to decide in advance what the product is not, and then hold that line in public.
01A general ledger
Journals, tax filing, bank reconciliation and payroll are solved problems with incumbents your accountant already knows. We export to them instead of rebuilding them worse.
02Machine and PLC connectivity
Reading signals off the machines themselves is a different product with different competitors. We are the planning and record layer above it.
03Finite-capacity scheduling
The kind that produces a beautiful schedule nobody on the floor believes. Constraints, dates and a plan a supervisor can adjust; not an optimiser that overrules them.
04An all-or-nothing rollout
There is no configuration in which you must take every module on the same Monday. If that is what you want, we are the wrong vendor and will say so early.
04Who this is for
Built to order, not to a forecast.
A strong fit
- You make to order or engineer to order, and no two jobs are identical
- Customer changes mid-build are normal, not exceptional
- You need batch or serial traceability for customers or inspectors
- Your stock lives in a spreadsheet only one person really understands
- You want to start with one module rather than replace everything
Probably not a fit
- You need a general ledger and full statutory accounting in one system
- You want machine-level OEE and PLC data collection
- High-volume repetitive make-to-stock, where cheaper tools already fit
- You need it live across every department next month
Still not sure it fits?