Your trade customer wants to order again at their agreed price. Decide what they can choose, what submitting an order means and how unavailable items are handled before adding a checkout to your catalogue.
A B2B catalogue needs ordering when customers can make a useful buying decision from the information and terms it provides. If staff still need to agree the specification, price or delivery for each purchase, a clear request-for-quote service may be the better fit.
Customer prices, permitted products, pack quantities and stock information each add a separate job. Decide what the customer should be able to do, then see how much an existing commerce platform can already handle.
Take a fictional wholesaler selling cleaning supplies. A buyer at a hotel group regularly orders the same products for its North branch. The branch has an agreed price for a particular bottle size, and the wholesaler sells that product in packs of six.
The buyer wants eighteen bottles. They also want an item that is currently unavailable. A useful ordering service lets them complete the routine purchase and understand what happens to that exception.
Start with the account. Who is signed in, and which company and branch are they buying for? The North branch's product range and agreed prices should follow the intended assignment. A buyer for another branch may have different terms. A signed-out visitor may see a public catalogue or a public price instead.
Shopify provides one current example of these distinctions. Its B2B catalogues define products and prices, with capabilities that differ by plan. Its assignment guidance also shows why the matching company location and market conditions matter. A login alone does not establish that every visitor will see the intended price.
For our fictional buyer, the page should make clear whether the price is per bottle or per pack, which bottle size it covers, and whether the quantity box counts bottles or packs. Eighteen bottles would mean three packs in this example. The customer should be able to understand that before submitting anything.
Minimum quantities, increments and discounts for larger purchases answer different questions. Shopify's quantity-rule documentation distinguishes these rules and applies them to product variants. A rule for one bottle size does not automatically mean that mixing several sizes meets it.
Show the range assigned to this buyer and branch. Decide what an unintended account or public visitor may see.
Show the intended agreed price for that product and unit. Name the source staff use to resolve a disagreement.
Explain units, packs and permitted increments. Keep quantity rules distinct from any discount for buying more.
These choices can come from different places. Product details might be maintained in the commerce system, negotiated prices in the sales system, and stock in warehouse software. Name the authoritative source for each, along with the person who resolves a mismatch. Connecting the systems helps only when they agree on what an item, a unit and a customer mean.
Now the buyer reaches the end of the order. Decide what submission does in your operation. Does it send a request for staff to review, or accept an order under the business's agreed terms? When is stock allocated, and when does fulfilment begin? These decisions should be reflected in the wording, acknowledgement and staff view.
In our example, suppose the wholesaler chooses staff review before acceptance. The buyer submits eighteen bottles and receives a request number with a clear message that staff will confirm the order and delivery. Staff see the intended branch, item, quantity and price together. Payment arrangements remain those agreed with the customer; the website does not silently approve new credit terms.
The unavailable item needs its own resolution. Staff can offer a confirmed later date, an agreed alternative or removal from the request. The buyer should understand which items are still awaiting a decision and which have been confirmed. Avoid silently replacing an item or treating a request receipt as a delivery promise.
A warehouse total is useful context, but it may include goods already committed to other orders or set aside. Shopify, for example, distinguishes on-hand, available, committed and reserved quantities. Its inventory model also tracks quantities by item and location. Those are provider-specific definitions, worth checking against the system your business actually uses.
For the hotel buyer, the relevant question is whether the wholesaler can offer those eighteen bottles from the location that will supply them. Agree what the website may say when stock information is missing or its connection is unavailable. It could keep the item available for a quote request while withholding an availability or delivery commitment.
A stock connection supplies information. The business still has to decide when an order can be accepted, when goods are allocated and who handles an exception. Match the customer-facing message to those decisions.
An informational catalogue can be enough when customers need to discover products and speak to someone before buying. A request-for-quote catalogue can carry their selected items and quantities into that conversation, saving them from describing the same basket again.
If repeat customers can order on established terms, ask a supplier to demonstrate the journey in the proposed commerce platform and edition. Check the intended catalogue, account assignment, price, quantity rule, order review and unavailable-item path. Existing configuration may cover the work.
An extension or a connection becomes relevant when a specific rule or source is missing, such as bringing approved customer prices from the system where staff maintain them. Compare its ongoing care and platform-update requirements with the work it removes.
A custom platform becomes a candidate when distinctive ordering work remains important and poorly served by the available configuration and extensions. The comparison should include maintaining those rules, operating the connections and changing the service later. A familiar catalogue with one missing connection calls for a different scope from a business with a distinctive order process.
We can help with ecommerce work around the customer journey you need. Bring an ordinary repeat purchase and an exception, so the discussion can stay tied to what buyers and staff actually need to complete.
Use invented customers, prices and products in a supported separate test environment, with real orders, customer messages, payments and fulfilment suppressed. Watch the hotel buyer place the routine request, enter an invalid pack quantity and encounter the unavailable item. Then try another branch, an unintended account and a signed-out visitor to check product and price visibility.
Follow the request into the staff view and back to the buyer's acknowledgement. Ask what happens if the price source disagrees or the stock connection is unavailable. Record what the demonstration established and what remains unverified.
The result is a concrete decision: keep the catalogue informational, add quote requests, configure ordering, connect a missing source or commission the remaining custom work. Choose the option that supports the purchase you are prepared to offer and the exceptions your staff can handle.
Yes. It can let customers select products and quantities while staff confirm specification, price or delivery. It fits when a conversation is still part of making a useful offer.
The intended buyer, company and branch under the assignments your business chooses. Check those assignments with another account and a public visitor as well as the intended buyer. Login alone is not proof that the rules are correct.
Not by itself. It may include goods already committed or set aside. Check the supplying location, the stock system's definitions and the business's acceptance rules before making an availability promise.
The acknowledgement should explain whether this is a request awaiting review or an accepted order under the agreed terms. It should also make pending items and the next staff or customer action clear.
Last newsletter: making more money from a subscription site or app you already own.
The one before: how to spot AI nonsense from real success stories.
Interested?
Weekly Or just let us know and we'll adjust it for you. Sounds good?
