A 3PL Is an Outsourced Fulfilment Partner#
A 3PL (third-party logistics provider) is an outsourced operations partner that handles warehousing, fulfilment, and shipping on behalf of brands that do not want to run their own warehouse. The brand owns the inventory and the customer relationship; the 3PL owns the warehouse and the workflow.
This article defines what a 3PL actually does, when brands use them, the software stack a modern 3PL runs on, and the realistic cost ranges in ANZ markets.
The Definition#
A 3PL is an outsourced operations partner that handles warehousing, fulfilment, and shipping on behalf of brands that do not want to run their own warehouse. The brand sends inventory to the 3PL's facility; orders flow from the brand's storefront (Shopify, marketplaces, B2B portal) to the 3PL's WMS; the 3PL picks, packs, and dispatches under the brand's name and packaging.
The defining shape: the brand owns the inventory and the customer relationship; the 3PL owns the warehouse and the workflow.
What a 3PL Actually Does#
The functional surface of a typical 3PL:
- Receives inbound stock against PO or ASN, with quantity and quality verification
- Stores and tracks inventory at bin-level, with per-brand isolation
- Receives orders from the brand's storefront and marketplaces via WMS integration
- Picks, packs, and dispatches under the brand's packaging (often custom-printed boxes, branded inserts, kitted components)
- Handles returns receiving and disposition (restock / refurbish / scrap)
- Books carrier pickups and submits manifests
- Reports KPIs back to the brand — throughput, accuracy, dispatch SLA, exception rate
Larger 3PLs add value-added services (VAS): kitting, light assembly, photography, quality inspection, FBA prep, custom inserts, returns refurbishment. The pricing for VAS is typically per-minute or per-unit on top of the base storage and pick fees.
What a 3PL Is Not#
A 3PL is not the brand's ecommerce platform. Shopify, WooCommerce, marketplaces stay on the brand's side. The 3PL receives orders from those platforms but does not own the storefront or the checkout.
A 3PL is not the brand's OMS. Order routing across channels and across warehouse locations is usually still the brand's decision. If a brand uses multiple 3PLs (one in NZ, one in AU, one in the UK), the OMS layer that decides which 3PL fulfils which order sits on the brand's side.
A 3PL is not the brand's finance system. Inventory ownership and revenue recognition stay on the brand's books. The 3PL invoices the brand for fulfilment services; the brand's ERP records both the cost of fulfilment and the revenue from the sale.
A 3PL is not a freight forwarder. Freight forwarders move freight between locations (origin to port to destination); 3PLs store and ship individual orders from a warehouse. Some companies do both, but the functions are distinct.
3PLs sometimes get called 4PL or 5PL providers when they take on broader scope (4PL = logistics orchestration across multiple 3PLs; 5PL = strategic supply chain partner with technology and consulting layers). For most ANZ operators, "3PL" is the right term.
When Does a Brand Use a 3PL?#
The honest triggers for outsourcing fulfilment:
- Order volume has outgrown the founder's garage or warehouse. The most common trigger. The brand has the orders but lacks the labour and warehouse infrastructure.
- Geographic expansion without opening a warehouse. Brand wants to ship to AU customers without setting up an Australian operation. 3PL in Sydney or Melbourne becomes the AU base.
- Capital allocation favours marketing and product over operations. The brand's strategic priority is product and customer acquisition; fulfilment is a commodity capability.
- Fulfilment quality matters but is not the brand's differentiator. The brand wants reliable fulfilment but does not want to compete on warehouse operations.
- Seasonal volume spikes (Black Friday, Christmas) need flex capacity. 3PLs scale labour up and down across multiple brand clients in ways a single-brand warehouse cannot.
Brands that run their own fulfilment ("in-house" or "1PL") usually do so because the customer experience around dispatch IS the differentiator — custom packaging, white-glove delivery, founder-signed cards, premium unboxing.
The 3PL Software Stack#
A modern 3PL runs on a WMS designed for multi-client operations. The key requirements:
- Client isolation. Each brand's inventory is segregated; one brand's stock cannot bleed into another's order. Allocation, picking, and reporting all respect the client boundary.
- Per-client billing. Storage fees, pick fees, pack fees, value-added service charges all tracked per brand for invoicing.
- Channel integrations. The WMS receives orders from each brand's Shopify, WooCommerce, Amazon, TradeMe, B2B portal, EDI feed.
- Reporting per client. Each brand gets a self-serve dashboard showing their inventory, orders, exceptions, and KPIs.
- Receiving by ASN. Inbound stock matched against advance ship notices, not improvised. Variance per brand is logged, not buried in a shared exception queue.
- Brand-restricted user access. Brand client account managers can be scoped to see only their assigned brands; 3PL ops staff see everything.
The depth of multi-client support separates 3PL-grade WMS platforms from single-tenant WMS platforms posing as 3PL-ready.
3PL Software Options in ANZ#
Three common architecture shapes:
Dedicated 3PL WMS. Built specifically for multi-client ops. Mintsoft, SoftEon, Logiwa, Cin7 Omni at the upper-SMB end. Manhattan Active, Blue Yonder at enterprise scale. The pricing is typically per-licence plus per-brand-client, with implementation in the 6–24 week range.
Modular ERP with 3PL capability. Treats 3PL as a client-isolation pattern within a broader ops product. NetSuite OneWorld with WMS+, OpsUI Warehouse, MYOB Acumatica Distribution. The pricing is typically modular and lower at SMB scale; implementation is faster.
Enterprise WMS. For 3PLs above ~50,000 orders/day. Manhattan, Blue Yonder, Korber. Heavy implementation, deep capability, six-figure annual licences plus six-figure implementation.
For ANZ 3PLs serving SMB and lower-mid-market brand clients, the modular ERP shape is usually the cheapest path — modular pricing means a small 3PL can start with Inventory + Warehouse + Shipping modules and add CRM, Analytics, or Finance as the operation grows.
The Brand-Side Software Stack#
The brand using a 3PL also needs software to manage the relationship:
- Their ecommerce platform (Shopify, WooCommerce, Magento) for the storefront.
- Their ERP or inventory system to track inventory ownership, COGS, and finance flows.
- An OMS if they use multiple 3PLs or multiple fulfilment locations.
- Integration to the 3PL's WMS — typically REST API or EDI.
The integration between brand-side and 3PL-side systems is where 3PL relationships succeed or fail. Brands evaluating a 3PL should ask explicitly which integration patterns the 3PL supports natively, what the per-order data flow looks like, and how exceptions are escalated.
Realistic ANZ 3PL Pricing#
For SMB and lower-mid-market brands:
- Receiving: NZ$5–15 per pallet, sometimes per-carton for less-than-pallet inbound
- Storage: NZ$15–40 per cubic metre per month, sometimes per-pallet per month
- Pick fees: NZ$1.50–4 per line picked
- Pack fees: NZ$2–6 per order packed
- Shipping: at-cost or with a modest margin
- VAS: NZ$30–60 per hour or per-unit pricing for kitting, photography, custom inserts
A typical 500-order/month brand pays NZ$2,000–5,000/month all-in. A 5,000-order/month brand pays NZ$15,000–35,000/month. The mix between storage and pick/pack fees shifts with order velocity — high-velocity brands pay more in pick/pack, low-velocity brands pay more in storage.
When the 3PL Relationship Fails#
Common failure modes:
- Inventory accuracy drift. The 3PL's WMS and the brand's ERP get out of sync. Monthly reconciliation eats hours.
- Exception handling. The 3PL surfaces exceptions in their own ticket system; the brand has to log in separately to see them.
- Reporting gaps. The 3PL's reports do not match the brand's ERP reports. Finance cannot close the month confidently.
- Carrier integration mismatch. The brand wants a specific carrier service tier (e.g. NZ Couriers same-day); the 3PL's WMS does not support it natively.
- Per-client billing disputes. The 3PL's invoice line items do not match what the brand was promised in the contract. Resolution takes weeks.
Each failure mode traces back to the integration between brand-side and 3PL-side software. Brands evaluating a 3PL should ask about each of these failure modes directly: how the 3PL prevents them, and what the escalation path looks like when they happen.
For deeper coverage, see What is a WMS?, What is an OMS?, and Inventory Management Module Architecture.