Should I replace my legacy ERP or add a custom layer?

Ripping out a platform the business already knows and has paid for is rarely the right first move. The gap sits beside it, not underneath it. The platform stays. Only the missing piece gets built.

What decoration-specific workflows do generic ERPs miss?

Decoration BOMs, a blank plus a decoration method plus thread or ink plus setup time, are rarely represented cleanly in a generic ERP. Blank versus finished goods tracking and supplier artwork versioning are likewise missing from most platforms.

How does the layer-stack model work, the platform stays, what changes?

The existing platform continues handling stock, orders, and accounts exactly as it always has. A custom layer sits beside it handling decoration BOMs, blank-to-finished-goods mapping, and artwork versioning, exactly the jobs the platform does not do.

How do I know what my platform needs beside it?

A Clarity Audit produces a written assessment of what your current platform handles well, what it does not, and a fixed price for the layer that closes the gap.

Is replacing our legacy ERP always a bad idea?

Ripping out a platform is rarely the right first move. Most businesses save time and money by adding a custom automation layer to do the decoration-specific jobs the ERP was never built for, keeping the platform they already know and have paid for.

The problem

The platform you bought ten years ago wasn't built for decoration.

Generic ERP and stock systems are built for businesses that buy and sell the same thing they hold in the warehouse. Decoration doesn't work like that. A blank garment becomes a different, finished product the moment it's printed or embroidered, and most platforms have no clean way to model that.

Book a free 60 minute call

A blank polo shirt beside its decorated version, the same product, two entirely different things to a generic ERP. — BLANK STOCK, FINISHED PRODUCT

Sound familiar?

Seven signs the platform wasn't built for this.

If you recognise three or more of these, the problem isn't your team working around the system. It's the system never having been designed for decoration in the first place.

Decoration BOMs are tracked in a spreadsheet because the platform can't model them
Blank and finished stock get confused, or tracked as if they're the same item
Supplier artwork lives in email threads, not attached to the order it belongs to
Print, embroidery, heat-press: every method needs its own workaround
The vendor's support team asks what “decoration BOM” even means
Customisation costs have exceeded what the licence was supposed to save you
You've quietly accepted this is “just how the software is” rather than fixable

The fix

Keep the platform. Add the layer it's missing.

Ripping out an ERP you've already paid for and trained staff on is rarely the right answer. Read bottom-up: the platform stays exactly where it is, and the missing layer sits on top of it, not instead of it.

Your platform, unchanged

Whichever one you run stays as the system of record for orders and accounts

Layer 1

The Decoded Data App

Decoration BOMs, blank-to-finished mapping, and supplier artwork, modelled properly for the first time

Layer 2

Website, marketplaces, trade portal

Every channel reading the same decoration-aware catalogue, instead of a generic one

Layer 3

How I help

No rip-and-replace. Just the layer that was missing.

I don't start by asking which new platform to buy. I start with what your current platform already does well, then build the layer that fills the gap: decoration BOMs, artwork, blank-to-finished stock. Without touching what already works.

A Clarity Audit tells you honestly whether that's a small layer, a bigger one, or whether the platform genuinely needs to change. Rarely the last one.

Find out what layer your platform is actually missing.

A Clarity Audit scopes the gap and prices the fix, before anything gets ripped out.

Book a free 60 minute call See the Data App