AusPost eParcel setup

OrderOps ships Australia Post on your own eParcel contract. This page covers the credentials you need, where they're stored, and what you get once connected.

What you need

An AusPost eParcel account with API access. From it, three values:

• API client ID
• API client secret
• Charge account number

OrderOps doesn't resell postage and doesn't pool accounts. The rates you see are your contract rates, and AusPost bills your account directly.

How credentials are stored

Encrypted at rest with AES-256-GCM, scoped to your organisation. There is no shared fallback: if your org hasn't entered credentials, OrderOps won't buy a label. Credentials are validated when you save them — a bad secret fails at setup, not at the pack bench on Friday afternoon.

Sender address

One sender address per organisation. It prints on every label and doubles as the destination for return labels. There's no per-warehouse sender today — if you dispatch from more than one site, tell us before you onboard.

What you get once connected

• Live rate quotes per product as dimensions change, with signature, ATL and transit cover gated by what each product supports
• Labels in A6 or A4 layouts
• Multi-parcel shipments with per-article tracking
• International with CN22/CN23 customs forms
• End-of-day manifests and the order summary PDF
• Voiding before manifest, with charges reversed
• Tracking events normalised into one status stream

One quiet reliability detail: if AusPost rejects a branded label with error 70010, OrderOps automatically retries unbranded. The parcel ships; nobody notices.

Address checks

Destination addresses are checked against AusPost's address search (free with your account), with Google as a backup where configured. Validation is advisory — it flags problems but never blocks a shipment.