Starshipit Is the ANZ Shipping Middleware Layer#
Starshipit is the dominant multi-carrier shipping platform in the ANZ market. It serves the operational gap between ecommerce platforms (Shopify, WooCommerce) and inventory platforms (Cin7 Core, Unleashed, DEAR) on one side, and the carriers (NZ Couriers, NZ Post, Australia Post, Toll, DHL, etc.) on the other.
This guide covers what Starshipit does, how it integrates into the broader ANZ operations stack, realistic 2026 pricing, and the architectural decisions about whether to use it.
What Starshipit Actually Does#
Starshipit's core function is multi-carrier shipping orchestration. The operational surface includes:
Order ingestion. Pull orders from ecommerce platforms (Shopify, WooCommerce, Magento, BigCommerce) and inventory platforms (Cin7 Core, Unleashed, DEAR, Xero).
Rate shopping. Compare carrier rates across configured services at quote time or pick time. Choose the cheapest, fastest, or operator-preferred carrier per shipment.
Label printing. Generate carrier-compliant labels for all configured carriers from one UI. Bulk label printing for batch dispatch.
Tracking and customer communication. Send branded tracking emails to customers. Provide carrier-agnostic customer-facing tracking pages.
Manifest submission. Submit end-of-day manifests to each carrier via their respective APIs or file-based handoff.
Returns automation. Generate return labels and manage RMA workflows.
Reporting. Carrier performance, shipping cost analysis, exception tracking.
For Shopify and Cin7 Core operators without deeper ERP/WMS integration, Starshipit fills a real operational gap.
How Starshipit Integrates#
Source-side integrations (where orders come from)#
- Shopify — direct REST API integration, the largest customer base
- WooCommerce — WordPress plugin or REST API
- Magento — Magento extension
- BigCommerce — REST API
- TradeMe (NZ) — direct integration for ANZ marketplaces
- Cin7 Core (DEAR) — inventory-side integration
- Unleashed — inventory-side integration
- NetSuite — ERP-side integration via SuiteCloud
- Microsoft Dynamics 365 BC — limited integration
- Xero — limited integration (more for billing reconciliation than order flow)
Carrier-side integrations (where labels go to)#
New Zealand carriers: - NZ Couriers (via NZ Post Limited) - NZ Post / CourierPost (eShip and CourierPost APIs) - Mainfreight - PBT Freight - Castle Parcels - Pass The Parcel (PTP)
Australian carriers: - Australia Post (MyPost Business and eParcel) - StarTrack - Sendle - Aramex Australia (formerly Fastway) - Toll Priority and IPEC - TNT Express - Hunter Express - Couriers Please
International: - DHL Express and DHL eCommerce - FedEx - UPS
Carrier integrations are added regularly; the live list is on the Starshipit website.
Starshipit Pricing in 2026#
| Tier | Monthly cost (NZD) | Included shipments | Overage cost |
|---|---|---|---|
| Starter | ~NZ$50 | 100 | ~NZ$0.40/shipment |
| Standard | ~NZ$110 | 500 | ~NZ$0.25/shipment |
| Advanced | ~NZ$220 | 1,500 | ~NZ$0.15/shipment |
| Enterprise | Custom | Custom | Custom |
Realistic annual cost ranges:
| Operation size | Realistic Starshipit annual cost |
|---|---|
| 500 orders/month | NZ$1,300–2,000 |
| 2,000 orders/month | NZ$3,000–6,000 |
| 5,000 orders/month | NZ$8,000–15,000 |
| 10,000+ orders/month | NZ$15,000–40,000+ |
Pricing is on top of ecommerce platform subscriptions and any ERP/inventory platform costs. Starshipit is middleware, not a replacement for those layers.
Where Starshipit Fits in the ANZ Operations Stack#
The typical ANZ ecommerce stack with Starshipit:
`
Customer
↓
Shopify (or WooCommerce, etc.)
↓
Cin7 Core / Unleashed / DEAR (or directly to Starshipit)
↓
Starshipit (multi-carrier shipping middleware)
↓
Carriers (NZ Couriers, NZ Post, Aus Post, etc.)
↓
Customer
`
The alternative stack with direct carrier integration:
`
Customer
↓
Shopify (or storefront)
↓
ERP/WMS with native carrier APIs (NetSuite, MYOB Acumatica, OpsUI, etc.)
↓
Carriers (direct API)
↓
Customer
`
Both architectures work. The decision is about whether the middleware layer (Starshipit) adds enough value to justify its monthly cost and operational complexity.
When Starshipit Is the Right Choice#
Stack composition where Starshipit earns its keep:
- Shopify or WooCommerce + Xero, no ERP/WMS. Carrier integration in this stack is otherwise manual — login to each carrier portal, copy paste, print labels. Starshipit's unified UI saves significant time.
- Cin7 Core or Unleashed deployments. These platforms have lighter native carrier integration than full ERPs. Starshipit fills the gap; many Cin7 and Unleashed implementations include Starshipit as standard.
- Multi-channel ecommerce with diverse carrier mix. Operators shipping across 5+ carrier services daily benefit from Starshipit's rate shopping and unified workflow.
- Small dispatch teams (1–3 people) needing productivity tools. Starshipit's UX is purpose-built for shipping staff; ERP shipping UX is typically more generic.
- Returns volume above ~5% of dispatches. Starshipit's returns automation is meaningfully better than most ERP-native returns workflows.
- Customer experience around tracking matters. Branded tracking emails, customer-facing tracking pages, and SMS notifications come out of the box.
For these scenarios, the NZ$3,000–10,000/year cost is reasonable for the value delivered.
When Starshipit Is the Wrong Choice#
Stack composition where Starshipit becomes duplicate cost:
- ERP with native first-party carrier integration. NetSuite SuiteShip, MYOB Acumatica Distribution, OpsUI Shipping, Microsoft Dynamics 365 Supply Chain — all include native carrier API integration. Starshipit on top is middleware paying for capability the ERP already has.
- High-volume operations (>5,000 shipments/month). Starshipit's tier-based pricing becomes significant at scale. Operators at this scale typically have ERP/WMS with carrier APIs and don't need the aggregator layer.
- Single-carrier operations. If you ship 95% with NZ Couriers and 5% with NZ Post, Starshipit's multi-carrier value is minimal. Direct NZ Couriers integration plus occasional NZ Post handling may be cheaper and simpler.
- Operations requiring real-time tracking back to ERP order timeline. Starshipit pushes tracking to customer-facing channels; direct integration pushes tracking events back to the ERP for order timeline visibility and exception management.
- Tightly negotiated carrier rates. Some Starshipit features use Starshipit's consolidated/aggregated rates. Operators with negotiated direct carrier accounts may prefer direct integration to ensure their negotiated rates apply.
Architectural Considerations#
Single source of truth#
With Starshipit in the stack, you have two operational systems (ERP/inventory + Starshipit). This means: - Two places to reconcile shipping cost - Two failure surfaces (Starshipit could be down, or carriers, or both) - Two UIs for dispatch staff - Two integration points to maintain
For some operations, the additional surface is worth the productivity gain. For others, consolidating to one platform is the architectural goal.
Carrier account ownership#
Starshipit can route shipments via: - Your carrier accounts with your negotiated rates (most common) - Starshipit's aggregated accounts with their consolidated rates (some carriers, some plans)
For operators with negotiated carrier rates, ensure Starshipit configuration uses your accounts, not their aggregated rates.
Webhook and tracking events#
Starshipit sends tracking events to customer-facing channels by default. To get tracking events back to your ERP order timeline, you need either: - Starshipit webhooks to your ERP (configurable, requires development) - Direct carrier webhook integration in your ERP (only if your ERP has direct carrier integration)
Many Starshipit deployments don't capture tracking events in the ERP, which creates support visibility gaps later.
Alternatives to Starshipit#
For operations that need shipping aggregation but want to consider alternatives:
Shippit. Australian-built aggregator; strong AU carrier integration. Less NZ depth than Starshipit. Comparable pricing.
Shipster. Newer ANZ aggregator. Smaller carrier list. Often cheaper at entry tier.
ShipStation. US-built but available in ANZ. Strong Shopify integration. Less ANZ carrier depth.
Native ERP carrier integration. OpsUI Shipping, NetSuite SuiteShip, MYOB Acumatica Distribution, Microsoft Dynamics 365 Supply Chain — for operations with these platforms, the aggregator is redundant.
Direct carrier APIs. Some operations integrate carriers directly into their ERP or custom software. Highest control, requires development capability.
Migration Patterns#
Moving from Starshipit to direct integration#
Common scenario: business outgrows Shopify-only operations and adds an ERP with native carrier APIs. Migration approach:
- Configure carriers directly in the new ERP
- Test carrier integration in parallel with Starshipit
- Migrate dispatch staff workflow to new ERP
- Cancel Starshipit subscription
Typical timeline: 2–4 weeks of parallel running before cancellation. Cost savings of NZ$3,000–15,000/year typically.
Adding Starshipit to existing stack#
Common scenario: business grows past spreadsheet shipping and needs aggregation. Migration approach:
- Sign up for Starshipit
- Configure carrier integrations against existing carrier accounts
- Test order flow from ecommerce platform through Starshipit to carriers
- Migrate dispatch staff workflow
Typical timeline: 1–2 weeks. Lower-risk addition than removal.
Operational Considerations#
Multi-warehouse / multi-location#
Starshipit handles multi-warehouse adequately for ANZ SMB operations. Each warehouse can have its own carrier accounts and dispatch profile. For complex multi-warehouse routing decisions (where to ship from based on stock and proximity), the routing logic typically lives in the ERP or OMS upstream, not in Starshipit.
Multi-channel orders#
Starshipit aggregates orders from multiple ecommerce sources (Shopify, WooCommerce, marketplaces) into one dispatch queue. This is valuable for operators selling across channels without a unified OMS.
Returns workflow#
Returns automation in Starshipit includes return label generation, RMA tracking, and customer communication. For deeper returns disposition (restock, refurbish, scrap with inventory adjustments), the workflow needs to extend back into the inventory/ERP platform.
EDI and chain retailer shipping#
For B2B operators shipping to chain retailers (Foodstuffs, Woolworths, Coles, Mitre 10) via EDI, Starshipit isn't typically the right tool — EDI integration is usually direct between the ERP and the retailer, with carrier dispatch via direct API or via the chain retailer's nominated carriers.
Selection Framework#
Use this framework to decide on Starshipit:
| Your situation | Recommended approach |
|---|---|
| Shopify + Xero, no ERP | Starshipit — fills real gap |
| Cin7 Core, growing volume | Starshipit — augments Cin7 shipping |
| Unleashed, multi-carrier | Starshipit — fills Unleashed shipping gap |
| NetSuite with SuiteShip | Direct integration — Starshipit is duplicate |
| MYOB Acumatica Distribution | Direct integration — duplicate cost |
| OpsUI with Shipping module | Direct integration — first-party carriers built in |
| Microsoft Dynamics 365 SCM | Direct integration — duplicate cost |
| Single-carrier operations | Direct integration — aggregator overhead not justified |
| High-volume (5,000+/mo) | Direct integration or Enterprise tier — evaluate carefully |
Bottom Line#
Starshipit is a well-built ANZ shipping platform that solves a real problem — multi-carrier shipping complexity in stacks that don't have native carrier integration. For Shopify operators, Cin7 Core users, and SMB ecommerce businesses, it's a meaningful productivity layer.
For operations with ERPs that have first-party carrier APIs (NetSuite, MYOB Acumatica, OpsUI, Microsoft Dynamics 365 SCM, Sage X3 Distribution), Starshipit becomes duplicate middleware. The architectural decision is whether to consolidate to one platform or maintain the aggregator layer.
The most common mistake is keeping Starshipit out of inertia after migrating to an ERP with carrier APIs. The honest move at that point is to cancel and route directly through the ERP.
See Also#
For broader context, see What is a WMS?, What is an OMS?, Inventory Management Module Architecture, Supply Chain Module Design, and the various per-platform integration guides (Shopify-integration patterns, Xero integration patterns, etc.).