16 September 2026
In short
What should warehouse software do for a business at Magna Park Lutterworth?
Most occupiers at Magna Park cannot change their warehouse system, because the client contract names it. So the useful work is the layer around it: label standards, pick confirmation and reporting across contracts. GTX Digital builds that layer without touching the WMS.
- On a contract site the WMS is a given. The layer around it is yours.
- A label standard is worth more than a module, and costs almost nothing.
- Pick confirmation is the difference between a stock figure and a guess.
- No client-mandated WMS reports across two clients, and that is the number you need.
- Build outside the WMS so a contract change does not take your tooling with it.
Think this applies to your business?
We will tell you straight whether it is worth doing, what it would take, and what we would do instead if it is not.
Operating a contract site here? Book a technology review. Bring the contract, not just the system — the constraint is usually in the paperwork.
There is a question people at Magna Park almost never get to answer. Which warehouse system should we use?
Why the system is not your decision
On a third-party contract the client usually names the WMS. Sometimes they own the licence. Sometimes they own the hardware too.
That is not unreasonable. They need their stock visible in their own estate, and they are paying for the operation.
But it does mean the normal advice — pick a better system — is useless here. We wrote about what that leaves in software development for businesses at Magna Park Lutterworth. This article is the warehouse half of it.
Start with the label, not the software
The cheapest improvement on most sites is a labelling standard, and it is routinely skipped because it sounds administrative.
Here is what it decides. Whether a pallet can be scanned once and understood by three systems. Whether a mixed pallet can be broken down without a keyboard. Whether your customer's barcode and your location barcode can ever be confused.
| Decision | Cheap version | What it costs later if skipped |
|---|---|---|
| Location naming | Aisle-bay-level, fixed width | Every new starter transposes two digits for a year |
| Pallet ID | One licence plate per pallet, never reused | Two pallets with one identity, found at stock count |
| Customer references | Stored as data, printed as barcode | Someone retypes an order number at despatch |
| Mixed pallets | A parent-child relationship | A pick face that disagrees with the rack |
None of that requires access to the WMS. All of it changes what is possible afterwards.
Pick confirmation is the real line
There are two kinds of warehouse. One knows what was picked because it was confirmed at the face. The other knows what was supposed to be picked.
The second kind has a stock figure that is a forecast wearing a uniform.
If the mandated WMS does not confirm at the face, that is the single highest-value thing to build around it: a scan at the moment of the pick, reconciled back, with the exceptions surfaced rather than buried.
It is also the one that makes a stock count survivable, because you are reconciling a short list rather than auditing a quarter.
The number no mandated system will give you
Ask a client-provided WMS how your site performed last week across all contracts and it will politely decline. It knows one contract. It is not supposed to know the others.
So the thing you most need as an operator — cost and performance per unit shipped, across the whole building — has to live outside the WMS.
That is a small warehouse of your own: hours from the time system, volumes from each contract, a shared dimension for date and shift. Not glamorous. It is the number that tells you which contract is actually profitable.
Build it so a contract change cannot take it with it
This is the part worth insisting on at design time.
Contracts end. When one does, the client's WMS goes with it, and anything you built inside that system goes too.
So the layer you own should sit outside, read from whatever each system exposes, and store its own history. Then losing a contract costs you the contract rather than three years of operational data.
We build this as bespoke software development, with the local engagement on the Lutterworth page.
Proof of delivery, briefly
Two rules cover most disputes.
Capture it at the moment of handover, not from the office afterwards. And attach it to a reference your customer actually quotes, as well as to your own.
A photograph with a timestamp and a signature beats a note in a system every time, and it costs the price of the device already in the driver's hand.
What tends to come first
In order of how often it pays back on a park like this.
- Pick confirmation at the face, if the mandated system does not do it
- A labelling standard, written down and enforced at goods-in
- Cross-contract reporting, owned by you rather than a client
- The customer feed somebody has already asked for in writing
- Returns, if you move anything with a serial number or a core
Damages and shorts deserve their own reasons
Every site has them, and most record them badly.
A short pick gets adjusted. A damage gets written off. A mis-ship gets credited. Three different events with three different causes, and in a lot of systems all three end up as one adjustment reason called something like stock correction.
So nobody can say whether the problem is the supplier, the racking, the picker or the carrier.
Giving those events distinct reasons, captured at the moment they happen, is a half-day change. It pays for itself the first time you argue with a supplier about inbound damage and have the numbers.
Where this fits locally
Magna Park is the largest concentration of this kind of operation in the Triangle, which means the labour pool understands the work and the systems arrive from somewhere else.
We work with logistics and 3PL and distribution and wholesale businesses along this corridor, and the wider local picture is on the Lutterworth page.
The ERP side of the same question — getting this data into a finance system that was never designed for it — is in ERP integration for Magna Park Lutterworth businesses.
A reasonable first step
Walk to a pick face and look at the label. Then look at the label on the pallet it came from.
If you cannot tell from those two labels alone what the item is, where it belongs and whose it is, you have found the first project. Talk to us.
Common questions
Can we change the warehouse system on a contract site?
Usually not. If the client specified it, it is part of what you agreed to operate, and replacing it reopens the contract. Building around it does not.
What can be built without touching the WMS?
Most of what people actually want: cross-contract reporting, labour and cost per unit, label and barcode standards, customer feeds, and the exception handling the WMS treats as an afterthought.
Will building around it cause data to disagree?
Only if you let two systems both believe they own stock. Decide the master record first and the rest follows.
Next step
Start with a technology review, not a proposal.
A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.