Maco B2B for the IT team

The store presents the data, the ERP stays its owner

A wholesale customer also places orders outside the store: by phone, by e-mail, with a sales rep. So the credit balance, invoices, unit conversions and order minimums have their owner in the accounting system, and the store keeps a reflection of them. Data arrives as a state, not an increment, and is written by natural key: tax ID, code, invoice number. A repeated message from the middleware does not duplicate a record.

All the logic sits in services, and the store controller and the REST endpoint call the same service, so the interface and the API do not drift apart in behaviour. Permissions are checked on the server: a customer endpoint returns only the data of their company, and swapping an identifier in the address exposes nobody else’s data. The whole storefront is on Hyvä, with no Luma, RequireJS or Knockout.

Every entity, every attribute added to a native entity, every user action and all data arriving from the ERP has its REST endpoint. We add GraphQL where it is genuinely needed, for example under a headless storefront.

What comes alongside the platform

Two products sit outside Maco B2B and come in when the scale calls for them. The price engine takes over pricing policy once it stops being a simple price list: rule hierarchies, customer and product-group matrices across hundreds of thousands of rules, margin monitoring in real time. Maco B2B has one entry point for reading a price, and an external source calculates it, so swapping the engine for the client’s own API does not touch the store.

Maconnector is the middleware for exchanging data with the ERP and in practice accompanies every B2B rollout. If you are still weighing up the platform itself, start with the overview of B2B platforms, and if the technology is what interests you, with the Magento page.