Shopify ERP Integration: When Official Connectors Are Enough

The connector went live on a Tuesday. Products synced, stock showed up per warehouse, and the first web order landed in the ERP without anyone retyping it. Then the first wholesale account logged in, added 60 units of a part they buy at a break price above 50, and saw the price they pay for one.

Nothing was broken. The official connector did exactly what its documentation says. That is the trouble with treating a vendor connector as a finished Shopify ERP integration: the documentation says where it stops, and almost nobody reads that part before go-live. Below is that part, for the two official connectors B2B operators ask us about most, plus a self-test you can run in an afternoon.

Quick answer: An official ERP connector is enough for Shopify ERP integration when you sell from a list: one price per item or customer group, stock counted per warehouse, and orders that do not change after entry. It stops being enough when B2B decisions happen at the moment of the order. Microsoft's Business Central connector exports prices calculated for a quantity of 1, and its documentation describes no credit check on orders. Infor's M3 connector is documented as a business-to-consumer integration that maps every Shopify account to one M3 customer. Contract pricing, credit limits that stop an order, availability net of other channels, or orders that change after entry all call for an integration built for B2B.

What is an official Shopify ERP connector?

An official ERP connector is an integration the ERP vendor itself builds, publishes, and maintains, usually listed on the Shopify App Store. It syncs a defined set of records between Shopify and the ERP, such as products, stock, customers, and orders. Its scope is fixed by the vendor and documented, which makes its limits checkable before you commit.

Shopify encourages this route. Its help center says Shopify has "partnered with a number of the leading ERP providers to create direct integrations," and Microsoft Dynamics 365 Business Central is on that list. The same page carries a warning worth taking seriously: some App Store integrations "aren't fully compatible with Shopify B2B, specifically companies and catalogs." In other words, a connector that works perfectly for a consumer store can still map company, pricing, and customer data badly for a wholesale one.

Start with the official connector anyway. It is free or close to it, its vendor keeps it current, and for plenty of operators it is the right answer. The work is knowing which side of the line you are on.

The Business Central Shopify connector, in Microsoft's own documentation

Microsoft's connector covers more than most people expect. Per Microsoft's overview, it syncs products both ways, sends inventory to multiple Shopify locations, syncs customers and B2B companies in both directions, imports orders from the online store, POS, and B2B channels with payment terms and PO numbers, and exports posted sales invoices so buyers can see them. Microsoft's Dynamics 365 Business Central app is free to install from the Shopify App Store, and Microsoft's FAQ notes the connector is preinstalled on new environments and requires both a Business Central license and a Shopify license.

Its limits are documented just as plainly. These are the ones that land on B2B operations:

• Online only. The FAQ states the connector "isn't available for on-premises deployments."
• Prices for a quantity of 1. To calculate a price, the connector creates a temporary sales quote at quantity 1, and Microsoft is explicit: "You can't export different prices or discounts based on quantity." Shopify's own B2B feature list includes quantity price breaks, so the gap is in the sync, not the storefront. The price sync page also notes that a price sync run from the job queue completes successfully even when items are skipped, without a warning.
• Credit limits as data, not a decision. Microsoft's customer sync guidance assumes most businesses manage credit limits in Business Central and lists credit limits as an example of data you can store in Shopify metafields. A metafield describes a limit. Nothing in the connector documentation describes it stopping an order.
• Company mapping by rule. Business Central has only a customer entity, while Shopify has customers and companies. Companies map by email and phone, by tax ID, or to a default company.
• Order changes after processing. Per the order sync documentation, if a Shopify order is edited after Business Central processed it, the connector flags it and reports that changes weren't propagated, so someone updates the sales document by hand.

Each is a reasonable design choice for a general connector. Our Business Central integration page carries the full documented list, the API limits, and a ten minute fit check. If you run Finance and Operations, NAV, or GP instead, there is no Microsoft-built connector to start from, which the Microsoft Dynamics integration overview covers product by product.

Infor's official M3 connector: built for business to consumer

Infor's official connector is listed on the Shopify App Store as the Infor eCommerce Connector for M3 CE. It is free, and its listing headline promises "real-time sync of Products, Pricing, Inventory & orders." The same listing describes "Daily Bulk Jobs" for inventory and pricing and states "Only newly created Shopify orders are synced with the ERP."

Infor's own integration guide, version 1.3, published March 2025, is more direct about scope. It calls the connector "a basic integration supporting a Business-to-Consumer (B2C) engagement model." What follows from that, in the guide's own terms:

• Every Shopify account maps to a single M3 customer ID, which Infor calls the Anonymous Customer philosophy.
• Orders are treated as paid in full at entry, so no credit check is required on the order type and ERP invoices for that customer should be suppressed.
• Shopify receives a stock file once a day on a net change basis. Only on-hand stock can be sold, with no future available to promise, and Shopify is unaware of orders placed through other channels.
• Promotions, rebates, charges, taxes, and order-level discounts are unsupported. Styles, variants, configurable items, and kits are excluded.
• Order cancellations are unsupported, and Shopify cannot consume external updates to the order.
• One company, one accounting entity, one currency, and no release planned for M3 13.4 on-premises or single-tenant.

Read against a B2B checklist, the guide never mentions Shopify B2B companies or catalogs at all. For a direct-to-consumer store selling standard stocked items in one currency, it is a sensible free tool. For trade accounts, our Infor M3 integration page covers what M3 exposes through its API Gateway and ION beyond the connector. If you run SX.e, SyteLine, or LN, the Infor integration overview explains why there is no official connector to start from.

Where Shopify ERP integration needs decisions, not copies

Put the two documents side by side and a pattern shows. Both connectors copy values into Shopify: a price calculated once, a stock count, a payment terms code, a credit limit stored as a field. B2B commerce runs on decisions the ERP makes at the moment of the order.

What does this account pay for 60 units today, under the contract that renewed on the first? How many can this branch promise after the counter sale an hour ago? Is this order inside the account's credit? Those answers are calculated, not stored, and an exported copy is correct only until the next contract renewal, counter sale, or open invoice changes it. That is the core idea behind how ERPs resolve contract and matrix pricing, and it is why a daily stock file can never be available to promise rather than on hand.

A connector is not wrong for copying. It was scoped for stores where copying is enough.

The self-test: is your ERP connector enough for B2B?

Answer these against your own operation. Each one maps to documented behavior above, so wherever your answer collides with what the connector does, you have found a known gap, not a guess.

1. Company accounts. Do several buyers order under one account, with separate ship-to locations? The Business Central connector supports companies, mapped by email, phone, or tax ID, so check how clean your customer master is. The M3 connector maps everyone to one customer. 2. Contract pricing. Is any price negotiated per account, tied to a quantity break, or effective on a date? Business Central exports quantity 1 pricing per catalog. M3 sends one price list with no promotions. 3. Credit limits. Must an order stop when an account is over its limit? Neither connector documents a credit check on Shopify orders. 4. Payment terms. Do you invoice on net terms? Business Central maps payment terms. M3 treats every order as prepaid. 5. Multi-location availability. Do buyers need availability per warehouse or branch, net of orders taken by phone, counter, or EDI? Business Central syncs per location from its own stock calculation. M3 sends a daily on-hand file and recommends a dedicated warehouse. 6. Order write-back. Do reps edit, backorder, or cancel orders after entry, and does the buyer need to see that? Business Central flags post-processing edits for manual work. M3 cannot push order updates back to Shopify. 7. Catalog shape. Do you sell variants, configured items, or kits? M3 excludes them. 8. Deployment. Are you on premises, or on single-tenant M3? Neither connector serves that deployment. 9. Failure ownership. Who notices a skipped price or a failed order on a Saturday?

> How to read your score. All answers comfortable: use the official connector and spend the budget elsewhere. One or two gaps: extend the connector at its documented points, which Microsoft supports through public events and codeunits. Three or more, especially pricing, credit, or write-back: you need a Shopify ERP integration built for B2B, not a connector with workarounds.

When the answer is "more than the connector," the next question is which method. Our comparison of the three Shopify B2B ERP integration methods covers that decision, and the guide to what each ERP's API actually exposes shows what you can build against once you step past the connector.

What a Shopify ERP integration built for B2B does differently

The design rule is simple: the ERP decides, Shopify asks. Price, availability, and credit are resolved by the ERP's own logic for the logged-in account, and orders go back through the ERP's business rules rather than around them.

That is how Uncap Connect is built. It is embedded natively inside Shopify, with no separate middleware platform to babysit, and keeps pricing, inventory, customers, and orders in real-time, two-way sync. Customer-specific pricing, credit terms, and tax behave the way B2B actually works, multi-location inventory stays aligned, and audit logs and a retry queue give your team somewhere to see what failed. For a specific ERP and the depth of sync you need, the Uncap team confirms fit directly rather than promising it on a web page.

Uncap has been a Shopify Platinum Partner since 2013, with 380+ storefronts launched on Shopify, including for manufacturers, distributors, and wholesalers. Book a Demo and bring your self-test answers. The questions where your operation and the connector disagree are usually the scope.