ItemlumeAssets & tasks / DECISION CHECK
My product image is ready. Why does Merchant Center still show pending?
First read the exact Merchant Center issue and image history. A finished file, a successfully fetched image and an approved Shopping product are three different states. Regenerating a photograph does not resolve a crawl queue or a feed mapping error.
Identify which system is waiting
Open the affected product in Merchant Center and record the destination, item ID, issue text, submitted image URL and time of your last change. Check the image history rather than relying on the thumbnail in your store. The history can reveal whether Google has inspected the new file at all. Compare that time with your own publication record.
A generation task marked complete in Itemlume only establishes that a creative file was returned. It does not submit a feed or monitor Google approval. Conversely, a pending external review does not prove the generator failed. Keep the approved file while you diagnose the external state.
Use a state-based decision
| Observed state | Next evidence | Useful action |
|---|---|---|
| Pending; new image not crawled | Submitted URL and crawl history | Check access, then allow processing |
| Crawled; specific image issue | Current fetched image and issue text | Repair the documented defect |
| Old thumbnail remains | Old and new URL plus update times | Check replacement and transition |
| Image approved; item blocked | Non-image product issues | Investigate the listed attribute |
Google describes processing delays and possible use of an older approved image during replacement. Those periods are guidance rather than a deadline promise for your particular account. Do not delete and recreate products merely to force a new thumbnail.
Keep one change interpretable
For an illustrative ceramic-mug listing, first verify that the newly submitted URL opens the intended mug image without sign-in. If it does, leave that URL stable and record the check. If it redirects to an expired download, publish a durable public asset and correct the feed reference. Changing the prompt, file, product ID and feed source together makes the result harder to diagnose.
Use the Merchant image diagnosis CSV as a manual record. Its sample row is fictional. Replace it with your own authorized evidence; the worksheet does not connect to or change any external account.
Know when to escalate
If the image is accessible but the status remains unresolved beyond the guidance shown for the issue, collect the item ID, timestamps and image history for platform support. Exclude credentials from screenshots. Treat a rejection as a concrete repair request: an overlaid discount calls for a clean export; an inaccessible URL calls for delivery work. A prettier scene is not evidence that either problem was fixed.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Does pending mean my image broke a rule?
Not by itself. Read the status, issue and crawl history together.
Should I generate again while waiting?
Only if you have identified a defect in the file itself.
Can Itemlume approve a Google listing?
No. Approval and feed processing belong to Google.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits