Understand Merchant Center Readiness
Inspect the Google destination, latest generated file and available provider evidence. Correct source or account issues before assuming that a listing is eligible to advertise.
Read the full user guideHow it works
The AdexPilot workflow
Connect the destination
Google requires Merchant Center. Meta requires a Meta connection. A missing destination is explained in Catalog Health; it does not need an empty feed.
Wait for the initial build
After the connection is ready, AdexPilot requests the destination’s initial feed using complete Shopify source data. If the import is not ready, the build waits.
Follow scheduled updates
Connected feeds update through the existing 12-hour store refresh. Check Catalog Health and Activity for progress, waiting reasons and the next scheduled update.
In practice
Automatic means no Generate button
Merchants do not manually generate or retry the regular catalog feed. Saving market or feed settings does not start an extra build.
- Only connected, enabled destinations are built.
- Google Ads alone does not enable a Google catalog feed.
- Saved feed changes apply in the next scheduled update.
- An initial build may wait for current work or the required source import.
- The separate supplemental-label workflow is not a manual refresh control for the catalog feed.
In practice
Three separate statuses
A file can be generated successfully without being accepted by the provider or without every product being eligible.
- File generation: AdexPilot produced a feed from available source data.
- Provider delivery or acceptance: the destination fetched, registered or processed it where confirmed evidence is available.
- Product eligibility: Google or Meta determines whether individual listings can be used.
- Unknown provider status must stay unknown; it is not an approval.
- Inspect issue details for missing images, prices, identifiers, stock or market information. Correct the relevant source data.
In practice
Labels and supplemental data
Labels can help organize products for review or campaign grouping. Their value depends on the available product evidence and the provider’s feed setup.
- Use labels to group test, scale, fix or stock-review candidates.
- Do not infer profitable products from missing costs.
- Check the supplemental workflow and provider setup separately.
- A label dependency is not usable for campaign targeting merely because its file exists.
Reference
Common questions
Does signing in refresh my feeds?
No. Initial destination setup and the scheduled store cycle drive regular generation. Signing in or opening Catalog Health does not start another build.
Are all products guaranteed compliant?
No. AdexPilot checks and formats feed data, but provider policies, source quality, website consistency and account setup determine acceptance and eligibility.