Represent the merchant bundle as the offer actually being sold

Establish the bundle classification from the commercial offer

Google describes is_bundle for a merchant-created combination of a main product with different complementary products sold together for one price. It distinguishes these from manufacturer-defined bundles. Check the current requirements for the destination and specific offer, including any special cases, before applying a blanket rule.

Record who assembled the commercial offer, what the featured main product is and what the buyer receives. A supplier's factory kit, a retailer accessory combination and a group of identical items can look similar in a warehouse but require different feed decisions. Use the approved bill of contents as evidence, while keeping the feed classification distinct from fulfillment instructions.

Decide which facts describe the whole offer

Create a field review rather than copying the main product's row wholesale. The total price, title, description and imagery need to communicate the bundle the customer actually buys. Check whether included accessories change compatibility, condition or the version of the main product represented. A default component image can be technically accessible yet commercially incomplete.

Keep facts about the main product distinct from statements about every included component. For example, a warranty attached to one item should not automatically become a promise covering the whole set. Route unclear claims to the responsible commercial owner. The feed operator's task is faithful representation, not extending service commitments to make the combined offer sound more attractive.

Resolve identifiers and mixed-condition edges deliberately

Consult the current identifier guidance for the bundle type rather than generating a code or borrowing an accessory's identity. Retain manufacturer evidence and the rationale for the approved mapping. Avoid a universal rule that a bundle always lacks identifiers or always inherits every identifying attribute from the main product.

Review mixed-condition sets separately. A new main item with a used accessory is not made wholly new by its headline component. Google specifically addresses condition in its bundle guidance; apply the current rule and ensure the page describes the actual contents. If an accessory is optional at checkout rather than included in the submitted price, establish whether the catalog row describes a bundle at all. The answer should follow the sold offer, not the campaign theme.

Test the bundle row against a complete buying path

Open the submitted link and confirm the intended configuration is selected or clearly offered at the submitted total. Follow the approved test process far enough to verify the set, without placing an order. Check that removing an accessory does not silently become the default offer while the feed continues to describe the full combination.

Create regression fixtures for a manufacturer kit, a merchant-created main-product bundle, identical-item multipacks and optional add-ons. Each should exercise a different branch of the mapping. After release, inspect processed attributes and retain the representation sheet. Revisit it whenever the bundle contents change, even if the marketing name stays the same. A stable title cannot substitute for a stable commercial meaning.

Make the reasoning concrete.

A fictional music shop adds a stand and cable to a keyboard for one price. Another row sells a factory-packaged starter kit unchanged. The export currently marks both rows from the number of box contents alone.

The team classifies the offers from their creator and commercial structure, checks the full set at the submitted price and records the applicable identity decision. Warehouse assembly feasibility remains a separate control.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Creator

   Who defined and packaged the offer being sold?

2. Main item

   Which product is featured and which items complement it?

3. Whole offer

   Which fields must describe the complete set rather than one component?

4. Identity

   What current guidance and evidence support its identifiers?

5. Edges

   Are any components used, optional or excluded from the shown price?

Watch for the wrong conclusion.

• Inferring bundle semantics only from the number of pieces.
• Copying the main item row without reviewing whole-offer claims.
• Assuming optional checkout accessories are included in the feed price.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

• Google Merchant Center: Bundle →Primary platform documentation · Supports: Supports the merchant-created main-product bundle distinction, whole-bundle descriptive fields and the documented used-component condition rule. Representation checks are original editorial analysis.