Skip to content

Solution

B2B ecommerce for manufacturers and distributors

Customer-specific pricing, quotes, bulk ordering, approvals and ERP integration in a self-serve portal your buyers will actually use.

Risks removed
3
Delivery phases
4
Deliverables you keep
4

The situation

Orders still arrive by email, phone and spreadsheet. Your sales team re-keys them into the ERP, pricing lives in people's heads, and buyers ask why they can't just reorder online.

Who it’s for

  • 01Manufacturers and distributors selling to trade accounts
  • 02Businesses with contract, tiered or customer-specific pricing
  • 03Teams where the ERP is the system of record

Risks we remove

What usually goes wrong on this kind of project, and the fix we put in place for each.

  • Risk 01

    Wrong prices shown to buyers

    How we remove it. Pricing read from the ERP as the single source of truth, with automated checks per account.

  • Risk 02

    Low portal adoption

    How we remove it. Quick order, CSV upload and reorder built around how your buyers already work.

  • Risk 03

    Sync failures

    How we remove it. Queued, retried integrations with alerts before a buyer notices.

How we approach it

Each phase ends with something you can review before the next one starts.

  1. Phase 1 of 4

    Map

    Document account structures, pricing rules and the order flow your ERP expects.

  2. Phase 2 of 4

    Design

    Design the portal around repeat ordering and approvals, tested with real buyers.

  3. Phase 3 of 4

    Connect

    Build the ERP sync for products, prices, stock, orders and invoices.

  4. Phase 4 of 4

    Roll out

    Onboard accounts in waves, measure online order share and fix friction.

What you get

Everything below is handed over in your name: code, accounts, documentation and credentials.

Handover manifest

4 of 4 handed over

  1. 01Company accounts with roles, permissions and approvalsYours
  2. 02Customer pricing, quotes and purchase ordersYours
  3. 03Quick order, CSV upload and order historyYours
  4. 04ERP integration with monitoringYours

Repositories, accounts, licences and credentials are created in your organisation from day one.

Typical stack

Chosen at architecture, not by habit.

Typical stack: Medusa.js, Next.js, Node.js, ERP APIs, PostgreSQL.

Questions we’re asked

Can buyers see their own negotiated prices?

Yes. Prices are resolved per company account, including tiers, contracts and volume breaks.

Which ERPs can you connect?

We integrate through the ERP's API or middleware. Tell us your system in the review and we'll say plainly whether we've connected it before.

Who owns the code?

You do. Repositories live in your organisation from the first commit, and every licence, credential and deployment is in your name.

Do you sign an NDA before we share details?

Yes. We sign a mutual NDA before any discovery call where you share architecture, data or commercial details.

Book an architecture review

A 60-minute session with a senior architect. We review your current platform, integrations and growth plans, then send a written summary of risks and options.

  • For companies with a real platform decision coming up
  • NDA signed before we talk details
  • The written summary is yours to keep
Your project

What are you planning?

Where you are today

Where are you today?

Platform Optional
Annual online revenue Optional
When do you need to decide? Optional
Your details

A senior engineer replies within one working day.