Automation for food manufacturers and suppliers

Forty sites, forty ways of ordering, one production plan due by three

In short: For a food manufacturer or delivered food supplier, the valuable automation is usually order intake: the daily or weekly orders from many customer sites, arriving by email, portal, phone and spreadsheet, collated into a production plan, label quantities and delivery notes. Standing orders and late amendments are handled in one place, with a person approving the plan before it goes to the factory floor.

Mark builds tomorrow's production plan from forty emails

Mark is the operations manager at a food manufacturer supplying schools and care homes. Orders come from forty sites. Some email a spreadsheet, some fill in the portal, one cook texts. Every afternoon Mark copies them all into one workbook to work out what the factory makes tomorrow.

At ten to three a school rings to add 30 portions. He writes it on the printed plan in biro. The labels were printed from the earlier version, so the van goes out 30 labels short.

Orders from every site land in one list for each delivery day, with the standing orders already filled in. The 30 extra portions are entered once and the plan, the labels and the delivery notes all change together.

Mark reads the plan through, approves it and sends it to the factory floor. What the van carries is what the plan says.

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 food manufacturers and suppliers

  • Dozens of customer sites send orders in different formats by different deadlines.
  • Someone collates them into a spreadsheet each afternoon to work out what to make.
  • Late amendments arrive by phone and are hand-written on the plan.
  • Labels and delivery notes are produced from a second copy of the same data.
  • Larger customers want EDI, smaller ones send a text message.

We speak your language

standing orders · order cut-off · production plan · batch and lot codes · use-by dates · allergen declarations · delivery notes · multi-site customers · short shelf life

What usually pays for itself first

Order intake into a single production plan

All channels into one checked list per delivery day, with standing orders applied and amendments tracked, approved before release.

Labels and delivery notes from the approved plan

Quantities per product and per drop, generated from one source, so the van carries what the plan says.

Invoices to the accounts system

Delivered quantities posted to Sage or Xero without re-keying, with a daily exceptions list.

Systems we see in this sector

Sage 50, Sage 200, Xero, Spreadsheets and Word documents, Bespoke and legacy systems with no API. If yours is not listed, it almost certainly still has a route in; see systems without an API.

Questions people ask

We have EDI with the large retailers. Does this duplicate it?

No. EDI stays for the customers who use it. The automation handles everyone else, and the two feed the same production plan.

Can it handle allergen and batch information?

The automation carries whatever your product records hold. Allergen and batch data stay in your systems of record; the automation moves and prints them, it does not decide them.

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.