BigCommerce and InRiver
Integration Agency & Consultants
Product launch cycles usually slow down when manual data entry and inconsistent attributes across BigCommerce storefronts start causing customer confusion. We connect InRiver to BigCommerce by mapping product models to specific storefront custom fields and variant structures. This maintains catalogue integrity and prevents the broken filters or missing technical specs that often follow a PIM sync, protecting your speed to market as SKU complexity grows.
Auditing your product data architecture
We connect your BigCommerce and InRiver integration swiftly, supporting your ecommerce and PIM ambitions. Our consulting services are invaluable, with our system audit providing a thorough review of your BigCommerce and InRiver set-up. This enables our consultants and your team to identify inefficiencies and take decisive action, ensuring your ecommerce and PIM technology ecosystems run smoothly and efficiently. As a result, you can deliver a consistently excellent experience to your customers and maintain a competitive edge in the market.
Solution Design
The design for BigCommerce and InRiver integration prioritises InRiver as the source of truth for product enrichment and media. A key design decision involves mapping InRiver’s complex entity models to BigCommerce’s custom field and variant structures. We typically recommend a defined sync trigger for product data rather than real-time updates for every minor edit. This creates a trade-off: while it introduces a slight lag to storefront updates, it ensures only validated, enriched data reaches the customer, preventing broken filters or missing attributes. Finance and ops teams work from InRiver for product specifications, while the ecommerce team manages the storefront. This structure ensures that PIM flexibility does not undermine BigCommerce’s SEO metadata or SKU-level requirements.
Synchronising validated entities and hierarchies
InRiver acts as the single source of truth for product enrichment and media. The integration typically uses a defined sync trigger to push validated product entities and categories to BigCommerce. We maintain data integrity by mapping InRiver hierarchies into BigCommerce variant structures and custom fields, ensuring complex models do not break storefront filters. We sequence the sync so physical SKU attributes move alongside storefront SEO metadata. Monitoring is embedded at the attribute level to detect missing required values before they reach the storefront. This prevents the BigCommerce control panel from becoming cluttered and removes the need for manual data fixes after a publish event.
Orchestrating workflows via secure middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between BigCommerce and InRiver for Ecommerce and PIM needs. IPaaS simplifies connecting BigCommerce with InRiver, automating Ecommerce workflows and PIM data exchange. Benefits include centralised management, reduced manual effort, and robust data protection, ensuring integrations are reliable and compliant with the highest security standards.
Surfacing sync exceptions and attribute failures
Clear visibility and reporting are vital when integrating BigCommerce with InRiver, as they ensure accurate Ecommerce data flow between your PIM and Ecommerce platforms. This transparency allows you to quickly identify and resolve issues, maintain data integrity, and optimise performance. Cogent2 delivers this by providing real-time dashboards, automated alerts, and detailed reporting, giving you full oversight of your BigCommerce and InRiver PIM integration for reliable, efficient Ecommerce operations.
Transferring ownership to your merchandising team
Product, ecommerce, and merchandising teams must own the transition from flexible product modelling in InRiver to structured storefront data in BigCommerce. We hand over a clear operating model that defines where product data, media, and CVL keys live. Your team learns what to check on a regular schedule, such as verifying attribute consistency and responding to sync alerts if a validation rule blocks a launch. We provide operational documentation written for the people running the business, not technical manuals for IT. This ensures that your team can manage attribute sets and category filters without needing external support for daily catalogue updates. Training is anchored in your specific configuration to ensure internal ownership of the product data cycle.
Maintaining catalogue integrity and launch stability
Post-launch support focuses on operational stability rather than just technical uptime. We monitor the integration for sync exceptions, specifically targeting attribute validation failures and broken media links that often stall a product launch. When an issue occurs, we identify whether it is a modelling error in InRiver or a structural constraint in BigCommerce and escalate it to the correct owner. As you add new product categories or variant sets, we provide visibility into integration health so your merchandising team can focus on catalogue enrichment while we manage data integrity. Escalation paths are defined to ensure any blockage in the product pipeline is identified before it impacts store availability.
Common failures
Attribute and variant data loss
Operational impact: This arises when mapping rich InRiver product models to BigCommerce's options and custom fields. Merchandising teams discover that key filtering attributes are missing from storefront category pages, damaging the user journey and losing sales. It also increases the support workload as the customer service team fields enquiries for products that are difficult to find.
Prevention / Action: The integration's design phase must include a rigorous data mapping exercise between the InRiver entity model and BigCommerce's objects, including Product Options, Option Sets, and Custom Fields. Define a clear strategy for handling complex specifications or multi-value lists (CVLs), which may require serialising data into text fields. This mapping requires formal sign-off from operational and merchandising teams before development begins.
Stale catalogue data
Operational impact: When a product's enrichment is retracted in InRiver, or it is removed from a channel, the integration often fails to update BigCommerce. This leaves discontinued or unready products visible and available for purchase on the storefront, creating poor customer experiences and order exceptions for the fulfilment team. This failure undermines merchandising's control of the live catalogue and erodes trust in the PIM as the source of truth.
Prevention / Action: Integration logic must be designed to explicitly handle 'unpublish' or 'delete' events, not just creation and updates. This requires defining a clear trigger in InRiver, such as a specific completeness status or being unlinked from the designated BigCommerce channel. The sync process must include a step to query for entities that need to be removed or hidden and then execute the corresponding API calls in BigCommerce.
Inefficient media synchronisation
Operational impact: Pushing high-resolution images from InRiver to BigCommerce on every product update consumes significant API quota and can cause rate-limiting errors. This leads to slow, unreliable synchronisation cycles that delay time-to-market for new products. For customers, it results in products appearing online with missing images, which directly impacts conversion rates.
Prevention / Action: Decouple media asset updates from standard product data synchronisation. The integration process should first check if an asset already exists in the BigCommerce media gallery before attempting an upload, for example by comparing filenames. Design the media sync to run on a separate schedule using a queue with built-in retry logic to manage transient API errors gracefully.
Frequently asked questions
How do you handle complex product attributes from InRiver within BigCommerce?
We map InRiver models to specific BigCommerce data objects, typically using BigCommerce custom fields for filterable storefront attributes and metafields for technical specifications. This ensures that when enrichment is updated in InRiver, all attributes land in the correct storefront location. This approach prevents data loss or incorrect formatting when pushing InRiver data into a flat storefront structure.
If we retract a product in InRiver, will it automatically be removed from BigCommerce?
Deleting a link in InRiver does not always trigger an automatic deletion in BigCommerce. In many implementations, we use a specific status in InRiver to manage visibility. When a product is retracted, the integration instructs BigCommerce to hide the SKU or update its availability. This prevents 404 errors and ensures customers only see validated, available stock.
Our product launches are slow due to manual data entry. How does this integration fix that?
The integration establishes InRiver as the source of truth for all enrichment and media. Your teams work in InRiver to validate attributes before they hit the storefront. Once a defined trigger is met, the integration creates the product record and variants in BigCommerce. This removes the need for manual cleanup in the BigCommerce control panel and eliminates the gap between the PIM and the channel.
Can we edit SKUs in both InRiver and BigCommerce?
We advise against editing SKUs in both systems, as this creates source-of-truth ambiguity. The SKU should remain unchanged once it is created in InRiver and synced. Changing a SKU in BigCommerce without updating the PIM risks creating records that no longer receive attribute updates, leading to data drift between the storefront and the PIM.
What happens if our InRiver model uses multi-select attributes?
Pushing an InRiver multi-select list into a standard BigCommerce field can cause data loss. Combined with BigCommerce's specific field requirements, we map these values into compatible metafields or delimited custom fields. This ensures all selected attributes are correctly displayed on the product detail page, preserving data integrity.