ContactBook a call

Industries/ Wholesale/ Trade ordering portals

A B2B ordering portal that knows each buyer's price, pack and terms

Each customer logs in to their own order pad: contract prices, pack sizes, minimums, delivery days and the credit left on the account. They start from last week's order, submit it at whatever hour suits them, and it reaches your ERP checked and ready to pick.

A cafe owner, a man in his thirties with a beard and a denim apron, behind the counter placing a supplier order on a tablet, shelves of coffee bags and paper cups behind.
Used by
Trade buyers, your sales office and credit control
Takes the place of
Emailed order lists, voicemails and PDF price lists
Connects to
Your ERP or accounts package, stock and card payments
Built with
Our online stores service

Where it hurts today

A normal week, before it exists

After service, a restaurant's head chef counts the walk-in and types tomorrow's order into an email from memory, using their own names for things, such as 'the big mayo' or 'chips, usual'. They don't know whether a line is in stock, what they will pay this week, or whether anyone has seen the order, so they leave a voicemail too.

Next morning your sales office opens an inbox full of these. Someone works out that 'the big mayo' means the 10 litre tub, checks the contract price in the pricing spreadsheet, checks the account isn't on stop, and keys it all into the ERP before the first van's cut-off. Every guess risks a wrong item, a credit note and an annoyed chef.

A consumer web shop doesn't fix this. It shows one price to everyone, takes a card at checkout and knows nothing about pack sizes, delivery routes or account terms. An ERP's own customer web module may show the right prices but feel like the back office: slow, awkward on a phone, with no quick reorder. Buyers try it once and go back to email.

What it does

Trade ordering portals, feature by feature

What the portal does for the buyer and your office, and what a consumer shop cannot.

  1. 01

    Customer-specific pricing

    Every product shows the price this account pays: its contract price, a volume break or a current promotion, worked out by the same rules your office uses. Buyers never see a list price they don't pay, and a change shows at their next login.

  2. 02

    Minimum order quantities and pack sizes

    Quantities step in whole cases or outers, and the minimum for each line and for free delivery shows before checkout, not after. If a buyer types 7 of a line sold in sixes, the portal asks whether they meant one case or two.

  3. 03

    Order pads and quick reorder

    Each account gets an order pad built from what it actually buys, laid out in the order the buyer counts stock. They can repeat last week's order with a few changes, or save regular orders by name, such as the Friday top-up.

  4. 04

    Delivery days and order cut-offs

    The portal knows which route serves each delivery address and when the next van's cut-off is. A buyer ordering at 9pm sees which day the order will arrive, and orders placed after the cut-off move to the next delivery day, with the buyer told before they submit.

  5. 05

    Credit limit checks at checkout

    When a buyer submits, the account's credit limit and overdue balance are read from your accounts system. Orders within terms go straight through. One that would breach the limit is held, the buyer sees a plain message, and your credit controller decides with the figures in front of them.

  6. 06

    Multi-site accounts and approvals

    A group with several sites can give each site manager a login that orders to that site's address, while the group buyer sees every order and approves anything above a value the group sets. Invoices follow the account's setup in your ERP.

A day with it

How the day runs instead

A normal weekday with the portal running, from a buyer's late order to the van leaving the yard.

  1. 9.40pm
    Restaurant head chef

    After service, the chef opens the order pad on a phone and repeats last Thursday's order: three drums of oil instead of two, no cream. The portal confirms tomorrow's delivery, because the cut-off is 11pm.

  2. 11.05pm
    The portal

    The cut-off passes. Tonight's orders have been checked against credit and stock, and most are already in the ERP as sales orders. One account has an invoice sixty days overdue, so its order waits in the credit queue.

  3. 6.30am
    Warehouse supervisor

    The pick list prints from the ERP as it always has, with the overnight portal orders on it and nothing keyed by hand. One line is short, so its buyer gets a message before the van is loaded, not a gap on the delivery note.

  4. 8.45am
    Credit controller

    Opens the held order and sees the overdue invoice beside the customer's payment history. A quick call, a promise of payment by Friday, and the order is released for the late route. The decision and the note are saved against the account.

  5. Afternoon
    Area sales rep

    With no orders to key, the rep checks which regulars haven't ordered this week and calls the two whose usual order is missing. One has moved part of its order to another supplier, which is worth a visit.

What it connects to

Works with what you already run

The portal sits in front of systems you already run. It reads from them and writes to them, and does not try to become them.

  • ERP or accounts package

    Customers, products, stock and account balances come from your ERP, for example Sage, NetSuite or Business Central where it offers an API. Orders go back as sales orders in the form your warehouse already picks from.

  • Pricing rules

    Contract prices, customer groups, volume breaks and promotions, read from wherever they live today or from a pricing tool, with one place in charge of every price a buyer sees.

  • Card payments

    For new accounts or cash-with-order customers, card details go straight from the buyer's browser to a payment provider, for example Stripe or Adyen. The portal only records whether the payment succeeded.

  • Email and SMS

    Order confirmations, cut-off reminders, short-stock messages and held-order notices, sent from your own domain so buyers recognise them, with replies going to the sales office inbox rather than a dead address.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Logins for a first group of willing accounts, each invited by a link
  • Account-specific prices and pack sizes, read from your ERP or price file
  • An order pad per account with reorder from the last order
  • Credit and overdue checks at submission, with held orders queued for a person
  • Orders written into your ERP as sales orders, with any failure alerted

Once it is in use

  • Group logins with site buyers and head office approval
  • Agreed substitutes offered when a line is short or discontinued
  • Invoices, statements and signed delivery notes to download
  • PunchOut ordering for large accounts that buy through procurement systems

Buyer's guide

Before you commission one

Four decisions worth making before anyone builds a portal. Getting them right matters more than any single feature.

  1. 01

    Platform, ERP module or built for you

    If your prices fit a few simple tiers, a B2B e-commerce platform's wholesale features or your ERP's own customer portal may be the better buy, and we will say so. A portal built for you earns its place when prices follow contracts and volume breaks, credit checks run against your ERP, or B2B plan and app fees outgrow owning one.

  2. 02

    What to gather first

    Your price list in every form it really exists, including the overrides. A product file with pack sizes and minimums. Your delivery routes and cut-off times. A list of the accounts most likely to try it first, and a dozen of their real orders, which tell us more than any requirements document.

  3. 03

    Who should own it

    Usually the sales or customer service manager, not IT, because the portal is a sales channel. They decide which accounts are invited, answer buyers' first questions and judge when a held order should be released. Finance owns the credit rules and IT owns the ERP connection, but one named person should own the portal's day-to-day running.

  4. 04

    How you will know it is working

    Watch which accounts order through it without being reminded, how many orders still arrive by email from accounts that have logins, how often held orders really needed holding, and how many pricing queries and credit notes your office raises. Ask the reps too, because they hear first whether buyers like it.

Terms worth knowing

The words you will meet

Customer-specific pricing
Prices that depend on who is logged in: a contract price for one account, a group discount for another, a volume break for a third. It is the main thing that separates a trade portal from a consumer shop, and the first thing to test before any buyer sees it.
PunchOut catalogue
A way for large customers to shop your catalogue from inside their own procurement system. The buyer clicks through, fills a basket on your site, and the basket returns to their system for approval as a purchase order. It usually runs on cXML, and is worth asking about if big accounts buy that way.
PCI DSS
The card industry's security standard. Under version 4.0.1, the last of its future-dated requirements became mandatory on 31 March 2025. When card details go straight to your payment provider, most of it sits with them, but your payment page still carries duties, which we work through with your provider.

Handled with care

The details that matter here

A portal puts your prices and your customers' accounts online. These are the parts we treat with the most care.

  • Prices behind the login, and only there

    Product pages that search engines can see show no trade prices at all. We set up caching so logged-in pages are kept per account, test accounts on different contracts side by side before launch, and mark any price list download with the account it was made for.

  • Who in the customer's business can order

    Buyers move on, and a former kitchen manager with a working login can still order on the account. We give each customer an admin who adds and removes their own users, offer passkeys or one-time codes instead of shared passwords, and record which person placed every order.

  • Holds, not silent refusals

    An order that fails a credit or stock check is never simply rejected. We design the hold so the buyer is told in plain words what happens next, your team sees why, and the release or cancel decision is recorded with a name and time.

  • Usable on a phone after a long shift

    We design to WCAG 2.2 level AA, including its minimum tap target size and sign-in that works with password managers, and test the order pad with real buyers. If consumers can also buy from you in the EU, the European Accessibility Act has applied since 28 June 2025, and we plan for it with you.

Guides

Worth reading first

Questions

What buyers ask first

Can a B2B portal show each customer only their own prices?

Yes, and it is the first thing we test. Prices are worked out on the server for the logged-in account, so a buyer's page contains only their own figures, and public product pages show none. Before launch we compare accounts on different contracts side by side, and every later price list change is recorded with who made it.

Can sales staff place orders on behalf of customers in a B2B portal?

Yes. Office staff can open any account and place an order as that customer, with the same prices, minimums and credit checks, and the order is marked as entered by staff. Phone orders then follow the same rules as portal orders, and a rep can walk a buyer through their first order during a visit.

Should we use our ERP's customer portal instead?

If your buyers use it and it shows the right prices, keep it, and we will tell you so. ERP web modules often handle the data well and the buying badly: slow pages, no order pad, no quick reorder, little that works on a phone. In that case we can build the portal in front and let the ERP keep doing what it does well.

Does a B2B ordering portal support PunchOut?

It can, where your customers need it. Some larger buyers can only order through a procurement platform, and a PunchOut connection lets them open your portal from inside it, see their contract prices and send the basket back for approval. The approved purchase order then arrives like any other order. We build it for the accounts that ask, because each procurement platform needs its own setup.

Who owns a custom B2B portal and its data?

You do. The code, the hosting account and the data about your customers and their orders belong to your business. We document how the portal is built and run, so another developer could take it over. If you want us to keep looking after it after launch, we can, but nothing is set up so that only we can run it.

Show us how your buyers order today

Send us a few real orders as they arrive, emails and voicemail notes included, and a sense of how your prices are set. We will reply within 48 hours with what a portal would look like for your accounts.

More for wholesale

What else we build for wholesale and b2b

The same idea, in other sectors