What the solution is
CURABIS is a Danish house specialising in moving companies from NAV and C5 to Business Central and in building apps for the ERP. Business Central Webshop is their commerce product, running on their Cross Channel platform, which brings orders, products and stock together across storefronts and marketplaces.
The load-bearing choice in the product is that the storefront builds on Business Central's data model rather than on its own. There is therefore no commerce database of items and prices that has to be kept in agreement with the ERP. It is the same approach as the other solutions in the catalogue where Business Central is the backend, but here with a headless frontend on top.
How the integration works
The platform runs as true SaaS in Microsoft Azure and communicates in real time with Business Central. Content and data are administered in the ERP, so there is one place to change a price, a text or a stock figure.
The frontend is headless. That means the presentation layer can be built and changed freely without touching the data layer, and it is the property separating the solution from the other BC-driven solutions in the catalogue. If you want a wholly bespoke design or a frontend in a modern framework, that is possible here, where it is not in an app that generates the pages itself.
Only Business Central online is documented. The vendor also works on upgrades from older installations, so the on-premises question is reasonable to ask, but we have found no written coverage for it.
Prices, discounts and agreements
Because the data model is Business Central's, the pricing logic is Business Central's too. Customer-specific prices, agreed prices, volume discounts and discount groups are decided by the ERP, and there is no flat price matrix to keep fresh between two systems.
The scaling trap of customers times items therefore does not exist. That is the single most important fact for a company with many customers each on their own terms, and it is worth holding up against the synchronised alternatives in the catalogue.
In return there is no independent campaign layer. Campaigns are created in Business Central. If you sell bundle deals whose price depends on the contents of the basket, that should be demonstrated, because Business Central's own bills of material do not always reach that far.
The order and the finance function
The order lands in Business Central as a sales order, and from there it continues in the ERP's own flow. Partial shipments, back orders, returns and credit memos are therefore Business Central's responsibility rather than the storefront's.
Because the Cross Channel platform also handles marketplaces, there is a detail worth noting for the finance function: orders from a marketplace land in the same track as orders from the storefront. That makes reconciliation simpler than when each channel has its own flow, but it requires the customer setup in Business Central to carry it.
VAT is decided by Business Central. Reconciling payment settlements and marketplace fees is still a separate job, and it should be priced.
Who the solution fits
The solution fits a Danish company on Business Central wanting storefront and marketplaces in the same track, and which values there being only one data foundation. The combination of ERP-driven logic and a headless frontend is rare in the catalogue.
It also fits if you have a design ambition going beyond a theme. The headless frontend makes it possible to build a store that looks the way you want without leaving the ERP-driven data model.
The solution fits less well if you sell outside the Nordics or need support in languages other than Danish and English. The vendor is a smaller Danish house, and partner coverage is correspondingly concentrated.
What to settle before you decide
Pricing is not public. Our bands are an estimate with low confidence. Ask to have the licence, the hosting and the frontend development priced separately, because a headless setup means the frontend is a development effort of its own with its own maintenance.
That last point is the most important one. A headless frontend gives freedom, but you own that freedom afterwards. Settle whether CURABIS builds and maintains the frontend, or whether it is you or an agency, because it moves the maintenance item noticeably.
Ask also for an answer on on-premises and for a named reference customer where the product can be recognised in the page source. That is the fastest way to verify the solution runs in production somewhere other than in a demo.