Your Best Customers Are Still Ordering by Phone

Illustration of a wholesale dispatch area in early morning light, with a long timber packing bench and rows of crates and cartons packed and waiting for collection, each carrying a tag with abstract marks, and a roller door open to soft daylight

It’s Sunday night, and the operations manager of a small café group is placing the week’s order with their food wholesaler. The wholesaler has a website, and a decent one. The prices on it are list prices, not the ones the group pays. There’s no way to repeat last week’s order, and the checkout wants a credit card although the account has been on thirty-day terms for six years. So on Monday morning the order goes in by email, as a spreadsheet, and someone at the wholesaler types it in.

Versions of that happen in plenty of industries. A fit-out company furnishing a forty-desk office orders by email because the supplier’s site only shows retail prices and the contract pricing lives in a PDF. Retailers restocking from a distributor often find it quicker to read forty product codes down the phone than to find each one on the website. On building sites, plenty of supervisors still ring the electrical wholesaler at seven.

Each of those suppliers paid for a website, and for the customers who matter most to the business, it’s become a catalogue they browse before picking up the phone. The usual cause is that the site was built as a retail store, and business customers buy in a completely different way.

How is B2B ecommerce different from retail?

B2B ecommerce means selling online to other businesses, and businesses buy differently from members of the public. They order much the same things again and again, at prices negotiated for their account, on credit terms, and often with several people involved in a single order. A retail store platform is designed around a one-off shopper who finds a product, pays the list price by card and goes away.

That difference shapes almost every screen. A retail store is designed to get someone browsing, while a business customer usually knows exactly what they want and would like to spend as little time as possible getting it.

What do business customers need from a website?

Most of it comes down to five things, and the people who take orders by phone and email could list all of them from memory.

Their own prices. A logged-in customer should see the price their account pays: their price list, any contract pricing on particular lines, and the discount that applies at their order quantity. Those rules usually live in the accounting or ERP system already, and the website should read them from there. Keeping a second copy of the pricing in the website means someone has to update both, and sooner or later the two disagree in front of a customer.

Fast reordering. Most business orders are repeats or close to it. Order history with a button to order the same again, saved lists for each venue, project or store, and a quick-order box where someone can type product codes or paste a list will move more orders online than any amount of product photography. These need to work on a phone as well as a desktop, because plenty of orders are placed from a kitchen, a warehouse floor or a building site.

Buying on account. Business customers expect to order on their credit terms, enter their own purchase order number, and receive an invoice that matches what their accounts team is expecting. The website should check the order against the account’s credit limit, and the invoice should land in your accounting system without anyone re-keying it. Card payment stays available for customers without an account.

More than one person per account. In a café group, the head chef may put the order together, the operations manager may approve it, and the accounts team may pay it. Each of those people needs their own login under the company’s account, with limits on what they can spend or approve. Orders often go to a different address each time, a particular venue or a project site, with notes like “deliveries via the laneway before 10am”.

Stock and delivery that match reality. Which warehouse has the item, what the minimum order quantity is, what the cut-off time is for next-day delivery. Retail stores tend to show “in stock” or “out of stock”, which is not enough for someone planning next week’s menu or tomorrow’s install.

Can Shopify or WooCommerce handle B2B?

Partly, and better than they used to. The larger platforms have added B2B features in recent years, including company accounts, customer-specific catalogues and payment terms. Shopify’s fuller set sits on its higher plans, and WooCommerce relies on plugins. For a business whose account pricing is a simple percentage off the list price, with a modest catalogue, a platform with those features switched on may be all it needs.

They struggle when the business’s own systems are doing the real work. If prices are calculated in the ERP and change daily, if credit limits need checking against the accounting system at the moment of ordering, or if products are configured or quoted rather than picked off a shelf, the platform has to be extended. That can mean a custom middle layer that keeps the store and the back office in step, or a separate ordering portal built beside the retail store. We describe one trade supplier whose platform was customised for its pricing, and what that cost, in Pick the Problem Before You Pick the Platform.

How the choice gets made between a platform as it comes, a platform with custom work around it, or a store built for the job is set out on our custom ecommerce development page. It depends mostly on your pricing rules and the systems the store has to agree with, which is why we look at those first.

Should business and retail customers share one store?

Usually they share one catalogue, and sometimes one store. A retail store that shows account prices after login works well when the two groups buy mostly the same products in similar ways.

When they don’t, a separate ordering portal fed from the same product data is often cleaner. A buyer restocking a shop wants a dense table of product codes, pack sizes and their own price, which would look strange on a retail page built around a large lifestyle photo. Keeping one source of product data and two front ends means each can be designed for the people using it, without anyone updating a product twice.

Where should a supplier start?

Start with the phone and email orders. Ask the people who take them, and your sales reps, what the twenty most common orders look like, and look at your order data for how many account orders are repeats or near repeats. The answer usually points to two features: account pricing and fast reordering. Those two move more orders online than anything else, and they’re where the first stage of the work should go.

Then decide how you’ll measure it. The useful number is the share of account orders placed online, tracked month by month. If it isn’t moving, ask the customers why. A business customer who still phones after a new portal has launched will usually tell you exactly what’s missing, often in a single sentence.

The work involved in connecting a store to the systems behind it is covered in Why Don’t My Systems Talk to Each Other?, and it’s worth reading before talking to any developer about online ordering for business customers, because the connections are usually where the effort goes.

Still taking most account orders by phone or email?

Contact our team to work out what your business customers need from your website.


Simon Paul is a Business Solutions and Technology Specialist at Code Brewery who’s spent 25+ years turning business ideas into software that actually earns its keep. He has watched a lot of sales teams re-type orders that the customer could have placed in two taps. Reach out to Simon to talk through moving your business customers’ ordering online.