Fulfil and InRiver
Integration Agency & Consultants
Operational drift begins when new products are enriched in InRiver but are not ready for fulfilment in Fulfil. This bottleneck is most visible during a new collection launch, where manual data entry results in catalogue errors and delayed pre-orders. We align these systems to ensure that rich product content and operational item records stay in step. This prevents stock drift and allows your team to manage high-volume product launches without increasing headcount for data entry or manual reconciliations.
Diagnosing gaps between ERP and PIM
We connect your Fulfil and InRiver integration swiftly, ensuring your ERP and PIM systems work together efficiently. Our consulting services are invaluable, offering a comprehensive system audit that uncovers inefficiencies and integration gaps between Fulfil, InRiver, ERP, and PIM platforms. This enables our consultants and your team to take decisive action, optimising your technology ecosystem for smooth operations. With our expertise, you can deliver an outstanding customer experience and keep your business running efficiently as you grow.
Solution Design
We architect the Fulfil and InRiver connection by establishing Fulfil as the system of record for inventory and order operations, while InRiver acts as the definitive host for enriched product content. A primary design decision involves the movement of stock levels from Fulfil to ensure catalogue data reflects actual availability. We typically favour a scheduled approach for complex attribute enrichment to maintain data integrity, acknowledging the trade-off that high-frequency syncs for complex product updates can increase system load. This design ensures finance can rely on Fulfil for reconciliation of orders and inventory, while ecommerce teams work from a consistent, enriched product master in InRiver. The result is an operating model where product richness and operational accuracy are harmonised across all channels.
Mapping item entities and inventory syncs
InRiver acts as the product master for enriched attributes, while Fulfil serves as the system of record for inventory and order operations. The integration maps InRiver entities to Fulfil items, ensuring SKU-level data remains consistent. Stock levels flow from Fulfil to keep product availability accurate. We prioritise unique ID mapping to prevent duplicate records and monitor for sync exceptions that could cause listing errors. This ensures that when a product is enriched in InRiver, the operational data in Fulfil is ready to support the sale without manual re-entry.
Orchestrating workflows through middleware layers
Cogent2 uses IPaaS to streamline integration between Fulfil 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 order fulfillment across platforms.
Surfacing validation errors and data drift
Dashboards often hide the quiet failures that erode customer trust. A successful product update in InRiver might report as sent but fail to map correctly in Fulfil due to a validation error. Our approach surfaces these operational exceptions before they manifest as customer complaints. We monitor for data drift where content in the PIM no longer matches the operational record in the ERP. Visibility means knowing exactly which records failed to sync and why they failed. This level of intelligence prevents hidden inconsistencies from compounding into a larger reconciliation crisis.
Operational documentation for cross-functional teams
Handover focuses on the teams running the business: ecommerce, operations, and finance. We provide operational documentation that defines exactly where each data object lives and who owns specific exceptions. Ecommerce teams learn to manage product enrichment in InRiver and verify its flow to Fulfil, while operations teams are trained to monitor inventory syncs. We define what needs to be checked on a daily, weekly, and monthly basis to maintain data truth. Training includes reading alerts from the integration layer to ensure the team can act before a sync failure impacts customer experience. This ensures the operating model is sustained by the people using the systems every day.
Maintaining integrity between enrichment and availability
Our support model focuses on the connection between InRiver enrichment and Fulfil availability. We monitor for sync failures, such as when a product update in InRiver does not reach Fulfil, potentially leading to incorrect listings. We manage the investigation of these exceptions to prevent operational issues in the warehouse. Issues are prioritised based on their impact on data integrity or order flow, ensuring the link between your product master and your inventory remains trustworthy as your catalogue scales.
Common failures
SKU identifier drift.
Operational impact: When the SKU, the primary identifier linking InRiver and Fulfil, is editable in both systems, it frequently leads to divergence. A manual SKU edit in Fulfil, perhaps to correct an error, breaks the link to the InRiver master record. This results in failed inventory updates from Fulfil because the original SKU no longer exists, and can lead to overselling or unsellable stock accumulating against an orphaned SKU.
Prevention / Action: Establish InRiver as the locked-down source of truth for the SKU identifier upon its creation. The integration should be configured to prevent edits to the SKU field in Fulfil once an Item record is created from an InRiver source. Any change must follow a formal end-of-life process in InRiver, which triggers the creation of a new SKU and the deactivation of the old one across all connected systems.
Inventory latency and overselling.
Operational impact: Fulfil is the master system for stock levels, but if updates to InRiver are slow or batched infrequently, the PIM will syndicate stale availability data. At scale, this lag directly causes overselling. This creates a high volume of exception handling for customer service and operations teams, who must manage order cancellations, refunds, and customer complaints.
Prevention / Action: Instead of relying on periodic full-catalogue batch jobs, the integration should push inventory adjustments from Fulfil to InRiver based on events or on a frequent, scheduled basis. The design must include robust queue handling and retry logic specifically for stock messages. A dedicated monitoring dashboard should be implemented to track the age and success rate of these updates, alerting operators to backlogs before they cause overselling.
Discontinued products are not deactivated.
Operational impact: When a product is set to 'end of life' in InRiver, the corresponding Item record in Fulfil often remains active. This allows operations teams to continue purchasing or receiving stock against a discontinued SKU, leading to unusable inventory and financial write-downs. It also clutters Fulfil's master product data, complicating reporting for merchandising and finance teams.
Prevention / Action: The integration must be designed to propagate lifecycle status changes from InRiver to Fulfil. When the merchandising team archives a product in InRiver, this should trigger an automated workflow that sets the corresponding SKU in Fulfil to an 'inactive' or 'non-orderable' status. This prevents new purchase orders but preserves the record for historical sales analysis.
Frequently asked questions
How is the 'source of truth' for product data managed between Fulfil and InRiver?
In this operating model, InRiver acts as the master for all product marketing and specification data, including descriptions, images, and attributes. This enriched content is then synchronised to Fulfil, which remains the system of record for live operational data like inventory levels and sales orders. This ensures product listings are consistent and based on rich data from InRiver, while inventory counts in Fulfil remain accurate.
How do inventory updates work? Does stock level data flow both ways?
No, inventory data flow is one-way from Fulfil to InRiver in this model. Fulfil is the master for all stock levels because it processes the actual sales orders, returns, and purchase orders. It then pushes these inventory updates to InRiver to ensure the product catalogue accurately reflects what is available to sell, which prevents overselling.
What happens when we create a new product? Where do we create the SKU?
The correct process starts with creating the new product and its rich content within InRiver. Once this is complete, the data is pushed to Fulfil to generate the corresponding Item Record and SKU. Creating SKUs directly in Fulfil first often causes data mismatches and orphan records, because InRiver will not have any product information to link back to.
My product data is inconsistent across channels. How does this integration fix that?
This integration centralises all product enrichment within InRiver, establishing it as the single source for marketing descriptions, specifications, and digital assets. By automatically synchronising this master data with Fulfil, you remove the risk of manual data entry errors in your core operational system. This ensures the data used for sales orders and inventory management in Fulfil always matches the approved content from InRiver.