Insight · 19 November 2026 · 5 min read

Business buying journeys need their own brief

A useful B2B commerce brief starts with how customers get purchases agreed, placed and fulfilled.

Business buying journeys need their own brief

PJH has appointed Brave Bison Commerce to lead a B2B ecommerce transformation, according to Little Black Book’s report on 18 November 2026. The appointment provides a current UK example of investment in business buying journeys. For organisations preparing their own commerce plans, it is a useful prompt to examine what goes into the brief.

The important design decisions begin before anyone draws a product page. Who can see an account’s prices? Who can build an order, approve it or change the delivery address? What happens when a repeat purchase meets a changed product range? Those questions define the service customers need and the work the platform must support.

Research the purchase across the whole account

A B2B research plan should follow a purchase through the people involved. The person finding a product may have a different role from the person authorising the spend, receiving the delivery or checking the invoice. Treating them as one customer can leave important decisions hidden inside a generic checkout journey.

We’d start with recent purchases and ask customers to walk through what happened. That should include a straightforward order, a purchase that needed approval and one that required help. Interviews become more useful when participants can show the emails, order references and documents they used, with appropriate permission and sensitive details removed.

Research should also include the supplier’s account managers, customer service staff, finance team and fulfilment colleagues. Their work can reveal where the online journey needs a decision from someone else. A buyer might be able to submit an order immediately, while the supplier still needs to confirm a delivery arrangement or resolve an account restriction.

The output should be a service blueprint connecting customer actions with staff activity, business rules and the systems that support them. For a UK organisation selling to business accounts, the relevant unit of research is often the relationship between those people, rather than an individual browsing session.

That gives the brief something firmer than a list of features. Each requirement can describe who needs it, the circumstances in which it is used, the rule it must follow and the outcome that counts as success.

Make permissions and approvals specific

“Account management” is too broad to be a useful requirement on its own. The brief needs to distinguish between viewing an account, seeing negotiated prices, creating a basket, placing an order, approving expenditure and managing other users. Research should establish which responsibilities belong together and which need to remain separate.

Consider a customer with several branches. A branch buyer might need access to its own deliveries and order history, while a central purchasing team needs a wider view. The design question is how those responsibilities work in practice: who grants access, how changes are checked and what happens when somebody leaves or moves branch.

Purchasing approval needs the same attention. An organisation might approve orders above an agreed amount, restrict certain products or require a purchase order reference. The service brief should record the rules discovered through research, including what happens when the usual approver is unavailable.

These decisions affect the interface directly. A saved basket awaiting approval needs a clear status. The buyer needs to understand whether stock or pricing has changed while the decision is pending. An approver needs enough information to make the decision without reconstructing the order through emails.

Prototype testing should therefore include more than the happy path. Ask a buyer to submit an order, an approver to reject part of it and the buyer to revise it. The test is whether each person understands what has happened and what they can do next. That is stronger evidence than agreement that the screens look sensible.

Treat repeat orders and terms as working rules

A repeat-order button looks simple until the previous order contains a discontinued item, a changed pack size or a delivery address the customer no longer uses. Research should establish what customers mean by repeating an order. They may want the same products, the same quantities, a regular replenishment list or a starting point they can edit.

Those distinctions should shape the brief. A customer rebuilding a standard stock order needs to see changes before committing. A buyer ordering for several sites may need to split deliveries. Where alternatives are offered, the customer needs enough information to judge whether the replacement is suitable.

Negotiated terms also need explicit rules. The brief should establish where account pricing comes from, who maintains it and when the customer sees it. If the price shown during browsing can change before submission, the journey needs to explain that clearly and provide a route to resolve a discrepancy.

Payment terms, credit restrictions and delivery charges deserve the same treatment wherever they apply. A purchase that requires staff review should have a visible status and a defined next step. Customer service colleagues should be able to understand what the buyer saw when the order was submitted.

This is where early technical investigation earns its place. A small test of how account prices or order status move between systems can expose constraints before detailed design. Otherwise, a team can spend weeks refining a journey around information that arrives too late, or cannot be retrieved reliably enough to support the proposed interaction.

Write acceptance tests before choosing the screens

The research should become testable scenarios that design, technology and operations teams can use together. A platform brief is more useful when it describes a purchase that must work from beginning to end, including the supplier’s response.

A short initial set might include:

  • A branch buyer prepares an order that a central approver can review, amend and release.
  • A returning customer repeats an order and understands every product, price and delivery change before submitting it.
  • An account with restricted purchasing can request help, see the request’s status and continue once it is resolved.
  • A customer service colleague can explain an order’s status using the same information available to the buyer.

Each scenario needs an expected outcome, an owner and a way to test it. It should also identify which information comes from which system. That helps separate a screen-design decision from a policy decision or a piece of integration work.

Measures should follow the tasks customers are trying to complete. Depending on the research, useful candidates could include completion of repeat purchases, approval turnaround, orders requiring correction and contacts asking for an order’s status. Establishing a baseline before launch makes later evaluation more meaningful.

There will still be choices about catalogue presentation, search, checkout and platform capability. The service brief gives those choices a common reference point. Teams can judge whether a proposed feature supports the agreed purchasing scenarios and what effort it requires behind the scenes.

The practical question before design begins is simple: can the brief explain how a customer’s purchase moves through its people, rules and systems? If it cannot, further discovery is likely to be more useful than another round of screen designs.

Share this article