Add Bundle
Table of Contents
1. Features
Need to sell multiple products together as gift sets or product kits? Create one bundle item here, define which products it contains and in what quantities, and the warehouse automatically gathers every component for shipping when a customer orders — no need to place separate orders for each product.

Quick links: Form Fields | Stock Push Ratio Exceptions | Step-by-step
1.1 Form Fields
Basic Information
Fields marked * are required
| Field | How to fill | Notes |
|---|---|---|
| *Bundle Name | Enter a name that you and your team can easily recognize, e.g. "Christmas Gift Set A" | - |
| *SKU | Enter the bundle's SKU, e.g. GIFT-XMAS-2024 | See the FAQ below for SKU restrictions and reuse after deletion |
| Barcode | Type or scan the barcode | Optional; used for warehouse scanning |
| *Status | Toggle enabled or disabled | Enabled by default |
💡 Tip: A type prefix makes SKUs easier to recognize, e.g. GIFT- for gift sets, PROMO- for promotional bundles, SET- for kits.
Bundle Products
| Field | How to fill | Notes |
|---|---|---|
| *Product Name | Search by product name or SKU and select | If the same product with the same inventory type is added on multiple rows, they are automatically merged into one row with quantities summed on save; the same product can't have both a "Default Inventory Type" row and a row with a specific inventory type — see the FAQ below |
| *Quantity | Enter the quantity needed per set | Must be greater than 0 |
| Inventory Type | Select from the dropdown (optional) | When specified, shipping only uses that inventory type (e.g. sellable stock never ships defective items); when left unspecified, shipping follows the inventory type set on the order or sales channel |
1.2 Stock Push Ratio Exceptions
A bundle has no stock of its own. The quantity pushed to an e-commerce platform is the number of sets its component products can make, multiplied by a push ratio. By default every e-commerce account uses its own "Push Percentage"; you only need to add an exception under "Stock push ratio exceptions (optional)" when you want a specific account to use a different ratio for this bundle. You can set it while creating the bundle — no need to save first.
| Action | How | Notes |
|---|---|---|
| Add an exception | Click "Add exception" and pick an e-commerce account from the dropdown; the account's current push percentage is filled in, then change it to the number you want | "Push ratio" is required; each account can have only one row |
| Go back to the account's default | Delete that account's row and save | An empty ratio can't be saved — delete the whole row to go back to the default |
| Set more than 100% | Allowed, for deliberately pushing more than you have (overselling) | A yellow warning appears when a single row exceeds 100% or the ratios across accounts add up to more than 100% (counted per warehouse actually used; accounts without a fulfillment warehouse count toward the default warehouse) |
The dropdown only lists e-commerce accounts whose "Stock Push Method" is not "Off" and whose sales channel has "Product Mapping Rule" set to "By SKU" (unset counts as by SKU). Accounts using another rule are listed in the blue notice above: when platform orders come back, only channels that map by SKU can recognize a bundle, so bundle stock isn't pushed to those accounts.
How the pushed quantity is calculated
For each component product, take "sellable quantity ÷ quantity needed per set" (rounded down), take the smallest of these, then multiply by the push ratio (rounded down). For example, product A has 10 sellable and each set needs 2 (5 sets), product B has 3 sellable and each set needs 1 (3 sets): at 100% the push is 3; at 50% it's 1.
- A component's sellable quantity only counts stock this channel can ship: only stock in the e-commerce account's "Fulfillment Warehouse" counts (the default warehouse when none is specified), not other warehouses; a component with a specific inventory type counts only that type; "Default Inventory Type" counts only the sales channel's primary inventory type (the secondary inventory type only serves as a backup during allocation); stock that doesn't meet the channel's expiration requirement is excluded.
- A component that has its own stock push turned off still counts toward the bundle's buildable sets.
- After a bundle is deactivated or deleted, the next "Manual Stock Sync" sets this bundle's platform stock to 0 — unless its SKU is now used by another product or bundle, in which case 0 is not pushed so that item's platform stock isn't wiped out.
- Bundle quantities are recalculated and pushed when "Manual Stock Sync" is clicked on the e-commerce account detail page. When the account's "Stock Push Method" is "Scheduled sync (every 30 min)", a bundle whose component stock counted for that account (the sales channel's inventory types or those specified in the bundle, in the fulfillment warehouse), contents, push ratio, or active status changed is also recalculated and pushed in the next scheduled round (within about 30 minutes). "Push on inbound" doesn't include bundles. See EC Account Detail for the conditions.
1.3 Step-by-step
▸ Step 1: Fill in basic information
- Enter the Bundle Name
- Enter the SKU
- (Optional) Enter the Barcode
- Confirm the Activated
▸ Step 2: Add component products
- Click "Add Product"
- Search for and select a product
- Enter the Quantity
- (Optional) Select the Inventory Type
- Repeat until all products are added
▸ Step 3: (Optional) Set push ratio exceptions
- Under "Stock push ratio exceptions (optional)", click "Add exception" and pick an e-commerce account
- Enter the "Push ratio"
▸ Step 4: Create
- Review all the data
- Click "Create"; on success you'll return to the list page
- 💡 Tip: To create several bundles in a row, click "Save and Add Another" instead — the form clears after saving so you can enter the next one right away.
2. FAQ
Quick links: FAQ | Important Notes
2.1 FAQ
▪ How many products must a bundle contain?
At least one — a bundle cannot be created without any products. You can add or remove products any time on the edit page afterwards.
▪ Can a bundle contain another bundle?
No. Bundles can only contain regular products, not other bundles.
▪ What's the difference between SKU and barcode?
The SKU is the required code the system uses to identify the bundle. The Barcode is for scanning and is optional.
▪ Can I create a new bundle with the original SKU after deleting it?
Yes. After a bundle is deleted, its SKU can be reused under the same merchant. The old bundle retains its original SKU for historical reference. Deactivating a bundle does not release its SKU. Creation is still blocked if a product, flexible product, or another bundle that has not been deleted uses that SKU under the same merchant.
▪ Can't find the product you want to add?
The product hasn't been created yet. Go to "Products" → "Product List" to create it first, then come back and add it to the bundle.
▪ What happens if I add the same product on two rows?
- Both rows have the same inventory type: they are merged into one row with quantities summed when you save.
- Each row specifies a different inventory type: both rows are kept.
- One row is "Default Inventory Type" and the other specifies an inventory type: the bundle can't be saved, and the error message names the product. The default inventory type uses the sales channel's inventory types, which may be the same stock as the specified row — counting it twice overstates the buildable sets and leads to overselling. Make all rows for that product use one or the other.
▪ What is an inventory type?
When a product has multiple kinds of stock (e.g. sellable, defective), you can restrict the bundle to ship a specific type. When left unspecified, shipping follows the inventory type set on the order or sales channel — in most cases no special setting is needed.
▪ Can I change the SKU after creating the bundle?
Yes. But if your sales channels match orders to this bundle by SKU (platform orders expand into bundle contents based on the SKU), orders carrying the old SKU will no longer match this bundle after the change — remember to update the SKU on your channels as well.
2.2 Important Notes
⚠️ Important
- A SKU conflict blocks creation; see the SKU FAQ for restrictions and reuse after deletion
- The Quantity must be greater than 0
- Unsaved data is lost when you leave the page
3. Related Features
| Feature | Description | Link |
|---|---|---|
| Bundle List | Browse and search bundles | Go |
| Bundle Details | View a bundle's full information | Go |
| Edit Bundle | Modify bundle settings | Go |
| Product List | Manage regular products | Go |