What the solution is
Znode is a B2B commerce platform from Amla Commerce in the United States, aimed at manufacturers and distributors in the upper mid-market. The platform has been named a Major Player in the IDC MarketScape for B2B digital commerce for the midmarket, and it collects medals in the Paradigm B2B Combine, meaning it is recognised in the industry analyses buyers of this kind of system read.
The architecture is headless throughout. The customer experience is separated from the administration console, and there are more than six hundred APIs. At the same time a finished frontend layer exists through a software development kit, so you do not have to build everything from scratch to get started.
How the integration works
The integration is called Commerce Connector and is a middleware layer with more than forty-five prebuilt touchpoints. On top sit Data Exchanges, which handle data flows for items, prices, stock, customers and orders, and which can run both in real time and on a schedule.
This is a different model from the other solutions in the catalogue. There is no app in Business Central, but an integration layer talking to the ERP from the outside. The advantage is that the same layer can talk to several systems, meaning ERP, PIM, warehouse management and customer service, and that the choice between real time and schedule can be made per data type. The price is one more layer to operate and one more layer to maintain.
Because the touchpoints are prebuilt but the data flows are configured per customer, the solution sits in the cell with a flexible integration the company configures itself. That is not a judgement on quality, but a statement about where responsibility for the mappings ends up when Business Central ships a release.
Prices, discounts and agreements
Here Znode differs clearly from the ERP-driven solutions. Complex pricing is a built-in strength of the platform, not something fetched from the ERP. Znode has its own price engine with account-specific prices, quantity tiers, price lists and campaigns.
For a company whose pricing logic is too complicated for Business Central, that is an argument rather than a drawback. The pricing logic can live in the commerce platform, where it is easier to change and where there are tools for it. For a company where the finance function owns pricing in the ERP, it is on the other hand two places to maintain a price, and that is why the solution carries the label for logic set up in two places.
The decision should be made deliberately and written down. The agreed price can come from Business Central through Data Exchanges, while quantity tiers and campaigns can live in Znode. That works, but only if someone has decided what belongs where.
The order and the finance function
The order is sent to Business Central as a sales order through the integration layer. Approval workflows, quote management and list management are built-in capabilities of the platform, so an order can pass through an approval before it becomes an ERP document.
That is a strength for large B2B setups with buyers and approvers, and it is at the same time a fact for the finance function: there is a place outside the ERP where an order can sit and wait. Agree for how long, and who checks.
VAT is in practice decided by the platform for open selling, and an external tax engine is the ordinary solution in this class of product. Reconciling the payment settlement is a separate job.
Who the solution fits
The solution fits a larger manufacturer or distributor with a complex assortment, many channels and a wish to own the frontend. Several stores from the same installation is a built-in capability rather than an add-on, which makes the solution relevant if you have several brands or several countries.
It also fits if you have a development team or an agency to build the experience. A headless architecture and six hundred APIs are an invitation to build, and that invitation costs something to accept.
The solution fits less well for a smaller company wanting something that works as it arrives. Both the licence and the implementation sit in the upper part of the catalogue, and there is no finished app for Business Central making setup short.
What to settle before you decide
Pricing is not public. Our bands are an estimate with low confidence and sit high, because the product is positioned in the upper mid-market with a headless architecture requiring frontend work. Ask for a quotation covering licence, Commerce Connector, frontend and operations separately.
Settle the division of labour on prices between Business Central and Znode's price engine, and write it down. That is the single most important question with this solution, and it is easier to answer before implementation than afterwards.
Finally, ask for a named reference customer in Europe on Business Central specifically. Znode has documented recognition in the market, but the combination of Znode and Business Central in Europe is the one you need confirmed.