B2B Reorder Portal: Saved Carts, Approvals, Contract Pricing

How to design a B2B reorder and account portal: saved carts, order history, approval workflows and contract pricing patterns that let procurement teams repeat a purchase in minutes.

B2B Reorder Portal: Saved Carts, Approvals, Contract Pricing

A procurement coordinator at a facilities company orders the same 40 SKUs every second Tuesday. On most B2B sites, that means 40 searches, 40 quantity fields and a quiet hope that the price on screen matches the contract. Then the order sits in someone’s inbox waiting for approval.

A well-designed B2B ecommerce reorder and account portal turns that hour into two minutes. This article breaks down the four interface patterns that do the heavy lifting, and how to tell whether a supplier is designing them properly.

Get a reorder portal your procurement buyers use without calling their rep, designed and built end to end.

Scope your account portal

Start with roles, not personas

Consumer ecommerce designs for one shopper. A B2B account portal serves at least four people inside the same customer company: the requester who builds the order, the approver who signs it off, the company admin who manages users and budgets, and someone in finance who needs invoices. Each of them sees a different version of the same order.

That is why the first design artefact should be a permissions matrix, not a mood board. Who can create a saved list? Who can see another location’s orders? Can a requester see the contract price, or only the approver? These answers shape every screen that follows.

The pressure to get this right is growing. In a survey of 646 buyers, Gartner found 67% of B2B buyers prefer a rep-free experience. For repeat purchasing, rep-free only works if the portal can answer the questions a rep used to answer: what did we order last time, what are we paying, and who needs to sign this off.

Saved carts are not wish lists

A common mistake in B2B builds is a saved cart implemented as a wish list with a new label. The mechanics differ. A wish list is a holding area that empties as items move to the cart. A procurement list is a reusable template.

Adobe Commerce makes this distinction explicit. Its requisition list documentation notes that a requisition list is not cleared after items go to the cart, uses a compact view for long item lists, and allows up to 999 lists per buyer account depending on configuration. Products can be added from product pages, catalogue pages, the cart, past orders and quotes.

Platform support is the easy part. The design work sits in four places:

  • Density. A list of 60 lines should fit on one or two screens, with SKU, description, pack size, contract price and an editable quantity on each row. Product imagery is optional here. Buyers recognise part numbers faster than thumbnails.
  • Scope. Lists need to belong to someone: a user, a team or a delivery location. A shared “Site B weekly consumables” list is far more useful than 12 personal copies drifting out of sync.
  • Validation at the moment of use. A list saved in March will contain a discontinued item by June. The interface should flag unavailable lines, substitutions and price changes before the buyer hits “add all to cart”, not after.
  • Bulk entry. Quick order by SKU, CSV upload and paste-from-spreadsheet are the routes most procurement teams already use. Treat them as first-class inputs to a list, not hidden utilities.

We have covered the dashboard layer around these lists in our piece on B2B account dashboards, so this article stays on the reorder loop itself.

Order history as a reorder engine

Most order history pages are built as receipts. A table of order numbers, dates and totals, each opening a static summary. That is a record. It is not a tool.

Procurement buyers search history by things the platform often does not index: their own PO number, the cost centre, the delivery site, or a SKU they remember ordering “sometime last quarter”. If the search only accepts the supplier’s order number, the buyer goes back to email. Index the fields your customers actually reference, and filter by location and requester for admins who see the whole account.

Then make every order actionable at line level. “Reorder all” is useful. “Reorder these three lines” is more useful, and “save these lines as a list” turns a one-off into a template. When the buyer reorders, show a clear diff: this line was 4.20 per unit last time and is 4.35 now under your current agreement. Silent price changes are the fastest way to lose a procurement team’s trust.

Finally, attach the documents finance asks for. Invoice PDFs, delivery notes and credit notes belong on the order, not in a separate portal with a separate login.

How do approval workflows avoid stalling the order?

Approval is where reorder speed usually dies. The interface submits the order, a notification fires, and the requester has no idea where it is or why.

The underlying rules are usually simple. Adobe Commerce’s purchase order approval rules let company admins set rules by order total (including tax), shipping cost, or number of SKUs, applied to specific company roles. The same page documents an edge case that teams often miss: if two or more users share the approver role, the creator of a purchase order cannot approve their own order.

Good approval UX makes those rules visible before submission. If the cart total crosses a threshold, say so in the cart: “This order needs approval from a Site Manager because it exceeds your limit.” The requester can then split the order, trim it, or submit knowing what happens next.

An approval workflow is only as fast as its least informed participant. Show the requester which rule fired and show the approver exactly what changed against the usual order.

On the approver side, design for a phone screen and a busy person. A pending order should show the total, the triggering rule, the requester, and any lines that differ from the account’s normal pattern. Approve, reject with a reason, or edit and approve should be one tap each. Delegation for holidays is not an edge case. Without it, orders queue for a fortnight every August.

Contract pricing the buyer can trust

A B2B buyer is not hunting for a deal. They are checking that the price on screen is the price they negotiated. That changes how pricing should be displayed.

Drop the consumer patterns. A struck-through list price next to the contract price invites the question “why is the list price higher than what we agreed?” Show the account’s price, label it as the contract or agreement price, and show volume breaks as a small table on the line rather than a promotional badge.

The platform model matters here. On Shopify, B2B catalogs control which products and prices each customer sees, and Basic, Grow and Advanced plans are limited to 3 active catalog assignments across B2B markets, a limit that does not apply on Shopify Plus. Plus can also assign catalogs directly to company locations, which is what you need when one customer’s depots have different agreements.

Quantity rules belong in the same conversation. Shopify’s quantity rules apply per variant, so a buyer cannot combine 5 gray and 5 blue units to meet a minimum of 10. If the interface only reveals that at checkout, every saved list becomes a trap. Surface increments and minimums on the list row, and snap quantity steppers to valid values.

Where pricing lives in an ERP rather than the commerce platform, decide early whether the portal reads prices in real time or syncs them on a schedule. Real-time calls are accurate but add latency to every list and history view. Scheduled syncs are fast but need a visible “prices as of” timestamp. That decision can tip the Shopify Plus or headless question on its own.

A build sequence that keeps procurement in the room

Reorder portals fail when they are designed from the supplier’s org chart. This sequence keeps the customer’s buying process at the centre.

This sits naturally alongside work on catalogue page design and faceted search, which handle the first purchase. The portal handles every purchase after it.

When you evaluate a supplier, ask to see their failure-state designs. A plausible agency shows the happy path. A competent one shows what happens when a saved list meets a price change.

Your next step: pull last year’s order export and count how many orders repeated a previous basket. That number tells you how much of your revenue runs through the reorder loop, and how much a slow one is costing your customers.

1

Mine the order data:

Pull 12 months of orders and identify how much volume is repeat purchasing, which SKUs recur together, and which accounts order across multiple locations.

2

Interview both sides of approval:

Talk to requesters and approvers at three or four real customer accounts. Ask where orders stall and what they check before signing off.

3

Write the permissions matrix:

Define every role, what each can see and do, and how roles map to locations and budgets. Get sign-off from sales and customer service before any UI work.

4

Decide the price source of truth:

Agree whether contract prices live in the ERP or the platform, how often they sync, and how the interface behaves when they disagree.

5

Design the failure states first:

Discontinued items, changed prices, broken quantity rules, rejected approvals and expired contracts. These screens determine whether buyers trust the portal.

6

Pilot with live accounts:

Launch to a small group of high-frequency customers, watch time-to-reorder and approval turnaround, and fix friction before the wider rollout.

Frequently asked questions

What is the difference between a saved cart and a requisition list?

A saved cart is usually a single paused basket that empties when it is checked out. A requisition list is a reusable template that stays intact after items are sent to the cart, so a buyer can reorder the same set of products repeatedly.

Which approval rules should a B2B portal support?

Most accounts need thresholds on order total, plus rules by role and location. Adobe Commerce also supports rules on shipping cost and number of SKUs. The interface should tell the requester which rule applies before they submit.

Should contract prices be shown with a list price strikethrough?

Usually not. Procurement buyers want to confirm the negotiated price, and a crossed-out list price raises questions about the agreement. Show the contract price clearly labelled, with volume breaks in a small table.

Can Shopify handle different contract prices for each customer location?

On Shopify Plus, catalogs can be assigned directly to company locations, which supports location-level pricing. Lower plans assign catalogs through B2B markets and have a limit on active catalog assignments.

How do you measure whether a reorder portal is working?

Track time from login to submitted reorder, the share of orders placed from lists or history, approval turnaround time, and the volume of pricing or order-status queries reaching customer service.

Make repeat purchasing the fastest path to order

You have seen how saved lists, actionable order history, visible approval rules and trustworthy contract pricing work together in a reorder portal. Moburst Digital Experience designs and builds these portals on Shopify Plus, Adobe Commerce or headless stacks, so your procurement buyers reorder in minutes instead of calling their rep.

Talk to our B2B team