Self-Service Reorder in B2B Commerce: An Overlooked Revenue Stream
A large share of orders in a B2B shop (business-to-business, trade between companies) is not a new purchase decision. It is the same buyer ordering the same forty items in the same quantity for the umpteenth time. Many Swiss B2B shops still force this customer back into the full product catalogue on every single order, as if they were shopping for the first time.
The short answer: Self-service reorder means that known orders can be repeated without a fresh catalogue search, directly in the shop. Four features carry this: an order history with one-click reordering, personal default carts or requisition lists per customer, quick entry by SKU (stock keeping unit, the item number) for larger orders, and, where the customer relationship justifies it, a connection to the customer's own purchasing or ERP system. This is not a convenience extra tucked away on the homepage. It decides directly whether recurring revenue stays visible in the shop, or ends as a phone call to inside sales, where no analysis ever captures it.
This is different from the question of how customers find an item they don't yet know in a large catalogue. That is a navigation and search question with its own solutions. Reorder assumes the items are already known, and answers only one question: how quickly does the customer get back there?
Reorder Is No Longer a Purchase Decision
How often B2B purchasing actually happens online is shown by a survey of 150 B2B buyers that Digital Commerce 360 published together with Forrester Research in October 2023: slightly more than half of respondents make a digital business purchase daily, and almost a third, 32 percent, do so several times a day. At that pace, a large share of orders is not new product research. It is the same purchasing department working through the same list again.
Even so, most B2B shop homepages are built for a different situation: someone who doesn't yet know a product and still has to find it. There are dedicated solutions for that task, from faceted navigation (filtering by several product attributes at once) to search by technical attribute, and it is a legitimate question in its own right. But it is a different one from the question here: someone who already knows what they need, and has ordered it before, shouldn't have to go through the same navigation again just to arrive at the same destination.
If the shop has no fast path back to the last order, customers don't automatically fall back on product search. They fall back on another channel: phone, email, their own spreadsheet order list that lands directly with inside sales, bypassing the shop. The shop keeps running, but part of the revenue runs past it, invisible to any analysis that relies on shop data.
What Self-Service Reorder Actually Needs
Four features carry a reorder experience that actually keeps this revenue inside the shop. None of them is new on its own. Combined, they make the difference between a shop that expects reorders and one that only allows them by accident.
Order History with One-Click Reordering
The basic feature is an order history that lets a previous order be repeated with a single click, without searching for every item again. In Adobe Commerce, one of the Magento platforms we work with, this feature is available as soon as the "Allow Reorder" configuration option is enabled: customers trigger the reorder directly from the "My Orders" overview or from the detail view of a single order. OroCommerce, which we also use for B2B projects, goes a step further: a click on "Reorder" copies all details of the original order and starts a new checkout straight away, where customers can still adjust their details before completing it.
What matters here is placement more than technology: this feature has to sit where a returning customer looks first after logging in, not three clicks deep in an account area that hardly anyone opens voluntarily.
Default Carts and Requisition Lists per Customer
Many B2B orders don't consist of a single repeated order, but of a personal list of core items that shifts slightly over time. That needs more than the last order history: dedicated, permanently stored requisition lists.
Adobe Commerce calls this feature "Requisition Lists" and describes it as a wish list for the B2B context: customers can keep several lists at once, by supplier, buyer, team or campaign, add items directly from a list to the cart, and export and import lists as CSV files (a tabular text format). The default limit is up to 999 lists per account, and the number is configurable. OroCommerce's Quick Order Form allows captured items to be assigned directly to a new or existing requisition list instead of ordering them immediately.
Organisationally, this means: a default order list shared by several people within a customer company requires a company account with multiple users and assigned permissions, not just a single login. Who may maintain a list and who may only order from it is a decision that needs to be settled before go-live, not after.
Quick Entry by SKU
For larger orders with many line items, even a requisition list is too slow if every item has to be clicked individually. This is where quick entry comes in, taking quantities directly by SKU.
Adobe Commerce's "Quick Order" feature reduces ordering to a few clicks for customers who already know the item name or SKU: several SKUs can be entered manually in sequence or uploaded via an import file, available to both logged-in customers and guests. OroCommerce's Quick Order Form offers the same idea through three entry paths: a direct SKU, a name search with autocomplete, or the import of a CSV, XLS or ODS file (common spreadsheet formats) that a purchasing department already maintains anyway.
This feature depends on clean item data: a SKU that shifts after a range clean-up, or is assigned twice, lets quick entry fail silently, without the cause becoming visible in the shop.
Integration with Customers' Own Purchasing Systems
For larger B2B customers who order regularly, a fast path within the shop itself is often no longer enough. These customers want to trigger orders directly from their own purchasing or ERP system, without switching to the shop at all.
What that looks like in practice is shown by our project with Herzog Elmiger, an independent trading company in the canton of Lucerne with around 120 employees and a warehouse exceeding 150,000 cubic metres. Thanks to the online shop's connection to the industry-specific ComNorm solution and the resulting direct data exchange, orders can also be placed directly through the customer's own ERP system (enterprise resource planning, the customer's own resource-planning system), without the detour through the shop interface. The project's biggest challenge lay not in the connection itself, but in the extensive breadth of Herzog Elmiger's product range.
Such a connection isn't worthwhile for every customer equally. It is an investment that should be guided by order volume and the depth of the relationship, not by the size of the overall catalogue.
Why This Is a Directly Measurable Revenue Stream
E-commerce is, according to McKinsey & Company's 2024 B2B Pulse Survey, now the highest-revenue channel for B2B companies that offer it, accounting for more than a third of total revenue. Within that channel, reorder is the single most frequent case, given that a large share of purchasing departments, per Digital Commerce 360 and Forrester, order daily or several times a day.
The real advantage of self-service reorder lies not only in the revenue itself, but in how provable it is. An order placed in the shop is a logged, analysable transaction: conversion rate, average order value and order frequency per customer account can be measured precisely and compared over time. An order that bypasses the shop by phone or email and lands with inside sales disappears from every one of these analyses before it even starts. This is the real reason self-service reorder is underrated: where no data is created, the lost revenue cannot even be quantified, let alone used as an argument for investment.
How large the share of recurring orders in a single shop's total revenue actually is can only be measured credibly against your own base, not derived from an industry-wide blanket figure. Two reasons for that: how many customers reorder at all says nothing yet about what share of revenue this produces, and a large account with few but sizeable repeat orders counts differently in this calculation than many small ones. Independently of such a figure, though, one thing already holds: every extra click between login and reorder costs a customer who orders several times a day a multiple of what the same click would cost a new customer, who only goes through the catalogue once anyway.
What It Takes Technically and Organisationally
None of the four features above is a frontend matter on its own. Each one depends on a data infrastructure that has to be decided long before the first design sketch.
Stable, unique item data. One-click reordering and quick entry by SKU only work if the referenced SKU stays stable over time. If a SKU changes after a range clean-up, or is assigned twice, the reorder breaks silently, without an error message anyone notices. This stability is a product data management task, not the shop's: Akeneo, with whom Arcmedia works as a solution partner, keeps product data in a PIM (product information management, a central repository for product information) centrally and governance-led for exactly this purpose, instead of maintaining it in parallel across several systems.
Live prices and stock per customer account. A reorder with an outdated price or a quantity that is no longer available is worse than no reorder at all, because it costs trust. Arcmedia runs exactly this task as a dedicated field on the Integration Services service page: robustly integrating orders, status, availability and prices between the shop and the ERP system, including price lists, customer groups, promotions and discounts that must stay consistent between both systems. In practice, this includes connections to various ERP systems, among them Opacc, SAP, Infor as well as Microsoft Dynamics 365 and NAV.
Roles within a company account. A requisition list shared by several people within a customer company needs a decision on who may create it, change it, or only order from it. Without that clarification, maintenance either falls to a single overloaded person, or doesn't happen at all.
A process for the exception case. What happens when an item from a saved list or a previous order has since been discontinued, or its price has changed? That question can't be left open until it happens live for the first time. A clear rule, whether the shop blocks the item, suggests a replacement, or shows the changed price transparently, belongs in the specification, not in the clean-up after the first support case.
The homepage after login. Finally, it takes a deliberate decision about what a returning customer sees first after logging in: a generic homepage built for new customers, or their own order history with a reorder button. This decision costs no extra budget, but it does require someone to actually make it, rather than leaving it to the default template.
Conclusion
Self-service reorder is not an additional feature at the edge of the product catalogue. It is the direct answer to ordering behaviour that already happens several times a day in many B2B shops. The four building blocks, an order history with one-click reordering, personal requisition lists, quick entry by SKU, and, where it makes sense, a connection to the customer's purchasing system, all depend on the same precondition: stable item data and live prices and stock that stay consistent between the shop and the ERP system.
The most practical starting point is a simple check in your own shop: how many clicks does a customer need today to repeat an order they've already placed, and what do they see right after logging in? Both answers can be found in a few minutes, and both reliably show whether your shop actually expects reorders, or only allows them by accident.
Planning to extend your B2B shop?
Arcmedia has been supporting companies with digital commerce projects since 1995, from analysis through implementation to ongoing operations. Our experts are happy to advise you on your project.
Always up to date with the latest trends and tips: subscribe to our newsletter.
Frequently Asked Questions About Self-Service Reorder in B2B E-Commerce
What distinguishes self-service reorder from good product search?
Product search and category navigation help customers find an item they don't yet know in a large catalogue. Self-service reorder assumes the item is already known and has already been ordered once, and deliberately skips the search entirely.
Is one-click reordering worthwhile for smaller B2B shops too?
The feature itself is available in platforms such as Adobe Commerce and OroCommerce regardless of shop size. What matters is how often the same customers order the same items, not the size of the catalogue.
Does quick entry by SKU need special software?
No. Both Adobe Commerce and OroCommerce already include this feature as part of their B2B capabilities. The real prerequisite is stable, unique SKUs in the underlying product data system.
Does an ERP connection need to be planned in from the start?
No. Order history, requisition lists and quick entry can all be implemented independently of an ERP connection. A direct connection to the customer's own ERP system only pays off once order volume justifies it, and is best planned as a separate, later expansion step.
Sources
- Digital Commerce 360, Mark Brohan, "B2B buyers do their homework, survey shows", 3 October 2023, survey with Forrester Research among 150 B2B buyers
- McKinsey & Company, B2B Pulse Survey 2024, "Five fundamental truths: How B2B winners keep growing"
- Adobe, official Commerce B2B documentation, page "Quick orders"
- Adobe, official Commerce B2B documentation, page "Storefront order management"
- Adobe, official Commerce B2B documentation, pages "Introduction to Adobe Commerce B2B" and "Customers > Requisition Lists"
- OroCommerce, official documentation, page "Manage Quick Order Form in the Storefront"
- OroCommerce, official documentation, page "Order Management Concept Guide"
- Arcmedia, Herzog Elmiger project page
- Arcmedia, Integration Services service page
