Skip to main content
Stokka

Getting off spreadsheets

When spreadsheets stop working: the MRP switchover

The signs that you have outgrown your production spreadsheet, the cost of staying, and a practical migration plan for small manufacturers making the jump.

20 April 20268 min read

Every small manufacturer runs on a spreadsheet until, one week, they don't. The moment is rarely dramatic. You miss an order. You build against a BOM that is two versions old. You tell a retailer you have stock and it turns out you had stock on Tuesday. The cost of the spreadsheet has, quietly, become larger than the cost of replacing it.

This is a practical guide to recognising that moment, understanding what actually breaks, and moving to an MRP system without losing a month of trading.

The honest signs you have outgrown it

Not theoretical. These are the real-world symptoms small manufacturers report when they finally switch:

  • Stock figures are wrong by Wednesday. Monday's count was clean. By midweek, nobody is sure which cells reflect reality.
  • Two people have different versions of the BOM. Production is running against an older one than purchasing.
  • You have started copying totals into a second file manually. The formulas broke. You replaced them with a weekly recon.
  • Reorder points live in someone's head. Your most experienced person is also your single point of failure for purchasing.
  • Traceability is a phone call. A recall would mean shutting down for an afternoon to reconstruct who got what.
  • Shopify / Xero inventory numbers never quite agree. You do a reconciliation monthly and never investigate why.

Two or more of these on a permanent basis is the signal. You are paying for the spreadsheet in silent errors, margin leak, missed orders, overbuying, expired stock, and you are paying more than software would cost.

What spreadsheets actually break

A spreadsheet is a brilliant calculator and a poor database. The specific things it does badly:

  1. Concurrent editing.Two people updating stock at once overwrite each other's cells.
  2. Relational lookups at scale. Finding every batch that used batch X across a year of production is technically possible and practically awful.
  3. Unit of measure discipline. Nothing stops you from entering grams in a kilograms cell.
  4. Audit trail. Who changed what, when, and why is not captured.
  5. Real-time integration.Shopify sells a unit and the spreadsheet doesn't know until someone opens it.

Spreadsheets are cheap, familiar, and wrong by Wednesday. They are the right tool for year one. They are the wrong tool for year three.

What an MRP system actually buys you

The specific capabilities, in order of how much pain they remove:

  • A single source of truth for stock, updated as orders ship and runs consume. Same number on every screen.
  • A production plan that reads demand (orders, subscriptions, forecast) and compares it to supply (on-hand plus work-in-progress) to surface the gap.
  • BOM-aware purchasing. Reorder suggestions come from usage and supplier lead times, not a sticky note.
  • Batch-level traceability, captured at the point of use, with the full downstream lookup available in seconds.
  • Integration with the systems you already use. Xero or QuickBooks for accounting, Shopify for orders, so stock counts don't drift.

The migration, in a practical order

The mistake most small manufacturers make is trying to move everything at once. A staged switchover over two to three weeks works better than a big-bang cutover.

  1. Week 1

    • Master data. Import products, BOMs, suppliers, customers, and warehouses. Clean up the names and units as you go. Do not import history.
    • Opening stock. Do a proper count on a quiet day and enter it as the opening position. This is also a good moment to close out the dead SKUs you have been meaning to.
  2. Week 2

    • Parallel run. For 5–10 production days, run both systems. Spreadsheet stays as the book of record, but everything new goes into the MRP too. You will find your UOM mistakes here.
    • Switch sales and purchasing. New sales orders and POs are created in the MRP only. Accounting integration goes live.
  3. Week 3

    • Traceability and reporting on. Batch capture at the shop floor. Standard reports replace the hand-rolled weekly sheet.
    • Archive the spreadsheet. Read-only. Reference-only. Not updated any more.

What to look for when picking

For a small manufacturer, the useful checklist is short:

  • Pricing that matches your stage, unlimited seats once you're past the entry tier. Per-seat models above a base plan punish the team that already runs lean.
  • BOMs with yield, sub-assemblies, and alternates. Anything less will trip you inside a month.
  • Batch-level traceability by default. Not a premium add-on. Not a module.
  • Native integrations with Xero / QuickBooks and Shopify. Zapier is not a plan.
  • A shop-floor view that runs on a tablet. The people doing the work cannot be the people not in the system.
  • Setup measured in days, not months.If the contract starts with “we'll need a discovery phase”, you are looking at enterprise software.

How Stokka fits this shape

Stokka was built for the gap between spreadsheets and enterprise ERPs. Quoted per deployment, with unlimited users and no per-seat fees. Every customer runs the full OS: multi-level BOMs with assemblies and disassemblies, multi-warehouse inventory, and full order lifecycle. Batch traceability is in the product today. Xero, QuickBooks and Shopify sync are coming at launch. Shop-floor tablet mode is on the roadmap.

You can import your existing spreadsheet on a Tuesday and be trading through the MRP by the following Friday. A 30-day free trial means the parallel-run fortnight costs you nothing.

Further reading

If you are at the research stage, read what MRP actually is and MRP vs ERP. If your BOMs are the weakest part of your current setup, start with how to build a bill of materials properly.

Keep reading

Related posts