Ecommerce for Business Central

Dynamics eShop

American storefront platform with its own AppSource app for Business Central and one product for both B2B and B2C. Prices and stock come from the ERP, while campaigns and bundles are set up in the storefront. Only Business Central online is documented.

Maker of the ecommerce solution
Dynamics eShop Inc.
Maker of the integration
Dynamics eShop Inc.
Last verified
2026-08-20

What the solution is

Dynamics eShop is a storefront platform from Dynamics eShop Inc. in the United States. The store is hosted by the vendor, and the integration ships as an app on Microsoft AppSource supporting both the Essentials and Premium editions of Business Central. The app's interface exists in a long list of languages, including English, Dutch, French, German, Spanish and Swedish, which is a useful sign that the vendor works outside the North American market.

Storefront, backend and integration come from the same vendor. The same product is sold for open consumer selling and for login-based selling where the customer sees their own prices and their own stock picture. It is a simple structure, and it means there is one place to go when something needs fixing.

How the integration works

The vendor describes the integration as continuous and real time for stock, prices and orders. The app in Business Central handles the connection, and it is obtained and updated through AppSource like any other released product. That is the main reason the solution sits in the cell with a finished integration to a separate storefront: you do not have to build data mappings to go live.

Only Business Central online is documented. We have not been able to find a description of running against an installation on your own servers, and the solution should therefore be treated as cloud only until the vendor says otherwise in writing. If you run on-premises, that is the first question to ask.

Where the line between real time and transfer sits is not documented field by field. We have set price and stock as live and the item catalogue as transferred, and that split matches the vendor's own wording. Ask to have it confirmed, and ask to see the response time on a product page with your own number of items.

Prices, discounts and agreements

Customer-specific prices, volume discounts and campaign prices with a validity period follow the setup in Business Central. That is the part the vendor puts first itself, and it is also the part that makes the solution interesting to a wholesaler rather than a pure consumer store.

Discount groups and trade agreements we have set as a transferred result rather than as a calculation in the ERP, because the documentation is not clear enough for the stronger answer. The difference matters: a transferred result holds for an agreed price and breaks on a condition that can only be decided once the basket is full.

Product bundles are set up in the storefront. That is why the solution carries the label for logic set up in two places, and it is the one question worth spending a demo on. Ask to put two items in the basket that together trigger a solution price, and see where the price is calculated.

The order and the finance function

The order is created as a sales order in Business Central, and from there it continues in the ERP's own flow. Partial shipments, back orders and credit memos are therefore Business Central's responsibility and not the storefront's, which is the arrangement the finance function usually prefers.

VAT on the order we have set as partly covered. The storefront can show and calculate VAT, but VAT authority effectively sits in the storefront for the open part of the selling, and an international VAT setup should therefore be reviewed concretely rather than assumed.

Reconciling the payment provider's settlement is not described as part of the solution. Count on that job being solved alongside, and get it priced before the budget is set.

Who the solution fits

The solution fits a company on Business Central online that wants both an open store and a customer portal from the same vendor, and which values the integration being a finished product rather than a configuration project.

It also fits if you need several languages in the administration. The number of languages in the app is unusual for a vendor of this size, and it makes an international setup easier than one might expect.

The solution fits less well if you run on-premises, or if you need editorial content and free design on a par with a CMS-based platform. The design and content part is the product's weakest area compared with the large platforms in the catalogue.

What to settle before you decide

Pricing is not public, and we have not been able to find a documented price list. The bands in the table below are therefore an estimate based on comparable solutions, and they carry low confidence. Use them to decide whether the solution is in the same order of magnitude as the alternatives, not to negotiate with.

Ask for written confirmation on three things: whether on-premises is supported, which fields are genuinely fetched live, and how bundles are priced. Those three answers move the solution noticeably in the assessment.

Ask also for a named reference customer in Europe. The vendor works internationally, but the centre of gravity is North American, and a European reference says something about how easy it will be to get help in your time zone.

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 solutionDynamics eShop
Maker of the ecommerce solutionDynamics eShop Inc.
Integration to Business CentraleShop Connect for Business Central
Maker of the integrationDynamics eShop Inc.
Solution typeAll in one, the same vendor for all three elements
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 productYes
Matrix cellFinished integration to a separate storefront
Logic labelThe logic is set up in two places
Other integrations to the same platform
Primary sourcedynamicseshop.com
Status of this entryDraft
Last verified2026-08-20
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 stretchedBounded
MethodsConfiguration in the product's own backend, Themes and templates
What it does to the commitmentThe vendor still covers it, the customisations are not on your account

Sales model

Open storefrontYes
Customer portalYes
NoteThe same product for both sales models.

Master data

ItemsSynchronised
CustomersSynchronised
InventoryRead live from Business Central
Product contentMaintained in the storefront
OrdersSynchronised
PricesRead live from Business Central

Pricing logic and discounts

Customer-specific and agreed pricesExecuted in Business Central
Tiered volume discountsExecuted in Business Central
Campaign prices with a validity periodExecuted in Business Central
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 termsThe result is transferred
VAT and tax calculationSet up in the storefront
Stock availability and delivery dateExecuted in Business Central

Order flow

Document created in Business CentralSales order
Reserves stockPartly
Partial shipmentsYes
Back ordersYes
Cancelled linesPartly
ReturnsPartly
Credit memoYes
Reconciling the payment provider's settlementNo
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
BatchingPartly
Spread across several service principalsNo
CachingPartly
Retry on a 429 responsePartly
Throttling handlingNot mentioned
API surfaces in Business CentralCustom API pages

Product data and PIM

VariantsYes
Max variants per item
Units of measureYes
AttributesYes
Multilingual product dataYes
Digital assetsPartly
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 numbersYes

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
Max storefronts
Nature of the limitsUnknown
Sourcedynamicseshop.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 modelFixed price against a template
Price per additional storefrontUnknown
Day-to-day work after go-liveSmall
Not included in the figuresinternal time, user licences in Business Central, payment fees, reconciliation of payment settlements
Small: Licence per yearEUR 5,000 to 20,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: SourceAssessed against comparable solutions
Medium: Licence per yearEUR 20,000 to 60,000
Medium: Implementation, one-offEUR 40,000 to 120,000
Medium: Maintenance per yearUnder EUR 5,000
Medium: Time to go live3 to 6 months
Medium: Three-year cost of ownershipEUR 120,000 to 400,000
Medium: ConfidenceLow
Medium: SourceAssessed against comparable solutions
Large: Licence per yearEUR 60,000 to 150,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 ownershipOver EUR 400,000
Large: ConfidenceLow
Large: SourceAssessed against comparable solutions

Functional requirements

SEO and indexabilityYes
Design and theme controlPartly
Content and landing pagesPartly
Search and navigationYes
Ordering on the customer's behalfYes
Several storefronts from one Business CentralPartly
Multilingual frontendYes
Openness and extensionsPartly
AccessibilityNo
Agent readabilityNo
PerformancePartly
Bulk editing, import and exportPartly
Change log in the backendPartly
An external search engine can be attachedNo
Facets on Business Central fieldsYes
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersNo
Hosted card fields, PCI scope kept outYes
Strong customer authentication and fraud screeningPartly
Consent managementPartly
Data protection and processing agreementPartly

Open storefront only

Guest checkoutYes
Card paymentYes
Campaigns set up in the storefrontYes
WishlistsYes
Right of withdrawal and returns portalPartly

Customer portal only

Account hierarchy with buyers and approversYes
Approval flow with amount limitsPartly
Invoice payment and open entriesYes
Quotes and requestsYes
Price list for print and downloadPartly
Sales rep viewYes
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
Payment methods per marketPartly
Who decides the VATThe storefront decides the VAT
Prices with and without VAT per customerPartly
VAT OSS and IOSSNo
Source of the currencyFollows the customer in Business Central

Vendor relationship and exit

Support languagesen
Support geographyus
Partner coverageUS, CA, NL, UK
SLAContractual
Data ownershipThe customer
Data can be exportedPartly
The frontend can be taken along in a moveNo

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