What the solution is
commercebuild is a commerce platform built for Business Central and for Acumatica, sold as a flat-rate subscription with no fee on revenue. The store is hosted by the vendor, and the integration is obtained as an app from Microsoft Marketplace. Storefront, backend and integration come from the same house.
The product covers an open store, a customer portal and a sales portal in the same licence. That is simpler packaging than several competitors, where the portal and the store are two line items, and it makes a quotation easier to compare.
How the integration works
The vendor describes the connection as direct to Business Central with no middleware and no batch runs. Prices, stock, customers and orders flow between the ERP and the store continuously, and that architecture carries the rest of the assessment.
The most important part is documented concretely. The store checks the best available price for the logged-in user when that user opens the item page, and it uses Business Central's own logic to do so. The customer's price agreements, item and discount groups, validity periods, quantity thresholds, currency and unit of measure all take part in the lookup. If no special price qualifies, it falls back to the price on the item card.
Only Business Central online is documented, however. If you run on-premises, that is the first thing to settle in writing. Likewise, ask to see the response time on an item page with your own number of items and your own price matrix, precisely because the lookup happens along the way rather than in advance.
Prices, discounts and agreements
This is where the solution stands out. Because the price is calculated by Business Central at the moment it has to be shown, there is no flat price matrix to keep fresh and no risk of the store and the ERP disagreeing. A new discount agreement in Business Central applies in the store immediately.
The scaling trap of a flat price matrix, meaning customers times items, therefore does not exist in this solution. That single fact is often the deciding one for a wholesaler with many customers and many item numbers, and it is worth holding up against the synchronised alternatives in the catalogue.
The price for the architecture is that there is no independent campaign layer in the store. If marketing wants to run a campaign without touching Business Central, that is not the route the solution is built for. Ask also to see how a product bundle is priced, because that is the one place where Business Central's price logic does not reach on its own.
The order and the finance function
The order is created as a sales order in Business Central with the price and the line discount the ERP inserts itself. That means the order looks from the outset as if a salesperson had created it, and that partial shipments, back orders and credit memos follow your ordinary processes.
VAT is decided by Business Central, which removes a classic source of error in international selling. A VAT setup that works in the ERP also works in the store.
Reconciling the payment provider's settlement is still a separate job. It is not described as part of the solution, and it should be priced separately before the budget is set.
Who the solution fits
The solution fits a company on Business Central online where the pricing logic in the ERP is the true source and nobody wants to maintain it in two places. The combination of a finished integration and logic that runs in Business Central is rare in this market, and it is exactly that combination this solution offers.
It also fits if the budget has to be predictable. A flat subscription with no revenue fee and no lock-in, and a fixed-price implementation over one to two months, is a different risk profile from a project billed by the hour.
The solution fits less well if you need a large editorial universe, free frontend control, or a marketing department that runs campaigns without going through the ERP. The CMS-based platforms in the catalogue sit closer there.
What to settle before you decide
Pricing is quoted on request across three tiers. The vendor stresses that there is no revenue fee and no lock-in, and that implementation is fixed price. Our bands are an estimate with low confidence, and they should be replaced by a real quotation before any further calculation.
Ask for a written answer on whether on-premises is supported, and on which tier contains what. The difference between tiers is functional and not only volumetric, and differences of that kind are expensive to discover after signing.
Finally, ask for a load test or at least a reference visit to a customer with a catalogue the size of yours. Live lookups are the right architecture for pricing logic, but they move the load into Business Central, and that is worth seeing with your own eyes.