Connect Commercetools with Brightpearl to keep inventory, orders, customers, and fulfillment status in sync across channels, while reducing manual fixes and stockouts.
• Order data is exported from commercetools to Brightpearl using API-based sync, mapping carts and orders to Brightpearl sales orders, customers, addresses, shipping methods, taxes, and discounts.
• SKU-level product identifiers are aligned so Brightpearl items map to commercetools variants, with attribute-based mappings used where required for size, color, or bundle components.
• Inventory availability is synchronized from Brightpearl to commercetools, with location or warehouse stock mapped to supply channels or scoped inventory models where applicable.
• Shipment and fulfillment events in Brightpearl are routed back to commercetools as parcel and delivery updates, including carrier, tracking number, shipped quantities, and status transitions.
• Payment and refund states are matched carefully between systems, with transaction references stored for reconciliation and to prevent double-capture or duplicate refund handling.
• Delta sync logic prioritizes changed records, while validation and error logging capture rejected payloads, mapping conflicts, and retries for later reprocessing.
.png)
We map Commercetools product variants and locations to Brightpearl warehouses, then sync available-to-sell stock back to Commercetools on a schedule or via webhooks. Safety stock and allocation rules can be handled in Brightpearl to prevent oversells.
Typically orders, line items, prices, discounts, taxes, shipping methods, and payment status are pushed into Brightpearl with the right customer record attached. We also sync cancellations and refunds when your process requires it.
Yes, we can route orders by store, region, or channel, and sync inventory per warehouse or stock pool. Currency and tax logic are defined up front so Brightpearl financials and Commercetools checkout totals match.
When Brightpearl marks items as picked, packed, or shipped, we send fulfillment status and tracking numbers to Commercetools. This keeps customer emails, self-serve order tracking, and support workflows consistent.
We use idempotency keys, strict status mappings, and retry queues with logging so each order is processed once. A reconciliation report flags price, tax, and inventory deltas before they become finance issues.














