Amazon's next virtual multipacks go on sale November 11. Filter for VMP_ before then
Amazon creates virtual multipack listings on selected FBA brand-owned ASINs and puts this wave on sale November 11, 2026. Default price is single-unit times quantity—and a deleted multipack cannot come back during the pilot.

Amazon's virtual multipack pilot creates multi-unit offers from existing FBA single-pack inventory with SKUs prefixed VMP_. The current wave was created by October 28, 2026 and goes on sale November 11; sellers were asked to review by November 10. Filter Manage All Inventory for VMP_, check price, title, images, and stock drain, edit only on the Edit virtual multipack page, and decide deletes before customers buy—reactivating a deleted multipack is not available during the pilot.
What a virtual multipack is
Amazon's virtual multipack pilot creates listings that sell two or more units of the same single-pack FBA product as one offer. Amazon fulfills by picking that many singles from existing FBA stock—you do not pack a new kit. Unlike a bundle, the multipack does not mix different ASINs.
Each multipack gets its own ASIN, a SKU that starts with VMP_ and shows the pack size (for example 2_PK), and title language such as "Pack of 2." It appears as a variation of the single pack. If no variation family exists, Amazon may create one, which changes how the detail page groups. Default price is the single-pack price times the pack size, and it can follow the single-pack price when that changes unless you set a multipack-specific discount.
Virtual multipacks sell inventory you already have, at a pack price you may not have chosen.
The current wave covers FBA brand-owned ASINs Amazon selects—there is no opt-in. FBM listings are outside this pilot. Amazon planned creation by October 28, 2026, with customer availability on November 11, 2026, and asked sellers to review by November 10. The pilot is described as running through 2027.
Sequence of work
Virtual multipack wave dates
- Oct 13 notice
Sellers report a review-by November 10 ask for the wave.
- By Oct 28
Amazon creates the multipack listings on selected FBA brand-owned ASINs.
- Nov 10
Practical last day to price, edit, or delete before customers buy.
- Nov 11
Multipacks go on sale; orders pull multiple units from single-pack FBA stock.
What to do before November 11
Filter for VMP_. In Manage All Inventory, find every multipack. Allow time for a new listing to look complete.
Check price. A pack of two at exactly 2× may be fine—or it may undercut your intentional multipack strategy. Set a multipack discount only if that is the policy.
Check stock math. Each multipack order pulls several units from the same single-pack pool. A November spike drains inventory faster than your single-unit forecast assumed.
Edit in one place. Amazon directs edits through the Edit virtual multipack page. Flat files, the API, and other tools can break the listing. Pack size cannot be changed after creation.
Decide deletes now. A deleted virtual multipack cannot be reactivated during the pilot. Leaving a bad pack live is often worse than deleting it before sale—but deletion is a one-way door for now.
Virtual multipacks sell inventory you already have, at a pack price you may not have chosen.
Variation and review side effects
If Amazon creates a variation family for you, review how the detail page reads and how reviews share across the family under Amazon's review-sharing rules. Multipacks are catalog surgery, not only a pricing footnote.
If you sell the same product FBA and FBM, only the FBA offer is in scope. Do not assume the FBM listing gained a pack twin.
Decision guide
Fix before sale vs mistakes that stick
| Consideration | Do before Nov 11 | Hard to undo later |
|---|---|---|
| Find VMP_ listings | Filter Manage All Inventory for VMP_ | Discovering pack pricing from a customer order |
| Set the pack discount | Set multipack discount if default × pack size is wrong | Changing pack size—Amazon says it cannot change once created |
| Edit in the right place | Edit only on Edit virtual multipack page | Flat file or API edits that break the listing |
| Delete unsupported packs | Delete packs you will not support | Expecting to reactivate a deleted multipack during the pilot |
How this sits next to fee letters
Sellers already juggling the 2027 FBA fee letter should treat VMP_ review as the same class of homework: a named owner, a filter, a decision per ASIN family. Do not open a multipack committee. Extend the contribution-margin working group that already owns fee changes.
Inventory and ads after packs go live. Once customers can buy multipacks, sponsored ads and retail dashboards that assume single-unit velocity will misread sell-through. Brief the ads owner that a multipack order is multiple units from the same pool. Brief replenishment that safety stock math needs a multipack-aware view through peak.
If a multipack undercuts a wholesale or DTC offer you already sell elsewhere, decide whether Amazon pricing should match or whether you delete the VMP_ listing. Channel conflict is easier to prevent on November 10 than to explain on November 20.
Keep a simple log: ASIN, VMP_ SKU, quantity, action (keep / reprice / delete), owner, date. That log is what you bring to the QBR when someone asks why a multipack appeared. Amazon selected the ASINs; you still owe the business an answer.
Variation families and the detail page. When Amazon creates a variation family for a multipack, read the detail page as a shopper would. Titles, images, and the way reviews share across the family can change how the single-pack offer reads. If the family makes the hero offer look wrong, fix it on the Edit virtual multipack page or delete before November 11.
Brand owners with agency partners should assign one editor for VMP_ changes. Multiple people "fixing" through flat files is how listings break. Put the Edit virtual multipack URL in the agency SOP with a stop-ship note on other tools.
After November 11, spot-check orders: confirm unit pull counts match pack size, and that fulfillment fees and ads attribution still make sense to finance. Multipacks are catalog and inventory work at once.
Sellers outside the selected ASIN set should still filter for VMP_ once—Amazon's automation can surprise catalogs that thought they were excluded. Five minutes of filtering beats a week of confused tickets after November 11.
Put this into practice
Before November 11, export or filter VMP_ SKUs, mark keep / reprice / delete, and confirm nobody will "fix" packs through a flat file. For ongoing marketplace catalog control, keep a weekly VMP_ check through peak.
If pack offers and inventory truth keep drifting apart, talk to TWIMCO.
If your brand registry and Seller Central access are split across agencies, make sure both parties filter for VMP_ before November 11. Multipacks created on brand-owned ASINs can land where only one party is watching. Shared ownership without a shared filter is how packs go live unpriced.
After the wave is on sale, watch return rates on multipack ASINs separately. A pack that looked fine on paper can create return friction if shoppers expected a sealed kit and received singles.
For brands that already sell intentional multipacks as separate FBA ASINs, compare those against any VMP_ Amazon created. Two multipack strategies on one detail page confuse shoppers and split reviews. Pick one approach per family before November 11 traffic arrives.
Set a Slack or email alert for any new SKU beginning with VMP_ through December so later pilot waves do not arrive unread.
Brief CS on pack-size language so tickets about "I ordered two but got two singles" have a written answer ready on November 11.
November 11 is a sell-through event; November 10 is still a catalog decision day.
If price sync tools touch VMP_ SKUs, pause them until the Edit page policy is clear.
Then stop editing elsewhere.
Share the log with finance.
Done.
Related work: Paddle8
We build alongside the people doing the work.
Bring us the problem you’re thinking about.