Automation for wholesale and distribution

The order that arrived at 7pm and missed the van

In short: For a wholesaler or distributor, automation usually means taking the daily stream of emailed, PDF and spreadsheet orders, reading them, checking each against the delivery-day cut-off, minimum order value and carriage rules, and queuing them for a person to approve before they enter the order system. The order desk keeps the phone and the exceptions; the typing goes.

Sandra finds the 7pm order at half past ten

A café owner cashes up, checks the fridge and emails tomorrow's order at seven in the evening. By morning it is under 40 newer emails. Sandra works down the inbox from the top, typing each order into Sage, checking the minimum order and the delivery day from memory.

She reaches the café's order at half past ten. The van for that round left at nine. The café gets its cheese a day late, and next month it tries another wholesaler.

Every order is read as it arrives, whatever the hour. At seven the next morning Sandra has them in delivery-round order, each one matched to its account, with the cut-off and the minimum already checked. The café's order is near the top, because its van goes first.

She approves the routine ones in a few minutes and spends her time on the two that need a phone call.

The people in this story are made up. The work is not. Your own figures come from the assessment.

What a week looks like for wholesale and distribution

  • Orders arrive by email, PDF, spreadsheet and phone, and every one is keyed into the order system by hand.
  • An order sent at 7pm sits under newer emails and misses the van.
  • A case is keyed as a single, or an old price goes through because the new agreement never reached the order desk.
  • The price list, the stock sheet and the order system disagree, and credits follow.
  • Standing orders and amendments live in people's heads.

We speak your language

cut-off time · minimum order value · carriage charge · pack size versus unit · back-orders · standing orders · customer-specific product names · price list · proof of delivery

What usually pays for itself first

Email and PDF orders into your order system

Read, matched to the right customer and products, checked against your rules, approved by a person, then created in Sage, Opera, Khaos or your own system.

Supplier price lists loaded safely

Supplier price files in PDF and spreadsheet form with different codes, matched to your products with a change report for your buyer to approve.

Order confirmations and delivery updates

Confirmation of what was accepted, what was substituted and when it will arrive, sent automatically from the approved order.

Systems we see in this sector

Sage 50, Sage 200, Khaos Control, Unleashed, Pegasus Opera 3, Spreadsheets and Word documents. If yours is not listed, it almost certainly still has a route in; see systems without an API.

Questions people ask

Our customers each use their own names for our products. Does that break it?

No. The matching step learns each customer's names and codes from their past orders and your records. Unknown names are held for a person the first time and remembered afterwards.

What about orders that break a rule, such as below the minimum?

The rule is applied exactly as your team applies it today: hold the order, add the carriage charge, or flag it for a call. You decide the rule; the automation applies it every time.

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.