How to select an ERP solution with the easiest B2B webshop
Five ERP systems compared on what it takes to get a B2B webshop running, and why the architecture, not the feature list, decides the budget.
Longer pieces on ecommerce and Business Central: what a migration does to a web shop that already runs, and how the routes out differ.
Five ERP systems compared on what it takes to get a B2B webshop running, and why the architecture, not the feature list, decides the budget.
There is no Microsoft migration tool from Dynamics AX, and none of AIF, the Business Connector or the AX Retail database has a counterpart in Business Central online. Three ways to rebuild the web shop connection.
The cloud migration tool moves the data, not the web shop integration. The three routes out of Dynamics GP, and what each one asks of you.
Business Central online locks the base application, so a web shop integration built into NAV objects has to be rebuilt. Three ways to do it.
Neither system is forced by Danish law, but e-conomic has no inventory, no variants and no customer pricing in its API, so every arrow between shop and accounts points the wrong way once Business Central becomes the ERP.
Fortnox's stock, orders and price lists map closely to Business Central, but variants, webhooks and quantity-break prices are the three things that break, and Fortnox's own web shop connectors move money, not products.
Microsoft's own QuickBooks migration tools move the accounts but explicitly not sales orders, and Shopify can't import archived orders either, so order history has no supported path from either side.
A Sage 100 web store reads over a read-only ODBC driver and writes through 32-bit COM, and neither has a Business Central counterpart, so the integration is rewritten rather than ported, whichever edition you run.
Direct SQL, the Sage 200 .NET SDK and the Sage 200 REST API each stop at the Sage boundary, so the web shop connection is rebuilt against the Business Central API rather than pointed at a new system.
In most Sage 50 Accounts businesses the web shop already depends on a mid-tier system, not on Sage 50 itself, so the ERP migration rarely breaks the storefront and instead forces the question of whether Business Central becomes the system of record.
Sage X3's web services and SQL access all have Business Central equivalents, but its product-site records, stock statuses and multi-legislation folder don't, so the integration ports more easily than the company fits.
An app inside Business Central against a platform beside it. Where the two packages actually differ, and which questions decide between them.
Both push pricing into Business Central, but one is the ERP document and the other asks it live. Where Abakion B2B Ecommerce and Sana Commerce Cloud actually differ, and which questions decide between them.
Both are all-in-one platforms configured per customer, but one keeps no database of its own and the other syncs one. Where Sana Commerce Cloud and Dynamicweb Commerce Suite differ, and which questions decide between them.