Skip to content

Settings and activity

1 result found

  1. 97 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rutger van den Brule commented  · 

    Hi, we’re evaluating the Bundles blueprint for our pet food shops (Shopware 6, multiple EU markets). +1 on configurable quantities per component (e.g. 3x Product X, or 2x X + 2x Y). That’s essential for us. On top of the points already raised, these are missing for our use case:

    1- Bundle as option in the variant selector. We sell a product in variants 700 g and 2 kg and want to offer a “6 kg value pack” (= 3x 2 kg) in the same selector: 700 g | 2 kg | 6 kg value pack. The bundle can stay a separate product, as long as the customer sees it as one product option.

    2- Existing variants as components. We need to keep our native variant structure (it’s used by marketplaces, feeds, analytics and our WMS). Variants should be selectable directly as bundle components.

    3- Availability derived from component stock. No separate stock for the bundle: 20x 2 kg in stock should mean max. 6 bundles of 3x 2 kg available, and selling one bundle should reduce the 2 kg stock by 3.

    4- Order structure via Admin API. For WMS integrations we need the bundle and its components as separate (child) line items, with SKU, quantity per component and the parent/child relation clearly available in the Admin API and order exports.

    5- Visibility control per bundle. Option to hide a bundle from listings and search while keeping it reachable via direct URL, cross-selling or the component’s PDP.

    6- Component data on the bundle PDP. A bundle should have its own description, but be able to show data from its components (e.g. ingredients, nutritional values, feeding guidelines), once per unique component, via CMS elements or Twig.

    Thanks, looking forward to the next iteration!