A trade ordering portal needs to reflect how your business accepts an order. The important questions are often less visible than the catalogue: which account is buying, which prices apply, what quantities are allowed and when the request becomes an accepted order.
Start with an anonymised example of an order your team handles regularly. Follow it from the customer's product list through your internal checks and into fulfilment. That gives a developer something concrete to scope and demonstrate.
Separate the customer company from its users
Write down whether several people order for the same business, whether they use different delivery locations and who may change account details. Avoid assuming that one shared login will cover every customer relationship.
Shopify's B2B documentation distinguishes the company, company locations and the individual purchaser. This is a useful example of why the account model matters; your own brief should describe the relationships you actually need. Shopify companies and customers.
Decide how new trade accounts are reviewed, how a departing buyer loses access and who can see the company's order history. Ask for tests involving two different companies, rather than a demonstration using only an administrator account.
Define the source of each important field
Before choosing screens, identify the system your team trusts for product codes, customer agreements and available stock. If the website and office software both contain editable copies, decide which one takes priority.
| Field | Decision for the brief | What the customer should see |
|---|---|---|
| Product code | Where is the definitive code maintained? | A clear match or an explained unmatched item |
| Account price | Which agreement and system are authoritative? | A confirmed applicable price, or a stated review step |
| Pack quantity | Are products sold singly, by box or in multiples? | The rule before submitting the quantity |
| Availability | How current is the information? | An honest status and the next action |
| Order reference | Which identifier follows the request internally? | A reference staff can trace |
If a price or availability check fails, agree the fallback. A portal should not silently invent a value or imply that a request has reached your order system when it has not.
Specify quick ordering without hiding mistakes
For buyers who know your product codes, a compact order-entry table may be more useful than browsing large image cards. If you accept pasted lists or file imports, show unmatched codes, invalid quantities and duplicate rows for review.
A repeat-order button should also be defined carefully. Does it rebuild a basket for checking, or immediately create another order? Decide how discontinued items, changed prices and unavailable quantities are presented before the customer confirms.
An illustrative test order might contain one valid product, one obsolete code and one item below its pack minimum. The useful demonstration is how the buyer resolves those problems, not merely how quickly valid rows are accepted. This is a sample acceptance exercise, not a reported Nolixia client result.
Make the order status match the real process
Keep a distinction between a saved basket, a submitted request, an accepted order and goods being prepared. Choose the states your team actually uses and decide who can move an order between them.
If an internal review is required, the customer should receive a request acknowledgement that explains the next step. Do not label it an accepted order solely because the website stored the form.
Ask what happens when an integration is unavailable. Staff need a way to identify the affected request, resolve it and check whether it has already been processed before trying again. Include that exception journey in the scope.
Check existing platform features before custom development
Your current commerce or business system may already cover part of the requirement. Compare it against your account rules using real test cases.
Current Shopify documentation describes B2B catalogues, quantity rules and volume pricing, with plan-dependent limits. It no longer makes sense to assume every B2B feature requires Plus; check the current plan against the specific catalogue and company-assignment requirements. Shopify B2B catalogues.
Use the ecommerce platform comparison guide for the broader buying decision. A custom portal is worth discussing when important requirements remain unsupported, not simply because a bespoke interface sounds attractive.
Ask a supplier to demonstrate the exceptions
- Two companies receive the correct products and account information.
- A quantity outside the agreed pack rule is clearly explained.
- A previous order is rebuilt using the agreed current checks.
- An unauthorised buyer cannot open another company's order.
- A failed internal transfer is visible to the responsible staff member.
- Customer-facing wording matches the request's actual internal state.
- Staff can export or trace the sample order without manually reconstructing it.
Prepare your trade portal brief
Bring your product-code structure, an anonymised order, company/user rules, quantity rules and the systems holding prices and stock. Mark which requirements are essential for the first release and which can wait.
Read about Nolixia's ecommerce website services, then send your ordering workflow. We can discuss the scope and whether an existing feature, integration or custom application fits the business process.
