Every charge can be explained
Each shipment records what the courier charged us, what you were charged, the margin between them and the tax inside it — kept as it was on the day, not recalculated later.
Plenty of tools will show you a shipping price. The question is whether you can explain it a month later.
Each shipment records what the courier charged us, what you were charged, the margin between them and the tax inside it — kept as it was on the day, not recalculated later.
Couriers are added behind a stable contract. The code your team wrote against the API does not change when we add the next one.
The shipment record and its wallet debit are written in one transaction. A crash between them cannot leave a parcel in the network with no charge against it.
The public site loads four stylesheets and three scripts. The application behind it pages large grids on the server rather than shipping ten thousand rows to a browser.
Role-based access with a database-driven privilege model, audit logs on sensitive actions, and carrier credentials that never appear in a page or a log.
Statuses follow the courier, invoices issue themselves, COD reconciles against the parcels. Automation you do not have to check is automation worth having.
Against the two things most teams do instead.
| Capability | Courier portals | A spreadsheet | This platform |
|---|---|---|---|
| Compare rates | One courier at a time | Manually, if at all | Every courier, one screen |
| Book and label | Re-type each address | Not possible | One step from the rate |
| Tracking | One portal per courier | Copy-pasted | One page, one vocabulary |
| COD reconciliation | Their summary | By hand | From the shipments themselves |
| GST invoices | Per courier | Assembled monthly | Issued automatically |
| API access | Different per courier | None | One contract for all |
Create an account, compare what your couriers would charge for a real parcel, and decide from there.