What goes back to the job
Once a shipment is booked, ParcelOffice sends the courier, shipment and tracking reference for that despatch back through SmartFACT Data to your factory software. Nobody has to copy numbers from a courier screen into the job.

Signed updates and retries
Each update is signed, carries a unique event identity and can safely arrive more than once. If it is not acknowledged, 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 does not cause a second booking.
If the booking outcome is uncertain
If the courier's reply is lost, a supervisor establishes the result with the courier and records the actual shipment identifier and one tracking number for each parcel. The despatch keeps its earlier uncertainty in its history, and recording the result does not book another shipment.

Each event is reported separately
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
Updates go from ParcelOffice to SmartFACT Data. What reaches your factory software from Data, and what your system does with each update, is agreed in the integration’s scope. Changing where ParcelOffice delivers updates is a reviewed administrator action, and a test delivery checks the connection before live use.
What ParcelOffice does not do
- Parcel tracking after booking. ParcelOffice returns the tracking reference; it does not follow the parcel or report delivery.
- Deciding when a job counts as despatched. Your system decides, from the separate events.
Common questions
What if a scan is repeated or the connection drops?
Scanning a despatch that already has a shipment opens that shipment instead of booking another. If the courier’s reply is lost after a booking request was sent, the despatch is held for a supervisor to check. A timeout never turns into a second booking.
Early access starts with an agreed workflow. Supported scope and onboarding arrangements are confirmed with you.
