Prices per relationship
Customer groups and price lists, including tiers. Contract prices can live in Medusa or come live from the ERP if that is the source.
Service
A B2B webshop on Medusa
In B2B, the price is rarely the price on the shelf. A customer has an agreement, tiered pricing, a minimum order or a colleague who has to approve. Medusa has the building blocks for that. We put them together so your account team and your customer see the same reality.
At a glance
- Prices per relationship
- Companies and employees
- Quotes and approvals
- Assortment per customer
Custom quote after a free intro call
What we do
What is included
Companies and employees
A company with several buyers, roles and spending limits. We use Medusa's open-source B2B starter as a starting point and adapt the rules.
Quotes and approvals
Not every order is a shopping cart. Quotes, a manager's approval or an order that sales still adjusts: we build it when the process needs it.
Assortment per customer
Sometimes a dealer may see a different catalogue than an end customer. We keep sales channels and prices apart, so guests never see contract prices.
Who it is for
Who this fits
- Wholesalers and manufacturers with agreements per customer.
- Dealer networks where not everyone may see the same assortment or price.
- Teams that handle quotes by email today and want repeat orders in the shop.
- Companies whose ERP owns the price, where the shop has to show that price, not override it.
- B2B suppliers selling across several EU countries, VAT regimes and currencies.
Honest advice
When we advise against it
- A consumer brand with one recommended retail price and an occasional business customer.
- A procurement portal with punchout or requisitions, unless we explicitly scope it as custom work. That is not standard in Medusa.
Price
What determines the price
A custom quote after a free intro call. These factors determine the price, not a menu.
- Number of price lists and exceptions
- Ten contracts are manageable. Hundreds of tiers per item, with dates, are a different project.
- Where the price is born
- Prices managed in Medusa are different from prices that have to come from an ERP for every cart.
- Quote and approval flow
- A cart behind a login is smaller than a quote with messages, versions and an approval.
- Roles within the customer's company
- One buyer is simpler than employees with a limit, an admin and a finance role that may only view.
Process
The process
- 01
The real order path
We map how an order flows today: email, phone, portal, ERP. The shop should shorten that path, not become a second source of truth.
- 02
Pricing model
Which prices are public, which only after login, and which come from another system.
- 03
Build and pilot customers
We test with a few real accounts: does the right person see the right price, and can they order without calling the account team?
- 04
Rollout
Training for sales and customer service. They get the questions, not just the developer.
Insights
Further reading
From this service to the articles, and from each article back again.
- ArticleMagento (Adobe Commerce) vs Medusa: licence, upgrades and B2BMagento and Adobe Commerce compared with Medusa: licence, upgrades, hosting, three-year cost and B2B. Honest about where Adobe Commerce is stronger.Read more
- ArticleLightspeed vs Medusa: plan limits, B2B and the POSLightspeed eCom and Medusa compared on plans, variants, languages, B2B, transaction fees and three-year cost. With prices from lightspeedhq.nl on 5 November 2026.Read more
- ArticleShopify vs Medusa: costs, flexibility and when to choose whichShopify and Medusa compared on subscription, revenue fees, apps, hosting, three-year cost and B2B. Prices as of 5 November 2026, and honest about where Shopify wins.Read more
- All articlesPlatform comparisons and the migration guide, with sources.To the articles
Can customers see their own prices?
Yes. A logged-in customer in a customer group sees the price list for that group. Guests see the public price, or no price if you prefer.
Does Medusa support quotes and approvals?
Not as a checkbox in the base install. The open-source B2B starter adds company accounts, quotes and approvals. We use it and change the rules where your process differs.
Can prices come from our ERP?
Yes. If the ERP owns the contract price, we fetch it when needed or synchronise price lists. Which of the two depends on the API and on how often prices change.
Does it handle several countries and currencies?
Yes. Medusa works with regions, currencies, tax settings and sales channels, so one backend can serve several EU markets. How VAT and invoicing work per country is something we settle with you and your accountant before the build.
Does the shop work when someone is not allowed to order?
Yes. We can hide prices, block ordering until an account is approved, or show a request form instead of a checkout. We record that in the scope.
Free intro call
What is your challenge?
Twelve shops that need to become one, an ERP that sets the price, or a checkout that does not do what you want. Tell us in one call. You will hear honestly whether Medusa fits.
Based in Nijmegen, the Netherlands, working with companies across Europe. How we work with European teams.