What the solution is
Dynamicweb Commerce Suite is a combined platform from Dynamicweb A/S in Denmark. It holds an editorial CMS, a product information system and a storefront in the same installation, and it is sold as a subscription. For Business Central, Dynamicweb ships its own plug-in, obtained from Microsoft Marketplace and installed in the ERP.
All three elements come from the same house, meaning the backend, the storefront and the integration. Unlike a pure commerce platform, the CMS part is not an afterthought: a campaign page, an article series or a landing page per market is built in the same tool as the product catalogue, and that is one of the strongest reasons to choose the solution.
How the integration works
The plug-in unit in Business Central exposes a web service that Dynamicweb calls. Against Business Central online, authentication is OAuth 2.0 service-to-service, registered as an app in Entra ID, and data is exchanged as XML. Against on-premises, traffic goes through Dynamicweb's own connector service. Both routes are documented, so the solution can be used in either kind of installation.
The integration has two modes, and the difference matters in practice. Scheduled integration moves master data in batches on a schedule. Live integration sends a call to Business Central while the page is being built, and is used for prices, stock and for letting the ERP calculate discounts and freight on the order. The two can be combined, which is exactly why the solution can be set up in several ways, each with its own operating profile.
That also makes setup a project. Field mappings, endpoints and add-in instances are configured per customer, and you own those mappings afterwards. The solution therefore sits in the cell where the company configures and maintains, regardless of the plug-in unit itself being a released product with version history.
Prices, discounts and agreements
With live integration switched on, customer-specific prices are fetched from Business Central when the price is rendered, and the ERP can decide discounts and freight fees on the order. Tiered volume discounts, discount groups and line and invoice discounts therefore follow the setup in Business Central rather than a copy in the storefront.
Product bundles are the most important exception. They are composed in Dynamicweb, not in Business Central, and that is why the solution carries the label for logic set up in two places. If you sell a solution deal whose price depends on the combination in the basket, that rule lives in the platform and has to be maintained there.
The same duality applies to campaigns. Dynamicweb has its own discount and campaign engine, and many setups use it for the editorial work while letting Business Central decide the agreed price. That is a strength if you want both options. It is a risk if nobody has decided what belongs where.
The order and the finance function
Which document is created in Business Central is decided in the setup, so both a sales order and a sales quote are possible. That is a real choice and not a technical detail, because it determines who approves the order before it becomes a commitment.
The integration keeps a log of every transfer, and failed orders can be run again. What needs to be agreed is who looks at the log. A queue with automatic retry handles transient failures, but an order that fails on a data error stays there until a person sees it.
VAT can be decided by Business Central through the live integration, and that is the setup we have assumed. Reconciling the payment provider's settlement against the general ledger is not part of the solution and has to be solved with a separate module or a manual process.
Who the solution fits
The solution fits a company selling both openly and to known customers, and which needs real content alongside the catalogue. With several brands, several countries and a marketing department that builds its own pages, this is one of the few solutions in the catalogue where all of it sits in the same tool.
The built-in product information system is worth costing out. The item card in Business Central is thin, and where other solutions lead to a separate PIM with its own licence and its own project, that part is included here.
The solution fits less well if you want to avoid a configuration project. There are many settings, and they have to be set by someone who knows both Business Central and Dynamicweb. If the wish is an installation that works as it arrives, other solutions in the catalogue sit closer.
What to settle before you decide
Pricing is not public. Publicly available overviews point to around fifteen hundred dollars a month as an entry point, meaning roughly twenty thousand euro a year, and upwards from there by features and scope. Our bands carry low confidence.
Settle how much should run live and how much should run on a schedule. That is the choice that determines both response times in the store and the load on Business Central, and it is easier to decide before implementation than to change afterwards.
Ask to have it written down who owns the field mappings, and what happens to them at a Business Central release twice a year. That is the item separating a finished app from a configured framework, and it belongs in the operating agreement with a name attached.