How to Fix Merchant Center Promotion Disapprovals

Open the Promotions dashboard and record the promotion ID, country, language, channel, start and end dates, current status, policy status, SKU status, and the displayed reason. Google says a promotion must pass both a policy review and an SKU review before it becomes live. Treat them as separate evidence lanes. A policy failure concerns the offer or editorial rules; an SKU failure concerns whether the offer works on the selected products and destination.

Do not edit first and investigate later. Capture the submitted promotion source, product mapping, landing page, cart, checkout result, code, and storefront terms as they appeared at the failure time. Assign a promotion owner, feed owner, ecommerce owner, and review deadline. If the promotion is still under review, compare its effective date and submission time with Google's stated review window before resubmitting. Duplicate submissions can create a second record without resolving the original cause.

Google uses the promotion ID to connect a promotion with eligible products. Compare the value character for character across the promotions data source, promotion builder, API record, and product data. Google's specification says the ID is case sensitive, has a maximum length, and should not contain spaces or certain symbols. Preserve leading zeros and capitalization when another system generates the value. A visually similar ID is not an exact mapping.

Next verify applicability. A storewide offer should work on every product that the promotion claims, while a product-specific offer should map only to eligible items. If filters and explicit promotion IDs are both used, Google applies the intersection. Export the affected product IDs, then test examples that should be included and excluded. Do not broaden the mapping simply to obtain approval. Correct the product group, filter, or offer rule so the public terms and submitted applicability describe the same population.

Use a safe test cart containing an eligible product and, when useful, an intentionally ineligible product. Verify the live price, minimum purchase, code entry, discount type, shipping or gift treatment, currency, customer eligibility, and final checkout total. Google lists mismatched codes, discounts that do not apply, conflicting sale prices, incorrect incentive types, and restricted applicability among common disapproval causes. Record the exact product IDs and time because pricing and inventory can change.

Test the storefront rule independently of Merchant Center. If the code fails, repair the ecommerce promotion configuration and confirm the correction before requesting another review. If the site works but the source record is wrong, repair the promotion data. Avoid changing the offer into a materially different promotion under the same ID without a documented decision. The shopper-facing title, terms, eligible products, redemption method, effective dates, and submitted attributes need one coherent contract.

Review the promotion title and terms for spelling, capitalization, abbreviations, unsupported urgency, and consistency with the actual incentive. Google documents editorial requirements as a review input. Use plain offer language that identifies the real discount and does not introduce a second code, different percentage, or broader availability. Keep promotional copy separate from product titles and descriptions unless the product-data rules explicitly allow the field.

Align effective dates, display dates, account time zone, site scheduling, and campaign dates. Submit with enough lead time for review rather than activating the offer first and expecting immediate approval. If a promotion remains under review, verify that the effective date has arrived and the source processed successfully. Do not repeatedly move dates forward to hide a missed launch. Record the operational delay and decide whether the public offer should pause, continue without Google promotion display, or move under an approved business owner.

After the source and site pass, use the review-status surface to resubmit or request the supported retest. Google notes that an SKU review rejected for a website error can be retested after the error is resolved. Save the submission time, person, reason, affected products, evidence link, and resulting status. Wait for the new decision before describing the promotion as approved or live. An accepted file upload is not the same as promotion approval.

Close the incident with a prevention checklist: immutable promotion ID, product mapping owner, test cart, storefront rule, code, dates, time zone, title, incentive type, source processing, policy status, SKU status, and approved state. Review repeated failures by source system and reason. Automate validation only after the human contract is stable. Do not claim revenue or conversion impact from approval alone; approval only establishes eligibility to display. Measure later results with a defined audience, period, costs, and attribution method.

Before the next launch, rehearse the promotion with a nonpublic staging rule or an approved test product when the commerce platform supports it. Verify the source export, scheduled activation, storefront terms, eligible cart, code, and review owner. Record which steps cannot be tested before the public start and assign a launch-day check. A promotion calendar should show review lead time and a cancellation decision, so a rejected offer does not remain advertised through another channel after the checkout rule changes.