SAP B1 and InRiver
Integration Agency & Consultants
Cogent2 uses AI-powered integration delivery and experienced operators to properly connect InRiver and SAP B1. We see that when a PIM and ERP disagree on product data, it creates costly financial reporting errors and sales friction. A clean, reliable connection ensures teams are working from a single source of commercial truth.
Diagnosing gaps in ERP and PIM workflows
Cogent2 connects your SAP B1 and InRiver systems efficiently, ensuring your ERP and PIM work in harmony. Our consulting services, including comprehensive system audits, identify inefficiencies and integration gaps, enabling your team to take decisive action. By optimising your tech ecosystem, we help your SAP B1 and InRiver platforms operate smoothly, ensuring your ERP and PIM deliver exceptional customer experiences. Our audits provide actionable insights, allowing your business to run efficiently and effectively, ultimately enhancing customer satisfaction and operational performance.
Solution Design
Design decisions for SAP B1 and InRiver focus on maintaining a clean separation between the marketing experience and the financial record. InRiver is the master for enriched product attributes, while SAP B1 remains the authoritative source for inventory and cost valuation. We typically sequence the flow to ensure ERP records are enriched before they impact sales or accounting. A primary trade-off in this pair is the choice of batch synchronisation for product catalogues versus targeted triggers for price and stock. Batch sync protects SAP B1 from excessive load and remains easier to reconcile, though it introduces a reporting lag compared to real-time events. This design ensures the finance team closes the month using validated ERP data while the ecommerce team operates with high-fidelity product content. Remaining manual checks are defined for the launch phase to manage edge cases safely.
Mapping product hierarchies to the item master
The integration functions by translating enriched attributes in InRiver into the fields required by the SAP B1 environment. Control lists and product hierarchies in the PIM are mapped to the Item Master where necessary. Data integrity is maintained through validation rules that prevent incomplete product data from reaching the ERP. We include issue detection by monitoring the flow of SKU updates; if a required attribute is missing in InRiver, the sync is flagged before it can affect the SAP B1 database. This ensures that the system of record for inventory and financials remains accurate.
iPaaS
The integration functions by translating enriched attributes in InRiver into the fields required by the SAP B1 environment. Control lists and product hierarchies in the PIM are mapped to the Item Master where necessary. Data integrity is maintained through validation rules that prevent incomplete product data from reaching the ERP. We include issue detection by monitoring the flow of SKU updates; if a required attribute is missing in InRiver, the sync is flagged before it can affect the SAP B1 database. This ensures that the system of record for inventory and financials remains accurate.
Detecting data drift before financial reporting
Standard dashboards often show that a sync has occurred, but they rarely show if the data inside is correct. Our approach surfaces hidden issues, such as mapping mismatches where a product in InRiver does not align with the structure in SAP B1. We monitor for instances where updates are accepted but fail to update the record correctly due to system constraints. By surfacing these issues early, we help prevent data drift that might otherwise only be discovered during manual stock-takes or financial reporting. The goal is to provide finance and ops with a clear view of the synchronisation status.
Training teams to manage data lifecycles
Handover ensures finance, ecommerce, and operations teams own their respective segments of the data lifecycle. We move beyond technical manuals to provide an operational reference that explains how the InRiver and SAP B1 connection actually runs. Your teams learn to verify that enriched product data in InRiver correctly maps to the financial and inventory structures in SAP B1. Training covers daily monitoring of the integration layer and identifying which team owns specific exceptions like mapping errors or valuation mismatches. Documentation is provided as an operational reference for the people running the business, rather than a technical archive for IT.
Resolving sync exceptions and attribute failures
After launch, we provide ongoing monitoring of your product data flow. Instead of basic technical support, we focus on identifying and resolving the root causes of sync exceptions before they create downstream gaps. Our monitoring helps detect issues like broken resource links or failed updates, ensuring that an issue in InRiver does not lead to a failure in SAP B1 reporting. We provide clear escalation paths and reviews to ensure the integration continues to match your business processes as you scale or add new product categories.
Common failures
Inconsistent product attribute mapping
Operational impact: If attributes like 'Costing Method', 'Tax Code', or 'Unit of Measure' are not perfectly mapped from InRiver to SAP B1 Item Master Data, it causes significant downstream errors. The finance team will see incorrect gross margin calculations on sales orders and inaccurate inventory valuation in the general ledger. This forces manual journal entry adjustments during month-end close and undermines trust in core financial reports.
Prevention / Action: Establish a strict data governance model where SAP B1 owns all core financial and logistical attributes and InRiver owns marketing enrichment. The integration logic should prevent enriched data from InRiver from overwriting protected financial fields in the SAP B1 Item Master Record (OITM). Prioritise a 'read-only' pattern for these critical fields and use exception reporting to flag any attempted mismatches during data synchronisation.
Deferred or incorrect inventory valuation
Operational impact: When a new product's cost price is not defined in SAP B1 before the first Goods Receipt PO is created, the system may post the stock with a zero or estimated value. This leads to incorrect cost of goods sold (COGS) postings when sales orders are fulfilled. The finance team then has to perform complex, manual inventory revaluation journal entries, which are error-prone and complicate margin analysis.
Prevention / Action: The integration process must ensure a product record is fully costed in SAP B1 before it can be included on a purchase order. This involves process sequencing: InRiver pushes the new SKU to SAP B1, where a holding status is applied. The procurement or finance team must then update the Item Master Data with the correct cost price before the item is made available for purchasing, preventing stock from entering the business without a valid cost.
Mismatched units of measure and BOMs
Operational impact: InRiver may catalogue a product as a 'Case' or 'Bundle', while SAP B1 must manage the individual SKUs within it as separate inventory items. If the integration only creates the parent product, sales orders are generated for an item that does not exist in stock. This disrupts the pick and pack process for the fulfilment team and generates incorrect stock deductions, creating downstream reconciliation work.
Prevention / Action: Define SAP B1 as the single source of truth for all Bills of Materials (BOMs) and unit of measure groups. InRiver can hold marketing-friendly descriptions, but the integration must create Sales BOMs in SAP B1 that accurately reflect the component SKUs. The data flow should pull UoM and inventory UoM definitions directly from SAP B1 tables (e.g. OITM, OUOM) to ensure all systems share a consistent definition of how stock is held and sold.
API overload from minor product updates
Operational impact: If every minor change in InRiver, such as a corrected typo in a product description, triggers an immediate API call to SAP B1, it can degrade ERP performance. This can lead to table locking on the Item Master Data (OITM), slowing down critical operations like sales order creation or stock lookups for all users. The cumulative effect is a sluggish system that impedes the finance, sales, and fulfilment teams during peak business hours.
Prevention / Action: Implement a batching and queueing strategy for synchronising data from InRiver to SAP B1. The integration should aggregate minor updates over a defined period, pushing them as a single, consolidated transaction. Critical changes like stock-related attributes can be prioritised for a faster queue, while non-critical marketing text updates are handled in a slower, off-peak schedule to minimise database contention.
Frequently asked questions
Should we create new products in InRiver or SAP B1 first?
We recommend creating the core Item record and SKU in SAP B1 to establish the financial and stock-keeping foundation. InRiver then subscribes to this new SKU, acting as the master for enriching it with marketing-focused attributes and images. This enriched data is then synchronised back to the SAP B1 Item Master Data record, preventing duplicate records and ensuring financial data integrity from the start.
What is the typical role of each system in this integration?
In a common operating model, SAP B1 acts as the system of record for all core financial and inventory data, including the initial creation of the Item record. InRiver serves as the Product Information Management (PIM) system, taking that core SKU and enriching it with detailed marketing copy, specifications, and digital assets. This ensures sales and finance teams are working from a single, accurate product definition tied to a financially-validated Item record in SAP B1.
Why do some product updates from InRiver fail to post to SAP B1?
Failures can occur when an attribute from InRiver has a dependency on a setting within SAP B1 that is not correctly configured. For instance, attempting to sync batch or serial numbers will fail if the corresponding 'Manage Item by' setting is not activated on the Item Master Data record in SAP B1. The integration must be designed to handle these specific validation rules for data to synchronise reliably between InRiver and the ERP.
Our stock levels seem to be wrong in our sales channels. How does this integration address that?
This often happens if the integration logic does not correctly handle SAP B1's warehouse data structure. For example, if you have multiple SAP B1 warehouses (OWHS) that need to be aggregated into one inventory figure for InRiver, a simple integration might fail or pull from the wrong source. A correctly configured integration aggregates inventory from specific SAP B1 warehouses to provide an accurate available-to-promise figure in InRiver for reliable stock synchronisation.
We already update SAP B1 from InRiver manually. What's the main reason to automate?
The decision to automate is typically driven by costly errors in financial reporting or sales operations. For example, a manual mistake in updating a product's dimensions or weight from an InRiver specification sheet into the SAP B1 Item record can lead to incorrect shipping charges and flawed inventory valuation reports. Automation prevents these manual errors by creating a direct, reliable link between the master product data in InRiver and the financial records in SAP B1.