OrderOpsBETA

Field notesProduct

Three carriers, one bench

Three carrier accounts feed one packing bench. Under the hood, each one has its own personality: AusPost and StarTrack speak modern REST and still manage to disagree about the rates endpoint, and Team Global Express wants OAuth plus client certificates plus GS1 barcodes. The pack panel hides all of that. The status chips don't.

What LIVE means

LIVE means the integration runs production round-trips on our own floor, daily, and its shapes are pinned by fixtures. For AusPost and StarTrack, 38 official request and response payloads sit in the test suite — auth, rating, multi-parcel labels, manifests, voids, tracking. A refactor that bends a payload fails CI before it can fail at your bench.

What BETA means

BETA means the code path is complete and tested against the carrier's spec, but we haven't supervised every operation against a live carrier account yet. TGE's dangerous-goods declaration matches the spec and our tests, but hasn't been round-tripped with the carrier. We'd rather print a hollow dot on the chip than find out on your freight. The beta carriers doc covers exactly what works today.

AUSPOST      ● LIVE
STARTRACK    ● LIVE
TGE / IPEC   ◌ BETA
OTHERS       → ON REQUEST

Your account, your rates

You bring your own carrier contract: your negotiated rates, your invoices, your account manager. Credentials are stored per organisation, encrypted with AES-256-GCM, and checked before any API call goes out. There is no shared account and no fallback to anyone else's.

Every rate quote also comes back with per-product capability flags — signature, authority-to-leave, maximum cover, dangerous goods — and the panel only offers what the product actually supports. We learned to trust the flags over the brochures. StarTrack rejects safe-drop outright, so we don't show it. AusPost accepts our safe-drop flags and then prints a label identical to signature-required — a carrier-side quirk that's currently with them, not ours to fix. The full option matrix is in the rates and services doc.

What we won't claim: there's no auto-selection. An operator compares the quotes and picks the carrier and service — there's no rules engine routing by weight or postcode, and the chips won't say otherwise until one exists. It's also one account per carrier per organisation for now; multiple trading entities on one bench is on the list, not on the floor.

Three carriers, one bench — OrderOps