Connect BigCommerce with MetaPack to return real-time delivery options at checkout, automate shipping labels, and keep orders tracked from dispatch to delivery.
• Order data is sent from Bigcommerce to MetaPack via API, with customer, address, line items, shipping method, and totals mapped to MetaPack order fields.
• Delivery option and service codes are mapped between MetaPack and Bigcommerce so the selected method remains consistent across checkout, order records, and downstream processing.
• Shipment lifecycle events from MetaPack (created, dispatched, delivered, exception, and canceled) are synchronized back to Bigcommerce as shipment updates and order status changes, based on mapping rules.
• Tracking identifiers, carrier names, and tracking URLs are written to Bigcommerce shipment records and exposed to customer notifications where supported.
• Delta-based updates send only changed orders and shipment events, with idempotency keys used to prevent duplicates during retries.
• Validation and error logging capture rejected payloads, mapping mismatches, and API failures, with correlation IDs used to trace each order across systems.
.png)
We pass cart address, service rules, and carrier availability from MetaPack to BigCommerce so shoppers see valid methods and prices before paying.
Orders, fulfillments, tracking numbers, label data, and delivery events can sync both ways, keeping customer service and the storefront on the same timeline.
Yes. Once an order meets your fulfillment rules, MetaPack can generate labels and push tracking back to BigCommerce for customer notifications.
It can be configured per storefront, region, currency, and service level, including different carrier mixes and cutoff times.
We QA checkout delivery logic, order-to-shipment flows, and key events in GA4 and tag managers; scandiweb has delivered 575+ eCommerce BI dashboards and 60+ certified analytics experts.










