The AU carrier mix: Australia Post, StarTrack, Sendle, and where each one wins
Three carriers carry the bulk of AU dispatch. Picking the wrong primary is the most expensive mistake in your dispatch process.
Here is the honest comparison, service tier by service tier, integration depth, and the real cost of mixing them.
Three carriers carry the bulk of AU dispatch. Picking the wrong primary is the most expensive mistake in your dispatch process.
Here is the honest comparison: service tier by service tier, integration depth, and the real cost of mixing them.
Most AU operators end up running two of the three; here is how to decide which two.
The three names you will end up choosing between
Australia Post (and its MyPost Business and eParcel products), StarTrack (sister brand for express and freight), and Sendle (API-first, carbon-neutral, no-account-required).
Together they cover the parcel and small-freight workload of most AU SMBs.
Australia Post: the parcel default
Strengths:
- Most complete national parcel coverage: metro, regional, remote
- MyPost Business for smaller volumes; eParcel Contract for higher-volume accounts
- Strong residential delivery network: parcel lockers, post offices, choose-where-it-goes flexibility
- Address validation against the AU Post address dataset is the cleanest in the market
Watchouts:
- Service tier vocabulary (Standard, Express, Parcel Post, eParcel) changes more often than the underlying products
- Smaller volume on MyPost Business with no contract means worse rates than negotiated eParcel
- B2B and freight-shaped consignments belong on StarTrack, not Australia Post parcel
In OpsUI: Australia Post (MyPost Business + eParcel) is configurable through the Shipping/Outbound module against your existing account.
See /integrations/carriers/australia-post.
The right account shape depends on volume. Most operators above 500 shipments per month negotiate eParcel.
StarTrack: when speed and freight need a dedicated answer
Strengths:
- Premium (express parcel) and Road Express (general freight) on one account
- B2B-shaped workflows treated as first-class, not parcel workflows pretending to be freight
- Sister brand to Australia Post but a separate carrier contract: different commercial terms
- Strong overnight performance between capitals
Watchouts:
- Residential delivery is not its strength. Australia Post is better for the last-mile to home addresses
- Account-management overlap with Australia Post can confuse procurement: both invoice separately
In OpsUI: StarTrack (Premium + Road Express) is configurable through the Shipping/Outbound module against your StarTrack account.
See /integrations/carriers/startrack.
Most operators run StarTrack and Australia Post side-by-side in the same dispatch queue, with service selection at order entry routing to the right one.
Sendle: API-first, carbon-neutral, the right shape for ecom
Strengths:
- API-first by design: the integration shape is unambiguously direct
- Carbon-neutral as a brand promise, increasingly mattering to retail customers
- No carrier-account contract negotiation: sign up and ship
- Door-to-door pickup for outbound; competitive rates for SMB volume
Watchouts:
- Not freight-shaped: parcel only
- Rural and remote pricing is less competitive than negotiated Australia Post eParcel
- Pickup cut-off times vary by region; build your dispatch flow around them
In OpsUI: Sendle is configurable through the Shipping/Outbound module via your Sendle API key.
See /integrations/carriers/sendle.
The flow is the cleanest of the three from a setup perspective because there is no contract negotiation in the way.
How most AU SMBs actually run this
Common stacks:
- Aus Post + Sendle: ecommerce-first operators with mostly residential volume. Sendle for the bulk, Aus Post for the addresses Sendle does not cover.
- Aus Post + StarTrack: B2B-leaning operators with regular freight or express needs. StarTrack for the B2B and time-critical, Aus Post for the parcel residue.
- All three: high-volume operators who want best-fit-per-shipment routing. Service selection at order entry picks the right one.
The wrong stack: putting freight-sized consignments through a parcel-only carrier to save the setup of a second account. The rate looks good until pickup-and-rejection kicks in.
The integration-depth question
A carrier "integration" in a WMS is not one thing. Worth asking:
- Does the rate come from the carrier API at order entry, or do we pick a service tier blind?
- Does the label print at pack with one click, or are we round-tripping through MyPost or the StarTrack console?
- Do tracking events flow back into the order timeline, or do we have to look them up in the carrier console?
- Does the end-of-day manifest auto-generate, or are we exporting CSVs at 5pm?
The depth across those four answers is the difference between a carrier integration that saves you twenty seconds per shipment and one that saves you two minutes per shipment. Across a thousand shipments a week, that is real money.
When you should not pick only from this list
Honest gaps:
- Trans-Tasman and Pacific routes: DHL or Aramex are often better. DHL is configurable in OpsUI. See /integrations/carriers/dhl.
- Mainfreight is the right answer for heavier freight or for operators already running it on the NZ side; configurable in OpsUI. See /integrations/carriers/mainfreight.
- Toll is a fourth option for AU freight and parcel that comes up in regulated industries; see /integrations/carriers/toll.
The decision in one paragraph
Start with Australia Post for parcel because the coverage is the most complete in the country.
Add Sendle the moment your ecom residential volume justifies a cheaper-and-cleaner second account.
Add StarTrack the moment B2B express or freight becomes a regular event, not an exception.
Three accounts, one dispatch queue, one team. That is what good looks like for an AU operation.
Frequently asked
Can I run Australia Post, StarTrack, and Sendle from the same dispatch screen in OpsUI?
Yes. The Shipping/Outbound module at /modules/shipping-outbound owns the dispatch queue and routes each shipment to the right carrier based on service selection at order entry. Most AU SMBs end up with Australia Post plus one or both of StarTrack and Sendle, all running through the same queue.
Is StarTrack just Australia Post under a different brand?
Both are part of the Australia Post group, but they are separate carrier accounts with separate contracts and different operational networks. StarTrack is B2B-leaning, faster on capital-city routes, and runs a freight-shaped workflow. Australia Post is parcel-shaped and stronger for residential delivery.
When does Sendle become the primary carrier instead of secondary?
When you are predominantly ecom-residential, mostly metro, and your volume sits in the SMB band that benefits from Sendle's pricing model. Sendle as primary plus Aus Post as the rural and regional backup is one of the most common AU ecom stacks today.
What about MYOB integration, does my carrier choice affect that?
Carrier choice does not change the MYOB integration story. The WMS owns dispatch, MYOB owns finance. See /compare/beyond-myob for the architecture pattern AU operators use to layer operations above MYOB. The MYOB sync ships via the Finance & Accounting module, wired against your MYOB tenant during rollout.
We ship to New Zealand too. Do we need a separate carrier stack for that?
Yes, usually. NZ has its own carrier mix, NZ Couriers, NZ Post, Mainfreight. And trans-Tasman volume runs cleanest through DHL or Mainfreight rather than through Aus Post International. Run the AU dispatch queue with this stack and a separate NZ dispatch queue with the NZ stack.
See how OpsUI approaches this differently.
No hidden fees. No six-month implementations. Just warehouse software that works.
Book a Demo