Free consultation, no commitment.Book a call
Menu

Maco B2B: the modules that turn Magento into a wholesale platform

A B2B sales platform on Mage-OS 3.x and Magento 2. It adds what the platform does not have: company accounts, contract pricing, trade credit, quoting, invoices from the ERP and a sales rep panel. Hyvä on the front, REST API across the whole scope.

Book a demoB2B platforms

Mage-OS 3.x · Hyvä Themes · module licence included in the rollout price

What the package covers

5

B2B selling areas in the standard, no tiers

3

roles in one store: buyer, company admin, sales rep

100%

of the package exposed over REST API

2012

delivering e-commerce since

100+

projects delivered

40+

specialists on the team

Why this package exists

The Magento B2B you read about is Adobe Commerce

The features that show up in search results as Magento B2B mostly belong to the paid Adobe Commerce B2B. They are absent from Magento Open Source and from Mage-OS, and it is not a matter of configuration: the packages themselves are missing. We checked that in the distribution manifest rather than in marketing documentation.

There are no company accounts with roles, no contract catalogues or prices, no multiple carts, no negotiated quote, no ordering by code, no approval workflow, no trade credit, no customer segmentation and no multiple wishlists. It is the list of modules whose absence you notice in the third week of a rollout. Maco B2B fills exactly that gap, and it does so on a distribution you pay no licence for.

What we do not do is rebuild anything the platform already handles. The dividing line is one sentence: if Mage-OS does something natively, we configure it rather than write it.

Weighing this against OroCommerce, which carries its B2B features in the core? That is the other road we take on new B2B rollouts, and we are a Silver Solution Partner on it.

OroCommerce

What we do not build

The platform ships these, we configure them

Every one of these is in Mage-OS straight after installation, and payment gateways and carrier modules go in as official extensions. A module repeating any of it would be code to maintain for no reason.

  • Customer groups
  • Tier pricing
  • Tax rules and net prices
  • Cart price rules
  • OpenSearch
  • Multistore and currencies
  • Payment gateways
  • Carrier modules

Maco B2B standard

Everything in the standard, no tiers

The standard has no tiers. We do not split it into Starter, Standard and Premium, because the modules reference each other: company accounts are the foundation the rest stands on.

  1. 01

    Company accounts

    Company structure with sub-users, roles and permissions per user, a spending threshold per order, branches and departments, company-level blocking, and the assigned account manager shown on the account.

    Foundation of the package

  2. 02

    B2B registration

    A company registration form beside the B2C one. Validating the tax ID against the national business register is mandatory: without a positive check the application cannot be completed. One submission creates the company and the applicant account together, with the price group and account manager taken from configuration.

    Checked against the register

  3. 03

    Trade credit

    Limit and balance per company, a yes, no or short-by-this-much decision before the order is placed, a block once the limit is passed, the limit drawn down only when the order is placed, and a limit application filed by the company administrator.

    Balance from the ERP

  4. 04

    Contract pricing

    The contract price is calculated in an external source and read live, while customer-group prices are materialised through native catalogue rules. One entry point for reading a price, and one place where its visibility is decided.

    Price from an external source

  5. 05

    Quick order

    An order-by-code page: type a SKU and a quantity, paste a list or upload a spreadsheet. Lines are recognised by SKU, the customer’s own codes, manufacturer codes and barcodes, and always reviewed before they reach the cart.

  6. 06

    Multiple carts

    Named carts per employee, one per site, branch or job, with a switcher on every page. A cart can be duplicated, handed to a colleague, printed with prices or turned into a request for quote.

  7. 07

    Reorder

    A whole past order repeated in one click, validated against availability and recalculated at current prices.

  8. 08

    Quoting

    A request for quote leaves the cart, the sales rep answers with prices, and the negotiation stays in the change history. A quote has an expiry date and converts into an order without anyone retyping the lines.

    PDF and price control: optional

  9. 09

    Customer dashboard

    The view after signing in answers the questions that get asked most: limit and balance, recent orders and their statuses, account manager details, shortcuts to ordering, lists, quotes and billing. Order history gains the search and filters the platform does not have.

  10. 10

    B2B payments

    Payment methods assigned per customer group, bank transfer with an individual payment term of 7, 14, 30 or 60 days per customer, and payment against the trade credit limit.

  11. 11

    B2B shipping

    Shipping cost by transport class, free shipping above a threshold, splitting an order by stock availability, a cost calculator in the cart, and the carrier and tracking number from the ERP.

    Carrier auto-select: optional

  12. 12

    Order minimums

    Minimum and multiple quantities differentiated per customer group and per company, a minimum order value per group, enforced in the bulk-add paths too. The values come from the ERP.

  13. 13

    Units of measure

    Selling always happens in the base unit of the item, exactly as in the ERP. Packaging, meaning piece, pack, carton and pallet, is a way of entering and presenting quantity. Conversion factors come from the ERP, and the selector works on the listing, the product page, the cart and the checkout.

  14. 14

    Product attachments

    Datasheets, certificates, manuals and declarations of conformity attached to the product, with visibility control: public, signed-in only, or per customer group.

    No native file type

  15. 15

    Invoices and settlements

    Invoices, corrections and delivery notes from the ERP attached to orders, with the KSeF number and QR code on the printout, payment status, overdue amounts and the settlement balance.

  16. 16

    Two-factor sign-in

    A second factor for customer accounts in the store, switched on by the user: an authenticator app or a code by e-mail, with the device remembered for 30 days.

  17. 17

    Sales rep panel

    The admin panel narrowed to a sales rep's own portfolio: their customers, orders, quotes and finances, ordering on behalf of a customer, a manager level and holiday cover.

Optional modules

Added on request

Quoted separately, because each answers a need not every wholesaler has. The list is open, and the scope of the standard stays fixed.

  • Approval workflow

    An approver role and multi-level order approval: an employee places, a manager approves, optionally a director as well. Value thresholds per role and a pending-approval queue in the company panel.

  • File area

    A central document repository for customers: catalogues, point-of-sale materials and commercial documents, with access granted per customer group.

  • Sales rep mobile app

    The sales rep panel on a phone, iOS and Android: portfolio customers, their orders and quotes, plus tasks, commissions and sales targets.

  • Returns and claims

    An RMA flow from the customer panel: statuses, messages, attachments, and a link to the order and the invoice. Built on an open source module for Mage-OS rather than on our own code.

  • Notifications

    An alert engine for the customer and the account manager: expiring quotes, a breached credit limit, inactivity, an abandoned cart.

  • B2B analytics

    Sales dashboards per customer, per product and per sales rep, plus trends, abandoned carts and search history.

  • Promotions and segments

    B2B customer segments, native price rules extended with the segment, banners and messages per segment, and a promotions page for signed-in customers.

  • Partner feeds

    XML and CSV feeds of products, stock and prices for partners, with access controlled by token or by IP address.

  • Home page segmentation

    A different home page and different content blocks per customer group: a distributor sees something other than wholesale, wholesale something other than retail.

  • GDPR and consents

    A versioned privacy notice, a register of its acknowledgements, separate optional consents and enforcement of the retention policy. Optional in the package, required in every rollout that falls under GDPR.

Architecture

The store presents the data, the ERP stays the owner of the truth

A wholesale customer also orders outside the platform: by phone, by e-mail, through a sales rep. So the credit balance, the invoices, the unit conversions and the order minimums have their owner in the accounting system, and the platform holds a projection of them. The input is a state rather than an increment, and writes are idempotent on the natural key, meaning the tax ID, the product code or the invoice number. A repeated message from the middleware never duplicates a record, which with queue-based integration is a requirement rather than an improvement.

The second rule concerns access to features. All the logic sits in services, and the storefront controller and the REST endpoint call the same service, so the interface and the API cannot drift apart in behaviour. Permissions are checked server-side: a customer endpoint returns only the data of the signed-in user company, and swapping an identifier in the address exposes nobody else’s data.

How data moves in a rollout

  1. ERP
  2. Maconnector
  3. Maco B2B on Mage-OS
  4. Hyvä storefront

Maconnector runs the exchange both ways: products, stock, prices, customers, discounts, orders, statuses and invoices. It has its own panel, monitoring and retries for failed messages, so a failed sync is an event somebody can look at rather than silence.

Integrations

The systems we connect the platform to most often

The exchange is run by Maconnector, our middleware. Product data can also arrive from a PIM system where the client uses one.

  • Comarch ERP XL
  • Comarch ERP Optima
  • Enova365
  • SAP S/4HANA
  • Microsoft Dynamics 365
  • Baselinker
  • Akeneo PIM
  • Pimcore

Choosing a model

Closed SaaS or a package on open source

Both roads deliver B2B features. The difference is what is left on the client side once the rollout ends.

A closed SaaS platform

  • the code belongs to the vendor, and migrating out can be impossible
  • the feature scope ends where the vendor plan ends
  • the subscription grows with the turnover of the store
  • one support desk and one supplier of changes
  • only the integrations that sit in the vendor catalogue

Maco B2B on Mage-OS

  • the code stays with the client, under an open source licence
  • every module can be extended or replaced with your own
  • the Maco B2B module licence is included in the rollout price
  • the team is replaceable: underneath it is standard Magento 2
  • REST API on every entity, attribute and action
  • ERP integration through Maconnector, with monitoring and retries

Rollout

Six steps from analysis to the first wholesale order

Every step ends in something that can be signed off. The longest part of the project is usually not the modules but getting the ERP data into a state you can sell on.

  1. Scope and data

    01 Pre-implementation analysis

    We agree the module scope, map the wholesale sales processes and write down the data the ERP has to supply. That document decides the timeline, not the number of modules.

  2. Repeatable set

    02 Baseline configuration

    We apply a repeatable set of settings: order statuses, catalogue and price visibility mode, the privacy notice and the retention policy for this rollout.

  3. Data exchange

    03 ERP integration

    Maconnector exchanges products, stock, prices, balances, invoices and order statuses. Writes are idempotent on the natural key, so a repeated message never creates a second record.

  4. Build

    04 Modules and storefront

    We install and configure the standard modules and the chosen optional ones, together with their Hyvä components. Every feature gets its REST endpoint at the same time.

  5. Acceptance

    05 Acceptance testing

    UAT scenarios on the client data, run with the people who will actually work in the platform: buyer, company administrator, sales rep, customer service.

  6. After launch

    06 Launch and beyond

    After go-live we add optional modules and further integrations. The package keeps compatibility with the latest stable Mage-OS release.

Complementary products

What comes alongside the package

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. The pricing module supplies the contract and the single entry point for reading a price, while 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 it 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.

Our rollouts end in a working platform

Read what our clients say

We've already had several large projects with external vendors, but the cooperation on Apteline with Macopedia was by far the best. The Macopedia team showed us what SCRUM really is and how to apply it in practice.
NEUCA Group logoProject Director
We confidently recommend Macopedia as experts in PIM system implementations. Akeneo's integration with SAP and data banks allowed us to create a complete database for product specifications and image files. The PIM implementation has significantly simplified our processes and eliminated unnecessary email communication.
Żabka logoProduct Owner
Macopedia offers the highest quality of its services, meets customer expectations, demonstrates innovative solutions and provides specialized advice of high business value. The professionalism of Macopedia's employees makes them quickly gain the trust of their clients. We are happy to recommend cooperation with this company to others, ourselves looking forward to maintaining business relations in the future.
LPP logoE-commerce Manager
Any client who is serious about their project will find Macopedia a good partner.
Raben Group logoDigital Marketing Manager
They are led by a very impressive technology management and a team of experienced developers who are very focused and knowledgeable. I was also impressed by their use of agile methodology and focus during Scrum Sprints.
Pearson logoeMarketing Manager
For almost a year I have been working with Macopedia on the MultiSport Zone (www.kartamultisport.pl). This is a very important project for us, as it is the first channel through which we have a chance to reach MultiSport card users directly. As a result, we depend on a comprehensive service and a reliable business partner.
Benefit Systems logoProduct Owner
We are very satisfied with the project's progress and results, and appreciate Macopedia's consultative support and expertise in modeling the target structure of the bicycle and accessories catalog. Knowledge, commitment and professionalism contributed to the successful implementation of PIM Akeneo in our organization.
Kross logoProject Manager

FAQ

Questions we get about Maco B2B

What is Maco B2B?
A B2B sales platform built on Mage-OS 3.x and Magento 2. The standard, always delivered in full, covers company accounts, contract pricing, trade credit, quick order, multiple carts, quoting, units of measure, invoices from the ERP and a sales rep panel. Extensions such as order approval or a mobile app for sales reps are added on request.
Does Magento not have B2B features natively?
It does not. Most of what appears online as Magento B2B belongs to the paid Adobe Commerce B2B. Those modules are absent from Magento Open Source and from Mage-OS, which we verified in the distribution manifest: company accounts, contract catalogues, quoting, quick order, approval workflow and trade credit are all missing. Maco B2B fills exactly that gap.
How does Maco B2B differ from Adobe Commerce B2B?
Adobe Commerce B2B needs a separate, paid Adobe licence. Maco B2B runs on Mage-OS, and the module licence is part of the platform rollout. The second difference is where the truth about the data lives. We take the credit balance from the accounting system as a state rather than calculating it in the store, because a wholesale customer also orders outside the platform. On top of that come things Adobe does not have: payment terms per customer, splitting an order by stock availability, several quotes in one order, and tax ID verification against the national register as a condition for completing registration.
Am I buying a licence for the modules?
The Maco B2B module licence is included in the rollout price. The code stays with the client and can be developed further with us or with anyone else, because underneath it is standard Magento 2.
Does Maco B2B work with Hyvä?
Yes. Every module with a storefront layer ships Hyvä Themes components, meaning Alpine.js and Tailwind CSS, with no Luma, RequireJS or Knockout. The checkout runs on Hyvä Checkout, whose one-off licence sits with the client.
Is everything available through the API?
Yes, through the Magento REST API. Every entity, every attribute added to a native entity, every user action and everything arriving from the ERP has its endpoint. A module without REST coverage does not pass our acceptance. We add GraphQL where it is genuinely needed, for example under a headless storefront.
Which ERP systems do you integrate with?
Most often Comarch ERP XL and Optima, Enova365, SAP S/4HANA and Microsoft Dynamics 365. The exchange is run by Maconnector, our middleware with a panel, monitoring and retries for failed messages. Product data can also come from Akeneo or Pimcore.
How long does a rollout take?
It depends on the scope and on how much data has to arrive from the ERP, which is usually the longest part of the project. The reference point for launching wholesale sales is twelve weeks in the packaged variant.
Can I take only part of the standard modules?
We deliver the standard in full, because the modules reference each other: company accounts are the foundation under pricing, the credit limit, lists and quoting. The choice concerns the optional modules, and those are quoted separately.
Can the whole store sit behind a login?
Yes. Catalogue and price visibility is one setting covering the whole package, per website: catalogue and prices open, catalogue open with prices after signing in, or everything behind a login with a list of pages reachable without an account. We check every channel for leaks while we are at it, the API and the feeds included, because hiding an element in the interface is not a safeguard.

We demo Maco B2B on a scenario from your sales, not on a feature list

The demo takes under an hour and we run it on a real customer with a credit limit, a contract price list and an order placed by product code. Afterwards you know what is native, what the package adds, and what needs data from your ERP.

Book a demo

Book a Maco B2B demo

Tell us what you sell and which system holds your customer records. We answer within one business day.

If you need an NDA, please email us first at sales@macopedia.com.