What the solution is
Sana Commerce Cloud is a commerce platform from Sana Commerce in Rotterdam, sold as a subscription and hosted on Microsoft Azure. The solution has four parts: a webstore, an admin module, Sana's own framework, and an add-on installed inside Business Central. That last part is what sets the product apart from the rest of the catalogue. The add-on runs in the ERP and answers the storefront's questions while the buyer is on the page.
One vendor stands behind all three elements, meaning the backend, the storefront and the integration. There is no third party to coordinate with when Business Central ships a release, and there is also no second vendor to turn to when something does not work.
How the integration works
Sana keeps no separate commerce database of items, customers and prices. The storefront asks Business Central over web services, and the sales documents, meaning quotes, orders, shipments, invoices and returns, live in the ERP. That removes the entire class of errors where two systems disagree about a price.
The price for it is that every page view becomes a call to Business Central. Response times in the store are therefore tied to how quickly your ERP environment answers and to how much can be cached. This is the most important technical trade-off in the solution, and it should be tried on your own data rather than on a demo account.
The add-on is supported against Business Central online and against on-premises, with a separate installation guide for each. Sana obliges the customer to upgrade the ERP connector at least every two years. It is not a large job, but it is a recurring one, and it belongs in the operating agreement from the start.
Prices, discounts and agreements
This is where the solution is strong. Customer-specific prices, tiered volume discounts, campaign prices with a validity period, discount groups and trade agreements are decided by Business Central, not by the storefront. Create a discount agreement in the ERP on Monday morning and it applies in the store on Monday morning, without anyone touching the store.
The consequence is that there is no independent campaign layer in the storefront. If marketing wants to run a campaign, it has to be created as a price or a discount in Business Central. For a company whose pricing already lives in the ERP, that is an advantage. For a brand that wants to work freely with campaigns in the frontend, it is a constraint that belongs in the assessment.
Product bundles rest on Business Central's own bill-of-material and assembly tools. Ask to see a bundle in a demo where the price depends on the combination in the basket. That is where the difference between a real ERP calculation and an imitation becomes visible.
The order and the finance function
The order can be created as a sales order or as a sales quote in Business Central, and that is a setting rather than a fixed choice. Partial shipments, back orders, cancelled lines, returns and credit memos are handled with the ERP's own processes, because the documents were in the ERP from the outset.
VAT and tax are calculated by Business Central. That means the VAT setup does not have to be maintained in two places, and that an international VAT setup in the ERP also applies in the store.
Reconciling the payment provider's settlement against the general ledger is not solved by the solution on its own. Fees vary per transaction, and if the settlement arrives as one daily amount, someone has to match it. Settle with your partner how that is done before the budget is set.
Who the solution fits
The solution fits a manufacturer or wholesaler selling to known customers on agreed terms, where the pricing logic in Business Central is genuinely complicated. With two thousand customers each carrying their own discount groups, currencies and units, this is precisely the situation where a flat price matrix breaks down, and where live lookups in the ERP are worth paying for.
The sales rep view, where an employee orders on the customer's behalf, is among the product's strongest parts, and so are quotes, reordering from order history and multiple delivery addresses.
The solution does not fit pure consumer selling with heavy editorial campaigning and fast page views. It can be set up for open selling, but that is not what the architecture is built around.
What to settle before you decide
Pricing is not public. Independent sources point to an annual licence from around ten thousand euro for a smaller setup and above one hundred thousand for a large one. Our bands therefore carry low confidence and should be read as a frame, not a quote.
Accessibility is worth asking about in writing. Sana states itself that it works towards WCAG 2.1 level AA for the default storefront, and that no certification is given, because the store can be configured freely. Responsibility for an accessible store therefore sits with you, and few vendors state that as plainly.
Three more things belong in the contract: who upgrades the ERP connector every two years, what an additional webstore costs in licence, and how you get out again. The frontend cannot be taken to another platform, while the data sits in Business Central and is therefore yours.