30-Day Free Trial on Eligible Hosting Plans

Contact Info

106 Anne Rd, Knoxfield VIC 3180, Australia

+61 (03) 82023009

info@ninjaweb.com.au

Contact us
Recommended Services
Supported Scripts
WordPress
Joomla
Drupal
Magento
JavaScript
Angular
React
Node.js
Wholesale customers order case packs matched to a purchase order by a NinjaWeb operator at a loading dock

Your wholesale customers have accounts on the new website. They have seen the launch email. Some have even logged in. Then the next order arrives in the sales inbox, attached as the same spreadsheet they used before.

It is tempting to call that resistance to change. First, try placing their normal order yourself.

Can you see the agreed account price? Can you enter a case quantity without guessing whether the cart means bottles or cartons? Can you attach the purchase-order reference their accounts team requires? Does the result go to the correct delivery location under the account’s actual terms?

If staff must repair those details after checkout, the customer has not necessarily rejected a better process. They may have chosen the route that still gets the order right.

Follow one repeat order through the current site

Consider a fictional trade customer buying cleaning supplies. Their usual order is 48 bottles of one product, packed as four cases of 12. The supplier requires at least four cases for this order. The customer also needs their purchase-order reference recorded and wants delivery to a particular branch.

These are example rules, not a claim about any NinjaWeb client or a universal wholesale model. They make the gap between a consumer cart and a trade order visible:

Buyer needs Ambiguous retail behaviour Useful trade behaviour
Four cases containing 48 bottles A quantity box labelled only “Qty” Quantity explicitly means cases, with bottles per case and total units shown
The approved account price A public price and a note asking the buyer to contact sales The authorised account price with a clear unit basis
A four-case minimum The order submits and staff later ask for an amendment A clear explanation before submission when the quantity is below the rule
A purchase-order reference and branch Details buried in an optional comments box Dedicated fields carried through to the operational order record

Suppose the buyer enters three cases. The portal should explain that the order is below the example minimum and offer an appropriate next step. It should not silently increase the order to four, switch the unit to bottles or let a success message conceal a pending correction.

That single journey is a more useful starting brief than “We need a B2B website.” It identifies what the customer does repeatedly and which errors the interface must prevent.

The account changes the transaction

Wholesale is not always retail with a discount code. An account may determine the visible assortment, price list, delivery addresses, permitted payment method and approval process. Where those rules exist, the website needs to apply them consistently rather than leave the buyer to negotiate them again on every order.

Start by identifying the source of each rule. If account prices are maintained in a business system, decide how the portal receives updates and what it does when that connection is unavailable. A stale price displayed confidently can be worse than an honest request for confirmation.

Access control deserves equal attention. Logging in does not automatically establish permission to see every account’s prices or orders. The system must check account ownership and buyer permissions on the server, including when someone requests a record directly. Hiding a link in the menu is not sufficient protection.

Within an account, the person preparing an order may not be authorised to approve it. Where the business actually uses that separation, the portal should distinguish a saved draft, an order awaiting approval and an accepted order. Where it does not, adding a complicated approval chain simply creates friction.

The point is to represent your trading rules accurately. Do not buy a collection of enterprise features just because they sound appropriate for wholesale.

A reorder must survive an exception

A “Buy again” button is useful until something has changed. The old order may contain a discontinued product, a different case pack, an unavailable item or a price that no longer applies. Copying it blindly can create an order neither party intended.

Revalidate the current rules and show material changes before the buyer submits. Keep the familiar order useful without pretending yesterday’s terms are still guaranteed. If one line needs review, preserve the rest of the work instead of sending the customer back to an empty cart.

Three exception decisions belong in the brief:

  • Unavailable stock: can the buyer request a backorder, select an approved alternative or ask sales to confirm? Show which choice has actually been made.
  • Changed price or pack size: does the buyer see the difference and approve the revised quantity and amount before submission?
  • Account restriction: can the buyer save the order while an authorised person resolves the issue, with a clear explanation of its status?

A request for review is not an accepted order. The confirmation message should say what the supplier has received, what remains undecided and what the buyer can expect next. The sales team needs the same interpretation, otherwise the portal merely moves uncertainty from email into a dashboard.

There is a reasonable case for keeping the first version simple. If trade buyers use the same prices, pack sizes and checkout rules as everyone else, a straightforward store may be enough. If orders are rare and highly negotiated, a structured quote request may serve the business better than instant ordering. The extra system is justified by recurring rules and workload, not by the label “wholesale.”

Start with the email your team has to fix

Collect a small, anonymised sample of repeat orders and the corrections staff made before entering them. Separate missing information from genuine exceptions. A missing branch code may be solvable with a better field; a negotiated substitution still needs a decision.

Choose one common reorder journey and one willing account for a controlled pilot. Measure whether the buyer can complete the intended order, how often staff must correct it and which steps send them back to email. Compare equivalent orders rather than treating every login as success.

Those observations provide a defensible brief for E-Commerce Websites: the ordering interface, account behaviour and integrations have concrete jobs. Business Solutions covers the rules around them, including who owns price changes, exceptions and the final handover to fulfilment.

Keep an assisted route for the unusual order. The aim is not to ban email. It is to make the normal repeat purchase easier and more accurate online, so customers have a reason to use the portal without another reminder campaign.

Before asking customers to change their habits, make sure the website can complete the order they already know how to send.

Share this Post