Disconnected systems create manual, error-prone work
When a waybill has to be captured in an internal system and then re-typed into a courier platform, every shipment carries the risk of a typo, a missed reference or a duplicate entry. The cost shows up later, in a failed delivery, a mismatched invoice or a customer who cannot get a straight answer on where their parcel is.
An API integration removes the re-typing step, but only if it is built to handle the full lifecycle of a shipment, not just the happy path of a single successful call.
A waybill has more than one state
Real operations need a shipment to exist as a draft before it becomes a committed, finalised waybill. A draft lets a quote or a partially captured order sit in the system without creating an operational shipment on the courier platform. Finalising should validate company, account, service type and parcel information, then push the shipment through — and only update the internal record once the courier platform confirms success.
Tracking needs both an internal and a public layer
Operations staff need authenticated, detailed tracking: manifest movement, hub scans, delivery progress and POD status. Customers need something simpler — a public endpoint that returns status by waybill number with no login required. Building both means a customer-facing tracking page or WhatsApp bot does not need access to internal credentials.
POD retrieval should match how people actually search
A finance team member usually doesn't have the waybill number handy — they have a customer reference or order number. An integration that only supports lookup by waybill number pushes that work back onto an operator. Supporting reference-based search, and bulk retrieval for teams that need many PODs at once, removes a recurring support request.
Business example: a POD request by reference number
A customer asks for proof of delivery using their order number. Staff search the courier platform manually by trying to match it to a waybill number.
The integration searches DCB Online/TMS-style waybill records for the account and reference, finds the matching waybill, and retrieves the POD automatically.
Deletion and rollback protect data integrity
A courier platform should only allow a waybill to be deleted while it's still in an imported, unprocessed state — and the internal system should only mark it deleted once the courier platform confirms it. The same discipline applies to waybill creation itself: if a save touches a header, parcel lines and invoice references, a failure partway through should roll the whole transaction back rather than leaving a half-saved record.
Dimension data and documents belong in the flow too
Parcel dimension (DIMS) data captured at a scale or scanning station can be pushed into the courier platform through middleware instead of being re-keyed. The same applies to labels and waybill PDFs — generating a secure, temporary link on demand keeps the document current and avoids emailing sensitive shipment data as a static file that goes stale.
The integration that only handles a successful booking call is not the integration a logistics business actually needs. It needs the one that handles drafts, retries, references and deletions correctly too.