Average order value is the most-neglected margin indicator in mid-market e-commerce. While all attention focuses on conversion rate and acquisition cost, the most profitable lever often remains invisible: growing the cart at the moment of purchase. Of all available tools (cross-sell, up-sell, free shipping above X), bundles and product packs move the needle most — between +18% and +35% AOV on stores that deploy them properly.
On PrestaShop, bundles are misunderstood and underused. The native « Pack » is limited, VAT raises questions, return management is complex, and many merchants give up. This article reviews the three bundle families, technical mechanics on PrestaShop, measured ROI, and pitfalls that fail 80% of deployments.
Three bundle families in 2026
Family 1: fixed pack
A fixed pack is a virtual product composed of several references at determined quantities, sold at a single price lower than the sum of components. Example: « Coffee discovery pack » with 3 different bags at €19.90 (instead of €24).
- Use cases: obvious complementary products (kit, set, gift box, discovery basket).
- Advantage: simple to model, predictable basket, controlled margins.
- Limit: no personalization, buyer takes all or nothing.
Family 2: composable bundle (mix & match)
The buyer chooses N products from a set themselves, with declining pricing. Example: « 3 t-shirts for €39 », buyer picks their 3 t-shirts from 50 references.
- Use cases: fashion, cosmetics, books, wines.
- Advantage: high conversion rate (personalization feeling, perceived good deal).
- Limit: high technical complexity (stock management, dynamic product page, cart).
Family 3: Frequently Bought Together (FBT)
Suggest on the product page « customers who bought this also bought » with one-click add. Dynamic bundle, proposed but not imposed.
- Use cases: universal but particularly effective on electronics, accessories, materials.
- Advantage: zero merchandiser effort if well-automated on algorithm.
- Limit: less powerful than fixed packs (customer can refuse), requires order data volume to be relevant.
Measured ROI: +18 to +35% AOV
From PrestaShop store audits 2025-2026 having deployed bundles structurally:
- Properly merchandised fixed pack: +12 to +22% AOV on visitors seeing a pack on home or dedicated category.
- Composable bundle: +20 to +35% AOV, +5 to +12 conversion points on dedicated bundle page vs individual product pages.
- Well-algorithmic FBT: +8 to +18% AOV on the portion of visitors accepting suggestion (typically 5-15% of buyers).
Combined effect: on a store with €75 AOV, introducing structured bundles typically raises AOV to €90-105 over 6-9 months. For a €1M/year store, that’s €200-400K additional revenue without acquisition cost.
Implementation on PrestaShop 8 and 9
Fixed pack: use native functionality
PrestaShop offers a « Pack » feature in the product back-office. Configuration:
- Product type: Pack.
- Add component products with quantity.
- Define if pack stock is calculated from components (recommended option) or managed independently.
- Configure component stock decrement on sale.
Native limit: the pack product page displays components read-only, without personalization. For elaborate marketing packs, theme customization or a module is needed.
Composable bundle: module required
Native PrestaShop doesn’t cover mix & match. Relevant modules in 2026:
- Dedicated mix & match module (several on Addons, €80-250).
- Custom Symfony development for high-volume stores or specific logic (€4-8K dev).
Technical logic:
- Dedicated bundle page (« Compose your pack ») with filterable list of eligible products.
- Cart add: single « Bundle X » line with component sub-lines, or several lines grouped by bundle_id.
- Price: calculation at add time (bundle price replaces sum of components).
- Stock: verify each component in stock at add time, decrement at validation.
Frequently Bought Together: modules + data
Available modules on Addons (DataFirefly dfcartcrosssell, others). Default algorithm: co-occurrence in past orders. More advanced variants: attribute similarity, navigation-based AI recommendations.
Success key: have enough order data (at least 1,000 orders/month) for co-occurrence to be statistically reliable. Otherwise, editor recommendations (manual FBT) are more relevant.
VAT and margin stakes
VAT
If the bundle contains products at different VAT rates (e.g., book at 5.5% + DVD at 20%), French tax rules require proportional VAT allocation across components, not a single rate. On the invoice, each component line must show its rate. Native PrestaShop pack handles allocation correctly; a custom bundle must be verified by the accountant.
Margin calculation
Common error: applying a discount on a bundle that eats all the margin on high-end components. Watch case-by-case:
- Gross margin component by component.
- Margin on complete bundle (per applied discount).
- Verify overall pack product margin stays positive and coherent with margin target.
Partial returns
If the customer returns 1 product from a pack of 3, how to refund? Three practical options:
- Refuse partial returns (explicit policy, product page mention).
- Refund at unit price outside pack (customer loses pack discount).
- Refund pro-rata of bundle value (customer keeps pro-rata discount).
The model must be clear, documented in T&Cs, and implemented in the return workflow. Without clarity, customer conflict and GDPR risk on undocumented processing.
SEO and merchandising: bundle as destination page
A well-built bundle isn’t just a catalog product — it’s an SEO page in its own right:
- Dedicated URL with optimized slug (
/coffee-discovery-pack-3-bags). - Specific title and meta description, optimized on target query (« coffee discovery pack »).
- Rich description: compositions, usage suggestions, comparison with individual purchase.
- Schema.org Product with offer and ProductCollection referencing components.
- FAQPage Schema on recurring questions (can items be substituted? delivery? gift offer?).
Well-referenced bundles capture organic traffic distinct from individual product pages — generally with higher purchase intent (« set », « kit », « pack » are end-of-funnel queries).
Pitfalls to avoid
1. Cannibalizing unit sales
If bundle discount is too strong, buyers who would have bought one product switch to the bundle. Gross margin drops instead of rising. Calculate bundle / unit mix before and after deployment, adjust discount to maximize total margin not raw AOV.
2. Creating bundles without merchandising coherence
« We’ll make packs to raise AOV » without product usage logic. Result: 50 packs created, none sell. Effective bundles have a narrative: « starter kit », « season essentials », « gift offer ». Without narrative, the bundle is invisible.
3. Underestimating stock complexity
On a composable bundle where each component may stockout, the system must handle available components in real time. A bundle page showing out-of-stock components bleeds conversion. Stock sync mandatory.
4. Not tracking bundles separately
Without specific tracking (distinct item_id in GA4, « Bundle » category in data layer), impossible to measure real lever ROI. Tagging bundles is the most-often forgotten step.
5. Confusing bundle and cross-sell
Cross-sell suggests adding a product to the current cart. Bundle is a product in itself, with dedicated page and bundle price. Both can coexist, but merchandising and SEO logic differ.
Conclusion: the most profitable AOV lever, underused
In 2026, bundles and product packs remain one of the most profitable growth levers on PrestaShop, and one of the least exploited relative to their potential. ROI is measurable within 30 days on properly deploying stores, with lasting effect beyond.
Success isn’t technical — PrestaShop handles native pack honestly, third-party modules cover mix & match — but merchandising and data: choose bundles with clear narrative, calibrate discount to maximize margin, track to measure, iterate each quarter. A store deploying 5-10 well-designed bundles, with dedicated SEO pages and coherent narrative, captures an AOV lever often surpassing paid acquisition efforts.
