Metapack ↔ Sage 200 Integration
Metapack (Auctane)Delivery managementSOP despatch to consignment booking, labels and tracking writeback — the loop between your warehouse and every carrier Metapack fronts.
Metapack sits between your ERP and dozens of carriers — one API for shipping options, consignment booking, labels, manifests and tracking. The awkward part is keeping Sage 200 in sync with it: which orders are ready to ship, which carrier service maps to which Sage shipping method, and getting tracking numbers back onto the despatch so 'order despatched' in Sage actually means 'carrier has it'. We build that loop — Sage 200 sales orders become Metapack consignments at despatch time, carrier/service selection honours Sage's delivery methods, and tracking + confirmation flows back so SOP despatch notes stay the single source of truth.
Data Flows
- 1
SOP → consignment
Orders released for despatch in Sage 200 create Metapack consignments: delivery address, parcel count, weight and dims pulled from SOP + stock item data. Carrier service is chosen from Sage delivery method via a mapping table — no re-keying in Metapack Manager.
- 2
Labels & manifest
Metapack returns the carrier label PDF and consignment reference at pack-station time; end-of-day manifests are generated inside Metapack as normal. Sage never holds label data — it holds the consignment reference and carrier/service used.
- 3
Tracking → Sage
Tracking number + carrier ID write back onto the despatch note (or a custom tracking table per despatch line), so despatch confirmation emails from your e-commerce store or CRM carry real carrier links.
- 4
Exceptions
Failed bookings (address rejection, service unavailable, weight mismatch) raise a queue entry — user fixes in Sage or Metapack, consignment retries. No silent drops.
Where These Integrations Go Wrong
The failure modes we design around — most Metapack (Auctane) ↔ Sage projects hit at least two of these.
Book after pick, not after save
Booking consignments on order save produces cancelled consignments every time an order is edited. The trigger should be despatch-complete (or a packing confirmation), not SOP creation.
Weights and dims are rarely in Sage
Metapack wants parcel weight/dimensions; most Sage 200 installs have them blank. We default from a packaging rules table (carton type per order value/line count) and let the pack station correct it — rather than blocking on missing data.
Service-code drift
Carriers rename services constantly. Keep the Sage delivery-method ↔ Metapack service map as data you can edit — not baked into code — or it breaks on every carrier update.
Northern Ireland & customs
NI shipments need customs data post-Windsor Framework. If you ship NI/EU from GB, line-level commodity codes and values have to flow from Sage stock items — that means the customs data model has to be right in Sage first.
What's Included
- SOP despatch → Metapack consignment booking (auto or pack-station triggered)
- Delivery-method ↔ carrier-service mapping table, editable without code
- Label print integration or pack-station handoff
- Tracking number + carrier writeback to Sage despatch records
- Exception queue with retry for failed bookings
- End-to-end UAT on your live Metapack account against a Sage 200 test company
Who It's For
Distributors and e-commerce businesses already on Metapack (or evaluating it) who still type addresses into Metapack Manager or copy tracking numbers back into Sage by hand. Works whether Sage 200 is on-prem or hosted, provided we can reach the database/API.
FAQ
Does this replace Metapack's Sage connector?
Metapack doesn't ship a maintained Sage 200 connector — their integrations target SAP/Dynamics/NetSuite or plain CSV import. This is the bespoke layer most Sage 200 + Metapack shops end up building anyway.
Can carriers be picked by cheapest quote?
Yes — Metapack's shipping/quote API can drive auto-selection (cheapest service meeting delivery date). The Sage delivery method then acts as the service-level constraint (next-day, economy, palletised), and Metapack picks the cheapest carrier inside that rule.
We run multiple warehouses — can parcels be created per warehouse?
Multi-location despatch works: each Sage 200 warehouse maps to its own Metapack origin/location (with its own manifests and label printers). Split-shipment orders produce separate consignments per despatch.
Scope Your Metapack (Auctane) Build
Fixed quote once we know your Sage version, the flows you need and the volumes.