Built for the volume you already ship

Volume plans

Pricing is published up to 2,000 shipments a month and you can size it yourself on the pricing page — the rate per shipment improves as the volume goes up. Above that ceiling there is no published number, so we quote it.

• 25 team seats on a volume plan, with role-based access — owner, member and a read-only viewer.
• One pool, not a monthly cliff. On an annual plan the whole year's shipments are a single pool, so a heavy quarter draws on a light one instead of hitting a wall.
• Everything in Business — full dashboard, live map, MIS reporting, customer alerts and API access included rather than priced separately.

Annual contracts and invoicing

Card-on-file is the default, and it is not the only option. An annual plan can be raised as an invoice rather than a card charge, payable on net-30 terms — the standard route for a procurement team that cannot put a subscription on a credit card.

• One invoice for the year, with the annual shipment pool attached to it.
• A purchase order or vendor reference carried on the invoice.
• Renewal notices ahead of the term ending, so nothing lapses without warning.
• Annual billing is also self-serve — switch the toggle on the pricing page to see the yearly price , 5% below twelve months of monthly.

Support

Volume accounts sit on the fastest response tier we run: 4 hours to a first human reply, measured in staffed hours. Every ticket carries its own countdown, visible to you inside the app, and a breach escalates on our side rather than waiting for you to chase it.

• Staffed hours: Monday–Friday, 09:00–18:00 Asia/Kolkata.
• Dedicated onboarding — we load your live references and set up your first MIS report and alerts with you, rather than handing over a login.
• An assistant that hands over. The in-app agent answers from your own account data and raises a real ticket the moment it cannot resolve something, so nobody is stuck in a chat box.

Security

What is in place today, stated plainly — no certifications are claimed here that we do not hold.

• API keys are stored hashed. The key itself is shown once, at creation, and cannot be recovered from our database — only a hash and a short prefix are kept, so keys can be identified without being readable.
• Webhook payloads are signed with an HMAC-SHA256 signature over the timestamp and body, so your endpoint can verify a delivery came from us and is not a replay.
• Data is scoped to your organisation at the query layer, and roles restrict what a member can reach within it. A viewer is read-only by construction, not by hidden buttons.
• Sign-in is one-time-code based, with Google and Microsoft SSO available; there is no shared password to leak.
• Administrative access is default-deny and audited. Our own staff reach a section only if their role grants it, and every action they take is written to an audit log with the actor on it.
• Everything is served over TLS, including the API and webhook deliveries.

Working through a security questionnaire? Send it over — we would rather answer your form than have you infer the answers from this page.

What the API covers

The full reference is on the developer page, including a sandbox that runs real requests without a key. Keys are rate-limited at 120 requests a minute by default, and the limit is on every response.