A trade customer and a retail customer look identical to a website until the moment they try to buy. The retail visitor wants a price, a photo and a delivery date. The trade visitor wants their account pricing, their payment terms, a compliance certificate, and to order forty of something in one action without being shown a marketing carousel first.
Light Planet supplies LED lighting to the Australian market, including trade customers. This is about what a business-to-business store has to do that a consumer store does not, and why bolting trade features onto a retail site usually disappoints both audiences.
Key Takeaways
- B2B pricing is customer-specific, so the store has to show different prices to different logged-in accounts rather than one public price list.
- Trade accounts need an approval step, because pricing and payment terms are extended to verified businesses rather than anyone who registers.
- Payment terms turn a store into a credit relationship, which changes checkout from a transaction into an account operation.
- In regulated product categories, compliance documentation is part of the product page, not a support afterthought.
What Does Light Planet Sell?
Light Planet supplies LED lighting products across Australia, positioned on performance, energy efficiency and long-term reliability. The business serves trade customers alongside general buyers, which is the fact that shapes everything about the store.
Why Is a B2B Store Harder Than a Retail One?
Because almost every assumption a standard e-commerce platform makes is wrong for trade.
Retail e-commerce assumes one price per product, payment at checkout, a single-item buying pattern and a customer who needs persuading. Trade assumes negotiated pricing per account, payment on terms after delivery, bulk and repeat ordering, and a customer who already knows exactly what they want and resents anything in the way.
Account-specific pricing
This is the requirement that most often forces a rebuild. In trade supply, the price depends on who is logged in. Two electricians can see different prices for the same fitting, and neither should see the other’s.
That has consequences well beyond a pricing field. Caching has to account for it, or one customer is served another’s cached prices, which is the single worst failure mode in B2B e-commerce. Search results, category pages and any product feed all have to respect the logged-in context. Retrofitting that onto a store built for public pricing is substantially harder than planning for it.
Trade accounts need approval, not registration
A trade account is not a user account. It carries pricing and often credit, so it is extended to a verified business rather than granted to anyone who submits a form.
The practical implication is that registration and approval are two different states, and the site has to handle the gap between them gracefully. Someone who has applied but not yet been approved needs to know where they stand rather than logging in and finding prices unchanged with no explanation.
Payment terms change what checkout means
Where an account buys on terms, the order does not end with a card payment. It creates an obligation, and the customer’s real questions afterwards are about their balance, their statements and their order history rather than about a tracking number.
That shifts the centre of gravity from checkout to the account area. On a consumer store the account page is an afterthought most customers never open. On a trade store it is where the relationship lives.
What Else Does Trade Buying Need?
Ordering built for volume
Trade buyers order repeatedly and in quantity. Features that would be clutter on a consumer store are the difference between usable and not here: fast reordering from history, saved lists for recurring jobs, and the ability to assemble a large order without clicking through a product page for each line.
Filtering that matches how the trade specifies
A consumer filters by room and style. An electrician filters by wattage, colour temperature, beam angle, IP rating and dimensions, because they are matching a specification rather than choosing a look. Product data has to be structured enough to support that, which is a data problem before it is a design one.
Compliance documentation on the product page
Electrical products sold in Australia are subject to standards, and the buyer specifying a fitting for a commercial job needs the documentation to prove compliance. Where that lives matters: buried in a support section it is a support ticket, and on the product page it is a reason to buy from this supplier rather than another.
What We Would Watch
Complexity is the standing risk. Each of these capabilities usually arrives as a separate extension, and a store carrying trade pricing, memberships, bundles, wishlists, filtering and a side cart has a large surface area where one update can break checkout. On a store where checkout is revenue, that argues for a staging environment and a tested update routine rather than updating in place.
The second is the caching interaction described above. It deserves repeating because it is both the most damaging failure and the easiest to miss in testing: nearly all testing is done logged in as an administrator, which is the one account whose pricing view is never wrong.
Frequently Asked Questions
Can one website serve both trade and retail customers?
Yes, but it has to be designed for it from the start. The store needs to behave differently by account type, which affects pricing, checkout, caching and navigation. Adding trade to a retail store later is usually a rebuild.
Should trade prices be visible to the public?
Generally not. Trade pricing is commercially sensitive and account-specific, which is why it sits behind an approved login rather than a public price list.
What is the most common B2B e-commerce mistake?
Caching pages that contain account-specific prices. It is invisible in administrator testing and it shows one customer another customer’s pricing.
Why does product data matter so much in trade supply?
Because trade buyers filter by technical specification rather than by appearance. Without structured attributes, the filtering they need cannot exist regardless of how the interface is designed. We treat this as part of e-commerce scoping rather than a content task.
Selling to Trade?
If you supply both trade and retail from one store and your trade customers phone their orders through instead of using the site, the site is not built for how they buy.
See more of our builds in our portfolio, read how we scope projects on our process page, or get in touch.
