ParcelBroker ↔ Sage 200 Integration
ParcelBrokerCarrier brokerUK multi-carrier broker — cheapest-quote booking across DPD/UPS/Parcelforce etc via one API; service selection rules, label print, consolidated tracking.
ParcelBroker sits between your Sage 200 and major UK carriers — one API for shipping options, cheapest-quote booking, label printing, and tracking writeback. The value is the broker layer: you submit a despatch in Sage 200 and ParcelBroker picks the cheapest viable service (meeting your delivery constraints), books and prints the label, and tracks consolidately across all carriers. That's the loop we build: Sage 200 despatch details become a booking request, ParcelBroker selects the optimal carrier/service, prints and delivers the label to your pack-station, and writes back the tracking references so 'despatched' in Sage 200 actually means 'carrier has it'.
Data Flows
- 1
Despatch → quote/booking
Sage 200 despatch details (pickup address, parcel count/weight/dims, service requirement) push to ParcelBroker API; it queries all UK carriers (DPD, UPS, Parcelforce, etc.), applies service-selection rules (cost constraint, delivery window, service level) and returns the cheapest viable quote. The broker can also book and print the label directly — no separate API call.
- 2
Labels → pack-station
Booked label (PDF or thermal print) returns to Sage 200 as a 'consignment reference' stored on the despatch note. The pack station receives the carrier label file via PDF viewer or direct printer integration; the label includes tracking, address and carrier-specific handling notes.
- 3
Tracking → Sage
Consolidated tracking feed from all carriers (DPD, UPS, Parcelforce, Royal Mail, etc.) pushes back to Sage 200 via tracking files or API: despatch reference + carrier + latest status (in_transit, out_for_delivery, delivered, exception). Updates appear on the despatch note and any custom tracking table.
- 4
Exceptions → queue
Failed bookings (address rejection, service unavailable, weight mismatch) push to a ParcelBroker exception queue with human-fix option. After correction, the booking retries automatically (per configured policy). Failed bookings are surfaced in Sage 200 for manual resolution if needed.
Where These Integrations Go Wrong
The failure modes we design around — most ParcelBroker ↔ Sage projects hit at least two of these.
Carrier service mapping drift
UK carriers rename or retire service codes constantly. The Sage 200 delivery-method ↔ ParcelBroker service-code mapping must be editable data, not baked into code — otherwise new service names break bookings or block on constraints.
Service cut-offs are hard
Each carrier has booking cut-offs (e.g., DPD by 4pm). If a Sage despatch lands after cut-off, ParcelBroker may pick a later-day service automatically (if enabled) or fail. This must be visible in Sage or routed to a human-fix queue before despatch.
Weights/dims in Sage
ParcelBroker needs parcel weight/dimensions; Sage 200 typically has them blank. We pull from a packaging rules table (carton type per order value/line count) or let pack station correct at booking — no blocking on missing data.
Cost vs service constraints
The cheapest service may not meet delivery window or customer expectation. The broker must support constraint-first selection (apply service-level constraints first, then cheapest) or alert when cheapest violates constraints. This is a business-rule, not technical problem.
What's Included
- Multi-carrier quote and booking via one API
- Service-level constraint enforcement (delivery window, service band) with fallback to next viable carrier
- Label print integration (PDF or direct to carrier printers) at pack station
- Consolidated tracking writeback to Sage 200 despatch records
- Exception queue with retry for failed bookings (address validation, service mapping)
- End-to-end UAT on your live ParcelBroker account against a Sage 200 test company
Who It's For
Businesses shipping UK parcel volume who want cheapest carrier selection without managing multiple carrier contracts themselves. Typically distributors, e-commerce platforms, and fulfilment houses that already have Sage 200 and need the shipping loop completed: Sage 200 despatch → booking → label → tracking → confirmed despatched. Works whether Sage 200 is on-prem or hosted, provided we can reach the ParcelBroker API.
FAQ
Can ParcelBroker handle multi-service orders?
Yes — each despatch can book multiple parcels with different services (next-day, economy, timed) based on service codes mapped from Sage 200 delivery methods. The broker applies constraints per parcel and can consolidate or split shipments.
What about international carriers?
ParcelBroker currently focuses on UK carriers (DPD, UPS, Parcelforce, Royal Mail). International expansion would require additional mappings and carrier contracts. The Sage 200 side remains the same; new carriers added via ParcelBroker admin.
How does this compare to using Metapack directly?
ParcelBroker is essentially the same as Metapack but for clients who don't have a Metapack account. The integration patterns are identical: one broker API, multi-carrier booking, label print, tracking writeback. This page shows the same depth of service as Metapack's page but positioned as an alternative broker.
Scope Your ParcelBroker Build
Fixed quote once we know your Sage version, the flows you need and the volumes.