Close the loop automatically
Once a shipment is booked, ParcelOffice sends your factory software the courier, shipment and tracking reference for that despatch. Nobody has to copy numbers from a courier screen into the job.
Updates your system can trust
Each update is signed, carries a unique event identity and can safely arrive more than once. If your system does not acknowledge it, ParcelOffice retries with increasing delays for up to a day, then keeps it for an administrator to replay. Rejected updates are shown for attention straight away. A pending update never causes a second booking.
Separate events, honestly named
A booked shipment, a label sent to the printer and a label someone saw printed are different facts. ParcelOffice reports them separately, so your system can decide when a job counts as despatched without treating an unconfirmed print as a parcel on its way.
Agree the receiving side
During onboarding we agree where updates are delivered and what your system does with each one. Changing the receiving address is a reviewed administrator action, and a test delivery checks the connection before live use.
Early access starts with an agreed workflow. Supported scope and onboarding arrangements are confirmed with you.
