CommerceTools and Scend
Integration Agency & Consultants
Fulfilment pressure becomes critical when CommerceTools inventory levels no longer reflect the physical stock in the Scend warehouse. At scale, manual workarounds fail and lead to overselling or delayed dispatches that damage customer trust. Cogent2 designs integrations for operators who need a dependable order-to-dispatch process that stays in sync during peak trading. This prevents stockouts and ensures tracking data returns to the storefront without manual intervention, protecting your reputation for timely delivery.
Scoping data flows and retail strategy
Integrate CommerceTools and Scend seamlessly to enhance your multi-channel and omnichannel retail strategy. Our expertise ensures quick connectivity and effective implementation. Leverage our consulting and delivery skills to boost operational efficiency, optimize your tech stack, and provide comprehensive training for rapid scaling.
Solution Design
Designing the CommerceTools and Scend integration requires a clear stance on data ownership. In most setups, Scend is the master for physical inventory levels and fulfilment status, while CommerceTools remains the source of truth for customer order data. A core design decision involves the trade-off between real-time inventory updates and platform stability. Pushing every stock change immediately protects against overselling during peak trading but can increase system fragility. We typically implement a high-frequency sync for inventory to maintain accuracy while protecting system performance. For orders, we prioritise immediate transmission to Scend to ensure fast fulfilment. This approach allows finance to reconcile daily based on Scend records, while CX teams provide customers with accurate status updates directly from CommerceTools.
Connecting SKUs and fulfilment triggers
Orders flow from CommerceTools to Scend based on defined triggers, usually following payment confirmation. We typically treat Scend as the physical inventory master, pushing available quantities back to CommerceTools to prevent overselling on the storefront. Success relies on a precise match between the CommerceTools SKU and the Scend Product Code. The integration manages the flow from order ingestion through to the return of tracking data once items are dispatched. We embed monitoring at the record level to catch stuck orders or SKU mismatches, ensuring exceptions are surfaced for early resolution before they delay warehouse operations or impact customer trust.
Orchestrating workflows through middleware layers
Cogent2 uses IPaaS to seamlessly integrate CommerceTools with Scend, enhancing data flow and process automation. Benefits include reduced integration complexity, faster deployment, improved scalability, and real-time data synchronization, enabling efficient management of e-commerce operations and consulting services.
Surfacing order exceptions and inventory drift
Dashboards often show that an integration is running while hiding the fact that specific orders are hiding errors. Visibility means detecting the SKU that exists in CommerceTools but is missing in Scend, or the fulfilment update that failed to post back to the storefront. We focus on identifying these exceptions early. Without this, hidden issues like inventory drift compound over days, leading to stockouts that your storefront cannot see. We surface these gaps so operations can resolve a data mismatch before it triggers a customer complaint or a manual reconciliation issue.
Operating manuals for daily data reconciliation
Handover prepares operations, finance, and CX teams to own the CommerceTools and Scend relationship. We clarify the operating model, defining Scend as the source of truth for physical inventory and CommerceTools for order capture. Training covers daily checks for order flow and periodic reconciliation of warehouse dispatches against storefront records. Teams learn to interpret alerts from the integration layer, identifying whether an issue requires a warehouse correction or a product data update in the storefront. Documentation is an operational manual for managing exceptions like SKU mismatches or sync delays, rather than a technical archive. This focus on practical ownership ensures teams resolve common data gaps without escalating every minor disruption.
Maintaining continuity and managing peak trading
Our support model focuses on maintaining operational continuity between the storefront and the warehouse. We monitor the data flow between CommerceTools and Scend to catch sync errors, SKU mapping gaps, or stuck orders before they impact warehouse operations. If an order fails to post or inventory levels stop updating, we isolate the cause and provide a path to resolution. This includes managing system exceptions and providing oversight during peak trading periods. We ensure your team remains confident in the numbers by providing a layer of operational intelligence that detects discrepancies before they become customer-facing stockouts.
Common failures
Inventory latency and overselling
Operational impact: When CommerceTools displays more stock than is physically available in Scend, overselling occurs. This creates failed sales orders that the customer service team must cancel, process refunds for, and communicate to frustrated customers. It also means the fulfilment team wastes labour attempting to pick stock that does not exist, which disrupts warehouse schedules.
Prevention / Action: The integration must enforce Scend as the single source of truth for available stock. Inventory updates should be synchronised to CommerceTools on a high-frequency schedule, ideally processing only deltas (changes) to reduce processing load. The integration logic should also account for stock reservations during the checkout process to minimise the risk of race conditions between a stock update and a customer placing an order.
Incomplete order data stalling fulfilment
Operational impact: Orders sent from CommerceTools with incorrectly mapped delivery options or incomplete address information often fail validation in Scend. This causes orders to enter an exception state, requiring manual review and correction by the warehouse operations team. The delay jeopardises promised dispatch and delivery timelines and creates a growing backlog that slows down the entire fulfilment workflow.
Prevention / Action: Map and validate all mandatory Scend order fields within the integration layer before attempting to create the order in Scend. A pre-transmission check on data like postcodes and delivery service codes is critical. Failed orders should be held in a queue with automated error notifications sent to an operations team, allowing them to correct the source Order in CommerceTools rather than fixing it downstream in the warehouse system.
Product record and SKU mismatches
Operational impact: If a new SKU is published in CommerceTools but does not exist as a corresponding item record in Scend, any order containing it immediately fails. The order becomes stuck, invisible to the fulfilment team, until a merchandising or data team manually creates the missing item in Scend. This not only delays the individual order but also risks the entire order being cancelled if the issue is not identified quickly by customer service.
Prevention / Action: Define a single system, either CommerceTools or an upstream PIM/ERP, as the master source for product data. The integration's process design must ensure that creating a new Product Variant triggers the creation of the corresponding, fully mapped item in Scend. This item creation in Scend must be confirmed before the product is made purchasable on the CommerceTools storefront. Regular monitoring should be in place to audit for and alert on any SKU discrepancies between the two systems.
Shipment notification synchronisation failure
Operational impact: Scend dispatches a parcel, but the integration fails to update the associated Order in CommerceTools to a 'Shipped' status. This means the customer never receives a shipment confirmation email or tracking number, triggering a high volume of 'Where is my order?' enquiries for the customer service team. It can also impact the finance team's ability to recognise revenue or capture payments if those processes are tied to the shipment event.
Prevention / Action: The integration's design must include a persistent queue and automated retry logic for fulfilment and shipment updates flowing from Scend to CommerceTools. The process should expect an explicit acknowledgement from the CommerceTools API upon success and trigger an alert if an update fails after a defined number of retries. Giving the customer service team read-only access to Scend's shipment view can provide a secondary source of truth for handling customer queries while the root cause is investigated.
Frequently asked questions
How do we prevent overselling if our stock data in Scend and CommerceTools gets out of sync?
This is a critical risk, as inaccurate inventory counts in CommerceTools directly lead to overselling and failed orders. The integration must correctly map Scend's definition of 'Available' stock to the CommerceTools inventory level for each SKU, filtering out any stock that is reserved or unsaleable. For example, if Scend's available figure includes damaged goods, syncing this incorrectly inflated number to CommerceTools will cause orders to fail fulfillment, damaging customer trust.
Our warehouse team is worried about new processes. How does an order actually get from CommerceTools into Scend?
The integration automates the existing process, it does not typically require new warehouse workflows. When a customer completes checkout, a confirmed order in CommerceTools triggers the creation of a sales order in Scend with all the necessary details for the pick and pack process to begin. Once the order is dispatched from Scend, a shipment confirmation is sent back to CommerceTools to update the order status, which can then trigger customer notifications.
We use CommerceTools' event-driven architecture. How do you ensure no orders are missed?
This architecture is powerful but can fail if events are not processed correctly. A common failure occurs if the integration misses a 'Change Notification' from CommerceTools (via Pub/Sub or EventBridge), causing an order not to be created in Scend. To prevent this, the connection must have robust error handling and retry logic to guarantee every order event from CommerceTools is successfully received and actioned by Scend.
Will the integration create race conditions if we use CommerceTools 'OrderCreated' webhooks?
Yes, this is a known risk if not managed correctly, especially during high-volume periods. Using the standard 'OrderCreated' webhook from CommerceTools can trigger the integration before all order data, like customer details or metafields, is fully saved. To avoid creating incomplete sales orders in Scend, the integration should use a more reliable trigger, such as an order 'state change' or a brief, managed delay, ensuring all data is present before sync.