Merret Retail Assist and InRiver
Integration Agency & Consultants
At retail scale, the gap between a marketing team's product description and the ERP's operational record creates real commercial friction. When product details in InRiver drift away from the master records in Merret Retail Assist, the result is usually an increase in returns and customer complaints. This integration ensures that enriched product content flows directly into the core of your retail operations, replacing manual data entry with a controlled synchronisation of master data. Use InRiver to drive the customer experience and Merret Retail Assist to manage the financial and fulfilment reality.
Auditing product data and ERP readiness
Cogent will swiftly connect your Merret Retail Assist and InRiver systems. Our consulting services, including system audits, are crucial for ensuring your ERP and PIM ecosystems operate efficiently. By identifying and addressing inefficiencies, our audits enable your team and consultants to take effective action, ensuring your tech systems run smoothly. This allows you to deliver an excellent customer experience. With Merret Retail Assist and InRiver integration, alongside ERP and PIM optimisation, our services are designed to support your business's operational success.
Solution Design
Our team collaborates closely with you to craft a blueprint for success, ensuring your Merret Retail Assist and InRiver integrations are expertly planned and executed. By designing a tailored ERP and PIM architecture, we put you in control, saving time and energy while laying the foundation for sustainable growth. Our consultants ensure your Merret Retail Assist and InRiver systems work harmoniously, integrating ERP and PIM solutions that support your business's unique needs and future aspirations.
Managing attribute mapping and sync triggers
The integration establishes InRiver as the master for enriched product content while Merret Retail Assist maintains the operational and financial record. Data typically flows on a defined trigger, such as a product reaching a defined readiness state within InRiver. This ensures that only validated attributes and media links move to the ERP. We monitor the mapping at the attribute level to detect missing mandatory details, preventing data inconsistency before it reaches downstream sales channels or warehouse records. By enforcing an explicit ownership boundary, the integration prevents processes where teams might otherwise attempt to edit marketing content directly in the ERP.
Orchestrating workflows with secure IPaaS layers
Cogent2 leverages IPaaS to deliver Merret Retail Assist and InRiver integrations efficiently and securely. IPaaS connects ERP and PIM systems, ensuring smooth data flow. With ISO 27001 and SOC 2 compliance and above, data security is paramount. Merret Retail Assist benefits from streamlined operations, while InRiver integrations enhance product information management. IPaaS offers agility, reliability, and ease of management, making it ideal for businesses seeking secure, scalable solutions for ERP and PIM integration.
Monitoring data flow and validation health
Standard dashboards often miss the silent failures of product data synchronisation, such as a missing attribute that prevents a SKU from appearing on a storefront. We provide visibility into the health of the link between inRiver and Merret Retail Assist, surfacing issues where enrichment does not match ERP validation rules. This allows teams to see why a product may be delayed, such as media transfer issues or mapping errors. By surfacing these exceptions, we help prevent errors that might otherwise require manual correction across multiple systems. You maintain a view of which products are enriched and which require attention.
Operational handover for merchandising and finance
Handover focuses on the Merchandising, Ecommerce and Finance teams. Each team must understand their part in the operating model. Merchandising manages the readiness triggers in inRiver that update Merret, while Finance verifies that synchronised product data aligns with reporting needs. We provide operational documentation that explains where attributes live, how to interpret synchronisation alerts, and who owns each exception type, such as mapping errors or missing media. This documentation is a practical guide for the people running the business. It helps teams manage the daily flow of product data and resolve common issues without needing technical support.
Post-go-live governance and error management
Post-launch, we provide ongoing monitoring of the inRiver and Merret Retail Assist synchronisation to help catch data issues before they impact your storefronts. We take ownership of the integration layer, handling escalations for mapping failures or asset transfer timeouts. Our support model is designed for retail operations, prioritising issues that block product launches or cause stock misalignments. We provide operational oversight intended to help your tech stack stay connected as your product catalogue grows.
Common failures
Incomplete product data synchronisation
Operational impact: A new SKU is created in InRiver, but critical data for Merret, like cost price, commodity code, or supplier details, is missing. This blocks purchase order creation and halts stock replenishment, causing lost sales. The finance team also faces inaccurate cost-of-goods calculations for any affected SKUs.
Prevention / Action: The integration logic must validate the completeness of core Merret-required fields before a product is queued for synchronisation from InRiver. A dedicated exception queue should hold incomplete SKUs for review by the merchandising or data team. This prevents them from creating unusable records in the downstream ERP.
Obsolete products persist in core systems
Operational impact: A product is discontinued and archived in InRiver, but the 'delete' or 'end-of-life' event is not processed correctly by Merret. This leaves 'ghost' records in the ERP, cluttering the active stock file and skewing inventory valuation reports for the finance team. Merchandising teams may also mistakenly include these obsolete SKUs in future purchase planning.
Prevention / Action: The integration must be designed to explicitly handle archive, disabled, or delete statuses from InRiver. This requires more than simple create and update logic, triggering a corresponding archival action in Merret. Monitoring must track the successful completion of these archival tasks, supported by a periodic reconciliation report to identify any discrepancies.
Mismatched attribute data structures
Operational impact: InRiver's product model uses rich, complex attributes like multi-value lists for materials or technical specifications. If Merret's item record expects a simple text field, this data is either lost on import or incorrectly concatenated. This makes the data unusable for ERP-based reporting or filtering, forcing manual data corrections by the operations or merchandising teams.
Prevention / Action: Conduct a detailed data mapping exercise to define how InRiver attributes will be transformed to fit the Merret schema. For complex fields, the integration logic must explicitly flatten, concatenate, or map the data according to rules agreed with the business. A clear process for managing and evolving these transformation rules is essential to prevent data degradation over time.
Frequently asked questions
We manage product descriptions in InRiver. Where should we create the initial SKU?
The core SKU or Item record is typically created in Merret Retail Assist first to anchor financial and stock-keeping data. InRiver then enriches this record with the marketing copy, specifications and imagery required for sales channels. If the PIM creates the SKU first, it can lead to issues where financial attributes are missing or incorrectly mapped in the ERP.
What happens if we delete a product in InRiver?
Integration logic usually prevents the automatic deletion of core Item records in Merret Retail Assist to protect historical sales and inventory data. When enrichment is retracted or a product is deleted in InRiver, the integration is commonly configured to update the status in Merret to 'inactive' or 'archived'.
How does the integration handle multi-select attributes like \"materials\"?
Data synchronisation often fails when InRiver provides a multi-value list to a field in Merret Retail Assist that expects a single value. This is a common failure point that requires careful mapping to ensure the data is compatible with the ERP structure without causing update rejections.
Does this eliminate manual data entry in the ERP?
It significantly reduces it. By establishing InRiver as the source of truth for all customer-facing attributes, you remove the need for teams to manually replicate descriptions or assets in Merret. This helps ensure that what the customer sees on the storefront matches the operational record in the ERP.