Sitoo and InRiver
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Incomplete product data at point of sale
Operational impact: When product enrichment in InRiver is not fully mapped to Sitoo, sales associates lack the information they need at the till. This can lead to incorrect product recommendations, an inability to answer customer questions about specifications or materials, and a frustrating customer experience. Merchandising and finance teams also suffer, as reporting based on incomplete Sitoo product attributes becomes unreliable for planning and analysis.
Prevention / Action: The integration build must begin with a rigorous data mapping workshop that defines exactly which InRiver entity fields correspond to Sitoo's product attributes. A clear source-of-truth ownership model is essential, where merchandising teams must meet a defined 'minimum information standard' in InRiver before any SKU is published to the sales channel. All data flows should be validated in a staging environment to ensure information appears as expected in the Sitoo POS interface before deploying to production.
Delayed price or product information updates
Operational impact: Relying on infrequent batch updates can mean critical changes from InRiver take hours to appear in Sitoo. This exposes the business to risk, such as selling products at an old price after a price increase, impacting profit margins on every transaction. It also means urgent product information corrections, like allergen updates, may not reach the shop floor in time, posing a risk to customers and the brand.
Prevention / Action: Design the integration to consume updates from InRiver on a frequent, scheduled basis or via webhooks if available. This ensures that changes to price, product descriptions, or other key attributes are processed in smaller, near real-time increments rather than large, slow batches. Implement monitoring to measure the latency between a change in InRiver and its successful update in Sitoo, with exception handling for any updates that fail to apply correctly.
Deleted or retired products remain active in Sitoo
Operational impact: If the integration only handles creating and updating products, the Sitoo catalogue will become cluttered with obsolete SKUs. When a product is archived or unpublished in InRiver, it must also be removed from sale in Sitoo. Failure to do so allows sales associates to attempt to sell discontinued stock, leading to fulfilment exceptions, manual order cancellations, and frustrated customers that the customer service team must then manage.
Prevention / Action: The integration logic must explicitly handle the 'unpublish' or 'delete' state within the InRiver data model. When a product's link to the Sitoo channel is removed in InRiver, this should trigger an automated process to deactivate the corresponding product record in Sitoo. A scheduled reconciliation process should also be implemented to compare active SKUs between both systems to identify and clean up any orphaned records that were missed by the event-driven logic.
Frequently asked questions
If we update product marketing copy in InRiver, how quickly does it appear on the Sitoo POS?
Updates to product data in InRiver are designed to be pushed to the corresponding item records in Sitoo on a scheduled or trigger-based cadence. This process directly addresses the delay between enriching product details in the PIM and having that information available to store staff. The goal is to ensure the marketing copy and specifications seen by the sales team on the Sitoo POS are always synchronised with the master version in InRiver.
What happens if we delete or unpublish a product in InRiver? Does it get removed from sale in Sitoo?
This depends on the integration rules, as deleting an entity in InRiver does not automatically trigger the deletion of the corresponding item record in Sitoo by default. A specific rule must be configured to watch for deleted or unpublished products in InRiver and then deactivate them in Sitoo. Without this, you risk having discontinued items remain available for sale on the POS.
How does the integration ensure new products from InRiver are set up correctly in Sitoo?
The integration establishes InRiver as the source of truth for product creation, automating the setup of new items in your POS system. When a new product entity is completed and approved for a specific sales channel in InRiver, the integration creates the corresponding SKU and item record in Sitoo. This process populates all required fields, like price and descriptions, avoiding manual data entry and ensuring data consistency from day one.
Our pricing is managed in InRiver. How do we ensure the price on the Sitoo POS is always correct?
In this operating model, InRiver is the master for all pricing data, including different price lists for various regions or promotions. When a price is updated against an item in InRiver, the integration's job is to update that price on the linked item record within Sitoo. This direct synchronisation removes the risk of store staff selling an item at an old price because of a manual update being missed in the POS.