CGS Blue Cherry and InRiver
Integration Agency & Consultants
Apparel operations lose speed when the technical skeleton in CGS Blue Cherry and the enriched content in InRiver fall out of step. At scale, this gap manifests as incorrect SKU listings on marketplaces and fulfilment teams shipping against the wrong product specifications. We connect these systems to ensure technical attributes, material compositions, and season codes remain consistent from the PIM through to Blue Cherry, protecting your operational truth.
Scoping data hierarchies and system boundaries
Connect seamlessly with CGS Blue Cherry and InRiver through our integration services, enhancing your multi-channel, omnichannel, and unified retail strategies. Utilize our consulting expertise to boost operational efficiency and tech stack performance. Our team ensures rapid scaling by providing comprehensive training and support, empowering your business to achieve its goals effectively and efficiently.
Solution Design
InRiver acts as the master for product content and rich attributes, while CGS Blue Cherry typically handles financial and inventory data. Our design prioritises this split to ensure that teams have control over product storytelling in InRiver without impacting the rigid ERP structures required for fulfilment. We often sequence product attribute enrichment first to establish a stable SKU baseline before connecting downstream sales channels. A key trade-off involves sync frequency: pushing updates in batches reduces system load on the ERP but introduces a reporting lag for intra-day changes. This approach ensures finance closes the month based on verified ERP data, while marketing operates off precise, enriched product information from InRiver. It prevents the manual rework that occurs when inconsistent product data reaches the warehouse or customer.
Defining SKU ownership and synchronisation logic
The integration positions InRiver as the authoritative source for product enrichment, while CGS Blue Cherry remains the master for financial and inventory data. New SKU headers are typically synchronised to allow for enrichment before they are pushed to sales channels with full marketing attributes. We establish clear ownership boundaries to prevent source-of-truth ambiguity, ensuring that volatile ERP metrics like wholesale pricing remain controlled by Blue Cherry. To maintain data integrity, we monitor for mapping failures or truncated descriptions, ensuring the ERP's validation rules are met before records are updated.
Orchestrating workflows through the IPaaS layer
Cogent2 uses IPaaS to streamline integration between CGS Blue Cherry and InRiver, enhancing data flow and process automation. Benefits include reduced integration complexity, faster deployment, improved scalability, and seamless connectivity, enabling efficient management of product information and supply chain processes.
Monitoring data integrity and sync exceptions
Standard dashboards often show that a sync has run but fail to highlight data integrity issues inside the payloads. Hidden errors, such as a product attribute mismatch between InRiver and CGS Blue Cherry, can compound over time and cause widespread fulfilment failures. Our approach surfaces these exceptions early, categorising failures by type so that teams can act before a customer is affected. Visibility is not just about uptime; it is about knowing that the enriched attributes being pushed to your store are accurate and complete. We help you move from reactive troubleshooting to proactive monitoring of the product data lifecycle.
Operating models for product lifecycle management
Ecommerce, marketing, and operations teams must own the product data lifecycle to maintain consistency across the business. We hand over a clear operating model that defines where attributes are enriched and how they flow into the ERP for fulfilment. Teams learn to check sync health daily and manage exception alerts from the integration layer to prevent listing errors. We specify who owns each exception type, such as missing SKU identifiers or invalid attribute mappings. Handover documentation is purely operational, written for the people running the business rather than IT. This ensures that the team understands how to read alerts and maintain the single source of truth for product information.
Post-launch governance and data health monitoring
Post-launch, we provide ongoing monitoring to ensure your CGS Blue Cherry and InRiver integration continues to perform as your catalogue grows. Our support model focuses on operational ownership, where we track sync health and escalate data exceptions before they impact sales. When an attribute mapping fails or a SKU record is rejected by the ERP, we provide the visibility needed for your team to resolve it quickly. This is not just technical support; it is active monitoring of the data integrity that underpins your commerce operations. We ensure that any issues are caught and prioritised to maintain a reliable flow of product information.
Common failures
Description truncation and API errors
Operational impact: Integrations often fail when InRiver attempts to push long-form marketing copy into Blue Cherry's character-limited 'Extended Description' fields. This causes silent truncation or API 400 errors, leaving product records incomplete in the ERP. Merchandising teams are then forced to manually audit and shorten descriptions inside Blue Cherry to unblock sales orders.
Prevention: We map InRiver attributes to match the specific character limits of the ERP. By validating description lengths before the sync trigger, we prevent technical failures and ensure marketing content fits within Blue Cherry's database constraints.
Reference data mismatch
Operational impact: Inbound data to Blue Cherry often fails if the 'Season' and 'Division' codes in InRiver do not exactly match the pre-configured validation tables in the ERP. Because Blue Cherry requires these codes to group Sales Orders, any mismatch stalls the product-to-market process and prevents the creation of valid purchase orders or sales activity.
Prevention: We treat Blue Cherry's reference data as the master for these codes. The integration logic must ensure that InRiver attributes align with the ERP's validation tables, preventing records from being rejected due to invalid metadata.
Volatile metric overwrites
Operational impact: Using InRiver to update Blue Cherry 'Available to Promise' (ATP) or wholesale pricing fields creates critical discrepancies. These are ERP-owned metrics governed by complex discount logic and live inventory levels. Overwriting them with static PIM data can cause incorrect pricing on EDI orders and fulfilment errors.
Prevention: We enforce a strict ownership boundary where InRiver never pushes data to Blue Cherry's pricing or ATP fields. This protects the integrity of the ERP's financial and inventory logic while allowing InRiver to master the rich product attributes.
Frequently asked questions
What is the source of truth for SKUs in a CGS Blue Cherry and InRiver setup?
InRiver is the master for product enrichment, but CGS Blue Cherry becomes the system of record for the core Item record and its SKU once created. To prevent orphaned inventory and sales order data, a robust integration locks the SKU field in InRiver after its initial push to Blue Cherry. Any subsequent changes to a SKU must follow a strict process managed within the ERP to maintain data integrity across the order-to-cash cycle.
If we delete a product in InRiver, does it automatically get removed from CGS Blue Cherry?
Typically, no, as this would create serious integrity issues for historical sales and inventory records in CGS Blue Cherry. Instead of deletion, the integration should update the corresponding item record in Blue Cherry to make it inactive. This preserves the historical data needed for financial reporting while ensuring the item is no longer available to be sold.
What happens if our product attributes in InRiver don't match the fields in Blue Cherry?
This is a common failure point that causes data synchronisation to fail, leaving product data incomplete in CGS Blue Cherry. For example, mapping a multi-select ‘Finishes’ attribute from an InRiver CVL (Controlled Vocabulary List) to a standard single-value field in Blue Cherry will cause the integration to reject the data. This requires careful data mapping to ensure all enriched product information from InRiver is accurately reflected on the Blue Cherry item record.
Can all product-related data be managed in InRiver and pushed to CGS Blue Cherry?
While InRiver acts as the master for marketing and enrichment data, some key operational data must be managed or added for CGS Blue Cherry. For instance, creating an item record in Blue Cherry often requires specific 'Division' or 'Warehouse' codes that do not originate in InRiver. A successful integration must be designed to either map existing InRiver fields or add this ERP-specific context during the data transfer process.