Trax, on the same interface
The second courier is the one that proves a courier layer is really pluggable. Trax books, tracks and reconciles through the same screens PostEx does, and the two can be compared on your own parcels.
Two couriers, one workflow
Adding a courier should not add a workflow. Trax uses the same booking screen, produces the same documents, feeds the same in-transit and delivered views, and reconciles through the same shipment-keyed matching as PostEx. What changes is only which carrier the parcel is handed to.
- Booking rules route orders by city, weight or value, so you state the policy once.
- The scorecard compares delivery rate, RTO rate and days to settle across both, computed from your own parcels.
- One profit ledger, regardless of who carried the order.
Read the scorecard with the volume next to it. Two couriers only compare fairly when they carry comparable work. If one of them is only ever given the difficult cities, its delivery rate is measuring the cities, not the courier — so the app shows the parcel count behind every rate.
Questions merchants actually ask
- Can I move all my volume to Trax?
- You can route as much or as little as you like through booking rules. The more useful move for most stores is to split by region and let the scorecard settle the argument after a few hundred parcels.