When WooCommerce trade orders still arrive by email

Your retail customers order through the website. Your trade customers email a list of product codes, ask whether last month's prices still apply and wait for someone to confirm the total. Staff then enter the order by hand.

If that sounds familiar, the useful question is what your WooCommerce wholesale ordering process needs to handle before customers can reliably use it themselves. A trade discount is only part of the job.

I am Adam, the developer behind DawsonyWeb. When discussing improvements to a store, I would start with a real repeat order and follow it from the customer's request through to the information your team needs to fulfil it.

Write down what staff currently decide

The person handling trade orders may be applying rules that have never been written down. They know which account gets a particular price, which products must be ordered in packs and when a delivery needs a separate quote.

Those decisions belong in the brief. Otherwise, a new trade area can still leave customers emailing to ask whether the total is correct.

I would ask for a typical order and an awkward one, with private customer details removed. For each, I would want to know:

• Who is allowed to order on the trade account?
• Which price list applies, and are there individual agreements?
• Does quantity mean individual units, packs or cases?
• What must staff check before accepting the order?
• What happens after the customer submits it?

The aim is to make those decisions explicit before choosing a plugin or estimating custom work.

Separate account registration from trade approval

A new account should not automatically receive every benefit intended for an approved trade buyer. I would agree what a customer can see while an application is pending, who approves it and how the customer learns that access is ready.

The same discussion should cover existing customers. If an account changes category or stops trading with you, who updates its access? If several people order for one business, do they need separate logins and different permissions?

This is operational detail, but it affects the implementation. A simple approved-customer group and a company account with several buyers are different scopes.

Make pricing rules understandable before configuring them

I would ask you to describe the intended price for a few representative baskets. That gives us examples to test against, rather than relying on a setting that merely sounds right.

For instance, take a hypothetical buyer who has an agreed product price and also qualifies for a quantity discount. Should the quantity discount replace that price, apply to it or be ignored? The business needs to choose. The software should apply the agreed rule consistently.

Also decide how promotions interact with trade pricing. If customers are entitled to a retail coupon as well, include that case in the tests. If they are not, the basket should make the outcome clear rather than leaving them to ask staff.

Can a WooCommerce wholesale plugin handle this?

Often, an existing extension is worth assessing before building custom functionality. For example, the B2B for WooCommerce documentation describes registration approval, role-based pricing, quantity rules and quotation features. These are extension features, not a claim that every WooCommerce installation includes them.

I would compare a candidate extension with your written examples and your existing store. A feature being listed is the start of the assessment. It still needs to fit your products, checkout, other extensions and staff process.

If an extension meets most requirements, a focused addition may be enough. If several overlapping plugins are needed to approximate one rule, I would pause and review the approach before adding another dependency.

Make repeat ordering faster for the buyer

A trade customer ordering familiar stock may have different needs from a retail visitor browsing product photographs. I would ask how they identify products and build their usual order.

Possible improvements to scope include searching by product code, entering quantities against a concise product list or starting from a previous order. These are options to evaluate, not features every store needs.

Repeating an order also needs a clear response when something has changed. A product may no longer be available, its price may have changed or the previous quantity may no longer meet your ordering rules. The buyer should review those changes before submitting.

Decide whether submission creates an order or a request

Some trade purchases can proceed directly to checkout. Others need staff to confirm delivery or agree details first. I would keep that distinction visible to the customer.

If the customer is requesting a quote, say what will happen next. If they are placing an order, make the confirmation reflect what has actually been accepted. A button labelled “Place order” should not quietly begin a process the customer understands as something else.

Where payment arrangements differ by account, the approved arrangements should be part of the scope and testing. I would implement the rules your business has agreed, rather than inventing commercial terms during development.

Follow the order beyond checkout

The project is not finished when an order appears on screen. Your fulfilment or accounting process may need a customer reference, product codes, quantities and the agreed prices in a particular format.

I would trace one representative order through that handover. Can staff identify the trade account? Does the reference reach the place where it is needed? If an integration fails, how does someone discover it and recover the missing work?

This is where a seemingly small ordering change can reveal a separate integration requirement. It is better to identify that while scoping the work than after customers start using the new flow.

Test retail and trade journeys together

Before launch, I would agree a test set covering the customers who share the store:

• A visitor browsing without an account.
• A regular retail customer placing an order.
• A trade applicant whose access is still pending.
• An approved trade buyer with a typical basket.
• A buyer using an individual pricing agreement or an unusual quantity.

For each relevant case, I would check the displayed price, basket calculation, allowed actions and order confirmation against the agreed examples. Changes intended for trade buyers should also be checked for unintended effects on retail customers.

Start with the orders you keep entering by hand

You do not need to arrive with a finished wholesale specification. Send me a description of the orders customers currently email, what staff change before entering them and which parts cause the most back-and-forth.

I offer WooCommerce development, custom functionality and integrations. You work directly with me to establish whether configuration, an extension or a scoped piece of development is the sensible next step. My service pricing explains the ways we can start.

Still entering trade orders from email?Tell me how your trade customers order today. I can help scope a WooCommerce workflow that fits your pricing and fulfilment process.
Discuss trade ordering with Adam