Map the promotion to the products that can actually redeem it

Define the offer benefit and the eligible item set

Google supports applying promotions to all products or specific products, including mapping through promotion_id. Its setup guidance identifies identifier mismatches and inconsistent applicability as common problems, and promotions undergo review. Check current country, account and promotion-type eligibility before implementation.

Write the approved benefit, redemption conditions and eligible assortment in plain language. Distinguish a checkout promotion from a sale price already reflected in the offer, using the current rules for the proposed mechanism. Do not create a second representation that implies an extra discount when customers only receive the existing price. The membership audit begins with the actual commercial terms, not a spreadsheet of items someone hopes to promote.

Join on identifiers with explicit inclusion rules

Create one authoritative promotion record and map its exact identifier to the intended product IDs through the supported configuration. Keep the shopper redemption code separate from the promotion identifier; they have different jobs even if the business chooses similar text. Avoid deriving the join from a translated title or a campaign slogan.

Preview the resulting membership before submission. Count included, excluded and unresolved records and inspect variants near the boundary. A category-wide filter may accidentally include premium editions excluded by the offer terms, while a fixed item list can miss newly launched eligible variants. Record whether membership is a frozen list or a maintained rule and who approves additions during the promotion.

Test redemption with both qualifying and nonqualifying items

Use an approved test process to confirm the benefit on an eligible configuration without completing an unintended purchase. Include a product that should not qualify, a boundary quantity or spend amount and any permitted combination of offers. A positive test alone cannot reveal a discount that applies too broadly.

Compare the advertised terms with the actual checkout result and promotion record. Check the currency, required code, effective period and any disclosed conditions. If the checkout behavior contradicts the approved scope, resolve that conflict before asking the feed to describe it. Do not widen product mapping merely to clear an unmapped warning when those items cannot legitimately redeem the benefit.

Separate mapping, review and observed display

After processing, inspect the product-to-promotion association and the promotion's actual review status. A file upload, a correct identifier join and an approved promotion are different checkpoints. Preserve the specific reason for any rejection rather than repeatedly recreating the promotion under new IDs.

At the end, verify that the intended benefit and references are retired or updated under the approved plan. Keep the membership snapshot with performance reporting so later analysis knows which products were actually included. Changes in stock, price or campaign allocation may explain observed results; do not attribute every sales movement to the promotion badge. The operational result is a supportable offer connected to the correct assortment, with its review and display state honestly reported.

Make the reasoning concrete.

A fictional backpack merchant offers a checkout discount on standard bags but excludes limited editions. A category filter maps the promotion to every bag, and the product source uses a shortened promotion ID.

The team resolves both the identifier mismatch and the assortment boundary, then checks review status. It reports successful mapping separately from approval and observed display.

Take the questions into your next brief.

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

1. Benefit

   What additional value and conditions did the business approve?

2. Join

   Do the product records reference the exact promotion identifier?

3. Membership

   Which items qualify, and how are new variants handled?

4. Negative test

   Which nonqualifying item must not receive the benefit?

5. Status

   Has mapping, review or actual display been verified?

Watch for the wrong conclusion.

• Confusing the redemption code with the promotion identifier.
• Using an all-products scope despite exclusions in the terms.
• Treating successful upload as promotion approval.

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: Choose products for your promotions →Primary platform documentation · Supports: Supports all-products versus specific-products scope and mapping promotions through promotion_id. Membership and redemption testing are original editorial analysis.
• Google Merchant Center: Get started with Promotions →Primary platform documentation · Supports: Supports promotion eligibility checks, policy and SKU review, and common exact-ID and applicability failures.