Simple Bundles & Kits review

Document the exact kits, multipacks, mix-and-match products, build-your-own sets, nested bundles, subscription bundles and wholesale packs the store needs. Record parent and component products, quantities, SKUs, inventory locations, sales channels, fulfilment routes and expected order volume. Baseline AOV, conversion rate, margin, returns, fulfilment errors and manual handling. Assign Shopify orders and inventory as operational truth, finance as the authority for booked revenue and margin, the 3PL, WMS or ERP as fulfilment truth and Simple Bundles as the bundle-processing layer.

Use Simple Bundles 2.0 unless a documented legacy dependency requires 1.0. Map which routes can use Shopify Cart Transform before checkout and which require post-order editing, including subscriptions, external marketplaces, post-purchase apps and orders created outside native checkout. For orders Shopify cannot edit, choose between an associated component order and a single-SKU inventory-only fallback. Associated orders are disabled by default for installations from 19 June 2026 and require customer-data permission, so obtain privacy and operational approval before enabling them.

Compare the Free plan for up to three bundles with Basic, Grow & Advanced and Plus. Confirm the merchant's Shopify plan, live app-billing price, monthly or annual term, bundle limits, multi-location requirements, POS locations, API, Flow, order metafields, Hydrogen, support level and theme assistance. Record that public prices are starting amounts and Freshly Commerce's terms state that paid subscriptions are billed in advance, renew automatically until cancelled, are final and non-refundable and remain active until the end of the current billing cycle after cancellation.

Choose Simple Bundle for fixed kits and multipacks, Infinite Options where customers choose from controlled options and BYOB for flexible mix-and-match builders. Decide whether the bundle uses a parent SKU or exposes only component SKUs to fulfilment. Create stable and unique product and variant SKUs, component quantities, option rules, minimum and maximum selections and nesting. Simple Bundles supports nested bundles up to ten processing levels. Audit quick-add, collection and recommendation buttons because unsupported shortcuts can bypass required Infinite Options selections.

Choose parent-price sync, manually fixed pricing or dynamic component pricing. Define how bundle price is allocated across components, including compare-at values, rounding and zero-value items. Test discount-code combinations, automatic discounts and quantity conditions because a bundle can count as one line item even when it contains several units. Set tax and VAT treatment at component level. Validate Shopify Markets and B2B catalogues because component prices can fall back to the default catalogue or converted base prices rather than the intended market-specific value.

Confirm the component quantities consumed by each bundle and whether availability should require all components at one fulfilment location or use an approved pooled or single-location method. Test the limiting component, low stock, out of stock, continue-selling settings, reserved inventory and inventory resynchronisation. Simple Bundles 2.0 can process up to 50 unique component items through Cart Transform before using an order-edit fallback, so record any large bundle that can cross this threshold. Validate every location used by Shopify, POS and the fulfilment provider.

Test native online checkout through Cart Transform. For subscriptions, document that one-time orders can use Cart Transform while subscription orders generally require post-order editing unless a supported cart-level integration is used. Configure the paid-plan POS extension for Infinite Options and validate automatic splitting for simple bundles. Test Shop and any external channel against the approved fallback. For Hydrogen, expose the documented bundle metafields and ensure the storefront sends complete selections. Review requires_components behaviour because incompatible channels and accelerated payment methods can be unavailable.

Map the exact parent and component line items, SKUs, quantities, locations, properties, discounts, fulfilment requests and order metafields that the 3PL, WMS or ERP receives. Confirm whether the provider consumes Cart Transform output, listens for post-order edits or needs an associated order. Ensure the integration does not fulfil the parent and components twice and does not capture an order before editing completes. Configure Shopify Flow, CSV or the paid-plan API only where ownership and error monitoring exist. Run failure tests for delayed edits, rejected edits and missing customer-data permission.

Create controlled orders for every builder, SKU method, channel, payment type, market, tax rule, discount, subscription, inventory location and stock state. Compare storefront, cart, checkout, Shopify order, associated order, 3PL or WMS pick list, component inventory, fulfilment, customer notification, analytics and finance. Test cancellations, partial and full refunds, returns, restocking and exchanges. Record differences caused by Cart Transform, order editing and single-SKU fallback rather than assuming all routes produce identical orders.

Launch a controlled set of bundles and channels first. Export the bundle configuration and preserve the approved SKU, price, location and integration maps. Review Simple Bundles analytics, Shopify bundle sales, AOV and units alongside finance margin, returns, inventory adjustments, fulfilment errors, customer contacts and manual handling. Separate bundle-attributed sales from incremental commercial impact. Expand only after operational accuracy and contribution thresholds are met, and keep a rollback plan for the prior app or product structure.