> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/bundles/shopify-bundles-that-fulfil-as-skus.md).

# Shopify bundles that fulfil as SKUs

See how Roadmap bundles stay grouped for shoppers while Shopify orders still use real SKUs.

Use Roadmap Bundles when you want a bundle experience for shoppers without creating duplicate fulfilment SKUs.

{% hint style="info" %}
Shoppers see a bundle. Shopify orders still contain the real component products and SKUs.
{% endhint %}

### What shoppers see

When a bundle is added to the cart, the included items stay grouped together.

This makes it clear what is included and reduces checkout confusion.

![Cart drawer showing a bundle with items grouped under an "Included in this bundle" section](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/HjSNovvXtlEQop2LLgqN/bundles%20cart%20open.jpg)

### What shoppers can and cannot change

After a bundle is in the cart:

* shoppers cannot add extra items into the bundle group
* shoppers cannot remove one item from the bundle group
* shoppers remove the whole bundle instead

If you want shoppers to choose items, set that up before the bundle is added to cart. Variant bundles are designed for that flow.

### What Shopify sees after purchase

Shopify creates the order with the individual component products.

Each line item can include:

* the product title
* the SKU
* a bundle reference such as **Part of: \[Bundle name]**

Your team fulfils the component SKUs, not a new bundle SKU.

### Why this matters operationally

* no duplicate fulfilment SKUs
* normal inventory deductions on component products
* standard ERP and 3PL workflows
* easier picking and packing for warehouse teams

### Common questions

<details>

<summary>Does Roadmap create a new bundle SKU?</summary>

No. The bundle sells as a grouped offer on the storefront, but fulfils using the existing component SKUs.

</details>

<details>

<summary>Can customers change bundle contents in the cart?</summary>

No. Bundle items stay locked together in the cart to protect the offer and keep fulfilment accurate.

</details>

<details>

<summary>How do I find bundle orders in Shopify?</summary>

Search Shopify orders by the bundle name, then review the line items for the bundle reference.

</details>

<details>

<summary>Will my ERP or 3PL need changes?</summary>

Usually no. Most systems continue to work because the order contains normal Shopify line items with real SKUs.

</details>

### Related guides

* [Bundle fulfilment & ERP integration](https://docs.roadmap.so/bundles/bundle-fulfilment-and-erp-integration.md)
* [Fixed vs variant bundles](https://docs.roadmap.so/bundles/fixed-vs-variant-bundles.md)
* [Bundle sales analytics & exports](https://docs.roadmap.so/bundles/bundle-sales-analytics-and-exports.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/bundles/shopify-bundles-that-fulfil-as-skus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
