Fix GMC Pre-Release Product Disapprovals on Shopify

Google’s pre-release product disapproval is among the most avoidable flags in Merchant Center - the underlying cause is almost always a timing mismatch between when a product enters your feed and when it actually becomes purchasable. On Shopify, that mismatch is often created automatically by platform features rather than any deliberate error. Understanding exactly which signal AdsBot picked up tells you which attribute to correct.

What Google means by “pre-release products”

Google’s policy at support.google.com/merchants/answer/6324448 states that products must be available for purchase at the time they are crawled. The policy language is explicit: “Don’t advertise products that customers cannot currently purchase.” The pre-release disapproval label is applied when AdsBot finds that a product’s stated availability attribute does not match what a shopper encounters on the product page.

Concretely, Google flags the following as pre-release violations:

• A product is tagged availability=in_stock but the product page shows a “coming soon” message, requires a password, or has no active add-to-cart button.
• A product has a future publication date - a scheduled Shopify launch - and was synced to the feed before that date passed and the product became purchasable.
• A product from an unreleased collection reached Google’s index via a shared URL, an early sitemap entry, or a link discovered through Google’s existing crawl graph, before the collection went live.
• A product is tagged in_stock but is accessible only through an influencer preview link or a press-kit URL shared ahead of the public launch.

Google distinguishes this from a general inaccurate-availability signal because the root cause is temporal: the product may be real and fully operational, but it is not yet purchasable at crawl time.

Why it triggers a disapproval on Shopify

Shopify’s Google & YouTube channel app synchronizes product availability directly from your store’s product catalog. Several Shopify-native behaviors create pre-release mismatches without any intentional mistake on your part.

Scheduled publications. Shopify lets you set a future publication date for a product or collection. The product can appear in your sitemap - and be discovered by AdsBot - before the publication timestamp passes and checkout becomes possible.

Pre-order plugins using the wrong inventory policy. Many Shopify merchants simulate pre-orders by enabling “Continue selling when out of stock” and using a button-label override plugin. Unless the Google & YouTube channel app is explicitly configured to map that state to availability=preorder, it submits the inventory policy literally: in_stock. Google receives an in_stock signal for a product shoppers cannot yet buy.

Draft-to-Active transitions. A product switched from Draft to Active in Shopify becomes immediately eligible for feed sync, even if it belongs to a collection with a future publish date. The GMC feed and the live storefront can be briefly - or significantly - out of sync during that window.

Early shared or indexed URLs. Preview links shared with influencers, unlisted product pages in press kits, and staging previews can trigger a Google crawl before launch. If AdsBot visits before launch day, it records the product as unavailable. That record persists in the disapproval log even after you go live, unless you request a re-review.

How to detect the issue on your store

Before touching any attributes, locate every product Google has flagged.

1. GMC → Diagnostics → Item issues. Filter by the “pre-release products” disapproval reason. Export the CSV. This gives you the exact item IDs - typically your Shopify product ID or GTIN - that triggered the flag.
2. Shopify Admin → Products. Open each flagged item and check: publication status, whether a future publication date is set, inventory policy (“Continue selling when out of stock” toggled on?), and whether the product belongs to any collection that is not yet published.
3. Your GMC feed. Via Merchant Center → Diagnostics → select a product → View item, or via the Google & YouTube channel’s product list in Shopify Admin, confirm the actual availability value being submitted. A product that appears “Available” in Shopify may still be submitting in_stock when it should be preorder.
4. The live storefront. Visit each flagged product URL in an incognito window as a logged-out user. Can you add the item to cart and see a price? If not, Google will disapprove the product regardless of what your feed states.

Step-by-step fix

The correct fix depends on which scenario applies to each flagged product.

Scenario A - Genuine pre-order (purchasable now, ships on a future date):

1. Set availability=preorder in your feed. Do this via a supplemental feed in Merchant Center, a product metafield mapped in the Google & YouTube channel settings, or a direct feed override.
2. Add the availability_date attribute with the expected ship date in ISO 8601 format. Google requires this field when availability=preorder.

availability: preorder
availability_date: 2026-06-15T00:00:00-05:00

3. In Shopify, confirm the product page clearly states the expected ship date - in the description, a banner, or a dedicated metafield-driven block. The storefront and the feed must tell the same story.
4. In Shopify Admin → Settings → Policies, confirm your refund policy addresses pre-orders. Google’s reviewers occasionally check this during manual reviews.

Scenario B - Product not yet released (cannot be purchased at all):

1. Set availability=out_of_stock if you want to maintain the GMC listing while the product is unavailable. This keeps the product indexed in Merchant Center but removes it from active Shopping ads.
2. Alternatively, switch the product back to Draft in Shopify. This removes it from feed sync entirely and prevents public access until launch.
3. Do not use availability=in_stock with a placeholder price or a $0 variant - this creates a secondary misrepresentation signal on top of the pre-release disapproval.

Scenario C - Scheduled Shopify publication caused a timing gap:

1. Keep the product in Draft status until after the publication timestamp has passed and the product is confirmed purchasable at checkout.
2. After the product goes live, trigger a manual resync in the Google & YouTube channel app or submit a feed fetch request in Merchant Center → Feeds → Fetch now.

Scenario D - An early shared URL triggered an AdsBot crawl:

1. Immediately set the product to Draft or password-protect the collection until launch.
2. In Google Search Console → URL Inspection, use “Request Indexing” to signal to Google that the URL state has changed after the product goes live. This does not guarantee an immediate re-crawl but deprioritizes the cached unavailable state.
3. After launch, re-enable the product and request a GMC re-review from the Diagnostics panel.

After applying the appropriate fix, go to GMC → Diagnostics → Item issues, select the disapproved items, and click Request review.

What to include in your appeal

For a product-level disapproval, correcting the feed attribute and clicking “Request review” in the Diagnostics panel is typically sufficient - a formal written appeal is not required. If the disapprovals are widespread or have triggered an account-level warning, prepare the following:

• A brief factual explanation of what caused the mismatch. For example: “Shopify’s scheduled publication feature synced the product to our feed 48 hours before the storefront page became purchasable. We have corrected the availability attribute to preorder and added an availability_date.”
• Evidence of the corrected feed values. A screenshot of the product’s current attributes in GMC Diagnostics, or a Merchant API v1 ProductStatus resource response showing availability=preorder and a valid availability_date.
• A screenshot of the live product page as a logged-out user, showing either an active add-to-cart button and a visible price (for in_stock or preorder), or a page that accurately reflects out_of_stock status.
• A description of the process change you are implementing to prevent recurrence - for example, committing to keep all products in Draft status until their launch date. This demonstrates systemic correction, not just a one-time fix.

Keep the explanation factual and concise. Google’s review process is data-driven. Reviewers are looking for evidence that submitted attributes now accurately reflect storefront reality.

Edge cases & when to escalate

Countdown timers and timed drops. A countdown timer does not automatically make a product a pre-order in Google’s classification. If shoppers can add the product to cart before the timer reaches zero, the product is in_stock. If the add-to-cart button is disabled until the countdown ends, the product is out_of_stock until that moment, then in_stock. The attribute must match the actual cart behavior, not the marketing experience.

High-volume pre-order businesses. If pre-orders are a recurring model - new sneaker drops, limited editions, made-to-order items - configure a permanent supplemental feed that maps your Shopify pre-order tag or metafield to availability=preorder and pulls availability_date from a custom product metafield. Managing this manually for each drop is error-prone and will generate repeated disapprovals across multiple product cycles.

Escalation to misrepresentation. A pattern of pre-release listings - particularly multiple products crawled as in_stock across several feed cycles before being purchasable - can escalate to a misrepresentation account suspension. Misrepresentation suspensions are harder to appeal, require a more detailed reinstatement report, and involve human review. If your account is suspended rather than products simply disapproved, treat it as a misrepresentation case from the outset.

When automated re-reviews fail. If you request a re-review two or three times and the disapproval persists despite confirmed data corrections, escalate via the GMC “Contact us” form. Provide your Merchant ID, the specific item IDs, and a before-and-after comparison of the feed attribute values. Automated reviewers may be acting on a cached signal that the manual team can clear.

DSA applicability. This disapproval type is not governed by the EU’s Digital Services Act - product data accuracy is a Shopping policy compliance matter, not a content moderation decision. Standard GMC re-review procedures apply in all markets.

Frequently asked questions

Frequently asked questions

My Shopify store has a pre-order button plugin. Why does GMC still show an in_stock disapproval?

Shopify pre-order plugins typically enable the Continue selling when out of stock inventory policy but do not change the availability attribute in your Google feed. The Google and YouTube channel app reads inventory policy and stock quantity, not the button label. To fix it, explicitly set availability=preorder in your feed - via a supplemental feed in Merchant Center, a product metafield mapped in the Google and YouTube channel settings, or a direct feed override - and add an availability_date attribute with the expected ship date.

Can I list a product as in_stock if it ships in two weeks?

Yes, provided the product is available for purchase at the time Google crawls it. Google's policy permits in_stock for items that are purchasable immediately, even if fulfillment takes several weeks. The disapproval applies only when the product cannot be added to cart at crawl time - for example, when a countdown timer is running and the product page does not yet allow checkout. If the add-to-cart button is active and the price is displayed, the product typically qualifies as in_stock.

How long does it take for GMC to re-approve products after fixing the availability attribute?

After you request a re-review in GMC Diagnostics, the automated review typically completes within 3 to 7 business days. Many merchants see resolution within 24 to 48 hours for straightforward attribute corrections. Feed re-crawls can take up to 2 business days after you trigger a manual fetch in Merchant Center under Feeds, then Fetch now. Monitor the Diagnostics panel for status changes.

Do I need to remove a pre-release product from my sitemap to prevent GMC disapprovals?

Removing the product from your sitemap reduces the chance that AdsBot discovers it before launch, but it is not sufficient on its own. AdsBot can discover URLs from shared links, Google's existing index, and other crawlers. The most reliable approach is to keep the product in Draft status in Shopify, which simultaneously removes it from feed sync and prevents public access until it is genuinely purchasable.

I run limited drop campaigns where products sell out in minutes. How should I manage availability?

Keep the product in Draft or explicitly set availability=out_of_stock in your feed during the pre-launch window. When the drop goes live, switch to in_stock and trigger a manual feed fetch in Merchant Center. Google does not penalize products that legitimately sell out after launch - the disapproval risk is specifically when a product is presented as available before shoppers can actually complete a purchase.

Can a pre-release product disapproval escalate to a full account suspension?

Yes, in some cases. A single product disapproval is a warning-level event. However, if Google detects a recurring pattern - multiple products listed as in_stock before they are purchasable, or items that cannot be purchased at all - the account can escalate to a misrepresentation-level suspension. Misrepresentation suspensions require a more detailed appeal and evidence of systemic process changes, not just a corrected feed attribute.

Sources & references

Authoritative sources cited

1. Google Merchant Center Help: Pre-release products https://support.google.com/merchants/answer/6324448
2. Google Shopping ads product data specification: availability attribute https://support.google.com/merchants/answer/7052112