Ecommerce for Business Central

BigCommerce + eConnect

American SaaS platform with no transaction fee, connected to Business Central by a connector from Dynamics eShop. Business Central is the system of record for items, prices, stock, customers and orders. Company accounts and payment terms require BigCommerce's B2B Edition.

Maker of the ecommerce solution
BigCommerce
Maker of the integration
Dynamics eShop Inc.
Last verified
2026-09-07

What the solution is

BigCommerce is an American SaaS commerce platform often chosen as an alternative to Shopify for two reasons: there is no transaction fee on sales, and the platform's APIs are open enough to build a headless frontend if you want one.

The integration to Business Central here is eConnect from Dynamics eShop, obtained from Microsoft AppSource. The same vendor stands behind a standalone storefront product in this catalogue, and eConnect is their connector line, which also covers Shopify, Magento, Amazon, WooCommerce and eBay.

How the integration works

The vendor describes Business Central as the system of record. Items, prices, stock, customers, orders and fulfilment information are synchronised between the store and the ERP, and updates happen continuously rather than in a nightly run.

It is a connector with a middleware layer, which means there is a place where an order can sit waiting to move on. That is not a weakness in itself, because it makes retry possible, but it makes it important to agree who monitors the queue.

Only Business Central online is documented. Both Essentials and Premium are supported. Note that the same vendor sells several connectors in the same family, which is a strength if you sell in several channels, and a fact to carry if you want to know how much resource sits behind the BigCommerce edition specifically.

Prices, discounts and agreements

Prices are synchronised from Business Central to BigCommerce. The agreed price therefore comes from the ERP, and that is the mechanism this site measures.

It is a transfer model, and the scaling trap applies. Customers times items quickly becomes many rows, and BigCommerce has historically had limits on the number of customer groups and price lists which are worth having confirmed against your own figures before signing the project off.

Campaigns and bundles belong in BigCommerce. The platform has a solid campaign engine, and for a consumer brand that is an advantage. It is at the same time the reason for the label about logic set up in two places. Company accounts, requisition lists and payment terms belong to BigCommerce's B2B Edition, and without it the B2B part is thin.

The order and the finance function

The order is created as a sales order in Business Central along with customer details, payment and shipping. That is more than several connectors in the catalogue cover, and it saves work in the accounts department.

Partial shipments, back orders and credit memos are handled in Business Central. Whether shipment status comes back to the store is worth having confirmed, because that is the piece of information customers phone about.

VAT is decided by BigCommerce on open selling, and an external tax engine is the ordinary solution when selling in several countries. Reconciling the payment provider's settlement is a separate job. In return there is no fee on revenue from the platform itself, and that is a real difference over three years.

Who the solution fits

The solution fits a company with mainly consumer selling and growing revenue, where a transaction fee would become expensive. That is BigCommerce's strongest argument, and it grows stronger the more you sell.

It also fits if you want the option of a headless frontend without leaving a SaaS platform. BigCommerce is built for both routes, and not every SaaS platform is.

The solution fits less well for a pure B2B business. B2B Edition is an add-on, and even with it, quote management and complex agreement logic are not in the same class as the dedicated B2B solutions in the catalogue.

What to settle before you decide

Pricing is not public for the connector, and BigCommerce's own plans are tiered with limits on annual revenue. Our bands are estimates with low confidence. Ask for prices on the platform, on B2B Edition if you need it, and on the connector.

Ask to have the limits on customer groups and price lists confirmed against your own number of customers. That is the one place this solution can prove too small, and it is information the vendor can give in a minute.

Finally, ask for a named European reference customer on BigCommerce and Business Central specifically. Both the platform and the connector are North American, and the combination is less widespread in Europe than in the United States.

All data on this solution

Every field in the schema, as it stands in the catalogue. A dash means we have no figure, which is not the same as a no.

Basics

Ecommerce solutionBigCommerce
Maker of the ecommerce solutionBigCommerce
Integration to Business CentraleConnect for BigCommerce
Maker of the integrationDynamics eShop Inc.
Solution typePlatform plus connector, two vendors
Where the storefront livesSeparate platform
HostingSaaS
Vendor's home countryUS
MarketEurope, USA
Centre of gravityNorth America
How the integration is obtainedMicrosoft AppSource
Supported Business Central deploymentsBusiness Central online
Works against on-premisesNo
Storefront included in the solutionYes
Storefront and integration are the same productNo
Matrix cellFinished integration to a separate storefront
Logic labelThe logic is set up in two places
Other integrations to the same platformBigCommerce Connector (xpr365), Tinx BigCommerce Connector (Tinx-IT), i95Dev Connect, CSM for BigCommerce (Suite Engine)
Primary sourcedynamicseshop.com
Status of this entryDraft
Last verified2026-09-07
Schema version1.3.0-udkast

Maintenance

Keeps up with Business Central's releasesThe vendor
Keeps up with the platform's APIThe vendor
The company's own configurationStandard setup
Derived matrix cellFinished integration to a separate storefront

Customisation

How far the solution can be stretchedFar-reaching
MethodsYour own frontend, headless, Field mapping in the integration, The platform's API
What it does to the commitmentThe customisations are yours and can break at a Business Central release

Sales model

Open storefrontYes
Customer portalPartly
NoteCompany accounts, purchase lists and payment terms require BigCommerce B2B Edition.

Master data

ItemsSynchronised
CustomersSynchronised
InventorySynchronised
Product contentMaintained in the storefront
OrdersSynchronised
PricesSynchronised

Pricing logic and discounts

Customer-specific and agreed pricesThe result is transferred
Tiered volume discountsThe result is transferred
Campaign prices with a validity periodSet up in the storefront
Discount groups and trade agreementsThe result is transferred
Product bundles and kitsSet up in the storefront
Line and invoice discountThe result is transferred
Prices per unit and per currencyThe result is transferred
Customer-specific assortmentThe result is transferred
Credit limit and payment termsNot stated
VAT and tax calculationSet up in the storefront
Stock availability and delivery dateThe result is transferred

Order flow

Document created in Business CentralSales order
Reserves stockNo
Partial shipmentsYes
Back ordersPartly
Cancelled linesPartly
ReturnsYes
Credit memoYes
Reconciling the payment provider's settlementPartly
Fees and freightYes
VAT on the orderPartly
Error handlingQueue with automatic retry
When the customer is chargedAt checkout
Drop shipping via a purchase orderPartly
Stock per locationYes
Consumer customers in Business CentralConfigurable

Integration mechanics

MethodMixed
Polling interval in minutes15
BatchingYes
Spread across several service principalsNo
CachingYes
Retry on a 429 responseYes
Throttling handlingMentioned
API surfaces in Business CentralStandard API v2, External middleware

Product data and PIM

VariantsYes
Max variants per item600
Units of measurePartly
AttributesYes
Multilingual product dataPartly
Digital assetsYes
Structured classificationNo
Product configuratorPartly
PIM built inPartly
Separate PIM requiredRecommended
Variants mapped to Business Central's variant codesYes
Bundles resolved into Business Central linesPartly
Blocked items and replacementsPartly
The customer's own item numbersPartly

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
Max storefronts1
Nature of the limitsUnknown
Sourcebigcommerce.com

Cost

The bands are set in euro and priced against three fixed reference scenarios. They cover licence, implementation and maintenance, and they do not cover your own time.

Pricing modelFixed price
Share of revenue in percent
Implementation modelBoth models offered
Price per additional storefrontExtra licence per storefront
Day-to-day work after go-liveMedium
Not included in the figuresinternal time, BigCommerce B2B Edition, payment fees, an external tax engine, apps in BigCommerce
Small: Licence per yearUnder EUR 5,000
Small: Implementation, one-offEUR 10,000 to 40,000
Small: Maintenance per yearUnder EUR 5,000
Small: Time to go live1 to 3 months
Small: Three-year cost of ownershipEUR 40,000 to 120,000
Small: ConfidenceLow
Small: Sourcebigcommerce.com
Medium: Licence per yearEUR 5,000 to 20,000
Medium: Implementation, one-offEUR 40,000 to 120,000
Medium: Maintenance per yearEUR 5,000 to 20,000
Medium: Time to go live3 to 6 months
Medium: Three-year cost of ownershipEUR 120,000 to 400,000
Medium: ConfidenceLow
Medium: Sourcebigcommerce.com
Large: Licence per yearEUR 20,000 to 60,000
Large: Implementation, one-offEUR 40,000 to 120,000
Large: Maintenance per yearEUR 5,000 to 20,000
Large: Time to go live3 to 6 months
Large: Three-year cost of ownershipEUR 120,000 to 400,000
Large: ConfidenceLow
Large: Sourcebigcommerce.com

Functional requirements

SEO and indexabilityYes, broadly covered
Design and theme controlYes
Content and landing pagesYes
Search and navigationYes
Ordering on the customer's behalfPartly
Several storefronts from one Business CentralYes
Multilingual frontendYes
Openness and extensionsYes, broadly covered
AccessibilityPartly
Agent readabilityYes
PerformanceYes, broadly covered
Bulk editing, import and exportYes
Change log in the backendPartly
An external search engine can be attachedYes
Facets on Business Central fieldsPartly
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersYes
Hosted card fields, PCI scope kept outYes, broadly covered
Strong customer authentication and fraud screeningYes
Consent managementYes
Data protection and processing agreementYes

Open storefront only

Guest checkoutYes, broadly covered
Card paymentYes, broadly covered
Buy now, pay laterYes
Campaigns set up in the storefrontYes, broadly covered
Shipping choice and pickup pointsYes
Gift cardsYes
Subscriptions and recurring ordersPartly
Order status without an accountYes
Product reviewsYes
WishlistsYes
Marketing platformYes
RecommendationsYes
Marketplace channelsYes
Product feedsYes, broadly covered
Right of withdrawal and returns portalYes
Cart abandonment and email flowsYes, broadly covered

Customer portal only

Account hierarchy with buyers and approversPartly
Approval flow with amount limitsPartly
Invoice payment and open entriesPartly
Quotes and requestsPartly
Price list for print and downloadNo
Sales rep viewPartly
Reordering from order historyYes
Several delivery addressesYes

Geography and compliance

Business Central localisationsalle
Several companies per storefrontNo
Several environments per storefrontNo
CurrenciesYes
Languages in the frontendYes
Tax engineExternal tax engine
Named tax enginesAvalara
E-invoicingNo
Data locationUSA, EU
Payment methods per marketYes
Who decides the VATThe storefront decides the VAT
Prices with and without VAT per customerYes
VAT OSS and IOSSPartly
Source of the currencyFollows the storefront or the country

Vendor relationship and exit

Support languagesen
Support geographyus, eu
Partner coverageUS, UK, NL, AU
SLAPublic
Data ownershipThe customer
Data can be exportedYes
The frontend can be taken along in a moveYes

Maturity

MaturityEstablished
A released version with version history within twelve monthsYes
Public documentation referencing a current Business Central versionYes
At least one named reference customerNo
A stated support channel with language and geographyYes