Magento 2 E-Commerce Support for Magento 1? That hourglass ran out a while ago.

We build Magento 2 shops for business customers: contract prices, sub-accounts, approvals, quick ordering and ERP integration. So sales no longer fixes every order by hand.

Discuss your Magento project See Magento 2 modules
Hourglass with all the sand run through

Is Magento a fit?

A big catalog alone is no reason for Magento.

A fit if

  • every customer has their own prices, assortment or payment terms,
  • several people per company order, with their own rights and approval limits,
  • prices, stock and orders need to stay in sync with an ERP or PIM.

Probably not if

  • you need a public catalog with a standard checkout and nothing else,
  • nobody on your team or at a service partner can look after Magento.

In purchasing

The shop takes the order. Sales finishes it.

Without B2B features

  • Sales corrects prices after the order has come in.
  • Regular customers assemble the same items from scratch every time.
  • Approvals run by email, somewhere outside the shop.
  • A failed ERP export only shows up when the customer calls.

With Magento B2B

  • After login the customer sees their assortment and their price.
  • Paste part numbers or a CSV list and the cart is ready.
  • Every buyer has their own login under the company account. Orders above the limit go to approval first.
  • Exports run through a queue with retries. Errors are visible in the backend.

For almost all of this there are ready-made modules for Magento Open Source, for example Customer Specific Prices, Quick Order and Sublogin with Order Approval. If something already fits, we use it instead of rebuilding it. See Magento 2 modules

Data flows

Every data flow has an owner. And a plan for when it fails.

  • Prices and stock

    Come from the ERP by import, before the customer needs them. A broken record is set aside instead of stopping the whole run.

  • Orders

    Magento accepts the order right away and exports it afterwards. If the ERP is unreachable, it retries without creating duplicate orders.

  • Customer accounts

    Customer number, price group and payment terms come from the ERP or CRM. A fixed mapping defines which rights they become in the shop.

How we work

Purchasing first. Then the code.

  1. Map purchasing

    Customers, prices, roles, approvals and the exceptions sales solves by hand today.

  2. Agree on ownership

    Which data belongs to Magento, ERP, PIM or CRM, and what happens when one of them fails.

  3. Build whole flows

    Complete paths in one go, such as login to an order at contract price, each with tests.

  4. Rehearse the launch

    Migration, redirects, queues, monitoring and rollback run once on staging before going live.

Common questions

What should be clear before the quote.

Is Magento Open Source enough for B2B?
Often, yes. Customer prices, sub-accounts, quotes and quick ordering can be covered with individual modules. Adobe Commerce is worth a look if its B2B package and license model suit you better.
Should checkout read prices and stock live from the ERP?
Only if the business really needs it. For most data an import is more robust than making every page wait for the ERP.
Do we have to rebuild the whole shop?
Not necessarily. Often it pays more to stabilise the integrations, replace risky custom code and rebuild a few buying journeys.
What do you need for a first estimate?
Your current buying process, customer groups, price sources, ERP interfaces, catalog size and the exceptions sales handles by hand. That helps more than a list of desired pages.

Bring your pricing logic. Not your wish list.

Discuss your Magento project