Connect BigCommerce to parcelLab to unify shipment events and send branded tracking emails and order status updates that reduce WISMO tickets and lift repeat purchases.
• Bigcommerce order data (order number, customer, shipping address, line items, and shipment records) is exported to parcelLab via API/webhooks when orders are created or fulfilled.
• Carrier and service information is mapped to parcelLab’s shipment model, including tracking numbers, label references, and delivery country/locale fields.
• Shipment status events are ingested by parcelLab from carriers and associated back to the originating Bigcommerce order using order and tracking identifiers.
• Delta-based updates send only changed shipment states and timestamps, reducing repeated payloads during in-transit periods.
• Event handling supports partial shipments by linking multiple tracking numbers to a single Bigcommerce order and maintaining per-shipment state.
• Sync operations are logged with request/response details and validation errors (missing tracking numbers, unsupported carrier codes, or mismatched identifiers) for troubleshooting.
.png)
We map orders, tracking numbers, and carrier codes from BigCommerce to parcelLab and validate the event flow end to end. Once events land, parcelLab can trigger status-based messaging off real delivery milestones.
Typically order ID, customer contact data, shipment IDs, tracking numbers, carrier, line items, and delivery status events. We also align custom attributes when you need segmentation, localization, or carrier-specific rules.
Yes, parcelLab can send messages when parcels hit key statuses like “shipped,” “out for delivery,” and “delivered.” The triggers are driven by carrier events, not manual updates in BigCommerce.
Yes, we support multi-carrier setups and split shipments by passing shipment-level identifiers to parcelLab. That keeps tracking accurate when a single order ships in multiple boxes.
scandiweb has delivered 2,100+ eCommerce projects and supports 450+ active clients, so integrations and ongoing fixes are routine work for our teams. We can own the build, QA, go-live, and post-launch monitoring.










