Logistics and distribution
Shipments, warehouses and invoices tracked as one flow
Warehouse, transport and carrier integrations, tracking and proof of delivery, joined to your ERP and finance.
Overview
Logistics depends on information moving as fast as the goods. Orders, bookings, tracking events, proof of delivery and invoices pass between shippers, warehouses, carriers and customs brokers, often in different formats.
We build and connect the systems that carry that information: warehouse and transport tools, carrier and marketplace integrations, EDI with trading partners, and the link to your ERP and finance. Every message is tracked, so a lost booking or a failed invoice is found early.
What we build
Warehouse tools
Receiving, put-away, picking and dispatch apps that extend your warehouse system, built for scanners and mobile devices.
Transport and dispatch
Order intake, planning inputs, driver apps and proof of delivery with photos and signatures.
Tracking and customer updates
One tracking view built from carrier events, with notifications to customers and exceptions to your team.
Freight billing and settlement
Rating, invoicing and checks on carrier invoices, connected to the ERP.
Operational data
A data platform for volumes, service levels and costs, fed by the systems above.
How it connects
Scroll sideways to see the whole drawing.
ERP to third parties: one platform, many partners
Business events leave the ERP once and the integration platform delivers them to each partner in the format it expects. Callbacks come back the same way. A message that still fails after its retries goes to a dead-letter queue and raises an alert with the payload attached.
- Primary flow
- Asynchronous
- Exception path
The flow, step by step
- From ERP to Integration platform: Business events, over REST · OData · webhook (primary flow).
- From Integration platform to CRM: Customers and orders, over REST/JSON (primary flow).
- From Integration platform to Logistics and carriers: Shipments booked, over REST/JSON (primary flow).
- From Logistics and carriers to Integration platform: Tracking events, over webhook (asynchronous).
- From Integration platform to E-invoicing and tax platform: Invoices for clearance, over SOAP/XML · REST (primary flow).
- From Integration platform to KYC and identity provider: Identity checks, over REST/JSON (primary flow).
- From KYC and identity provider to Integration platform: Check results, over webhook (asynchronous).
- From Integration platform to Dead-letter queue and alerts: Failed after retries, to a dead-letter queue (exception path).
- From Dead-letter queue and alerts to Support team: Alert with the payload and the error (exception path).
Typical integrations
Carriers
Carrier APIs and files for rates, labels, bookings and tracking.
EDI with trading partners
EDIFACT and ANSI X12 messages over AS2 or SFTP, for orders, despatch advice and invoices.
ERP and finance
Orders, stock, charges and invoices exchanged with your ERP.
Warehouse and transport systems
WMS and TMS platforms, through their APIs or message interfaces.
Engineering for the rules
Customs and trade data
We carry the data customs filings need and keep it consistent across documents, so declarations match the shipment.
Personal data in deliveries
Recipient names, addresses and delivery photos are kept only as long as needed, with access limited to the people who need them.
Questions and answers
Do you work with EDI?
Yes. We build and maintain EDI flows in EDIFACT and ANSI X12, over AS2, SFTP or a value-added network, for orders, despatch advice, invoices and status messages. We also translate EDI into APIs and events, so newer systems do not need to read EDI themselves, and we test each flow with the trading partner before it goes live.
Link to this questionHow do you integrate many carriers?
We put one carrier layer between your systems and the carriers. Your systems book, label and track through a single interface, and the layer maps each request to each carrier’s API or file format. Adding a carrier then means adding one mapping and its tests, not changing every system that ships. Rates, labels and tracking events come back in one format.
Link to this questionHow do we find out when a shipment goes wrong?
Tracking events from carriers and warehouses are compared with what should have happened. A missed collection, a delay or a failed delivery becomes an exception for your team, with the shipment and its last event attached, before the customer has to ask. Patterns in those exceptions show which partners and lanes need attention.
Link to this questionWhat drives the cost of a logistics integration?
The number of partners and formats, how many message types each one needs, the quality of the partners’ test environments, and how much of the process still runs on paper or email. We estimate per partner and per flow after a review, so you can start with the partners that matter most and add the rest in stages.
Link to this questionCan you work with our existing warehouse or transport system?
Yes. We extend existing systems through their APIs, message interfaces or databases, and add mobile tools and integrations around them. If a system has reached its limits, we plan a staged replacement, with both systems running until the new one is proven.
Link to this questionCan you monitor the integrations after go-live?
Yes, under a support agreement. We watch message flows and partner connections, alert on failures and backlogs, and fix or replay failed messages. If you prefer to run it yourselves, we hand over to your team with the dashboards and runbooks.
Link to this questionTell us what you need to build or connect.
Describe the systems, the timeline and the constraints. The right engineers take it from there.
- Our team will call you within 24 hours during your preferred time slot
- Our team is available 24/7