Case study · Illustrative example

Customer orders into the ERP without retyping, for a freight forwarder

Illustrative example. This shows how an engagement of this kind typically runs. It is not a report of a specific client's project, and the figures are typical outcomes, not measured client results. Your numbers depend on your data; the readiness assessment tells you what to expect.

The typical situation

Booking requests arrive as emails, spreadsheets and PDFs in a dozen customer formats. Three people retype them into the ERP, then forward confirmations by hand. Mistakes show up as wrong consignee details on the documents.

Nobody in a business like this wants a new system. They want the same ERP with less typing.

What the data looked like

A year of booking emails and attachments, the ERP's booking records for the same period, and the customer master. The past bookings show what every field should have been for each email.

What we built

  • A flow that reads each booking email and attachment, fills the ERP booking and holds it for one-click approval.
  • Checks against the customer master, so an unknown consignee or a mismatched address goes to a person instead of the ERP.
  • Automatic confirmations to the customer once a booking is approved.
  • A daily log of what was automated, what was edited and what was rejected.
Your systemsClean data layerModel or rulesAlerts and reports

Typical outcome

MeasureBeforeAfterPeriod
Hours spent retyping bookingsabout 18 a dayabout 4 a daytypical outcome
Bookings with data-entry errorsabout 3%under 1%typical outcome

What usually trips these projects up

Start with the five customers who send the most bookings. Covering every format from day one doubles the build for the last few percent of volume.

Have a similar problem?

Tell us what is going wrong and what data you keep. The first conversation is free and usually ends with a straight answer about whether this is worth doing.

Start the readiness checkTalk to us