Your Potteries ERP ends at the firing schedule, and that's where the money leaks
A custom ERP (Enterprise Resource Planning) for a Stoke-on-Trent pottery or fulfilment operation typically runs $95k to $180k over 6 to 9 months. You go custom when off-the-shelf systems like NetSuite or Odoo can model your finance and stock but cannot model a bottle kiln's firing cycle, biscuit-then-glost double firing, or seconds-grading, which is exactly where your margin and your stockouts hide.
NetSuite, SAP Business One and Odoo all assume a unit of stock either exists or it doesn't. A Potteries maker lives in the gap between those two states: a mug is clay, then biscuit-fired ware, then glost-fired finished stock, then either firsts or seconds depending on what came out of the kiln. None of the off-the-shelf ERPs have a native concept for a firing batch with a 14-hour cycle, a yield that varies by range, and a grading step that splits one production order into two sellable SKUs at different prices.
So the firing schedule ends up in a spreadsheet the ERP never reads. Your store shows 40 of a popular range available because the system counted the kiln load as finished, but eight came out crazed and got downgraded to seconds. The customer who ordered a wedding set gets a backorder email, and a six-generation family name takes the hit for a glaze fault no accounting package was ever going to predict.
Where the off-the-shelf tools fall short
- Kiln firing schedules and yield live in Excel; the ERP books the whole load as good stock before grading happens
- Biscuit and glost firing stages have no representation, so work-in-progress value is guessed at month-end
- Seconds and firsts split from one production order, but the ERP only knows one SKU per item
- Lead times quoted to trade buyers ignore real kiln capacity, so promised dates slip a fortnight
Custom erp: what Stoke-on-Trent teams actually get
A custom ERP encodes the actual physics of your floor: a clay batch becomes a fireable load, a firing run produces a graded yield, and that yield posts firsts and seconds to separate SKUs with real costs attached. When a kiln load finishes, available stock updates in the same second your ecommerce store reads it, and the cost of a fired mug includes the gas, the labour, and the proportion of the load that went to seconds. That's the number a generic SaaS will never give you, and it's the number that tells you which ranges actually make money.
- You fire multiple ranges across more than one kiln and grade output into firsts and seconds
- Online ranges sell out before stock counts catch up to graded reality
- You run both trade accounts and direct ecommerce and reconcile them by hand
- Energy is now a top-three cost and you can't attribute it per firing
- You make a single range, fire one kiln, and rarely grade down
- Your volumes fit comfortably inside Odoo's manufacturing module without firing nuance
- You sell only wholesale on fixed terms and don't run a live storefront
- Cash flow won't carry a multi-month build through a quiet trading season
- Stock counts that reflect graded kiln output, so popular ranges stop overselling before the firing finishes
- True per-firing cost including energy, labour and yield loss, broken down by range and kiln
- One system feeding your ecommerce store, your trade-account ledger and your dispatch labels from a single stock number
- Capacity-aware lead times quoted from real kiln slots, not a flat default that ignores the firing queue
- Seconds tracked as a managed revenue stream instead of a shrug at month-end
- You take on the maintenance burden a generic ERP vendor would otherwise carry, including upgrades and security patching
- A bespoke firing-yield model takes longer to validate than switching on a NetSuite module, often a full firing season
- If your team is used to Sage's familiar screens, retraining the office on a new flow is real change-management work
- Custom integrations to couriers and marketplaces need ongoing care as those APIs change underneath you
Feature priorities for Stoke-on-Trent teams
Stoke-on-Trent ERP: the full scope
The engagements Stoke-on-Trent teams bring us most often: SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP, manufacturing ERP and distribution ERP.
The honest cost picture for Stoke-on-Trent
| Project scope | Typical cost | Timeline |
|---|---|---|
| Firing-aware stock and finance core | $95k to $140k | 6 to 8 months |
| Full kiln-to-dispatch suite with grading and ecommerce sync | $140k to $200k | 8 to 11 months |
| Multi-site Potteries group (several factories, shared trade ledger) | $200k+ | 11 to 16 months |
Timeline: what happens, and when
Exactly what you get
You get an ERP that treats a firing as a first-class event, not an afterthought. When a kiln load is logged and graded, the system posts firsts and seconds to separate SKUs, updates available stock for your storefront in real time, and accrues the true cost of that load including gas and yield loss. Your office stops re-keying the firing schedule into a spreadsheet, your trade ledger and retail orders draw on one stock number, and your month-end work-in-progress value is calculated, not guessed. Pair it with a custom inventory management system and a warehouse management system and the dispatch end stops fighting the production end.
How to choose a developer in Stoke-on-Trent
Pick a team that asks to watch a firing before they write a line of code. The ones worth hiring will want to see how you grade ware, how seconds get priced, and where the dispatch sheet diverges from the store. Ask for a reference in UK manufacturing or fulfilment, insist on a parallel-run plan that spans at least one full trading cycle, and make sure the contract names who owns the courier and marketplace integrations long-term. A local team that understands the six-towns family-firm culture will earn trust faster on the shop floor than a remote vendor who's never smelled a kiln.
- !They demo a stock module but go quiet when you ask how it models a firing batch; ask them to whiteboard biscuit-to-glost-to-grading before you sign
- !They quote a fixed price before seeing your firing schedule; ask what assumptions that number hides
- !No plan for grading firsts and seconds from one production order; ask exactly how a downgraded load posts
- !They want to rip out Sage on day one; ask how they'll run the new system in parallel for one full season
- !They've never integrated a UK courier or marketplace; ask for a named reference in fulfilment
Teams investing in erp in Stoke-on-Trent usually scope it next to internal tools, shopify, inventory management, since these systems share data and budgets.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Can't NetSuite or Odoo handle ceramics manufacturing out of the box?
They handle the finance and the warehouse well, but neither has a native firing-batch concept. There's no built-in way to model a 14-hour biscuit-then-glost cycle, a yield that varies by range, or a grading step that splits one load into firsts and seconds. You can bolt that on with heavy customisation, at which point you're paying for a half-custom build inside someone else's framework anyway.
How long before a Stoke-on-Trent pottery sees payback?
Most makers see the firing-yield and energy-cost reporting pay for itself within the first full season, because it surfaces loss-making ranges you were subsidising blindly. The stockout fix, where popular ranges stop overselling, protects revenue and reputation from day one of go-live.
Will it sync with our Shopify store?
Yes. A core requirement is that graded stock pushes to your storefront the moment a load clears grading, so the available count online matches firsts in the rack, not the whole load you hoped was good. This is the single change that stops the oversell.
What about our existing Sage accounts?
A good build runs alongside Sage during a parallel season and migrates open balances, the chart of accounts and trade-account histories cleanly. You don't switch off your finance system until the new ledger has reconciled against it for a full cycle.