Adobe Commerce ships requisition lists and quick order as native B2B features, but neither renders on a Hyva storefront out of the box. The buyer-facing screens are legacy Knockout applications. To give wholesale buyers fast reorder on Hyva you need the Hyva Enterprise B2B modules, a compatibility bridge, or a custom Alpine.js rebuild.
For a distributor whose buyers place the same 40-line order every week, reorder speed is the difference between a five-minute cart and an abandoned one. This guide covers what requisition lists and quick order actually do, why they break on Hyva, and how to ship them fast without losing the Core Web Vitals a Hyva development project was supposed to win.
What requisition lists and quick order actually do
These are two separate Adobe Commerce B2B features that solve the same problem from different angles: getting a known, repeated basket into the cart without hunting through the catalog.
Requisition lists are saved, named baskets of products a buyer reorders on a schedule. Unlike a wishlist, a requisition list is not consumed when the buyer adds it to cart, so the same list survives week after week. A buyer can keep several lists (a weekly restock, a seasonal order, a per-location list) and add the whole list or selected lines to the cart in one action. Each line carries the live product data: name, SKU, current contract price, and configurable options.
Quick order is a form for buyers who already know their SKUs. They type or paste SKUs with quantities, use autocomplete by SKU or product name, or upload a CSV, and the form resolves each SKU to a catalog product before adding everything to the cart at once. For a buyer working from a printed pick sheet or an ERP export, this collapses a 30-minute catalog crawl into a paste and a click.
Both features are part of the Adobe Commerce B2B module set, which ships disabled and has to be enabled in the admin before buyers see anything. They are not in Magento Open Source. If you are on Open Source you get them through a third-party extension or a custom build, which changes the Hyva compatibility picture described below.
Why the default B2B storefront breaks on Hyva
Hyva replaces Magento’s legacy Luma frontend stack (RequireJS, Knockout, jQuery) with Alpine.js, Tailwind, and native JavaScript. That swap is exactly what produces the PageSpeed and Core Web Vitals gains. It is also what breaks the default B2B interfaces.
The Adobe Commerce B2B backend, its GraphQL and REST APIs, the data models, the admin, and the pricing logic all work untouched under Hyva. The problem is purely the storefront rendering layer. Company accounts, requisition lists, negotiable quotes, and quick order are all built as KnockoutJS storefront applications. Knockout is not loaded on a Hyva theme, so those screens render blank or throw. Adobe’s own documentation confirms these are separate storefront applications rather than server-rendered blocks, which is why a theme swap takes them down.
This catches teams off guard because the feature still works in the admin and over the API. A merchant tests B2B on their old Luma theme, sees requisition lists working, migrates to Hyva, and discovers the buyer-facing screen is gone even though nothing changed in the backend. The Magento development work is intact. The frontend just has nothing to render the Knockout widget it expects.
The three ways to get fast reorder on Hyva
You have three real paths. The right one depends on your Adobe Commerce license, your budget, and how much the reorder flow diverges from the default.
| Approach | What it is | Best for | Rough effort |
|---|---|---|---|
| Hyva Enterprise B2B | Official Hyva-native rebuilds of the B2B storefront modules, licensed on top of Hyva | Adobe Commerce merchants who want supported, standard behavior | Low: install and configure |
| Compatibility module | A third-party or agency bridge that adapts the Luma B2B frontend to run under Hyva | Teams on a tight budget who can accept a graft | Medium: install plus QA |
| Custom Alpine.js build | A ground-up reorder UI built in Alpine and Tailwind against the B2B GraphQL API | Merchants with non-standard workflows or Open Source B2B | High: design and build |
Hyva Enterprise B2B
Hyva Enterprise is the paid bundle that adds Hyva-native versions of the Adobe Commerce B2B and Sensei-powered features, including company accounts, requisition lists, quick order, and negotiable quotes. It is the shortest path for a merchant already licensed for Adobe Commerce B2B, because the screens are built and supported by Hyva and behave like the defaults buyers already know, with coverage that Hyva has extended across the Adobe Commerce B2B set over successive releases. You install the modules, configure the B2B features in the admin, and the storefront renders in Alpine and Tailwind. This keeps the speed you bought and the behavior your buyers expect. Hyva’s own enterprise documentation covers the install and configuration steps.
A compatibility module
If Hyva Enterprise is not in scope, a compatibility bridge can run the legacy B2B frontend inside a Hyva page. This is the cheapest route, but it grafts a Knockout island into an Alpine page, which adds the RequireJS and Knockout payload back onto the pages that use it. That is a real Core Web Vitals cost on exactly the pages (account, reorder) where B2B buyers spend their time. Treat it as a stopgap and measure the field data before and after.
A custom Alpine.js rebuild
When your reorder flow does not match the default (custom approval steps, ERP-driven pricing, a punchout tie-in, or Open Source B2B with a third-party module), a custom build against the B2B GraphQL API is the honest answer. You render the quick order form and requisition list in Alpine, call the same APIs the default UI would, and keep everything inside the Hyva build. This is the most work, but it is also the only path that gives you a reorder experience shaped around how your buyers actually order, and it keeps a single, fast frontend stack.
Performance: keep reorder fast, not just present
The reason to migrate to Hyva is speed, so a B2B build that ships reorder but tanks the account pages defeats the point. A few practitioner rules keep reorder both present and fast:
- Load the quick order and requisition data over GraphQL on demand, not on every page. A buyer hits reorder a few times a session, so there is no reason to ship that payload site-wide.
- Keep the reorder screens out of full page cache and serve buyer-specific data as private content, the pattern Hyva favors over ESI hole-punching.
- Paginate long requisition lists. A list with 400 lines should not render 400 DOM nodes at once. Virtualize or paginate so the initial render stays cheap.
- Debounce SKU autocomplete on the quick order form so a buyer pasting 50 SKUs does not fire 50 rapid catalog lookups.
These are the same disciplines that protect Interaction to Next Paint on any Hyva build, applied to the screens B2B buyers use most.
Requisition lists versus quick order versus reorder: which to offer
Merchants often ask which of these a buyer needs. The answer is usually more than one, because they serve different buying patterns.
| Feature | Buyer starts from | Best when | Persists after cart |
|---|---|---|---|
| Requisition list | A saved, named list they curate | Repeated baskets that change slowly | Yes |
| Quick order | A list of SKUs they already have | The buyer works from an ERP or pick sheet | No |
| Reorder from history | A past order | They want to repeat a specific past order | N/A |
A wholesale buyer who restocks the same core catalog weekly wants requisition lists. A procurement buyer working from a supplier SKU export wants quick order. Most B2B storefronts benefit from offering both, plus reorder from order history as a fast third path.
Where this sits in a wider B2B build
Requisition lists and quick order are one layer of a B2B storefront. They usually arrive alongside company accounts and roles, tiered and contract pricing, negotiable quotes, and payment on account, and they often need to reflect ERP-driven stock and pricing to be trustworthy. Bemeir builds these as a single system rather than a pile of features, and you can see the shape of that work on the Bemeir technology partners ecosystem that connects the storefront to payments, ERP, and fraud tooling. If you want the broader context of who does this work and why, the about Bemeir page covers the team behind the first US Hyva Gold Partner.
Platform choice matters here too. Adobe Commerce still has the deepest native B2B feature set, which is why wholesale reorder lives here, but Bemeir also delivers on Shopify, Shopware, and BigCommerce when a merchant’s catalog and account complexity fit those platforms better. For a fuller compatibility view of every B2B feature on Hyva, our Adobe Commerce B2B on Hyva compatibility guide maps each one, and the Hyva for B2B frontend guide covers account hierarchies and tiered pricing. The whole point of working with a specialist like Bemeir is that these decisions get made once, correctly, instead of discovered after a migration.
FAQ
Do requisition lists and quick order work on Magento Open Source?
Not natively. Both are Adobe Commerce B2B features. On Open Source you add them through a third-party extension or a custom build. That also changes the Hyva story, because you are then adapting an extension’s frontend rather than the Adobe Commerce B2B storefront, and few Open Source B2B extensions ship a Hyva-ready frontend.
Why do my requisition lists show up in the admin but not on the Hyva storefront?
Because the backend and the storefront are separate. The B2B data and admin run fine under Hyva. The buyer-facing screen is a Knockout application that Hyva does not load, so it renders nothing. You need a Hyva-native version of that screen, from Hyva Enterprise, a compatibility module, or a custom build.
Is quick order or a requisition list better for wholesale reordering?
They suit different buyers. Quick order is fastest when a buyer already has SKUs, from an ERP export or a pick sheet, and wants to paste and go. Requisition lists win when a buyer reorders a curated basket that changes slowly. Most wholesale storefronts should offer both.
Will adding a compatibility module hurt Core Web Vitals?
It can. A compatibility bridge runs the legacy Knockout frontend inside a Hyva page, which reloads the RequireJS and Knockout payload on the pages that use it. That is a measurable cost on account and reorder pages. Measure field data at the 75th percentile before and after, and treat the module as a stopgap rather than the destination.
How long does a custom Alpine.js reorder build take?
It depends on how far your flow diverges from the default. A close-to-standard quick order and requisition list built against the B2B GraphQL API is a contained project. Custom approval steps, ERP-driven pricing, or punchout ties add scope. The build cost is higher than installing Hyva Enterprise, but it is the only route that shapes reorder around your buyers rather than the default.
Does Hyva Enterprise cover all of Adobe Commerce B2B?
Hyva Enterprise covers the interactive B2B storefront features that break on Hyva, including company accounts, requisition lists, quick order, and negotiable quotes. It is the supported path for Adobe Commerce B2B merchants. Confirm your specific feature list against the current Hyva Enterprise documentation before scoping, since the covered set expands over time.
Fast reorder is where B2B buyers judge a storefront. Get it wrong on Hyva and the migration that was supposed to speed up the site leaves your best customers staring at a blank account page. Get it right and you keep the speed and the workflow. If you are planning a Hyva build with real B2B buyers behind it, that is the exact problem Bemeir was built to solve.
