Centra and InRiver
Integration Agency & Consultants
Catalogue truth often breaks down when product data is scattered across spreadsheets and manual Centra updates. As merchants scale into multiple markets, the pressure to maintain consistent attribute sets and localised descriptions increases. We integrate InRiver with Centra to ensure enriched product information flows directly from the PIM to the storefront, reducing the manual effort required to keep product stories accurate across global channels.
Mapping your multi channel architectural requirements
With a Centra and InRiver Integration, we swiftly connect you to these systems, enhancing your Multi-channel, Omnichannel, and Unified retail strategy. Utilize Cogent’s expertise to scale rapidly, boosting operational efficiency, tech stack performance, and training.
Solution Design
Design decisions for Centra and InRiver focus on maintaining catalogue integrity. In most implementations, InRiver acts as the master for enriched product data and multi-language attributes, while Centra manages pricing and channel-specific availability. A common trade-off involves asset synchronisation: pushing high-resolution media in real-time can lead to sync lag during peak trade. We typically recommend batching heavy media updates while keeping attribute changes and SKU additions on a more frequent schedule. This approach ensures merchandising teams can rely on catalogue truth without creating system instability. This design allows the ecommerce team to focus on Centra for commercial execution while product teams own the enrichment process within InRiver.
Synchronising enriched data with commercial logic
InRiver acts as the master for product entities, variants, and resource links, feeding enriched data into Centra. This flow ensures that descriptions, specifications, and media are consistent across every channel. We implement logic to map InRiver hierarchies into Centra's catalogue structure, ensuring locale-specific strings route correctly. Monitoring is embedded to detect when a data refresh fails or when links between entities are broken in the PIM. By prioritising data integrity at the source, we prevent broken product pages and ensure only fully enriched items are published. This avoids the need for manual data correction within the ecommerce platform.
Orchestrating complex data flows through IPaaS
Cogent2 uses IPaaS to streamline Centra and InRiver integrations, enhancing data flow and connectivity. Benefits include reduced integration complexity, faster deployment, scalability, and improved collaboration, enabling efficient management of diverse applications and data sources for clients.
Surfacing hidden data and synchronisation gaps
Standard dashboards often show that a sync happened, but they rarely show if the data is actually correct. Our approach surfaces hidden issues, such as missing attributes that prevent a product from being searchable in Centra or broken image links. We monitor for synchronisation gaps where a product is marked as complete in the PIM but remains partially enriched on the storefront. By detecting these failures early, we prevent the compounding errors that occur when merchandising teams begin trading against inaccurate or incomplete product data.
Operational handover for merchandising and PIM teams
Adoption focuses on the product and ecommerce teams who manage the journey from enrichment to storefront. We hand over an operating model detailing where product attributes live and how data maps to the storefront. Teams learn to check synchronisation health and identify specific exception types, such as failed resource links or incomplete variant mappings. We define clear ownership for data exceptions so the merchandising team can resolve gaps before they impact the live catalogue. Documentation is delivered as a practical operational guide for those running the business, not a technical archive. It is anchored in your specific attribute structure and enrichment workflow.
Maintaining catalogue truth post go live
Post-launch, we monitor the health of your product data flows to maintain catalogue truth. We detect and triage issues based on their impact on storefront accuracy and trading performance. While we manage the technical oversight of the integration layer, we provide your internal teams with the visibility to manage data-related exceptions. This includes monitoring of sync health to ensure that failed data refreshes are handled before they reach the customer. Support focuses on operational continuity, keeping the connection between InRiver and Centra stable during peak trading. Issue resolution follows a defined path to protect your merchandising timelines.
Common failures
Incomplete product data propagation
Operational impact: When a product data push from InRiver is partial or fails, SKUs can appear in Centra missing critical information like descriptions, attributes, or pricing. This leads to a poor customer experience, lost sales, and an increase in service desk queries. It forces the merchandising team to perform manual data entry in Centra, defeating the purpose of InRiver as the master data source.
Prevention / Action: The integration must be designed to handle product updates transactionally, ensuring that all data for a given SKU is committed to Centra or none at all. Implement robust monitoring and a queue for failed updates to be investigated and re-processed. Scheduling periodic, full catalogue reconciliations provides a safety net to catch and correct any data drift not caught by event-based syncs.
Mishandling of unpublished or deleted products
Operational impact: If a product is archived or a link to a channel is removed in InRiver, the integration may not send an explicit 'delete' or 'deactivate' command to Centra. This results in orphan SKUs cluttering the Centra catalogue, confusing merchandising teams and potentially skewing inventory reports. In a worst-case scenario, a discontinued product remains orderable, leading to CX issues and manual order cancellations.
Prevention / Action: Ensure the integration logic explicitly maps 'unpublish' or 'delete' events in InRiver to the corresponding action in Centra, such as setting a product to 'inactive'. This requires a clear definition of the product lifecycle across both systems. The process should be monitored, and regular data audits should be performed to identify and remove any orphan SKUs in Centra that no longer exist in the InRiver channel.
Direct synchronisation of high-resolution assets
Operational impact: Pushing large image files and other media assets directly from InRiver to Centra as part of a product data update creates significant performance issues. It can slow down the entire sync process, hit API rate limits, and cause timeouts which leave products without images on the live site. This puts avoidable strain on both platforms and delays the propagation of more critical data like pricing or stock levels.
Prevention / Action: Decouple asset handling from the main product data synchronisation process. InRiver should manage the product master data, but the asset files themselves should be hosted on a dedicated Content Delivery Network (CDN). The integration should then only sync the asset URLs from InRiver to Centra, not the binary files, ensuring data syncs are fast and the storefront loads images efficiently.
Frequently asked questions
Where should we manage core product data, in InRiver or in Centra?
InRiver should be the single source of truth for all descriptive product data, including SKUs, attributes, and marketing copy. Product records are enriched in InRiver and then synchronised to Centra. Editing product information directly in Centra is a common failure, as those changes are typically overwritten during the next data push from InRiver, creating catalogue inconsistencies.
If we delete a product in InRiver, will it be removed from our Centra store automatically?
Not necessarily, as this is a common failure point. Simply deleting or unlinking a product entity in InRiver does not guarantee its removal from the live Centra catalogue. The integration must be explicitly built to listen for these events and then trigger the archival or deletion of the corresponding Item record in Centra to prevent outdated products from remaining visible.
Will our complex product attributes from InRiver map correctly to Centra?
This requires careful configuration, especially for complex fields. For example, mapping a multi-select Controlled Vocabulary List (CVL) from InRiver to a Centra product metafield often fails if the integration does not correctly handle the data format. This can result in products failing to appear in the correct website collections, directly impacting filtering and findability for customers.
Why use InRiver for enrichment if Centra already has product fields?
While Centra holds the necessary data for transaction, InRiver is a specialised PIM built to manage rich, multi-channel product narratives at scale. This operating model ensures that your master product catalogue, including all specifications and digital assets, remains consistent. This becomes critical when you use Centra to serve different markets or storefronts that require distinct product information from a single, trusted source.