What the solution is
Digitroll AS is a Norwegian vendor that has built webstores against Navision, Dynamics NAV and now Business Central for more than twenty years. The store is built on Microsoft's .NET framework and is operated by Digitroll. Besides Business Central they also integrate with other Nordic business systems, among them Business NXT and 24SevenOffice.
The product is delivered in two ways. Either as a finished store that is set up and put to use, or as a headless setup where the frontend is built freely on top of the data layer. That is a real choice with different consequences for both price and maintenance, and it should be settled early.
How the integration works
What the vendor puts first itself is the price lookup. The customer gets the right price because the price is looked up directly in Business Central when the item is displayed. Stock, customer and product data are also updated automatically from the ERP.
The store supports both Business Central online and the older installations on your own servers, which follows naturally from the history with Navision and NAV. For a company that has not moved to the cloud yet, that is a short list of vendors to choose from, and this one is on it.
The storefront code is open. That is an unusual property in the catalogue, and it has two sides. It gives freedom to build exactly what you want, and it makes it possible to take the frontend along if the collaboration ends. It also moves responsibility for what you change over to you, and that belongs in the agreement.
Prices, discounts and agreements
Customer-specific prices and agreed prices are looked up in Business Central along the way. There is therefore no flat price matrix to keep fresh, and the scaling trap of customers times items does not exist for the price.
For the other rows we have found no written documentation. Tiered volume discounts, discount groups, campaign prices and product bundles therefore stand as not stated rather than as a no. That is not a claim that the solution cannot, but a statement that we have not been able to verify it.
That is also why the label reads transferred result rather than logic that runs in Business Central. If you get those four rows documented, the solution may well move, and it is a fair question to ask in writing.
The order and the finance function
The order is created as a sales order in Business Central, and from there it runs in the ERP's ordinary flow. Partial shipments, back orders and credit memos are therefore Business Central's responsibility.
Because the store is operated by the vendor and the code is open, there are two places an error can arise, and it is worth settling who monitors what. A queue with a notification is better than a log, but it requires someone to read the notification.
VAT is decided by Business Central when the price lookup comes from there. Reconciling the payment settlement against the general ledger is still a separate job, and it should be priced.
Who the solution fits
The solution fits a Norwegian company on Business Central wanting a store built and operated by a vendor with long experience in that particular ERP. The option of running against on-premises is an argument in its own right if you have not moved to the cloud.
It also fits if you need to be able to customise the store far. Open code and a headless option are two routes to the same thing, and they do not exist in most of the other solutions.
The solution fits less well if you want a product with version history and a public price list. This is a delivery partnership with a Norwegian vendor rather than an off-the-shelf product, and that should be known before comparing.
What to settle before you decide
Pricing depends on the number of stores, integrations and scope, and the vendor states that they provide a clear model before starting. Ask for that model in writing, and ask to have it split into licence, operations and development. Our bands are an estimate with low confidence.
Settle whether you choose the finished store or the headless one. That is the choice determining how much of the maintenance ends up with you, and it is hard to change later in the process.
Ask for documentation on the four pricing logic rows we have not been able to verify, meaning volume discounts, discount groups, campaign prices and bundles. They are quick for the vendor to answer, and they move the solution's placement noticeably.