Perspective
Stock You Can Trust: How We Get an ERP Right Before It Goes Live
An ERP is only as reliable as the stock movements it receives. We close the gaps first, so your first module runs on figures your team already believes.
4-minute read5 November 2026
In Brief
- An ERP acts on every figure it holds. Stock that moved without a record turns into refused orders, false shortages and valuations nobody can explain.
- We see four actions that decide the outcome, all before configuration: map the real movements, name an owner for each, settle the master data, and count until variances are explained.
- Thinqmesh makes this the opening stage of an ERP engagement, then brings a first working module live on your own system within four weeks.
Ask a business that holds physical goods why it wants an ERP, and the answer is usually the same: the screen says one thing and the shelf says another. A new system fixes that only once the recording is fixed. That is why we start on the floor with a stock report, and why our ERP engagements open with stock accuracy.
Stock Is Where an ERP Succeeds or Stalls
Purchasing, production, sales and finance all draw on one balance in an ERP, so it treats every recorded figure as true. A spreadsheet tolerates a gap between the record and the shelf, because experienced staff know how to correct for it. An ERP acts on the gap.
The movements behind that gap are ordinary: a part lent to another branch over the telephone, material booked at the end of a shift as a round figure, returns waiting in a corner, a carton-to-piece conversion held in one person's head. Each is a sensible response to a system that made recording harder than not recording. So the remedy lies in the process, and it comes first.
Four Actions We Take Before Configuring Anything
Each one makes the stock figure more dependable, and each one is useful in your current system too, so the work holds its value from the first day.
Map the Movements as They Really Happen
We follow your goods with the people who handle them, and let the adjustments show where the gaps are.
We trace receipt, storage, issue, transfer, return and dispatch on your floor, then compare that map with the adjustments posted over the past year. A product group that needs frequent adjustment shows exactly where an unrecorded movement lives, and it tells us where the first design effort will pay back.
Get started
- List the ten items adjusted most often last year.
- Walk each one from receipt to dispatch with the person who handles it.
Name an Owner for Every Movement
Each kind of movement gets one role that records it, as close to the moment as the work allows.
Where recording in the moment proves impractical, we change the work with scanning, a simpler document or a different layout. The easiest way of doing the job becomes the way that records it, which is what makes the change last.
Get started
- Write down who records each transfer, issue and return today.
- Mark any movement that nobody records at all.
Settle the Master Data
Units, conversions, item codes and locations are agreed early, because they shape the configuration.
We agree these with you and merge duplicates, with a clear decision on whose history survives. Settling them now spares you rework later, and it gives every department the same language for the same stock.
Get started
- Pick one product family and list every code it is known by.
- Check how it is bought, stored and sold, and write down the conversions.
Count Until the Variance Is Explained
A full count gives you a correct balance for one morning. Repeated counts tell you the process works.
We count a sample of items repeatedly and trace every variance to its cause. Once variances fall and the causes can be named, the new process is working and the opening balance is worth migrating.
Get started
- Count twenty items with the people who handle them, and reconcile against the record.
- Repeat in a fortnight, and write down the movement behind each variance.
How Thinqmesh Solves This
We begin on your floor with your stock report, and the first module runs beside the systems you already use, so you can judge it on real work.
- Week 1
Your Real Data, in a Working System
We stand up the platform with data representative of your business, and walk the floor to find where stock moves without being recorded. By the end of the week your team is reviewing a working system.
- Week 2
Your Rules, and a Named Owner for Every Movement
Approvals, access and costing rules are configured the way you operate, and each type of movement gets a role that records it.
- Week 3
Your Records, Moved Across and Checked
We connect the systems you rely on and migrate your records. If your current system cannot export its data, we tell you first, and extraction gets its own date.
- Week 4
Real Work Running on It
Stock accuracy or job costing goes live on your own system. Further modules are agreed one at a time, in writing, and they move faster because the foundation is in place.
You finish with one job running on your own system, on figures your team trusts, and a clear view of what comes next. The code and the data are yours.
