How much does manual trade pricing cost a wholesaler?

In a worked example of 30 orders a day at 7 lines each and 30 seconds of lookup per line, a business loses about 1 hour 45 minutes daily, roughly £6,370 a year in rep time, before adding around £12,000 of margin lost to pricing errors.

Why is trade pricing so slow in Linnworks?

Linnworks holds one retail price per SKU, but trade customers do not pay retail. The rep has to combine three things in their head: who the customer is, what tier they are on, and the tier price for that SKU, each often living in a spreadsheet or someone's memory.

How do B2B Price Tiers and Trade Order POS work together?

Assign a customer to a tier in B2B Price Tiers, and the next time you pick that customer in Trade Order POS every cart line auto-fills at the right tier price. Below-minimum orders and below-cost lines trigger prompts, so the rep does zero lookups.

Do these Linnworks pricing apps need a particular subscription?

Yes. Both B2B Price Tiers and Trade Order POS need a Linnworks Premium or Multichannel subscription to access the API; Linnworks Standard is not enough. Both offer 14-day free trials with no card details needed, billed by Linnworks via the Application Store.

The hidden cost of typing in trade prices manually (and the fix)

Every B2B wholesaler we talk to underestimates how much time their team loses to manual trade pricing. Here's the worked example we use with prospects to show them the shape of the leak — and the two-app fix that closes it.

The worked example

Take a small wholesale operation with these realistic numbers:

30 trade orders per day across counter + phone.
Average 7 line items per order.
Average 30 seconds spent looking up the right price per line — checking the customer's tier, scrolling a PDF or spreadsheet, manually typing it in.
That's 30 × 7 × 30s = 1 hour 45 minutes per day lost to price lookup.
Across one full-time rep at £14/hour fully-loaded: £24.50 per day, £6,370 per year in lookup time alone.

Now add the cost of getting it wrong. Industry data on B2B pricing accuracy suggests 2–5% of trade-counter orders have a pricing error. On £400,000 of trade turnover with a 3% error rate, that's £12,000 of margin walking out the door every year — usually in the wrong direction, because reps under time pressure undercharge more than they overcharge.

Total annual cost of doing it manually for this size of business: ~£18,000.

Why it happens

Linnworks gives you one retail price per SKU. Trade customers don't pay retail. So the rep has to combine three things in their head:

Who is this customer?
What tier are they on? (If you have tiers at all.)
What's the tier price for this specific SKU?

If any of those three pieces lives in a spreadsheet, the rep has to alt-tab to find it. If it lives in someone's head, the rep has to ask. Both are slow, both are error-prone.

The two-app fix

We built two apps that, together, collapse the lookup time from 30 seconds per line to zero:

B2B Price Tiers — the wholesale pricing engine. Define named tiers (Trade, Wholesale, Enterprise, RRP), drive them with simple formulas (cost × markup, or RRP × discount), apply attractive rounding automatically, sync prices into Linnworks as extended properties. £29.99/month, 14-day free trial.
Trade Order POS — lightning-fast B2B order entry. Scan barcodes, search by SKU or name, pick a customer from a database built from your last 3 years of Linnworks orders. Solo £28.79/month, Team / Pro £76.79/month, 14-day free trial.

The integration between them is the bit that earns its keep:

You assign a customer to a tier in B2B Price Tiers (or directly from inside Trade Order POS while taking an order).
The next time you pick that customer in Trade Order POS, every line in the cart auto-fills at the right tier price.
If the customer's tier has a minimum order value, the POS prompts the rep when the order falls below it.
If a line is priced below cost — by accident or override — a margin warning flags it.

The rep at the counter does zero pricing lookups. The order lands in Linnworks open orders at the right prices. The invoicing team has nothing to fix.

Re-running the worked example

With both apps wired up:

Lookup time per line: 30s → 0s.
Lookup time per day saved: 1h 45m.
Annual lookup time recovered: ~£6,370 in rep time.
Pricing-error rate: 3% → <0.5% (the only errors left are intentional overrides).
Annual margin recovered from pricing accuracy: ~£10,000.
Annual cost of the two apps: £28.79 + £29.99 = £58.78/month, or £705.36/year.

Net swing: ~£15,500 a year recovered, against ~£700 a year cost. 22× payback in the first year.

(Numbers go up linearly with your trade volume. The same logic on a £1M trade-turnover operation puts the recovery north of £35k a year.)

The honest caveats

You have to actually define your tiers. If your pricing is genuinely bespoke per customer (no patterns at all), tiering doesn't fit — but in our experience that's rare. Most "bespoke" pricing is three or four buckets in disguise.
You need someone to do the initial set-up — define the tiers, pick the formula per tier, map customers to tiers. That's a few hours of work, not weeks.
Both apps need a Linnworks Premium or Multichannel subscription to access the API. Linnworks Standard isn't enough.

How to test the model on your own numbers

Two-minute exercise: count the trade orders you took yesterday, multiply by lines per order, multiply by 30 seconds. That's the lookup time you can recover. Run it past your finance person before you commit.

If the maths works, both apps have 14-day free trials with no card details needed — you only subscribe (billed by Linnworks via the Application Store) once you decide to keep going. Wire them up and give your trade desk a week to feel the difference.

Want the numbers on your own catalogue and customer mix? Email hello@mcp-g.com with your trade order volume and tier structure, and we'll send back a 1-pager sizing what you'd recover.