Buying built for how trade works.
Company accounts, delegated approvals and negotiated pricing come together in one portal — every buyer sees their own catalogue and checks out without friction.
A B2B eCommerce agency building trade portals on Adobe Commerce (Magento) — company accounts, contract pricing, quote-to-order. Over 100,000 trade customers buy through what we have built.
Trade buying is not retail buying with a login. It is negotiated prices, approval chains, credit limits, reorders from last year's list, and a rep who needs to place the order on the customer's behalf. We have spent 15 years building that on Magento and Adobe Commerce — 25+ B2B projects, 100k+ trade customers, £1.3bn processed. Topps Tiles doubled its trade orders on the back of it.
Hierarchical company structures with role-based permissions and approval workflows for complex organisations.
Personalised catalogues with customer-specific pricing, availability and product visibility by contract.
Tier, contract and volume pricing with dynamic rules applied by customer segment.
A complete quote-to-order workflow with negotiation and seamless conversion to purchase orders.
Quick order, CSV import, requisition lists and reorder tools for high-volume purchasing.
Clean integration with ERP, CRM and PIM systems for unified B2B operations.
Company accounts, delegated approvals and negotiated pricing come together in one portal — every buyer sees their own catalogue and checks out without friction.
Quote-to-order workflows, CSV upload and requisition lists handle high-volume purchasing, while ERP and PIM integration keeps stock, pricing and orders in sync.
Adobe Commerce ships with a genuine B2B module rather than a bolt-on, and it covers more than most people expect:
Company accounts with buyer hierarchies, roles and delegated approval limits
Shared catalogues so each customer sees only their products, at their prices
Contract pricing including customer-specific price lists and tiered volume breaks
Quote-to-order — buyers request a quote, you negotiate, the agreed price becomes a cart
Requisition lists and CSV upload for high-volume repeat ordering
Credit management with configurable payment terms
What still needs building, every time, is the join to your existing systems. Trade pricing usually lives in an ERP, not in the storefront. Stock is real and finite. Credit limits change daily. The B2B module is the easy half; making it agree with the systems your business already runs on is the half that decides whether the project works.
That is where the 15 years go. Not into the features list — into the integration layer underneath it.
Most of our B2B clients are not purely B2B. They sell to trade and to the public, often from the same catalogue and the same warehouse, and they do not want two platforms to maintain.
Adobe Commerce handles that on one installation: separate storefronts, separate pricing, separate checkout rules, one back end. The trade customer signs in and sees their negotiated prices and their approval chain. The retail customer sees the standard catalogue. Stock is shared, so nothing oversells.
Topps Tiles is the clearest example — 332 stores, trade and retail, online and in-store unified. Trade orders doubled and customer revenue rose 30%. Adobe wrote it up as one of their own customer success stories, and it won the Experience Maker "The Mastermind" award. We are a little biased, but we think the interesting part is that none of it required a second platform.
Most platform decisions go wrong because someone assumed B2B is B2C with a login. These are the eight places the two genuinely diverge, and each one is a feature you either have or end up building.
| Feature | Standard B2C | Adobe Commerce B2B |
|---|---|---|
| Who buys | One person, one account | A company, with buyers, roles and approvers |
| Pricing | One price list for everyone | Negotiated per customer, with volume tiers |
| Catalogue | Everyone sees everything | Shared catalogues — each customer sees their own |
| Approval | None — you check out | Spend limits and delegated approval chains |
| Getting to a price | Listed price, add to basket | Quote-to-order — request, negotiate, convert |
| Repeat ordering | Re-browse and re-add | Requisition lists, reorder, CSV upload |
| Payment | Card at checkout | Credit accounts with agreed payment terms |
| Ordering on behalf | Not supported | Sales reps can order for their customers |
You can run both from one Adobe Commerce installation — separate storefronts and pricing rules, shared catalogue and stock. Most of our clients do exactly that.
The best measure of our success is the long-term partnerships we build.
Working with Tom&Co has been like an extension to our own business. Their collaborative approach and use of headless technology has increased productivity and delivered above and beyond our expectations. They are a key partner of ours.
Award-winning digital experiences crafted for ambitious brands. We don't just build websites; we engineer growth.
View full portfolioWhat trade businesses ask us first
Yes — all three are native to Adobe Commerce rather than extensions. Shared catalogues restrict what each company sees and set their prices; quote-to-order lets a buyer request a price, negotiate it and convert the agreed figure straight into a cart; and account-based pricing supports customer-specific price lists alongside tiered volume breaks. Company accounts add buyer roles and approval limits on top. The work in a real project is usually not enabling these — it is wiring them to the ERP where your trade pricing actually lives.
That is precisely the case it is built for. One back end can run many storefronts with their own catalogues, pricing and currencies, and the B2B module handles the account structures underneath. If your catalogue is small and your pricing is the same for everyone, it is more platform than you need.
The native B2B module, in almost every case. Third-party trade portals were common when Magento's own B2B support was thin; since Adobe Commerce absorbed it, bolting on a separate portal usually means maintaining two sources of truth for pricing. The exception is where you need something genuinely unusual — a configurator, a bespoke approval model — and we would build that against the native module rather than replacing it.
Yes, and for most of our clients they do. Separate storefronts, separate pricing rules, shared catalogue and shared stock, one platform to maintain.
For serious B2B, Adobe Commerce. The B2B module — company accounts, shared catalogues, quotes, requisition lists — is a commercial feature. Building the equivalent on Open Source is possible and we have seen it attempted; it generally costs more than the licence and is yours to maintain forever.
Four to eight months, and the variable is almost always integration. A trade portal talking to one clean ERP is quick. One talking to a legacy pricing system, a separate stock system and a credit-control spreadsheet is not, and we would rather find that out in discovery than in month five.
Have a word with our strategists about an Adobe Commerce B2B build that fits how you actually trade, here and overseas.
Let's Talk