Integration with courier services
Labels are printed straight from warehouse dispatches, pickups are booked, parcels tracked and returnable containers swapped, with parcel status updated every five minutes.
The new integration took over the parcels already in transit.
- Client
- Equipment sales and service company
- Our role
- Integration
- Years
- 2026
- Technologies
- TypeScript, courier REST API, node-cron, MongoDB change streams, AWS API Gateway, SQS, Jest
The task
Warehouse dispatches had to become courier parcels – with labels, pickup booking, tracking and returnable-container swaps – and a delivered parcel had to complete the dispatch and the order.
The solution
- Labels created from warehouse dispatch documents, with the courier service chosen by the system.
- Batch PDF printing.
- Pickup booking without duplicates.
- Swaps of returnable containers.
- Parcel status polled every five minutes – added when the courier's callbacks stopped arriving.
- A delivered parcel completes the dispatch and the order.
- Migration from a shipping aggregator to the courier's own API.
Business management systemWarehouse dispatch
- Recipient
- Laura S., Kaunas
- Packages
- 2
- Courier service
- Chosen by the system
CourierPackage 1 of 2
4051 7730 0186 52
RecipientLaura S.Kaunas
Print labels2 labels in one PDFPickup booked
6 Oct 202614:00–17:00
Booked once, without duplicates
Parcel statusChecked every five minutes
- Registered6 Oct 2026, 09:12
- Picked up6 Oct 2026, 15:40
- Out for delivery7 Oct 2026, 08:05
- Delivered7 Oct 2026, 11:26
Returnable container collected
Dispatch and order completed
Results
- Parcel status is at most about five minutes old.
- Parcels already in transit were taken over by the new integration.
- More than 100 automated tests.
Want a similar solution?
A few sentences are enough – we'll reply and talk through how we could help.