How to submit WooCommerce bundles and multipacks to Google Merchant Center

How to submit WooCommerce bundles and multipacks to Google Merchant Center

Submitting WooCommerce bundles and multipacks to Google Merchant Center requires more than placing several products on one landing page.

The merchant must determine whether the offer is:

• A single product
• A manufacturer-defined multipack
• A retailer-defined multipack
• A manufacturer-defined bundle
• A retailer-defined bundle
• A group of products sold separately
• A product variation
• A promotional offer that does not create a new trade item

This classification controls whether the product should use the bundle [is_bundle] attribute, the multipack [multipack] attribute or neither.

A retailer-defined multipack contains multiple identical products grouped by the merchant and sold as one offer.

A retailer-defined bundle contains a main product combined by the merchant with one or more different complementary products and sold for one total price.

A package created and identified by the manufacturer is normally treated as a manufacturer-defined product. The merchant should not label it as a retailer-defined bundle or multipack merely because the package contains several physical items.

WooCommerce product types and bundle extensions do not automatically determine the correct Google classification.

A WooCommerce product named “bundle,” “kit,” “set,” “box,” “pack” or “collection” may still represent different commercial structures. The actual items, packaging, identifiers, price and purchasing process must be examined.

The short answer

To submit a WooCommerce bundle or multipack correctly:

1. Open the exact WooCommerce product.
2. Identify every physical item the customer receives.
3. Determine who created the package: the manufacturer or the merchant.
4. Determine whether the included products are identical or different.
5. For identical products grouped by the merchant, use the multipack attribute.
6. For different products grouped by the merchant around a main product, use the bundle attribute.
7. Do not use these attributes for a package already defined by the manufacturer.
8. Submit the total price of the complete offer.
9. Use the correct product identifiers for the package classification.
10. Describe the complete package in the title and description.
11. Show the included products clearly on the landing page.
12. Check stock for every component.
13. Submit the corrected WooCommerce offer.
14. Review the processed product in Merchant Center.

Do not use is_bundle merely because a WooCommerce bundle plugin created the product.

Do not use multipack for several different products.

Do not multiply a manufacturer-defined inner pack quantity when calculating the multipack value.

Do not use the GTIN of an individual unit as though it identifies a different manufacturer-defined pack.

Bundle, multipack or single product?

The following distinction is the foundation of the complete workflow:

Actual offer	Correct general classification	Relevant attribute
One individual product	Single product	Neither
One package created by the manufacturer containing identical units	Manufacturer-defined multipack	Normally neither
Several identical manufacturer-defined products grouped by the merchant	Retailer-defined multipack	multipack
Different products packaged together by the manufacturer under one product identity	Manufacturer-defined bundle	Normally neither
A main product combined with different complementary products by the merchant	Retailer-defined bundle	is_bundle
Several related products displayed together but purchased separately	Separate products	Neither
Different sizes or colours of the same product	Variations	item_group_id, not bundle
A discount applied when customers add several products to the cart	Promotion or cart rule	Not automatically a bundle or multipack

Google’s official multipack attribute documentation defines a multipack as multiple identical products grouped together by the retailer.

Google’s bundle attribute documentation defines a retailer-created bundle as a main product grouped with different products and sold together for one price.

These two attributes describe different offers and should not be used interchangeably.

What is a retailer-defined multipack?

A retailer-defined multipack exists when the merchant combines several identical manufacturer-defined products into one offer.

Examples include:

• Three identical bottles of shampoo
• Six identical notebooks
• Four identical T-shirts in the same size and colour
• Two identical manufacturer-packaged boxes of coffee capsules
• Five identical printer cartridges
• Three identical 20-pen packages grouped by the retailer
• Twelve identical cans sold together as one merchant-created offer

The customer cannot purchase only one of the grouped products through that Merchant offer.

The landing page presents the complete quantity, the displayed price covers the complete quantity and checkout adds the entire multipack as one purchasable offer.

For these products, the multipack value represents how many identical manufacturer-defined products the merchant has grouped together.

How to calculate the multipack value

The most common multipack mistake is counting the total number of physical pieces rather than the number of manufacturer-defined products grouped by the merchant.

Consider these examples.

Three individual bottles grouped by the merchant

The manufacturer sells each bottle as one product. The merchant combines three bottles.

The correct multipack value is:

3

Three manufacturer-defined 20-pen packages grouped by the merchant

Each 20-pen package is already one manufacturer-defined product.

The merchant combines three of those packages.

The correct multipack value is:

3

It is not:

60

The official Google requirement states that if a merchant groups three manufacturer-defined 20-packs, the multipack value remains three.

One manufacturer-defined package containing six bottles

The manufacturer created, packaged and identified the six-bottle product.

The merchant sells one manufacturer-defined six-pack without creating another grouping.

Do not submit:

multipack: 6

The offer is one manufacturer-defined product.

Google recommends using applicable unit-pricing attributes when the number of units within a manufacturer-defined package needs to be communicated.

Two manufacturer-defined six-bottle packages grouped by the merchant

The manufacturer defines each six-bottle package as one product.

The merchant combines two of those packages.

The correct retailer-defined multipack value is:

2

The visible title and description can still explain that the customer receives 12 bottles in total.

What is a retailer-defined bundle?

A retailer-defined bundle is a package created by the merchant that contains:

• One identifiable main product
• One or more different complementary products
• One combined selling price
• One purchasable offer
• One landing page describing the complete package

Examples include:

• A camera with a lens and carrying bag
• A games console with a controller and game
• A laptop with a mouse and laptop case
• A printer with ink cartridges and paper
• A drill with drill bits and protective glasses
• A phone with a case and charger
• A coffee machine with cups and coffee
• A bicycle with a helmet and repair kit

The camera, console, laptop, printer, drill, phone, coffee machine or bicycle is the main product.

The additional products support or complement that main product.

The retailer-defined bundle should use:

is_bundle: true

In Merchant API product attributes, isBundle is represented as a Boolean field:

"isBundle": true

The current Merchant API ProductAttributes reference also represents multipack as an integer-formatted string containing the number of identical products in a business-defined multipack.

A bundle needs a main product

The is_bundle attribute is intended for a merchant-created package containing a main product.

A random collection of products does not automatically qualify.

For example, a package containing:

• A camera
• A lens
• A carrying bag

has a clear main product: the camera.

A package containing:

• A mug
• A notebook
• A candle
• A pair of socks

may not have one clearly identifiable main product.

Do not select an arbitrary component merely to make is_bundle technically available.

The merchant should evaluate whether the set has a genuine primary product, whether it is represented as another recognised product type or whether the products should be submitted separately.

The WooCommerce product name is not evidence by itself.

A product titled “Holiday bundle” can still lack the main-product structure required for a retailer-defined Merchant bundle.

Manufacturer-defined bundles are different

A manufacturer-defined bundle is created, packaged and identified by the manufacturer.

Examples can include:

• A branded camera kit packaged by the camera manufacturer
• A console edition officially packaged with a game
• A manufacturer’s power-tool starter kit
• A skincare gift set created by the skincare brand
• A manufacturer-packaged keyboard and mouse set
• A cookware set supplied under one manufacturer product identity

When the manufacturer created the complete package, use the product information and identifiers assigned to that package.

Do not automatically set:

is_bundle: true

The package is treated as one manufacturer-defined product, even though it contains several physical components.

Google’s product identifier requirements distinguish manufacturer-created packages from bundles assembled by the retailer.

The package creator determines the classification

The same collection of products can require different Merchant data depending on who created it.

Scenario	Creator	Classification
Camera, lens and bag packaged under one manufacturer GTIN	Manufacturer	Manufacturer-defined product
Camera, lens and bag selected and grouped by the store	Merchant	Retailer-defined bundle
One manufacturer-packaged six-can product	Manufacturer	Manufacturer-defined multipack
Six individual cans grouped by the store	Merchant	Retailer-defined multipack
Two manufacturer-packaged six-can products grouped by the store	Manufacturer plus merchant	Retailer-defined multipack with value 2

This distinction must be documented in WooCommerce or the merchant’s product-information system.

Without a reliable source, an integration cannot determine who defined the commercial package merely by counting product components.

WooCommerce product types do not provide the final answer

WooCommerce can represent package offers through several structures:

• Simple products
• Variable products
• Grouped products
• Composite-product extensions
• Product-bundle extensions
• Mix-and-match extensions
• Custom product fields
• Custom post types
• Product add-ons
• Frequently bought together modules
• Cart discount rules
• Custom code
• ERP-generated products

These structures solve different store-management problems.

A WooCommerce grouped product often displays related products that customers can purchase separately. That does not necessarily create one Merchant bundle.

A “frequently bought together” section can recommend several items without creating a single product offer.

A bundle extension may deduct component stock while selling one parent product. That structure may represent a genuine retailer-defined bundle, but its title alone does not prove the classification.

A mix-and-match product may let customers select several identical or different products. The final classification depends on the specific purchasable configuration submitted to Google.

A cart discount such as “buy three and save 10%” does not create a multipack when the Merchant landing page and submitted offer still represent one unit.

Review the actual customer journey.

The offer must be purchasable as submitted

The Merchant product should match what a customer can purchase after opening the submitted URL.

For a retailer-defined multipack, the customer should see:

• The exact number of products
• The complete multipack price
• The availability of the complete multipack
• The identical product being repeated
• Any size, colour, flavour or other defining characteristic
• The complete quantity added to the cart

For a retailer-defined bundle, the customer should see:

• The main product
• Every included complementary product
• The total bundle price
• The bundle’s availability
• Any selectable bundle configuration
• The exact items added to the cart

Do not submit a bundle price if the landing page initially shows only the main product’s price.

Do not submit a six-unit multipack if the landing page initially adds only one unit.

Do not require customers to discover the actual package composition after starting checkout.

Use the total price

Google’s official price attribute requirements state that the submitted price should be the total price of the complete bundle or multipack.

For example:

Offer	Correct submitted price
Three identical bottles sold together	Price of all three bottles
Camera, lens and bag sold as one bundle	Price of the complete bundle
Two manufacturer-defined six-packs sold together	Price of both six-packs
Laptop with mouse and case	Price paid for the complete package

Do not submit:

• The price of one unit from the multipack
• The price of only the main product
• The sum before an automatically applied package discount
• A “starting from” price when the submitted configuration costs more
• A per-unit price as the main product price
• A price that excludes a required bundle component

Unit pricing can provide additional quantity context, but it does not replace the total offer price.

WooCommerce, the product page, structured data, cart and checkout should expose the same payable amount.

Use identifiers according to the package type

Product identifiers are especially important because an individual item, manufacturer package and retailer-created offer can represent different commercial identities.

Google’s product data specification provides the following general direction:

• For multipacks, use identifiers related to the multipack.
• For retailer-defined bundles, use identifiers associated with the main product.

The exact source depends on who created the package.

Manufacturer-defined bundle

If the manufacturer created the complete bundle, use:

• The GTIN assigned to the complete bundle
• The MPN assigned to the complete bundle
• The brand of the complete bundle

Do not replace the complete package’s GTIN with the GTIN of one component.

Retailer-defined bundle

If the merchant created the bundle, use:

• The GTIN of the main product
• The MPN of the main product
• The brand of the main product
• is_bundle: true

Google’s official GTIN guidance specifically distinguishes identifiers for manufacturer-created bundles from identifiers for retailer-created bundles.

Manufacturer-defined multipack

Use the identifiers legitimately assigned to that complete manufacturer-defined package.

Do not submit a unit GTIN if the package has its own GTIN.

Retailer-defined multipack

Use the identifier that accurately relates to the repeated product and multipack structure.

Do not invent a new GTIN for the retailer-created multipack.

Do not generate a random barcode.

Do not use:

• A WooCommerce product ID
• A variation ID
• A Merchant offer ID
• An order number
• An internal database key
• A temporary SKU

as though it were a manufacturer-assigned GTIN.

A WooCommerce SKU can remain a useful internal stock identifier and may support a stable Merchant offer ID. It does not automatically become a GTIN.

Do not use identifier_exists as an escape route

Bundles and multipacks can require careful identifier handling, but that does not mean identifiers should automatically be declared nonexistent.

Do not set:

identifier_exists: false

merely because:

• The merchant created the package.
• The parent WooCommerce product has no GTIN field.
• The bundle extension did not copy component identifiers.
• The multipack has a new internal SKU.
• The integration cannot locate the main product.
• A previous submission produced a duplicate-GTIN warning.

For a retailer-defined bundle, the main product can still have genuine brand, GTIN and MPN information.

For a manufacturer-defined bundle or multipack, the complete package may have its own identifiers.

The identifier decision should follow the real product and Google’s requirements, not the convenience of the WooCommerce data model.

Create an accurate product title

The title should describe the complete purchasable offer.

For a retailer-defined multipack, include the quantity naturally.

Examples:

• Brand X Shampoo, 500 ml, Pack of 3
• Brand Y Cotton T-shirt, Black, Medium, 4 Count
• Brand Z Coffee Capsules, 20 Count, Pack of 2
• Brand A Printer Cartridge, Black, Pack of 3

For a retailer-defined bundle, describe the main product and the important included items.

Examples:

• Brand X Mirrorless Camera with Lens and Carrying Bag
• Brand Y Laptop with Wireless Mouse and Protective Case
• Brand Z Games Console with Controller and Racing Game
• Brand A Cordless Drill with Bit Set and Safety Glasses

Google’s title requirements recommend describing the entire merchant-defined bundle or multipack.

Do not use vague titles such as:

• Special package
• Best bundle
• Value set
• Complete offer
• Mega pack
• Surprise box

unless the title also identifies what the customer actually receives.

Avoid promotional language that does not describe the product.

Describe every included product

The product description should explain:

• The main product
• Every included component
• The number of identical units
• The contents of manufacturer-defined inner packages
• Important specifications
• Compatible models
• Size and colour
• Condition
• Included accessories
• Excluded accessories
• Warranty information
• Any customer-selectable options
• Packaging details where relevant

For a multipack, distinguish between:

• Number of manufacturer-defined products
• Number of physical units inside each manufacturer-defined product
• Total physical unit count

For example:

Includes two manufacturer-packaged boxes. Each box contains 20 identical pens, for a total of 40 pens.

The Merchant multipack value for this retailer-created offer is still two.

The description can communicate the total of 40 pens without changing the meaning of the multipack attribute.

Use images that represent the complete offer

The main product image should help customers understand what they will receive.

For a bundle, the image should accurately represent the main product and included accessories.

For a multipack, the image should represent the submitted quantity without creating a misleading impression.

Check that:

• All mandatory items are represented.
• Optional items are not shown as mandatory inclusions.
• The quantity shown does not conflict with the title.
• The product variation matches the image.
• Manufacturer packaging is represented accurately.
• Accessories shown for context are clearly distinguished when not included.
• Promotional overlays do not hide product information.
• The main product remains identifiable.

If the image shows three bottles while the landing page sells one, the offer is inconsistent.

If the title says “camera with lens and bag” while the image shows only the camera body, customers may not understand the bundle.

Additional images can show individual components, packaging, product details and alternative views.

Calculate availability from the complete package

A bundle can be sold only when every required component is available in sufficient quantity.

For example, a camera bundle requires:

• One camera
• One lens
• One bag

If the bag is unavailable and cannot be replaced, the complete bundle is unavailable even when the camera remains in stock.

A multipack of six identical units requires at least six eligible units for each complete offer.

If WooCommerce holds 17 individual units and each multipack contains six, the store can fulfil two complete multipacks, with five individual units remaining.

The exact stock calculation can depend on the bundle extension and inventory architecture.

Confirm that:

• Component inventory is deducted correctly.
• Parent inventory does not exceed component availability.
• Backorders are represented accurately.
• Optional components do not incorrectly block the package.
• Required variations are available.
• Scheduled inventory imports update the bundle state.
• Merchant availability matches the landing page.

Do not submit in_stock based only on the main product when a required accessory is unavailable.

Variable bundles need stable offer definitions

A bundle can allow customers to choose:

• Main-product colour
• Main-product size
• Accessory colour
• Storage capacity
• Included game
• Lens model
• Pack quantity
• Component type

Each submitted Merchant offer must represent a specific, stable and purchasable configuration.

If a landing page permits several configurations with different prices, images or identifiers, the submitted URL should lead to or clearly identify the exact submitted configuration.

Review:

• Offer ID
• Variation ID
• SKU
• Price
• Availability
• Image
• GTIN
• MPN
• Brand
• Condition
• Bundle status
• Multipack quantity
• Landing-page selection

Do not use one Merchant offer to represent several configurations with different payable prices.

Do not treat bundle options as ordinary colour or size variations unless they genuinely represent variations of the same product.

Bundles are not item groups

The item_group_id attribute connects variations of the same product.

Examples include:

• The same shirt in different sizes
• The same shoe in different colours
• The same phone in different storage capacities
• The same product in supported material or pattern variants

A retailer-defined bundle is a commercial package containing a main product and complementary products.

A multipack contains repeated identical products.

These are not automatically product variation groups.

Do not assign the same item_group_id to unrelated bundles simply because they share one component.

For example:

• Camera with bag
• Camera with tripod
• Camera with lens and bag

may represent separate bundle offers rather than ordinary variants.

The correct structure depends on whether the packages are true variations of one product or distinct commercial combinations.

Product condition applies to the complete offer

Every included item must be considered when determining the condition of a bundle.

Do not submit a package as new when a required component is used, opened or refurbished.

Examples:

• New camera with used lens
• Refurbished laptop with new mouse
• Used console with new controller
• New drill with open-box accessory set

The public page must explain the condition of every material component.

The Merchant condition should accurately represent the complete offer under Google’s supported new, used or refurbished values.

A bundle field cannot correct an inaccurate condition.

A multipack should not contain units represented as identical when their condition differs.

WooCommerce grouped products require special attention

WooCommerce grouped products can display several individual products on one page while preserving separate quantities and add-to-cart actions.

That does not necessarily produce one bundle.

Ask:

• Can the customer purchase each product separately?
• Is there one total package price?
• Is every component mandatory?
• Does one add-to-cart action add the complete package?
• Does the order contain one package or several independently selected products?
• Is there one Merchant offer for the complete package?
• Does the landing page describe a main product?
• Does the submitted image show the complete package?

If customers can freely select and purchase individual products, the items may need separate Merchant offers.

Do not set is_bundle: true solely because WooCommerce calls the product type “grouped.”

Promotions are not automatically multipacks

Offers such as:

• Buy two, get one free
• Buy three and receive a discount
• Add a case for 50% less
• Spend a specified amount and receive a gift
• Add any four products for a package price

can be promotions rather than permanent product packages.

If the submitted Merchant product still represents one individual product and the offer is applied conditionally in the cart, changing the base product into a multipack may be inaccurate.

Evaluate whether the Merchant offer itself has:

• A fixed quantity
• A fixed composition
• A fixed total price
• One package landing page
• One stable product identity

Promotional eligibility and bundle classification are separate questions.

Check all active Merchant data sources

A corrected bundle or multipack can remain wrong when another product source supplies conflicting values.

Review:

• Merchant API
• Scheduled XML sources
• Uploaded files
• Google Sheets
• Ecommerce platform connections
• Automatic website sources
• Supplemental sources
• Previous WooCommerce plugins
• Manual product records
• Country-specific data sources
• Language-specific data sources

For each source, determine:

• Which offer ID it controls
• Whether it supplies is_bundle
• Whether it supplies multipack
• Which GTIN it supplies
• Which price it supplies
• Which landing page it supplies
• How often it updates
• Whether it can overwrite corrected information

Do not leave two offers active when one describes a single unit and the other incorrectly describes the same offer as a multipack.

Correct the authoritative WooCommerce source

After classifying the offer:

1. Open the exact WooCommerce product.
2. Open the exact variation where applicable.
3. Identify the bundle or multipack extension.
4. Record every required component.
5. Record the manufacturer-defined product unit.
6. Determine the main product where applicable.
7. Determine who created the package.
8. Correct the product title.
9. Correct the description.
10. Correct the total price.
11. Correct component inventory.
12. Correct identifiers.
13. Set the supported bundle or multipack field.
14. Save the product.
15. Confirm the public landing page.
16. Confirm the cart contents.
17. Confirm checkout price.
18. Submit the corrected offer.
19. Record the operation result.
20. Review the processed Merchant product.

If an ERP or supplier import controls the product, correct that upstream system as well.

Otherwise, the next import can restore the previous classification.

Merchant API representation

Merchant API exposes the relevant fields through product attributes.

A retailer-defined bundle can include:

{
  "isBundle": true
}

A retailer-defined multipack of three manufacturer-defined products can include:

{
  "multipack": "3"
}

A product should not be represented as both merely because several physical items are present.

The integration must first classify the offer correctly.

Examples of inaccurate values include:

{
  "isBundle": "camera-kit"
}

{
  "multipack": "pack-of-three"
}

{
  "multipack": "3 bottles"
}

isBundle is a Boolean field.

multipack represents an integer-formatted quantity.

The submitted field format does not replace the commercial classification.

A technically valid value can still describe the wrong product.

Technical acceptance does not confirm package accuracy

A successful Merchant API operation confirms that the request was technically received or processed at that stage.

It does not prove that:

• The product is correctly classified.
• The multipack quantity is correct.
• The main product is correct.
• The GTIN is correct.
• The total price matches the landing page.
• Every component is available.
• The offer is eligible for free listings.
• The offer is eligible for Shopping ads.
• The product will be approved.
• The product will remain approved.
• The product will receive impressions.
• The product will generate clicks or sales.

Open the processed product after submission.

Review every applicable issue and destination.

How to verify the submitted product

After Google processes the update:

1. Open the correct Merchant Center account.
2. Go to Products.
3. Search for the exact offer ID.
4. Open the processed product.
5. Confirm the active data source.
6. Check the processed title.
7. Check the processed description.
8. Check the processed price.
9. Check the processed GTIN.
10. Check brand and MPN.
11. Check bundle status.
12. Check multipack quantity.
13. Check condition.
14. Check availability.
15. Open the submitted URL.
16. Confirm the complete package.
17. Add the product to the cart.
18. Confirm the exact quantity and components.
19. Continue to checkout.
20. Confirm the total payable price.
21. Review target-country status.
22. Review marketing-method status.
23. Review Needs attention issues.
24. Allow applicable processing time.
25. Check the product again after the next automatic synchronisation.

Do not verify only the API response.

The processed Merchant product and complete WooCommerce purchasing journey are the final operational checks.

What PW Merchant API can support

PW Merchant API provides an API-oriented workflow between WooCommerce and Google Merchant Center.

Depending on the installed version, supported fields, product structure and configuration, it can help merchants:

• Review WooCommerce product information.
• Work with supported simple and variable products.
• Maintain controlled product offer IDs.
• Prepare supported product attributes.
• Submit supported Merchant product operations.
• Update existing product information.
• Review successful and failed operations.
• Display applicable Merchant product issues.
• Compare WooCommerce information with processed Merchant results.
• Synchronise supported price, stock and product changes.

When bundle and multipack fields are supported by the installed product workflow, the integration can communicate those prepared values through Merchant API.

However, PW Merchant API cannot independently determine:

• Who created the physical package
• Whether products are genuinely identical
• Which component is the main product
• Whether manufacturer packaging was changed
• Whether a GTIN belongs to a unit or complete package
• Whether every bundle component is physically present
• Whether an internal product structure is commercially accurate

It cannot:

• Invent a bundle GTIN.
• Generate a legitimate manufacturer identifier.
• Turn several unrelated products into a valid bundle.
• Decide package identity only from a WooCommerce product name.
• Correct inaccurate supplier data without an authoritative source.
• Guarantee Google approval.
• Guarantee Shopping visibility.
• Guarantee impressions, clicks or sales.
• Override Google’s product-data requirements.
• Prevent another active source from overwriting information.
• Confirm physical inventory without accurate WooCommerce data.

WooCommerce remains the commercial source, the integration manages supported communication and Google independently processes and evaluates the submitted information.

Common mistakes

Using multipack for different products

A multipack contains identical products. A camera, lens and bag are different products and should not use the multipack attribute.

Using is_bundle for identical products

Three identical bottles represent a retailer-defined multipack, not a bundle.

Counting every physical item inside manufacturer packaging

Three manufacturer-defined 20-packs produce a multipack value of three, not 60.

Marking a manufacturer package as retailer-defined

A manufacturer-created bundle or multipack should use the identifiers assigned to the complete manufacturer product and should not automatically receive a retailer-defined attribute.

Submitting a unit price

The submitted price must cover the entire package.

Using the GTIN of one unit for a different manufacturer pack

A manufacturer-defined multipack can have its own GTIN. Use the identifier assigned to the exact trade item.

Inventing a bundle GTIN

Retailers should not generate random GTINs for packages they create.

Treating a grouped WooCommerce product as a bundle

A grouped product may still contain separately purchasable offers.

Ignoring component inventory

The complete bundle is unavailable when a mandatory component cannot be supplied.

Using item group ID for separate packages

Bundle offers are not automatically variations merely because they share a main product.

Correcting only Merchant Center

The next WooCommerce synchronisation may restore the old information.

Stopping after an accepted API response

Technical acceptance does not prove that the processed package data is accurate.

Frequently asked questions

What is the difference between a bundle and a multipack?

A retailer-defined bundle contains a main product and different complementary products. A retailer-defined multipack contains several identical manufacturer-defined products.

Should three identical WooCommerce products use is_bundle?

No. If the merchant combines three identical products into one offer, use the multipack attribute.

Should a camera with a lens and bag use multipack?

No. The products are different. When the merchant created the package and the camera is the main product, it can be represented as a retailer-defined bundle.

What multipack value should I use for three manufacturer 20-packs?

Use three. The manufacturer-defined 20-pack is the repeated product.

Should one manufacturer-created six-pack use multipack: 6?

No. The multipack attribute is for retailer-defined groupings. Use the exact manufacturer product information and applicable unit-pricing data.

Can I set is_bundle to true for a manufacturer-created kit?

Normally no. Treat the manufacturer-created kit as the manufacturer’s product and use the identifiers assigned to the complete kit.

Can a WooCommerce grouped product be submitted as a bundle?

Only when the actual offer meets the bundle requirements. A grouped product containing separately purchasable products is not automatically a Merchant bundle.

Can I submit a bundle without a main product?

The bundle attribute is intended for a merchant-created package containing a main product. Do not arbitrarily choose a main product when none exists.

Which price should I submit for a bundle?

Submit the total price the customer pays for the complete bundle.

Which price should I submit for a multipack?

Submit the total price of the complete multipack, not the price of one unit.

Which brand should a retailer-created bundle use?

Use the genuine brand of the main product.

Which GTIN should a retailer-created bundle use?

Use the legitimate GTIN of the main product where applicable and set the bundle attribute accurately.

Which GTIN should a manufacturer-created bundle use?

Use the GTIN assigned by the manufacturer to the complete bundle.

Can I invent a GTIN for my WooCommerce bundle?

No. Only submit legitimate identifiers assigned to the applicable product.

Can I use the WooCommerce product ID as a GTIN?

No. A WooCommerce database ID is not a manufacturer-assigned GTIN.

Can I use the bundle SKU as a GTIN?

Only if that value is genuinely a legitimate GTIN assigned to the exact product. An internal SKU is normally not a GTIN.

Should I set identifier_exists to false for every retailer-created bundle?

No. The main product can still have genuine brand, GTIN and MPN information.

Can different variations have different multipack quantities?

Yes, when each variation is a separate, stable and purchasable quantity. Each submitted offer must expose the correct price, quantity, identifiers and landing-page state.

Is a buy-two-get-one-free offer a multipack?

Not automatically. If the Merchant offer still represents one unit and the discount is applied conditionally in the cart, it may be a promotion instead of a separate multipack product.

Can the main image show only one unit from a multipack?

The image must accurately represent the offer and must not mislead customers about the quantity they will receive.

Does a successful Merchant API response prove that the bundle is correct?

No. Review the processed product, landing page, cart and Merchant issues after Google processes the operation.

Can PW Merchant API identify the main bundle product automatically?

It can work with supported product information available in WooCommerce, but it cannot reliably determine physical package identity or the main product without accurate source data and a supported mapping.

Will using is_bundle guarantee product approval?

No. Price, availability, identifiers, images, website requirements, policies and other product data can still affect eligibility.

Final bundle and multipack checklist

Before submitting a WooCommerce bundle or multipack, confirm that:

• The exact WooCommerce product was identified.
• The exact variation was identified.
• The Merchant offer ID was recorded.
• The SKU was recorded.
• Every physical item was listed.
• Every included quantity was recorded.
• The package creator was identified.
• Manufacturer packaging was inspected.
• Manufacturer product information was checked.
• Supplier information was checked.
• The package was classified as manufacturer-defined or retailer-defined.
• Identical products were distinguished from different products.
• A genuine main product was identified for a retailer-created bundle.
• A random main product was not selected merely to use is_bundle.
• A retailer-defined multipack contained identical products.
• A retailer-defined bundle contained different complementary products.
• A WooCommerce grouped product was not assumed to be a bundle.
• A bundle-plugin product was not assumed to meet Merchant requirements.
• A cart promotion was not assumed to be a multipack.
• A manufacturer-defined multipack did not receive a retailer multipack value.
• A manufacturer-defined bundle did not receive an unnecessary bundle value.
• The manufacturer-defined product unit was identified.
• The multipack value counted repeated manufacturer products.
• Inner manufacturer-pack quantities were not incorrectly multiplied.
• The total physical quantity was disclosed.
• The title described the complete package.
• The description listed every included product.
• The main image represented the complete offer accurately.
• Additional images clarified the included products.
• Optional accessories were not presented as mandatory inclusions.
• Excluded accessories were disclosed.
• The submitted price covered the complete package.
• The landing-page price matched the submitted price.
• Cart price matched the submitted price.
• Checkout price matched the submitted price.
• No required component was added later for an extra charge.
• Component inventory was checked.
• Parent inventory reflected component availability.
• Multipack inventory supported the complete quantity.
• Backorder status was accurate.
• The complete package could be purchased from the submitted URL.
• The correct configuration was selected on the landing page.
• Variations had stable offer identities.
• Different bundle packages were not incorrectly grouped as ordinary variants.
• The correct GTIN source was recorded.
• The correct MPN source was recorded.
• The correct brand source was recorded.
• Manufacturer-defined package identifiers were retained.
• Retailer-created bundles used main-product identifiers where applicable.
• No GTIN was invented.
• No random barcode was generated.
• No WooCommerce product ID was used as a GTIN.
• No Merchant offer ID was used as a GTIN.
• No internal SKU was assumed to be a GTIN.
• identifier_exists was not used merely to avoid research.
• The product condition described the complete offer.
• Used components were disclosed.
• Refurbished components were disclosed.
• Bundle and multipack fields used supported formats.
• isBundle used a Boolean value.
• multipack used an integer-formatted quantity.
• The product was not marked as both without a valid reason.
• Every active Merchant data source was identified.
• Old XML sources were checked.
• Previous WooCommerce integrations were checked.
• Supplemental sources were checked.
• Automatic website sources were checked.
• No other source could restore incorrect package data.
• The authoritative WooCommerce record was corrected.
• Applicable upstream import mappings were corrected.
• The product was saved.
• The public page was checked while logged out.
• The correct product was submitted.
• The Merchant operation result was recorded.
• The processed Merchant product was opened.
• Processed bundle status was checked.
• Processed multipack quantity was checked.
• Processed price was checked.
• Processed identifiers were checked.
• Processed availability was checked.
• Target-country status was reviewed.
• Marketing-method status was reviewed.
• Needs attention issues were reviewed.
• The correction remained stable after scheduled synchronisation.
• No approval or performance guarantee was assumed.

A WooCommerce product does not become a valid Merchant bundle merely because its title contains “bundle,” “kit” or “set.”

The actual package structure determines the correct product data.

Use multipack when the merchant groups several identical manufacturer-defined products and sells them as one offer.

Use is_bundle when the merchant groups a main product with different complementary products and sells the complete package for one price.

Do not use these retailer-defined attributes for packages already created and identified by the manufacturer.

The submitted title, description, image, identifiers, availability and total price should represent the complete purchasable offer.

WooCommerce should remain the authoritative commercial source. PW Merchant API can manage supported communication and product operations, while Google Merchant Center independently processes and evaluates the submitted information.

Accurate package classification helps Google understand what is being sold and helps customers receive the exact quantity and combination they expected.