CGS Blue Cherry and Emarsys
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Inventory latency and inaccurate stock signals
Operational impact: Emarsys campaigns promote out-of-stock items because Blue Cherry's batch inventory updates create data lag. This results in wasted marketing spend and a poor customer experience. 'Back in stock' notifications may also trigger before inventory is truly available for picking, leading to customer complaints and cancelled sales orders.
Prevention / Action: The integration's design must account for Blue Cherry's typical batch processing of inventory levels. Instead of relying on real-time events, use scheduled delta or full catalogue updates to sync stock data to Emarsys. The logic should respect the sequence of inventory updates and a monitoring process should track the timestamp of the last successful sync to avoid using stale data.
Inaccurate customer segmentation
Operational impact: Customer segments in Emarsys become unreliable when transactional data from Blue Cherry is not synchronised correctly. As a result, recent high-value customers might receive incorrect discount offers, or new buyers are not added to welcome sequences. This reduces campaign effectiveness, erodes margin, and provides the finance team with misleading data on marketing ROI.
Prevention / Action: Establish Blue Cherry as the definitive source of truth for the core customer record, including all sales order history. The integration should map key transaction attributes, such as order values and dates, to specific Emarsys contact fields used for segmentation. Schedule periodic audits that compare Emarsys segments against Blue Cherry's transactional records to identify and correct discrepancies.
Mistimed transactional order communications
Operational impact: Emarsys may send 'Order Shipped' emails based on an interim status change in Blue Cherry, before a consignment is created and the parcel has left the building. This causes confusion and drives 'where is my order?' queries to the customer service team. Conversely, a failure to trigger the message at all leaves customers without updates, damaging trust.
Prevention / Action: The integration should trigger post-purchase emails in Emarsys from a definitive event in Blue Cherry, such as the creation of a final pick ticket or a dispatch confirmation record. Define which Blue Cherry status means 'shipped' from an operational perspective and ensure the integration logic acts only on that specific trigger. A queuing and retry mechanism is advised to manage API availability and ensure messages are not lost during sync.
Delayed return and refund data synchronisation
Operational impact: When return or refund data from Blue Cherry is not promptly synced, Emarsys continues to engage customers about products they have already sent back. Requesting a product review for a returned item creates a particularly poor customer experience. It also means customer lifetime value and purchase history segments in Emarsys become inaccurate, skewing marketing analytics.
Prevention / Action: Design the integration to monitor for the creation and completion of Return Authorisation or Credit Memo records in Blue Cherry. Once a return is processed, the integration should update the customer's contact record in Emarsys and tag the original order data accordingly. This ensures marketing campaigns can exclude recently returned products and that segmentation logic operates on accurate lifecycle data.
Frequently asked questions
How does the timing of inventory updates from CGS Blue Cherry affect our marketing campaigns in Emarsys?
CGS Blue Cherry often processes inventory updates in batch cycles, not in real-time. This delay means Emarsys could trigger a 'back in stock' campaign for a SKU that has already sold out again, leading to a poor customer experience. A well-designed integration must account for these batch schedules to keep marketing messages relevant.
We sometimes oversell popular items. Could the CGS Blue Cherry to Emarsys integration be a factor?
Yes, this is a common issue originating in the ERP. If CGS Blue Cherry's inventory feed includes stock from 'Open Work Orders' as available-to-sell, it inflates the quantity synced to Emarsys. This can prompt marketing campaigns for stock that is not yet ready for dispatch, resulting in overselling and customer frustration.
If our team manually changes a sales order in CGS Blue Cherry, will Emarsys be updated automatically?
Typically, manual edits to a sales order inside CGS Blue Cherry's modules do not trigger an automatic update to Emarsys. This data gap can lead to incorrect marketing communications, such as sending a shipping confirmation for an item that was manually cancelled. The integration process must therefore include a method to reconcile these changes.
How does the integration handle communications in Emarsys when we only partially fulfil an order from CGS Blue Cherry?
This requires careful mapping, as a common failure occurs when CGS Blue Cherry marks an entire sales order as 'Closed' after a partial cancellation. If the integration simply passes this status to Emarsys, it may prevent transactional emails for the items that did ship, creating a confusing customer experience and potentially losing future sales.