ContactBook a call

Industries/ Logistics/ Systems that talk together

Orders in, invoices out, and an alarm when a feed stops

We connect your customers' portals, EDI feeds and spreadsheets to your transport system, and your completed jobs to your accounts software, so each job is typed once or not at all. Every scheduled transfer is watched, and a failure raises an alert to a named person rather than waiting to be found at month end.

Two staff in a logistics office: a woman in her sixties with short white hair at a laptop and a young man in a high-visibility vest holding a tablet, comparing the same shipment record, warehouse beyond a glass wall.
Used by
Traffic office, customer service, accounts and your IT contact
Takes the place of
Retyping orders, unchecked overnight imports and month-end fixes
Connects to
Customers' systems, your transport system and accounts software
Built with
Our connecting systems service

Where it hurts today

A normal week, before it exists

Work arrives from customers in every shape. One sends orders through their own portal, which someone logs into each morning and copies from. Another sends an EDI file overnight. A third emails a spreadsheet whose columns change whenever their staff do. Smaller customers ring or email a few lines. All of it gets typed into the transport system by hand, usually first thing, by people who would rather be planning.

Then the same jobs are typed again. Completed work goes from the transport system into the accounts package line by line, or through an export someone runs and fixes on a Friday. Customers who want status updates and proof of delivery in their own systems get a spreadsheet emailed back, built by hand. Every handoff is a place where a pallet count or a reference number quietly changes.

The connections that do exist were often set up long ago by someone who has since left, and nobody is sure what they do. When an overnight import stops, nothing says so. The first sign is a customer asking why their deliveries are missing, or month-end numbers that will not add up, by which point a week of records has to be found and repaired by hand.

What it does

Systems that talk together, feature by feature

What the integrations do, and how they behave when something goes wrong, which in logistics is the part that matters most.

  1. 01

    EDI, API and spreadsheet orders in one shape

    EDI messages, portal downloads, spreadsheets, CSV files and emailed orders are each turned into the same shape of job before they reach your transport system. A new customer with a new format means one new connection, not a new set of habits in the office.

  2. 02

    Checks before anything is created

    Every incoming order is checked first: a valid postcode, a delivery date that has not passed, a known customer reference, a pallet count that makes sense. Orders that fail are held with a plain reason, so someone fixes the one bad row instead of the whole file failing.

  3. 03

    Completed jobs on to accounts

    Jobs marked complete with proof attached flow from your transport system to your accounts software with the customer, reference, charges and extras such as waiting time, so invoices can be raised the day the work is done rather than after a Friday export.

  4. 04

    Status and proof back to customers

    Customers who want updates in their own systems receive them the way each one prefers: an EDI status message, a file at set times, or an API call. Proof-of-delivery images can travel with them, so their teams stop asking yours for paperwork.

  5. 05

    A named person hears about failures

    Every scheduled transfer is watched. If one does not run, runs late or rejects more records than usual, a named person gets an alert saying what failed and why, and the records that could not be processed are kept for review rather than dropped.

  6. 06

    Every record traceable

    Each order can be followed from the file or message it arrived in, through every check, to the job in your transport system and the invoice line in accounts. When a customer disputes a charge, anyone with access can see where every figure came from.

A day with it

How the day runs instead

A normal day across the office, with orders, jobs and invoices moving between systems on their own.

  1. 6.30am
    Traffic clerk

    The clerk opens the integration screen before planning starts. Overnight, orders from the EDI customer and two portals were created as jobs. One spreadsheet row is held because its postcode is missing, so the clerk rings that customer and fixes it.

  2. 9.00am
    Customer service adviser

    A customer emails an order as a spreadsheet, as they always do. It is read, checked and turned into jobs without anyone retyping it. The adviser only steps in because one line asks for a delivery date that has already passed.

  3. 12.00pm
    Account manager

    A large customer's system receives its midday status file: this morning's completed deliveries, with proof images attached. Their transport team updates their own customers without phoning your office, and the account manager's inbox stays quiet.

  4. 4.20pm
    Operations manager

    The export to accounts fails because a password was changed. The operations manager gets an alert naming the feed and the error, passes it to whoever looks after the integration, and the jobs go across that evening once access is restored.

  5. Month end
    Accounts clerk

    Finance closes the month with jobs and invoices that already agree. When a customer queries a charge, the accounts clerk follows the invoice line back to the original order message and the proof of delivery, and answers in one email.

What it connects to

Works with what you already run

The kinds of systems a logistics firm usually needs connected, named by kind because every firm runs a different mix.

  • Customers' order systems

    EDI feeds, customer portals, emailed spreadsheets and the occasional API. We work with each customer's IT contact where they have one, and read emails and attachments where they do not.

  • Transport management system

    Jobs go in and completed work comes out, through its API where it offers one, or through import and export files where it does not. We tell you plainly which route is more fragile.

  • Accounts software

    Completed jobs, charges and credit notes flow on for invoicing, for example to QuickBooks or Microsoft Dynamics 365 where they offer an API, matched to the customer accounts finance already keeps.

  • Warehouse and partner systems

    Where you run a warehouse system, or exchange work with a pallet network or subcontractors, those feeds can be added the same way, each one watched like the rest.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • A map of every current import, export and connection, and who relies on it
  • Monitoring and alerts on the feeds you already run, before anything is rebuilt
  • Your busiest customer's orders flowing into the transport system with checks
  • Held records shown with a plain reason and a simple way to fix them
  • Completed jobs passed to your accounts software, ready to invoice

Once it is in use

  • Status updates and proof of delivery sent back into customers' own systems
  • Emailed orders and spreadsheets read automatically and turned into jobs
  • Warehouse, pallet network and subcontractor feeds added one at a time
  • A searchable history tracing each invoice line back to its original order

Buyer's guide

Before you commission one

Four decisions worth making before you commission integration work.

  1. 01

    Vendor connectors or custom integration

    Many transport systems offer ready-made connectors for accounting packages and common customer platforms, and EDI service providers handle standard message exchange. Use those where they exist and suit you. Custom integration earns its place for customers with unusual formats, for checks your vendor's connector will not run, or for monitoring that covers every feed rather than one at a time.

  2. 02

    What to gather first

    List every way work arrives and leaves: each customer's portal, file, feed or email, and every export to accounts. Note who set each one up, who fixes it, and what happens when it fails. Collect sample files, broken ones included, and ask your TMS supplier what their API covers. That inventory is the first deliverable, whoever builds the rest.

  3. 03

    Who should own it

    Someone in operations who understands the jobs, paired with whoever handles IT. Each feed needs a named person who is alerted when it fails and decides what happens to held records. Accounts should own the rules for what reaches the ledger. Without named owners, alerts land in a shared inbox that nobody reads.

  4. 04

    How you will know it is working

    Watch how much retyping disappears from the morning, how quickly held records are cleared, and whether failures are now found by an alert rather than by a customer. Month end should need fewer manual fixes, and a disputed invoice should be traceable back to its original order without anyone searching an inbox.

Terms worth knowing

The words you will meet

EDI (electronic data interchange)
A long-established way for businesses to exchange orders, status updates and invoices as structured messages rather than documents. It remains common between shippers, carriers and logistics providers. A customer who asks for EDI will usually specify the message format and how files are exchanged.
API
A documented way for one system to ask another for data, or send it data, directly. Many newer transport and accounting systems offer one. It matters because an API connection is generally easier to monitor and change than a nightly file export.
Data mapping
The agreed translation between one system's fields and another's: their delivery point becomes your consignee, their pallet type becomes yours. Each customer needs its own mapping, and getting it right with real sample files is most of the work in any integration.

Handled with care

The details that matter here

Integrations run out of sight until they break. These are the details we handle with particular care.

  • Nothing dropped silently

    Records that fail a check are parked with the reason, never discarded. We agree with you who is alerted for each feed, at what hours, and what counts as unusual, so a feed that quietly delivers half its normal volume is noticed as well as one that stops altogether.

  • Changes without a quiet hour

    Orders arrive overnight and at weekends, so there is no safe time to switch a feed off. We test changes against copies of real files first, run old and new versions side by side where we can, and keep a quick way back.

  • Customer data kept to its owner

    Feeds carry consignee names, addresses and phone numbers that belong to your customers' customers. We agree with your data protection lead what each feed may carry and how long copies are kept, and we check that each customer's returned data holds only their own consignments.

  • Documented for whoever comes next

    Each connection is written up in plain language: what it moves, when, what it checks, and who to call when the other side changes. You hold the code, the credentials and the documentation, so the next person does not inherit a mystery.

Guides

Worth reading first

Questions

What buyers ask first

Can you connect our TMS to a customer's EDI system?

Usually. Older EDI often runs over a file transfer or a network service that the customer's IT team manages, and the message formats are well documented. We work with their IT contact to agree the format and exchange test files before anything goes live. Where a customer cannot connect at all, their emailed orders and attachments can be read instead.

What if our TMS has no API?

Then we work with what it has: usually scheduled import and export files, and sometimes direct database access if the supplier permits it. These routes are more fragile than an API, so we watch them more closely and tell you plainly where the risk sits. If a supplier upgrade looks likely to break a connection, we would rather you heard that from us before you agreed to it.

Can you monitor our existing integrations?

Yes, and that is often the best first step. We map what runs today, put monitoring and alerts on each feed, and leave the connections themselves alone. It carries very little risk, it shows where the real problems are, and it gives you an honest picture before you decide whether anything needs rebuilding.

Who owns the integrations once they are built?

You do. The code, the credentials, the documentation and the monitoring all sit in accounts that belong to you. We can look after them on a care plan, with response times agreed in writing, or hand them to your own IT team. The aim is that nobody inherits a connection only one person understands.

Should we use EDI or an API for customer integrations?

Whichever each customer can support, and often both across your customer base. Many larger shippers still send work by EDI and expect status messages back the same way. Newer systems tend to offer an API, which is easier to monitor and change. Smaller customers may have neither, so their emailed spreadsheets are read instead. Inside your business, everything becomes the same shape of job.

Show us where orders get typed twice

Walk us through how one customer's order reaches your transport system and then your accounts. We will reply within 48 hours with which steps could run on their own and which feeds to watch first.

More for logistics

What else we build for logistics