The Two-Direction Problem: Why B2B Commerce Integrations Fail

Most ERP-to-ecommerce integrations are designed for a simple, one-directional flow: products and prices go from the ERP to the website, orders come back. For B2C retail, this is usually enough. You publish your catalogue, customers buy at the listed price, and orders flow into the back office.

B2B is different. The data flow isn’t just bidirectional — it’s conditionally bidirectional. What a customer sees, what they pay, and how their order is processed all depend on who they are and what commercial relationship they have with your business.

Where one-direction breaks down

In a B2B context, pricing isn’t universal. Customer A might pay $10 for an item while Customer B pays $8.50 for the same item. Customer C might get a further discount at volume — buy 100 and the price drops to $7.

This pricing lives in the ERP. It’s maintained by your sales team, negotiated with each customer, and updated as relationships evolve. For the ecommerce channel to work for B2B, this pricing needs to flow from the ERP to the storefront, per customer, in real time.

But it goes further than pricing. Product visibility might differ between customers. Order approval workflows might apply. Credit limits might restrict purchasing. Payment terms might vary. All of this is managed in the ERP, and all of it needs to be reflected on the ecommerce platform.

Why generic connectors struggle

Most Shopify-ERP connectors were built for B2C. They handle the basic flow: product catalogue out, orders back. When you try to extend them for B2B, you hit limitations quickly.

Customer-specific pricing requires mapping individual customers in the ERP to authenticated users on the storefront, then serving the right price list to the right person. Generic connectors either can’t do this at all, or require complex workarounds that are fragile and hard to maintain.

The native Acumatica connector for Shopify is a good example. It has the B2B features on paper — but configuring them requires significant Acumatica-side work: entity mappings, sync templates, and ERP expertise. Most businesses find it harder and slower to deploy than expected, and when something breaks there’s no single team owning both sides of the integration.

What a proper B2B integration looks like

A B2B integration that works needs to handle:

• Customer authentication and account mapping between the ERP and Shopify
• Customer-specific pricing flowing from ERP price classes to Shopify Plus price lists
• Volume-based pricing tiers that update when ERP pricing changes
• Product visibility rules that determine what each customer can see and buy
• Orders flowing back to the correct debtor account with the correct pricing applied
• All of this updating in near-real-time as the ERP data changes

This is what InSyncer was built to handle. Not as a bolt-on to a B2C connector, but as a core capability designed from the ground up for how MYOB manages B2B relationships.

The takeaway

If you’re evaluating ERP-to-Shopify integration for B2B, the key question isn’t “can it sync products and orders?” — every connector does that. The question is: “can it sync the commercial relationship between my business and each individual customer?” That’s the two-direction problem, and it’s where most integrations fail.