B2B buyers do not shop. They reorder. A facilities manager, a parts buyer, a purchasing clerk – they know exactly what they need, they order it every week or every month, and the last thing they want is to browse a catalog like a consumer. If your storefront makes them hunt for products they have bought fifty times, they will go back to emailing their rep, and your portal will have failed at the one job that mattered.
This guide covers the ordering mechanics that make a B2B portal actually usable for repeat buyers: requisition lists, quick order by SKU and customer part number, bulk/CSV upload, saved carts, and one-click reorder. What each does, which ERP data it needs, and when you actually need it.
Why B2B buying is reordering, not browsing
The mental model matters because it changes what you build. A B2C shopper discovers products; a B2B buyer executes a known purchase. Optimizing a distributor’s storefront for discovery is optimizing for the wrong behavior. The features below all serve one goal: let a buyer who already knows what they want place the order in as few actions as possible, at their price, without a phone call.
Requisition lists: the standing shopping list
A requisition list is a saved, named list of products a buyer orders regularly. They build it once, then add the whole list (or part of it) to a cart in one action, adjust quantities, and check out. Good implementations support:
- Multiple named lists – by job site, by department, by season, by category. A contractor keeps one per active project; a multi-location buyer keeps one per branch.
- Shared lists across a company account – so several buyers at the same customer draw from the same maintained list.
- Live pricing and availability on every line – the list shows the buyer’s contract price and current stock, resolved from the ERP, not a stale snapshot.
Adobe Commerce ships requisition lists in its B2B module – see our review of the Adobe Commerce B2B module for where the native features hold and where they don’t. Shopware delivers the same behavior through its B2B components. On either platform the feature is easy; feeding it real ERP pricing and availability is the actual project.
Quick order, and ordering by the customer’s part numbers
Quick order lets a buyer type or paste SKUs and quantities straight into an order form – no browsing at all. The version that wins accounts adds one thing: the customer’s own part numbers.
Distributors keep customers by speaking their language. A buyer searches for the part number in their system, not yours. That cross-reference – their number to your SKU – lives in the ERP, and surfacing it in quick order and search is one of the highest-return, most-overlooked features in B2B commerce. Without it, buyers translate part numbers by hand and give up; with it, they order in seconds.
Bulk and CSV upload for large orders
For orders of dozens or hundreds of lines, buyers need to upload a file or paste a block of SKUs and quantities. The mechanic is simple; the discipline is in the validation:
- Map each line to the right SKU (via your SKU or the customer’s part number).
- Apply the buyer’s contract pricing per line as it imports.
- Check availability and flag shortfalls before the order is placed, not after.
- Return clean errors on the lines that failed, without discarding the ones that worked.
Done well, CSV upload turns a spreadsheet that used to be emailed to a rep into a self-served order. Done carelessly, it just relocates the rekeying errors.
Saved carts, reorder, and recurring orders
Three more mechanics round out how B2B buyers actually order:
- Saved carts – pause an in-progress order and finish it later, or route it for approval. Distinct from a requisition list: a cart is one transaction, a list is a reusable template.
- One-click reorder – repeat a previous order (including ones placed by phone, EDI, or a rep) from order history. Because the ERP is the system of record for all channels, reorder should show every order, not just web ones.
- Recurring / standing orders – the same order on a schedule, for consumables and maintenance supplies. It automates the reorder the buyer was doing manually anyway.
Native or custom on Magento and Shopware?
Adobe Commerce covers the most of this natively (requisition lists, quick order, CSV upload) inside its B2B module; the gaps are usually customer-part-number search and ERP-accurate pricing on every line, which are integration work regardless of platform. Shopware covers the behaviors through its B2B components and a bit more custom development, with the advantage of a cleaner base to extend. On both, the platform is rarely the constraint – feeding these features live, customer-resolved data from the ERP is. That is the same lesson as pricing: the mechanic is easy, the ERP-accurate data behind it is the work.
Who we are
Web Solutions NYC builds ordering experiences for distributors and manufacturers who live on repeat purchasing – anonymized examples include a bath-products manufacturer whose distributors configure and reorder against live manufacturing capacity. We are a Shopware Platinum Partner and official Adobe Commerce partner, and we wire these features to the ERPs that hold your part numbers, pricing, and stock: NetSuite, SAP, Dynamics, Acumatica, Sage, and Epicor P21.
Frequently asked questions
A requisition list is a saved, reusable list of products a business buyer orders regularly – a standing shopping list they can add to a cart in one action, adjust quantities on, and reorder without searching the catalog each time. It is a core B2B feature because business buyers repeat-purchase the same items; it is not a wishlist, it is an operational ordering tool.
Adobe Commerce (Magento) includes requisition lists natively in its B2B module. Shopware handles the same behavior through its B2B components and custom development. On both, the feature itself is straightforward; the real work is feeding it correctly – the customer’s own part numbers, their contract pricing on each line, and live availability – which all come from the ERP.
Through a cross-reference that maps the customer’s internal part numbers to your SKUs, stored in the ERP and made searchable in the storefront. Buyers search and build orders in their language, not yours. It is one of the highest-value and most-overlooked B2B features, because it removes the friction that sends buyers back to phoning their rep.
A saved cart is a paused order you intend to finish. A requisition list is a permanent template of frequently ordered items you draw from repeatedly – it persists across orders, supports multiple named lists (by job, location, or category), and is meant for reordering, not for finishing one transaction.
Yes, and serious B2B buyers expect it. Bulk/CSV upload and quick-order-by-SKU let a buyer paste or upload dozens or hundreds of line items at once – essential for large or recurring orders. It must validate against the customer’s own part numbers, contract pricing, and availability as it imports, or it just moves the errors from the phone to the spreadsheet.
Buyers reordering by phone because your site makes them hunt? That is fixable, and it is usually the fastest win in a B2B build. Let’s talk.