Choosing your NZ carrier stack: NZ Couriers, NZ Post, Mainfreight compared

Three names cover the bulk of NZ dispatch. Picking the wrong primary carrier costs more than freight rates.

Here is the honest comparison — service tier by service tier, integration depth, and where each one wins.

Most ops teams run two of the three; here is how to decide which two.

The three carriers that cover most of NZ

NZ Couriers, NZ Post (which includes CourierPost and eParcel), and Mainfreight together carry most of the country's parcel and freight volume.

Pick one as your primary and you have made the biggest cost-and-service decision your warehouse will make this year.

NZ Couriers — the parcel default for most SMBs

Strengths:

• Best-in-class API for direct integration — labels, rates, tracking, manifest all flow without middleware
• Reliable nationwide overnight service in major centres
• Strong North Island metro performance; competitive South Island reach via partner depots
• Service-tier flexibility — domestic, overnight, International Air all on one account

Watchouts:

• Rural pickup windows tighten outside the Auckland-Hamilton-Tauranga triangle
• Bulky-freight handling is parcel-shaped; over 25kg per item really wants a freight specialist

In OpsUI: NZ Couriers is the live, in-production carrier integration today.

See /integrations/carriers/nz-couriers.

Rate, label, track, and manifest flow through the Shipping/Outbound module without a separate console.

NZ Post — coverage in places NZ Couriers does not reach as cleanly

Strengths:

• The most complete rural and regional coverage in the country — CourierPost reaches places other carriers route through partners
• eParcel for cross-border outbound; integrated customs paperwork through the same account
• Address validation against the NZ Post address dataset is the cleanest in the market — fewer failed deliveries

Watchouts:

• API documentation is less unified than NZ Couriers' — some flows route through eShip, some direct
• Service tier vocabulary changes more often than the underlying products

In OpsUI: NZ Post (CourierPost + eParcel) is configurable today through the Shipping/Outbound module — the specific connector shape (direct API vs eShip handoff) is confirmed during scoping against your existing account.

See /integrations/carriers/nz-post.

Mainfreight — when parcel is not the right shape

Strengths:

• B2B freight, palletised, full-truck — first-class workflow, not retrofitted parcel
• Mainchain visibility for consolidated freight customers
• Trans-Tasman freight integrated with the same account if you ship into Australia

Watchouts:

• Parcel-sized work is technically possible but usually wrong tool for the job — Mainfreight earns its keep on freight, not packets
• EDI and file-based handoff is common; less likely to be slick API in the way NZ Couriers is

In OpsUI: Mainfreight is configurable through the Shipping/Outbound module — most customers run the EDI handoff Mainfreight has already provisioned for them.

See /integrations/carriers/mainfreight.

How most NZ SMBs actually run this

The most common stack:

• NZ Couriers for daily domestic parcel — overnight and standard
• NZ Post for rural deliveries and any cross-border eParcel
• Mainfreight for anything palletised or B2B freight over 25kg

Some operators flip primary and secondary. Rural-heavy operations often lead with NZ Post. Urban-only ecom often runs NZ Couriers alone and uses NZ Post only for the cross-border exceptions.

The wrong stack: trying to push freight-shaped consignments through a parcel carrier to consolidate accounts. The freight rate looks good until pickup-and-rejection kicks in.

The integration-depth question

A carrier "integration" in a WMS is not one thing. Here is what to ask:

• 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 MyParcels or eShip?
• 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 and submit, or are we exporting CSVs at 5pm?

The depth on 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:

• Pure cross-border volume to the US or EU: DHL Express or DHL eCommerce is often the right primary, with NZ Post or NZ Couriers as secondary. See /integrations/carriers/dhl.
• Australia-bound trans-Tasman volume: most operators run a separate AU carrier mix from the NZ stack — Australia Post, StarTrack, or Sendle on the AU side.

The decision in one paragraph

Start with NZ Couriers for parcel because the integration is live and the API is clean.

Add NZ Post the moment your rural failure rate or cross-border volume justifies a second account.

Add Mainfreight the moment a palletised consignment becomes a regular event, not an exception.

Three accounts, one dispatch queue, one team. That is what good looks like.