Starshipit vs direct carrier integration: when each one wins

Starshipit is the dominant ANZ shipping aggregator.

Most ANZ Shopify and WooCommerce stores route their carrier integration through it.

The alternative is direct first-party carrier integration: your ERP or WMS talks straight to the carrier API.

Here is the honest comparison and when each one wins.

What Starshipit actually does

Starshipit is a shipping aggregator (a "multi-carrier shipping platform") that sits between your ecommerce store or ERP and the carriers. It connects to your Shopify, WooCommerce, Cin7, Unleashed, or NetSuite on one side, and to NZ Couriers, NZ Post, Australia Post, Toll, DHL, Aramex, Sendle, and a handful of others on the other side.

The Starshipit value proposition:

• One UI for all carriers (instead of NZ Post Web, NZ Couriers MyParcels, Australia Post Business Portal, etc.)
• Bulk label printing across carriers
• Rate comparison at order entry
• Pick lists and packing slips
• Returns label automation
• Manifest submission per carrier
• Customer tracking emails

For Shopify operators without a real ERP or WMS behind the store, Starshipit is a meaningful productivity gain. Without it, dispatch staff are logging into multiple carrier portals every day.

What Starshipit costs

Starshipit pricing (2026 ANZ):

• Starter: ~NZ$50/month, ~100 shipments included
• Standard: ~NZ$110/month, ~500 shipments included
• Advanced: ~NZ$220/month, ~1,500 shipments included
• Enterprise: custom-quoted, typically NZ$500+/month for high-volume operations

Overage fees apply above included shipment counts. For an operation shipping 2,000 orders/month, realistic annual Starshipit cost is NZ$3,000–6,000.

This is on top of your ecommerce platform subscription and your ERP/WMS subscription. Starshipit is the middleware layer.

What direct carrier integration looks like

The alternative: your ERP or WMS talks directly to each carrier's API. Labels, tracking, manifest, all generated from inside the operations platform.

For OpsUI specifically: NZ Couriers, NZ Post, Australia Post, Toll, DHL, StarTrack, Sendle, and Mainfreight all wire as first-party integrations through the Shipping/Outbound module. No Starshipit subscription required.

For other ERPs: NetSuite has SuiteShip; MYOB Acumatica has direct carrier integration modules; Microsoft Dynamics 365 has shipping connectors. The depth varies by vendor and by carrier.

When Starshipit wins

Starshipit is the right answer when:

• You run Shopify or WooCommerce without a real ERP behind it. Your operations stack is "ecommerce + bookkeeping app" and there's no ERP layer to integrate carriers into.
• You use Cin7 Core, Unleashed, or DEAR. These platforms have lighter native carrier integration and Starshipit fills the gap cleanly.
• You ship across 5+ different carrier services daily. The single-UI advantage is real when carrier-switching is a constant operational decision.
• You have a small dispatch team and need a productivity layer. Starshipit's UX is purpose-built for shipping staff; ERP shipping UX is usually generic.
• You bill customers for shipping and need rate comparison at quote time. Starshipit's rate-shopping engine is a meaningful UX advantage.
• You want the customer tracking experience without building it. Starshipit handles tracking emails and customer-facing tracking pages out of the box.

For most ANZ Shopify operators between 100 and 5,000 orders/month, Starshipit is genuinely useful.

When direct carrier integration wins

Direct integration is the right answer when:

• You have a real ERP or WMS with native carrier integration. Paying NZ$3,000–6,000/year for Starshipit on top of an ERP that already has carrier APIs is duplicate spending.
• You want one source of truth. Two systems (ERP + Starshipit) mean two reconciliation surfaces, two failure points, two places to log into.
• You have specific carrier accounts with negotiated rates. Direct integration uses your carrier account; some Starshipit features may use Starshipit's consolidated rates instead.
• You need real-time tracking events back to the ERP, not just to a customer email. Starshipit pushes tracking to customers; direct integration pushes back to your order timeline.
• You operate at scale where Starshipit pricing crosses break-even. Above ~5,000 shipments/month, the Starshipit annual cost approaches or exceeds the cost of building/buying direct integration.
• You have IT capability or vendor support to maintain integrations. Direct integration shifts the maintenance burden from Starshipit to you or your vendor.

The honest reality: Starshipit is duplicate cost when your ERP has carriers

The most common scenario where Starshipit becomes wasteful:

A growing Shopify operator buys Starshipit at ~NZ$110/month. They scale and need a real ERP/WMS. They evaluate ERPs and pick one with native carrier integration (OpsUI, NetSuite SuiteShip, etc.). They keep paying for Starshipit out of inertia. After 18 months, they're paying NZ$2,000–5,000/year for middleware their ERP no longer needs.

The honest test: if your operations platform talks to your carriers directly, Starshipit is duplicate cost. Cancel it.

The exception: if your operations platform has weak or partial carrier integration (basic labels only, no manifest, no tracking webhooks), Starshipit fills a real gap and is justified.

How OpsUI handles carriers

OpsUI's Shipping/Outbound module is the first-party carrier integration layer. No Starshipit required.

Live carrier integrations:

• NZ Couriers: live in production today, full API integration including rates, labels, tracking webhooks, manifest
• NZ Post / CourierPost: configurable through the Shipping module against your eShip / CourierPost account
• Mainfreight: consignments, labels, tracking via direct API or EDI
• Australia Post: MyPost Business and eParcel via direct API
• StarTrack: direct API integration for B2B dispatch
• Toll: Priority and IPEC services
• DHL: Express and eCommerce services
• Sendle: direct API for AU SMB operations

Each carrier ties to your existing carrier account (no rate aggregation overlay) and runs through OpsUI's native dispatch workflow.

See /integrations/carriers/nz-couriers for the NZ Couriers integration detail, or /integrations for the full carrier roster.

Selection framework

Use this framework to decide:

Stay on Starshipit if:

• Your operations stack is Shopify + Xero + nothing else, and you're not adding ERP
• You're on Cin7 Core or Unleashed and Starshipit's integration is meaningfully deeper than the platform's native shipping
• You need the rate-shopping UX for daily carrier-switching decisions
• The NZ$3,000–6,000/year cost is acceptable for the UX value

Move to direct integration if:

• You have or are planning a real ERP/WMS with native carrier APIs
• You want one source of truth across operations and shipping
• You ship at scale where Starshipit pricing is significant
• You want tracking events back to the order timeline, not just to customer emails
• Reducing the number of platforms in your stack is a strategic goal

Bottom line

Starshipit is a good product solving a real problem: multi-carrier shipping complexity in stacks that don't have native carrier integration. For Shopify-only operators and businesses on lighter inventory platforms, it earns its keep.

Once your operations stack has a real ERP or WMS with first-party carrier APIs, Starshipit becomes duplicate middleware. The honest move at that point is to cancel it and route directly through your operations platform.

For ANZ operators evaluating OpsUI: the carriers are first-party. You will not need Starshipit.