Connect Commercetools with Lightspeed Retail to sync products, prices, customers, and inventory in near real time, so online and in-store teams sell from the same data.
• Products and variants are mapped between Commercetools product projections and Lightspeed Retail item and variant records, including SKU, barcode, pricing fields, and tax classes where available.
• Inventory updates from Lightspeed Retail are synchronized to Commercetools inventory entries per location, with configurable aggregation rules for what the storefront treats as “available.”
• Order data from Commercetools can be exported to Lightspeed Retail as sales transactions, with tenders, discounts, and taxes mapped when corresponding entities exist in POS.
• Customer records are matched using shared identifiers such as email and external IDs, with deduplication rules applied before creating or updating profiles across systems.
• Delta-based syncs transmit only changed records, while full syncs are used for initial alignment or reconciliation, with timestamps controlling conflict handling.
• Integration jobs log requests, responses, and validation errors per entity, and retries are handled for transient API failures to keep sync queues consistent.
.png)
We map ownership rules per location, then sync stock movements from Lightspeed Retail into Commercetools using APIs and webhooks. This keeps online availability aligned with sales, returns, transfers, and receiving.
Yes, we align SKU, barcode, and variant models, then automate product and attribute updates in the direction you choose. We also add validation so new items do not break POS scanning or online merchandising.
It can, but pricing rules need a clear source of truth because POS and eCommerce often differ by channel. We can sync base prices, store-specific price books, and tax settings where the APIs allow it.
We can sync customer identities, contact data, and loyalty IDs, then link in-store transactions to online profiles for service and marketing. Sensitive fields can be excluded to match your privacy rules.
Yes, the integration can be built with store-level mappings for locations, assortments, and stock buckets. This is critical when the same SKU behaves differently by market or warehouse.














