What the solution is
Brink Commerce is a Swedish commerce platform that is pure API. There is no frontend, no themes and no storefront administration in the sense the other solutions in the catalogue have one. The platform delivers commerce logic, meaning basket, order, prices, campaigns and payment, as services you build on top of.
That is a deliberate position and not a gap. Brink is chosen by brands that want to own their customer experience completely and that have a development team able to carry it. If that is not you, it is not the right solution, and that is the most important sentence on this page.
How the integration works
Junipeer's Brink connector links the platform to ERP, warehouse management, product information systems, payment providers and analytics tools, and Business Central is one of the supported ERPs. Items, prices, stock, customers and orders synchronise between Brink and Business Central.
Because Brink is itself composed of services, the integration layer is more central here than in the other solutions. Junipeer is not merely a bridge between two systems but one of several links in a chain, and every link has to be monitored. That is why our assessment of the maintenance burden is the highest in the catalogue for this solution.
Setup consists of field mapping and a test run. We have found no documentation of retry logic or of monitoring, and with an architecture of this kind that is the most important thing to have demonstrated. Only Business Central online is documented.
Prices, discounts and agreements
Prices are transferred from Business Central to Brink. The agreed price therefore comes from the ERP, but it is not recalculated at every call, and the scaling trap of customers times items applies.
Campaigns, discounts and bundles are part of Brink's own services and are set up there. For a brand with a development team that is often the whole point: the campaign logic can be written exactly as the business needs it, rather than having to fit inside a storefront platform's frame.
The price for that freedom is that there is no interface a marketing employee can go into unaided. Everything that has to be changed has to be changed through what you have built yourselves, and that belongs in the calculation of ongoing operations.
The order and the finance function
The order is written to Business Central as a sales order through the integration layer, and partial shipments, back orders and credit memos are handled in the ERP.
Because there are several links in the chain, there are several places an order can be lost. That is not an argument against the architecture, but it is an argument for spending time on monitoring and alerting during implementation rather than deferring it until after go-live.
VAT is decided by what you build, with Brink's services underneath. If you sell in several countries, the VAT setup is a development task rather than a configuration task, and it should be priced as such.
Who the solution fits
The solution fits a Nordic brand with an internal development team, where the customer experience is a competitive advantage and where the decision has been made to own it. Within that profile an API-first platform is the right choice, and Brink is one of the strongest Nordic offerings.
It also fits if you need commerce logic no finished platform can deliver, meaning unusual price models, unusual basket rules or a sales process that does not look like an ordinary storefront.
The solution does not fit without a development team. There is no route to production that does not go through development, and there is no version of the solution that is cheap or fast. That has to be a decision rather than a surprise.
What to settle before you decide
Junipeer's price starts at 399 euro a month and is public. Brink's own pricing model is not public, and the development of the frontend and of everything that normally comes with a platform is the largest item. Our bands are estimates with low confidence and therefore sit high on implementation and maintenance.
Count on the maintenance not stopping. A bespoke frontend on a composed platform has to keep up when the platform's APIs change, and that is a recurring item rather than a one-off. That is the most honest thing to say about this solution.
Ask for a complete architecture diagram with every link named, including who operates each link. That is the one thing determining whether the project can be managed, and it is free to ask for.