> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/commerce-and-integrations/woocommerce/add-to-cart.md).

# WooCommerce Add to Cart Methods

Sell bundles and modular products through your WooCommerce cart. Learn how Mimeeq turns configurations into cart items and where each method is set up.

Some products are simple — a customer picks some options, one item goes in the cart. But Mimeeq also supports more complex setups: a single configuration that should become several cart items, or a "bundle" made up of multiple parts sold together. This article explains how that's set up and what actually happens when it reaches WooCommerce.

**Where this gets configured:** the detailed bundle rules (what counts as a "component", how pricing splits, which WooCommerce products or variants map to which part) are set up **in your Mimeeq account**, not in WordPress. WordPress only needs one thing turned on to support any of it — see below.

{% hint style="warning" %}
**Required first step:** turn on **Enable advanced add-to-cart functionality for configured products** under **WP Admin → Mimeeq → Extension Settings**. Without this, only simple single-product configurations work.
{% endhint %}

***

## Two kinds of products, two kinds of bundling

### Standard (single) products

If a bundle needs to be built out of otherwise-separate WooCommerce products, there are two ways Mimeeq can build it:

<table><thead><tr><th width="58.03515625">#</th><th>Method</th><th>What happens</th></tr></thead><tbody><tr><td>1</td><td><strong>Cart Bundle</strong></td><td>The bundle is put together on the fly, right when the customer adds it to the cart — no extra WooCommerce products are created ahead of time</td></tr><tr><td>2</td><td><strong>Admin Bundle</strong></td><td>A bundle product is created in WooCommerce ahead of time</td></tr></tbody></table>

### Modular products

Modular products are made of interchangeable parts (think: a sofa where the customer picks the frame, then the cushions, then the legs, each as its own "element"). Mimeeq supports four different ways to turn that into WooCommerce cart items:

<table><thead><tr><th width="61.30859375">#</th><th>Method</th><th>What the customer's cart ends up with</th></tr></thead><tbody><tr><td>1</td><td><strong>Custom Product</strong></td><td>One single product, with all the chosen elements recorded as details on that one line</td></tr><tr><td>2</td><td><strong>WC All Elements as Single Items</strong></td><td>Every element becomes its own separate line in the cart</td></tr><tr><td>3</td><td><strong>WC Single Bundle With All Elements</strong></td><td>All the elements are grouped together as one bundle line</td></tr><tr><td>4</td><td><strong>WC Custom Defined Logic</strong></td><td>A custom mix of the above, following rules you define in your Mimeeq account</td></tr></tbody></table>

{% hint style="info" %}
Only elements the customer actually sees on the finish screen are included. Anything marked **Hide on Finish Screen** (in Mimeeq) is left out.
{% endhint %}

***

## Where the detailed rules live

All of the following is configured **in your Mimeeq account** (not in WordPress):

1. Open the product in your Mimeeq account
2. Go to its **Pricing and Codes** tab
3. Find **Add to Cart Configuration**
4. Choose the bundling method and fill in its details (component names, prices, quantities, which existing WooCommerce product or variant each part maps to, and so on)

![Add to Cart Configuration section in the Pricing and Codes tab of a Mimeeq product](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FbSldLHrW6Vqyd3MX5xUs%2F07-add-to-cart-methods-01-add-_1clj2c3.png?alt=media)

For the exact fields and options available on this screen, refer to Mimeeq's own help documentation — it may change independently of this WordPress plugin. As a rough guide, you'll typically be naming the bundle, deciding how its price is calculated (per-item Mimeeq pricing, or based on the WooCommerce product/variant price), and — for Cart/Admin Bundles — mapping each component to a WooCommerce product, variant, or a brand-new custom product created on the spot.

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>WooCommerce Admin Settings</strong></td><td>Configure API, cart, product naming and sync settings.</td><td><a href="/commerce-and-integrations/woocommerce/admin-settings.md">WooCommerce Admin Settings</a></td></tr><tr><td><strong>WooCommerce Storefront Setup</strong></td><td>Add the configurator with Gutenberg blocks, Elementor or shortcodes.</td><td><a href="/commerce-and-integrations/woocommerce/storefront-setup.md">WooCommerce Storefront Setup</a></td></tr><tr><td><strong>Custom Field Mappings</strong></td><td>Map configuration data to WooCommerce product custom fields.</td><td><a href="/commerce-and-integrations/woocommerce/custom-field-mappings.md">WooCommerce Custom Field Mappings</a></td></tr></tbody></table>


---

# 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://help.mimeeq.com/commerce-and-integrations/woocommerce/add-to-cart.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.
