Every trade order that goes out wrong costs you twice: once to fix it, and once in the customer's slightly lowered opinion of you. The good news is that trade counter errors are not random — they fall into five predictable types, each with a known cost profile and a known fix. If you want to reduce order entry errors, the first step is naming them. Here is the taxonomy, what each one costs, and the process and software changes that kill each one at source.
Error one: the wrong SKU
The classic. Similar part numbers, near-identical products in different sizes or ratings, or a staff member typing from memory. The 22mm valve instead of the 15mm; the left-hand hinge instead of the right. The cost is a full round trip — pick, pack, dispatch, customer discovers it, return shipping, re-pick, re-dispatch — plus a restocking job and, on a job-critical part, a customer whose project stalled because of you. Realistically £15–40 in direct handling per incident before you count goodwill.
The fixes are mechanical. First, scan instead of typing wherever a barcode exists — a scanned SKU is the right SKU. Second, for items without barcodes, use a search that shows the product name and live stock next to the code, so the picker of the order is effectively double-checked by the person keying it. Third, clean up your catalogue: if two SKUs are routinely confused, rename them so they cannot be. A counter tool like Trade Order POS handles the first two directly — USB scan-to-add and live search by SKU, barcode or name against your Linnworks inventory.
Error two: the wrong price
Wrong-price errors split into two families. Undercharging is silent — nobody rings to complain — which is what makes it dangerous. A counter hand gives a walk-in the trade price, or quotes last year's price from memory, and the margin simply evaporates. Overcharging a trade regular is louder and worse: he checks, he rings, and now there is a credit note to raise and trust to repair. Either way, the root cause is the same: the correct price for this customer on this item was not in front of the person taking the order.
Fix the information problem and the error disappears. Per-customer price memory — defaulting each line to what this customer actually paid last time — removes guesswork for repeat business. Deliberate structures beat memory at scale: named price tiers with formula-driven prices mean the trade price is the trade price, not an opinion. And when a genuine override is needed, it should be an explicit, visible act on the order line, not a habit. We have covered the structural side in tiered pricing in Linnworks without spreadsheets.
Error three: the wrong customer
Two customers called Dave, three businesses with "Building Services" in the name, and an order lands on the wrong account. The direct cost looks small — re-key the order — but the downstream cost is nasty: the wrong business gets invoiced, statements go out wrong, and if the misfiled order included agreed pricing, customer A has now seen customer B's rates. That last one can sour a relationship permanently.
Process fix: confirm the account, not the first name — read back the company name and postcode before taking the order. Software fix: customer auto-fill from order history, so you are selecting a real account record with its address attached rather than free-typing a name that may or may not match. Selecting from history also brings the right pricing with it, which closes off error two at the same time.
Error four: the wrong address
Trade customers are the hardest addressing problem in commerce because the goods rarely go to the account address. They go to site — and the site changes weekly. Send a pallet of materials to the builder's yard when the brickies are waiting on plot 14, and you have not just lost a delivery, you have idled his trades for a morning. Redelivery cost, plus a genuinely angry customer.
The process fix is a hard rule: every delivery order gets the destination read back and confirmed, however well you know the customer. The software fix is making the delivery address and delivery notes explicit fields at order entry — "Site: plot 14, Wainwright Rd, call Micky on arrival" captured in the order's delivery notes travels with the order into Linnworks and onto the courier paperwork, instead of living in the counter hand's short-term memory.
Error five: the missed delivery charge
The quietest leak of the lot. The order is right, the price is right, the customer is right — and the £18 pallet delivery never made it onto the order. Nobody notices, because nothing goes wrong: the goods arrive, the customer pays the invoice, and you have donated the haulage. At two missed charges a week that is comfortably over £1,500 a year, straight off the bottom line.
Fixes: make delivery charge a standard field in the order flow, so keying an order for delivery without a charge is a visible act rather than an invisible omission. Then audit — once a month, list delivered orders with a zero delivery charge and ask why. Most businesses that run this audit once are startled by what they find. Related leak, same family: minimum order values that exist in theory but are never enforced at the counter — see our piece on minimum order values for trade accounts.
Building the error-resistant counter
Pulling the threads together, the pattern behind all five fixes is the same: replace memory with systems, and typing with selection.
- Scan what can be scanned; search-and-select the rest. Never free-type a SKU.
- Let prices come from customer history or defined tiers, with overrides as visible exceptions.
- Select customers from records, and read the account back.
- Capture delivery address and notes as fields on the order, confirmed aloud.
- Make the delivery charge a step you consciously skip, not one you can forget.
And send a confirmation. An automatically emailed order confirmation turns the customer into your final proofreader — if the PDF that lands in his inbox shows the wrong quantity or the wrong site address, you hear about it while the order is still on the bench, not after the van has left.
Trade Order POS builds these guardrails into the counter for Linnworks sellers — scan-to-add, customer auto-fill with price memory, delivery charges and notes on every order, and automatic branded PDF confirmations, from £28.79/month with a 14-day free trial via the Linnworks Application Store. Try it at trade-pos.mcp-g.com and start cutting the cost of getting orders wrong.