The off-the-shelf trap
Most supply chain teams start with off-the-shelf software because it's the obvious first move: it's already built, it has a sales team ready to demo it, and it promises to handle everything from purchase orders to warehouse picking out of the box. For a while, it usually does. The trouble tends to show up later, once the business has grown into shapes the software wasn't designed for.
That's when the workarounds start. A spreadsheet bolted on to handle the one workflow the system doesn't support. A second system for the part of the business the first one never fit. A person whose actual job has quietly become "translate between the systems by hand." None of this is a failure of judgement. It's what happens when a generic tool meets a business that isn't generic.
Why "generic" is the actual problem
Off-the-shelf supply chain software is built to serve as many businesses as possible, which means it's optimised for the average case, not any specific one. A distributor with a single warehouse and a manufacturer running multiple production lines might both be sold the same platform, then both spend months configuring it toward two very different realities it was never quite built for.
This shows up in predictable places:
- Approval workflows that don't match how the business actually signs off on purchases or stock movements.
- Reporting that shows what the vendor decided mattered, not what this specific operation actually needs to see.
- Integrations with the other systems the business runs that are either unsupported or require an expensive add-on.
- Terminology and structure that doesn't map cleanly onto how the business actually organises its inventory, suppliers, or facilities.
Every one of these is survivable individually. Together, over years, they add up to a system the business works around rather than a system that works for the business.
What custom software actually buys you
The case for custom software isn't that it's inherently better than an off-the-shelf platform. It's that it's built around how a specific business actually operates, instead of asking the business to reshape itself around the software.
That shows up concretely: approval chains that match who actually needs to sign off, not a generic three-tier hierarchy. Reports built around the decisions this business actually makes. Integrations with the specific systems already in use, rather than a marketplace of pre-built connectors that may or may not cover them. And critically, the ability to change the system as the business changes, without waiting on a vendor's product roadmap or paying for a tier upgrade to unlock a feature that should have been basic in the first place.
Where this makes the most sense
Custom software isn't the right call for every part of every business. A small operation with simple, standard processes and no urgent scaling pressure can genuinely do fine on a well-chosen off-the-shelf platform for a long time.
It starts to make sense once a few things are true at once:
- The workarounds are multiplying. Each new workaround is a sign the underlying system doesn't fit, not a one-off exception.
- Growth is exposing the ceiling. A system that worked at one location or one product line starts to strain as the business adds more of either.
- Data is scattered across tools that don't talk to each other, and someone is manually reconciling it.
- The "customisation" available is really just configuration, and the business needs something the platform's configuration options don't cover.
Build vs. buy is really build vs. workaround
The honest comparison usually isn't "custom software vs. a perfect off-the-shelf fit." It's custom software vs. the accumulated cost of workarounds around a system that's close but not quite right. That cost is real, it's just spread out and harder to see on a single invoice: the hours spent reconciling spreadsheets, the errors that come from manual data entry between systems, the person who's become the unofficial translator between two tools that should be one.
If that pattern sounds familiar, supply chain software development built around how the business actually operates, rather than how a generic platform assumes it should, is usually the more honest comparison to make. Sometimes the right answer is still an off-the-shelf tool. But it should be a decision made with the real cost of the workarounds on the table, not just the sticker price of the software.