Microsoft Dynamics Business Central and InRiver
Integration Agency & Consultants
Catalogue fan-out becomes a liability when rich marketing content in InRiver lives in a silo from core item data in Business Central. At scale, this disconnect often prevents product launches from hitting deadlines because teams are manually verifying mismatched SKU details. We align these systems to ensure enriched marketing records stay in step with the master item record, reducing the manual work required to keep your catalogue accurate across channels.
Mapping the Business Central and InRiver gap
We connect Microsoft Dynamics Business Central and InRiver quickly, ensuring your ERP and PIM work together efficiently. Our consulting services, including our system audit, uncover integration gaps and inefficiencies between Microsoft Dynamics Business Central, InRiver, ERP, and PIM platforms. This enables our consultants and your team to take decisive action, helping your technology ecosystem run smoothly and efficiently. With our expertise, you can deliver a great customer experience by ensuring your ERP and PIM systems, including InRiver, are optimised for your business needs.
Solution Design
Designing the integration between Microsoft Dynamics Business Central and InRiver requires clear ownership of the item master. Typically, Business Central serves as the source of truth for core SKU and inventory data, while InRiver owns the enriched marketing attributes. A key design decision involves how frequently attribute updates flow to sales channels. We often prioritise a batch approach for marketing enrichment to ensure data completeness before publishing, acknowledging the trade-off that real-time updates can lead to incomplete product pages during peak upload periods. This design ensures that finance can trust the item ledger in Business Central while ecommerce teams work confidently within InRiver. The operating model is built on this split, allowing operations to manage stock levels without impacting the rich content managed by marketing.
Synchronising item cards and marketing attributes
Product data accuracy usually depends on a clear boundary between technical ERP fields and marketing enrichment. In a Microsoft Dynamics Business Central and InRiver integration, Business Central typically serves as the source of truth for foundational data including SKUs, base descriptions, and units of measure. InRiver acts as the enrichment layer where teams manage marketing copy, media assets, and channel-specific attributes.
The core process involves synchronising Item Cards and Variants from Business Central into InRiver on a defined schedule or trigger. This ensures that when a new product is created in the ERP, it is immediately available in the PIM for merchandising. Common operational risks include data drift where technical changes in Business Central (such as a SKU update or category shift) fail to reflect in InRiver, leading to incorrect product listings.
Visibility into this sync is vital for merchandising teams to ensure that only fully enriched products are published to downstream channels. Integration monitoring focuses on identifying items that have failed to transition or those missing mandatory ERP data. This approach protects against the risk of incomplete or inaccurate product information reaching the customer, maintaining consistency between the warehouse records and the digital catalogue.
Securing the ERP and PIM handshake
Leveraging IPaaS with SO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Microsoft Dynamics Business Central (ERP) and InRiver (PIM). This approach simplifies connecting Microsoft Dynamics Business Central with InRiver, ensuring ERP and PIM data flows safely. IPaaS platforms reduce manual effort, support scalability, and maintain compliance, making integrations more reliable and secure for businesses handling sensitive information.
Surfacing attribute level data drift early
Standard dashboards frequently miss the subtle data mismatches that occur between InRiver and Business Central. While a sync might technically 'succeed', a missing 'Item Category Code' or a mismatched 'Unit of Measure' can prevent a product from being sold. Without clear visibility into these exceptions, product data drift creates manual work for the merchandising and finance teams.
Visibility requires surfacing these failures at the attribute level. This typically includes monitoring for missing mandatory fields in Business Central, failed price updates, and status drift where a product is marked 'Live' in the PIM but remains 'Blocked' in the ERP. By identifying these gaps early, you prevent downstream errors in your sales channels and ensure that the 'Item' record in Business Central remains a reliable source of truth for operations.
Operational handover for merchandising and finance
Handover focuses on the operational ownership between ecommerce, marketing, and operations teams. Specifically, we define how marketing teams manage enriched product attributes in InRiver while operations maintain the core item master in Microsoft Dynamics Business Central. Training covers the specific operating model for this pair, ensuring teams know where data sits and what to check for sync errors. We outline how to read alerts from the integration layer and identify who owns specific exception types, such as attribute mapping failures or inventory mismatches. Documentation is provided as a practical reference for the people running the business, anchoring teams in the practical daily management of their product data.
Maintaining data flow integrity after launch
Support for Microsoft Dynamics Business Central and InRiver focuses on maintaining the integrity of the data flow between enriched marketing content and foundation item masters. We monitor for specific sync failures, such as attribute mapping errors that prevent product launches. This ongoing operational oversight ensures that technical issues do not stall commercial timelines. Rather than just technical fixes, our support model provides visibility into the integration health, alerting teams when data drift occurs between the ERP and PIM. This approach ensures that your operations remain reliable, with escalation paths defined by the real impact on your product catalogue and sales channels.
Common failures
Source-of-truth ambiguity in core product data When InRiver marketing data overwrites core fields mastered in Business Central, it creates significant operational risk. Incorrect pricing, dimensions, or item categories flow to sales channels, leading to inaccurate Sales Orders and flawed financial reporting. This creates ownership leakage where finance can no longer trust the item master for logistical accuracy.
Prevention: Establish a strict ownership boundary for every attribute. Business Central must master logistical and financial data like SKUs, base price, and tax codes. The integration should permit InRiver to update only marketing-specific fields, with any attempt to write to protected ERP fields triggering an exception rather than failing silently.
Asset synchronisation causing sync problems Syncing high-resolution images or large digital assets through the same queue as core data updates frequently causes timeouts. This often results in product data getting stuck behind a backlog of asset transfers. Campaigns may go live with missing images because the assets failed to publish in time for the launch.
Prevention: Separate digital asset synchronisation from core data updates by using dedicated, queue-based paths. The integration should only push assets that have changed since the last sync. For high-volume catalogues, synchronise the URL string from your DAM or CDN rather than moving the file itself through the ERP middleware.
Workflow fracture during product archival If a SKU is discontinued in Business Central but the archival event does not reach InRiver, 'ghost' products remain active on storefronts. This leads to Sales Orders for items that cannot be fulfilled, causing customer service friction and manual order cancellations.
Prevention: Use status-based triggers rather than simple deletion events. When an Item record in Business Central is marked as 'Discontinued', the integration must trigger a status change in InRiver to un-publish the entity from all downstream channels. This ensures a controlled retirement process that keeps the storefront and the warehouse aligned.
Frequently asked questions
Which system owns the master product data: InRiver or Business Central?
InRiver is the source of truth for rich marketing content like detailed descriptions and attributes, while Microsoft Dynamics Business Central remains the master for core logistical and financial data like the SKU, inventory levels, and pricing. The integration ensures that when a new Item record is created in Business Central, it is enriched in InRiver before being published. This prevents discrepancies between what is sold and what is stocked.
Will connecting InRiver and Business Central create another data silo for our teams to manage?
A correctly designed integration prevents data silos by establishing clear ownership, rather than creating new ones. Business Central acts as the master for the core Item record and inventory data, while InRiver manages the marketing enrichment for that same item. This ensures that updates, like a price change in Business Central or a new product image in InRiver, are synchronised to maintain a single, consistent product catalogue.
Our product launches are slow because data is inconsistent. How does this integration help?
This integration directly targets that problem by creating a clear workflow for product setup and enrichment. A new SKU is created in Microsoft Dynamics Business Central, which triggers a task in InRiver for the marketing team to add rich content and imagery. Once complete, the fully enriched product data is synchronised and ready for publishing, reducing the manual coordination that delays product launches.
What happens if data mapping is wrong between InRiver attributes and Business Central fields?
Incorrect mapping is a common failure, leading to incomplete product data reaching your sales channels. For example, a critical specification field from InRiver might not populate the corresponding attribute on the Business Central Item record. This means when the product data syncs to your e-commerce site, customers see missing details, which can damage trust and reduce sales.
How does the integration handle products that are unpublished or retired in InRiver?
This requires specific configuration, as simply deleting an entity in InRiver does not automatically update Microsoft Dynamics Business Central in a standard setup. The integration must be explicitly built to recognise an 'unpublish' action and use it to deactivate the corresponding Item record in Business Central. Without this, you risk showing discontinued products as available for sale or in your catalogue.