B2B Quick Order Design: Saved Carts, CSV, SKU Search
Repeat B2B buyers choose the fastest route to a correct order. Here is how saved carts, CSV upload, SKU search and contract pricing should work to beat the phone call.
A procurement manager has 40 lines to reorder before Friday. She can log in to your portal, or she can ring the rep who knows her account. If the phone wins, your platform has failed at the one job repeat buyers care about.
The cost is real. In McKinsey’s B2B Pulse research, 54 percent of buyers likely to switch suppliers cite poor-quality digital experiences as a reason. This is how a B2B quick order interface should be designed so the portal becomes the faster option.
Get a reorder flow your procurement buyers will choose over the phone, designed and built end to end.
Why does the phone still win repeat orders?
Because the rep does three things at once. They know the account’s negotiated prices, they recognise the buyer’s own part numbers, and they confirm stock in the same breath. A portal has to do all three, and do them faster than a two-minute call.
Most B2B storefronts fail here because they inherit a B2C template built for discovery: category pages, hero banners, product detail pages with lifestyle imagery. A repeat buyer does not browse. They arrive with a spreadsheet and want to turn it into an order.
McKinsey’s survey found buyers use an average of ten interaction channels, up from five in 2016, and it treats reordering as its own stage of the journey. The same research found that one-third of customers prefer digital self-serve at any stage, and that this holds for repeat purchases too. You will not get rid of the phone. The goal is to make self-serve the quicker path for the buyers who want it, and to make the handoff clean for everyone else.
Saved carts are shared working documents
In B2B, a saved cart belongs to a company account, not to a person. One buyer builds “Site 3 weekly consumables”, a colleague edits it when that buyer is on leave, and a finance approver signs it off. The interface should treat it like a shared file: named, owned, tied to a ship-to location, and stamped with who last ordered from it and when.
The most important engineering decision is what the cart stores. It should store SKUs and quantities, never prices. Prices are resolved again every time the cart is opened, because the contract may have changed since it was saved. When a price has changed, say so on the line (“price updated since last order”) rather than letting the buyer discover it on the invoice.
Discontinued items need the same honesty. Silently dropping a line is the fastest way to send a buyer back to the phone. Show the superseded SKU, suggest the replacement, and let the buyer accept it in one click.
Reorder from order history is a separate pattern. The history is a permanent record; “reorder” copies its lines into a live cart and runs current price and availability checks. We cover how both patterns sit alongside approval workflows and contract pricing rules in separate pieces.
CSV upload: the feature most builds get half right
Every major platform ships some version of bulk upload. Adobe Commerce’s Order by SKU feature accepts a CSV with SKU and Qty columns, merges duplicate SKUs into one cart line, and flags products with required options as needing attention in the cart. Its B2B Quick Order form offers a downloadable sample template. One scoping detail catches teams out: in Adobe Commerce B2B, you have to switch Quick Order off to enable Order by SKU. You choose one.
The built-in versions assume a tidy file. Real files are not tidy. They are exports from SAP or Oracle with the buyer’s own part numbers, extra columns, leading zeros stripped by Excel, and quantities in cases when you sell single units. A competent build is a small data pipeline, not an upload button.
An upload that rejects a 200-line file because of one bad row teaches the buyer to call. Partial success with a clear exception list teaches them to come back.
Accept the file they already have:
Take XLSX as well as CSV, detect the header row, and offer a column-mapping screen that remembers the mapping for that account next time.
Normalise before matching:
Trim whitespace, unify case, strip hyphens and spaces, and restore leading zeros where your SKU format makes them predictable.
Resolve identifiers in a fixed order:
Exact SKU first, then the account’s customer part number cross-reference, then superseded SKU mappings, then fuzzy candidates that a human must confirm.
Apply commercial rules:
Check minimum order quantities, pack multiples, unit-of-measure conversions and whether the account is entitled to buy that SKU at all.
Report row by row:
Mark each line as matched, adjusted (for example, rounded up to a full case) or unresolved, and let the buyer fix problems inline rather than re-uploading.
Commit partial success:
Add every valid line to the cart and park unresolved rows in a holding list the buyer or their rep can clear later.
SKU search for people who type part numbers
Quick-order search is not catalogue search. A buyer typing the first few characters of a part number wants every SKU that starts with them, ranked by what their account has ordered before. They do not want a relevance-scored list of blog posts and category pages.
That changes the index. SKUs need their own field with prefix matching and normalisation, so a code typed with hyphens, with spaces or in lower case still finds the same product. Customer part numbers should be indexed per account, so the search understands the buyer’s vocabulary as well as yours. Engines such as Algolia, Elasticsearch and Typesense all support this, but none of them set it up for you.
The result row matters as much as the match. Show SKU, name, pack size, the account’s price and stock, with a quantity field right there. Enter adds the line, Tab moves to quantity, and focus returns to the search box. A buyer keying 40 lines should never need the mouse.
Know what your platform gives you out of the box. Adobe’s Quick Order matches on SKU or the first few characters of a product name, and accepts pasted SKUs one per line or comma-separated without spaces. Shopify’s Quick order list section, supported on free Shopify themes version 11.0.0 or later, is added to product pages. It is excellent for ordering twelve sizes of one glove, but it is not an order pad for the whole catalogue. That needs a custom section or app, which is one input into the Shopify Plus versus headless decision. Search for browsing is a different problem, covered in our piece on faceted search for large catalogues.
Account-level pricing, visible before anyone asks
A buyer will not submit an order when they are unsure of the price. So the account’s net price must appear everywhere: search results, quick-order rows, saved carts and the upload report. Showing list price and applying the discount at checkout guarantees a phone call.
Under the hood, the price is worked out per company and often per location. The usual order is contract price list, then volume breaks, then catalogue default. Volume breaks belong next to the quantity field, so a buyer at 10 units can see what 12 would cost without leaving the row.
Personalised pricing has a performance cost. Full-page caching assumes everyone sees the same page, and contract prices break that assumption. The common fix is to cache the page layout and fetch prices separately with account-scoped keys, either in the browser or at the edge. Ask any supplier how they plan to handle this. A vague answer is a warning sign.
Finally, decide which system owns the price. If the ERP owns pricing and syncs nightly, the portal can show a price that changes before invoicing. Either sync in real time for priced lines or tell the buyer when prices were last confirmed.
How to tell whether the phone has stopped ringing
Track the share of repeat orders each key account places through self-serve, time from login to submitted order, and the share of uploaded lines that match on the first try. Two warning signs are especially useful: rep-placed orders that duplicate an existing saved cart (the buyer could not find the cart) and searches with no results that look like part numbers (your cross-reference is incomplete).
The prize is worth measuring. Among organisations that offer e-commerce, McKinsey reports it now generates more than one-third of revenue, ahead of in-person sales.
Take ten recent phone orders from your largest accounts and try to place each one through your portal using only the buyer’s original spreadsheet. Every lookup you had to make is a line in your brief.
Frequently asked questions
What is the difference between a saved cart and a requisition list in B2B ecommerce?
A saved cart is usually a single order in progress that a buyer intends to submit. A requisition list is a reusable template of products and quantities that a buyer loads repeatedly, such as a weekly consumables list. Both should store SKUs and quantities only and resolve prices fresh each time they are opened.
Should a B2B quick order form accept Excel files or only CSV?
Accept both. Most procurement teams export order lines from an ERP or keep them in a spreadsheet, and forcing a CSV conversion adds a step where leading zeros and formatting are often lost. Pair the upload with a column-mapping screen that remembers each account’s layout.
How should customer part numbers be handled in SKU search?
Store a cross-reference of each account’s own part numbers against your SKUs and index it per account. Search and CSV upload should both check that cross-reference after an exact SKU match fails, so buyers can order using their own vocabulary.
Does Shopify Plus support quick ordering natively?
Partly. Shopify offers a Quick order list section on recent versions of its free themes, which shows a product’s variants in a table with quantities and prices. It works on a single product page, so a cross-catalogue order pad with SKU search and file upload needs a custom section or an app.
How do you show contract pricing without slowing the site down?
Cache the page shell that every visitor shares, then fetch account-specific prices separately using cache keys scoped to the company or location. This keeps pages fast while ensuring each buyer sees their own negotiated price.
Which metrics show that a reorder interface is working?
Track the share of repeat orders placed through self-serve per key account, time from login to submitted order, and first-pass match rate on file uploads. Watch rep-placed orders that duplicate a saved cart and zero-result searches that look like part numbers.
Make reordering faster than a phone call
Saved carts, forgiving CSV upload, part-number search and visible contract pricing decide whether procurement teams self-serve. Moburst Digital Experience designs and builds reorder flows that let your key accounts place a correct order without calling their rep.