Shipping infrastructure for people who ship a lot
Multiple origins, multiple entities, your own courier contracts, scoped API access and the reporting to justify any of it internally.
Shipping as a service for your own sellers
Expose rating, label buying and tracking to the merchants on your platform under your brand, with per-seller scoping and consolidated billing.
See the developer platform
Every warehouse rated from its own origin
Origins carry their own boxes, courier accounts and cut-off times. Orders rate against the location that will actually pack them.
Explore fulfilment
Connected to the platforms your sellers already use
Enterprise questions
Yes. Link them and they are quoted alongside the aggregate rates, per shipment.
Yes — unlimited origins, each with its own boxes, courier accounts and pickup schedules.
Yes, with separate stores, branding and billing under one organisation.
60 requests a minute and 10 a second in production. Higher ceilings are available on enterprise agreements.
Yes, behaving like production at 6 a minute and 1 a second, with its own keys.
Bearer tokens carry `public.<resource>:<action>` scopes, so an integration can be granted rating without label purchase.
14, covering label creation and failure, tracking status changes, delivery outcomes and credit balance warnings.
Yes — your domain, your branding, on the tracking page and the notification emails.
Consolidated invoicing against a prepaid balance or terms, itemised per shipment and exportable.
Spend, transit performance and exception rates by courier, lane, store and warehouse, in the dashboard or over the API.
Yes, as part of an enterprise agreement, including support response targets.
Most teams are rating in sandbox within days. Full cutover depends on how many origins and platforms are involved.
Let us look at your lanes
Bring your volumes and destinations and we will model it properly.