Menu
Free consultation, no commitment.Book a call

Maco B2B · on Magento 2

The B2B sales platform for wholesalers, manufacturers and distributors

A ready wholesale store connected to your ERP. Your customers order in it themselves: at their own prices, on their own payment terms, with the invoices from your ERP to hand. Your sales reps stop retyping orders from e-mails.

17 B2B features as standard · ERP integration · licence included in the rollout price

What Maco B2B is

What Maco B2B is

A set of 17 wholesale selling features on Magento 2, which we roll out together with the store and the integration with your ERP.

  • A ready wholesale store

    Company accounts, customer prices, trade credit, quick order, quotes and the sales rep panel work from day one. In every rollout we fit them to your processes and data.

  • Connected to your ERP

    Prices, stock, credit limits, invoices and order statuses come from the ERP through Maconnector, our middleware. An order from the store reaches the ERP without retyping.

  • On Magento 2, with the code in your hands

    The platform runs on Magento 2 and Mage-OS. The Maco B2B licence is included in the rollout price and the code stays with you, so you develop it with us or with another team.

Who it is for

Who Maco B2B is for

Wholesalers, manufacturers and distributors who sell to companies. It works best in four situations.

  • 01

    Orders arrive by e-mail and phone

    Sales reps retype them into the ERP, and the customer waits for a confirmation and calls to ask about delivery.

  • 02

    Every customer has their own prices

    Individual price lists, discounts and tier prices live in the ERP, and the customer learns them from a sales rep or only on the invoice.

  • 03

    You sell on payment terms

    Credit limits and overdue items are watched by accounting, and the customer learns about a block only when ordering.

  • 04

    You have an ERP and want to keep it

    Comarch ERP XL or Optima, enova365, SAP S/4HANA, Microsoft Dynamics 365. The store works on its data.

Prices and catalogue

Every customer sees their own price

The price from their company’s price list, tier prices and the customer’s own product codes.

They type pieces, cartons or pallets, and the store rounds up to a full pack.

  • Individual price lists from the ERP
  • Units of measure and order minimums
  • Datasheets and certificates on the product
Product page with the company price, tier prices and the buyer’s own product code

Ordering

An order from a pasted list

The customer pastes a list from an e-mail or uploads a spreadsheet. The store recognises your codes, the customer’s own codes and barcodes.

Lines it is not sure about are shown for confirmation, and the rest go to the cart.

  • Quick order from a list or a spreadsheet
  • A separate cart for every site or job
  • Repeat an order from the history
A pasted product list recognised by company code, seller code and barcode

Quotes

Price negotiation in the store

The customer asks for a better price from the cart or the product page. The account manager answers in the panel with a new version of the quote.

A discount above the rep’s threshold is approved by the manager, and an accepted quote turns into an order.

  • Quote versions and counter-proposals
  • Approval of discounts above a threshold
  • One number from request to order
Quote from a sales rep with the list price, the quote price, the discount and the conversation

Payments

Payment terms and trade credit at checkout

Every company’s payment term and credit limit come from the ERP.

Before placing the order the customer sees how much credit is left and enters their own purchase order number.

  • A payment term for every customer
  • Credit limit from the ERP
  • PayU, Przelewy24 and Tpay gateways
Checkout: bank transfer with a payment term and purchase against the credit limit with the available amount

Settlements

Invoices and overdue items on the customer’s dashboard

After signing in the customer sees the amount to pay, the overdue documents and the available limit.

Invoices from the ERP, with the KSeF number and a QR code, sit on the orders.

  • Invoices and corrections from the ERP
  • Settlements and overdue documents
  • Delivery notes on the order
Buyer dashboard: credit limit, settlements with overdue items, tasks and recent orders

Sales rep panel

The sales rep sees their customers and their requests

The account manager’s panel holds their portfolio: customers, their orders, quotes to price and finances.

They can place an order on the customer’s behalf, at the customer’s price, and hand the portfolio to a stand-in for a holiday.

  • The account manager’s portfolio
  • A queue of requests to price
  • Ordering on the customer’s behalf
Admin panel: request-for-quote queue

Features in the standard

Every feature of Maco B2B, no tiers

We do not split the platform into Starter, Standard and Premium, because the features stand on one another. Each has its own page with a description, a worked example from a wholesaler and questions. Pick a role to see which features are its everyday tools.

Show features for a role 17

Integrations

The ERP systems we connect Maco B2B to

The exchange is run by Maconnector, our middleware: products, stock, prices, customers, orders, statuses and invoices, both ways.

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

Cost and time

What a rollout costs and how long it takes

  • Licence included in the rollout

    The Maco B2B licence is included in the rollout price. Its cost does not grow with the store’s turnover.

  • The integration sets the price

    The cost depends most on the scope of ERP data and the extensions you choose. You get the quote after the pre-implementation analysis.

  • About twelve weeks

    That is the reference for starting wholesale sales in the package variant. Preparing the ERP data usually takes longest.

Rollout

Six steps from analysis to the start of selling

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

  1. Scope and data

    01 Pre-implementation analysis

    We map the wholesale sales processes, pick the extensions and write down the data the ERP has to supply. That document decides the timeline.

  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 the rollout.

  3. Data exchange

    03 ERP integration

    Maconnector exchanges products, stock, prices, balances, invoices and order statuses. A repeated message never creates a second record, because writes go by tax ID, code or invoice number.

  4. Build

    04 Platform and store

    We configure Maco B2B and the chosen extensions, together with the Hyvä storefront in your company’s identity.

  5. Acceptance

    05 Acceptance testing

    Acceptance scenarios on the client data, with the people who will work in the platform: buyer, company administrator, account manager, customer service.

  6. After launch

    06 Launch and beyond

    After go-live we add extensions and further integrations. Maco B2B keeps compatibility with the latest stable Mage-OS release.

Extensions

Added on request

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

  • Order approval
  • File area
  • Sales rep mobile app
  • Returns and claims
  • Notifications
  • B2B analytics
  • Promotions and segments
  • Partner feeds
  • Home page per group
  • GDPR and consents

Technical information for the IT team

Architecture, the data flow through Maconnector, the ERP systems we connect the platform to, and the comparison with closed SaaS. A separate page for the person who will run it.

Macopedia in numbers

2012
delivering e-commerce since
100+
projects delivered
50+
e-commerce clients
40+
specialists on the team

What our clients say

Read what our clients say

FAQ

Questions we get about Maco B2B

What is Maco B2B?
A B2B sales platform built on Magento 2 and Mage-OS. The standard, always delivered in full, covers company accounts, registration with tax ID verification, customer pricing, trade credit, quick order, multiple carts, quoting, B2B payments and shipping, units of measure, invoices from the ERP and a sales rep panel. Extensions such as order approval or a mobile app for sales reps come 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. Magento Open Source and Mage-OS lack, among other things, company accounts, prices per customer, quoting, quick order, trade credit and order approval. Maco B2B fills exactly that gap, and what the platform can do alone we configure instead of rewriting.
How does Maco B2B differ from Adobe Commerce B2B?
Adobe Commerce B2B needs a separate, paid Adobe licence. Maco B2B stands on Mage-OS, and the licence is part of the platform rollout price. The second difference is where the truth about the data lives: the balance, invoices and payment terms come from the ERP, because a customer also buys outside the store. On top of that come things Adobe does not have: a payment term per customer, splitting an order by stock availability, several quotes in one order, and the tax ID checked in the national register as a condition of registration.
Does my sales rep get their own panel?
Yes, in the standard. The account manager sees only their portfolio in the panel: customers, their orders, quotes and finances. They can order on a customer’s behalf, price a request from the queue and hand the portfolio over for a holiday. The same panel on a phone is an extension.
Do I pay separately for a licence?
No. The Maco B2B licence is included in the platform 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. The whole Maco B2B store stands on Hyvä Themes, a fast storefront on Alpine.js and Tailwind CSS. The checkout runs on Hyvä Checkout, which has a one-off licence on the client’s side.
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 all data arriving from the ERP has an endpoint that calls the same service as the store. 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 come from the ERP, which is usually the longest part of the project. The reference point for starting wholesale sales is twelve weeks in the packaged variant.
Does the store issue invoices to the national e-invoicing system?
No, and it does not have to. Your ERP issues the invoice and sends it to KSeF, the Polish national e-invoicing system, and the store shows it to the customer on the order, with the KSeF number and a QR code on the printout.
Can I take only part of the features?
We deliver the standard in full, because the features stand on one another: the company account is the foundation under prices, the credit limit, carts and quoting. The choice concerns the extensions, and those we quote separately.
Can the whole store sit behind a login?
Yes. Catalogue and price visibility is one setting 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.

Book a Maco B2B demo on data from your sales

The demo takes under an hour and we run it on a customer with a credit limit, an individual price and an order from a list. Afterwards you know what you get at once and what needs data from your ERP.

Demo request

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.

Prefer to talk?

Beata Drozdowicz

Lead Project Manager

Call or email us. We reply within one business day.