Who this is for
Merchant or developer whose Merchant Center data source shows a failed fetch, a processing error or far fewer products than the file contains.
The data source reports that the file could not be fetched or processed, or products are missing after a scheduled fetch, usually after the file's location, format or generating script changed.
The result
Merchant Center fetches the named file from the agreed address on the agreed schedule and processes it. The latest-update report shows no file-level errors, and the number of items read matches the number of rows or items in the file.
What is included
- One Merchant Center data source fed by one hosted file, text or XML
- Read the data source's latest-update report, the file's address behaviour (redirects, status, type) and the file's structure against Google's file requirements
- Find the cause: address, access, extension and compression, delimiter and header names, XML escaping and tag case, encoding or size
- Correct the file-generating rule or export that you control, or give you a precise change list for the host or schedule
- Recheck the next processed report and reconcile the item count with the file
You receive
- A short cause statement with the evidence from the report and from requests to the file address
- The corrected file-generating rule or a change list for hosting and schedule settings
- A reconciliation of rows or items in the file against items processed
- Before and after data source reports
What is not included
- Item-level disapprovals caused by prices, availability, images or identifiers, which are separate jobs
- Google Sheets or other source types that are not one hosted text or XML file
- Google account suspensions or policy appeals
- Building a new feed from scratch or changing platforms
- Merchant API or direct API submission design
- Advertising campaign management
What we need from you first
- A redacted screenshot of the data source's latest-update report
- The first five lines of the file with invented or redacted values, and the file's address with any token removed
- How the file is produced and when it is fetched. No Merchant Center login, customer data or code in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- A request to the agreed file address from outside your network returns the file itself with no intermediate page, and the file's extension, compression and type match the data source settings. For a public file the request needs no login. If the source uses a login stored in your Merchant Center settings, your account holder makes the request with that login and sends us the record with the secret removed.
- After the next scheduled fetch or a manual fetch, the data source's latest-update report shows a completed processing with no file-level errors.
- The number of items Merchant Center read equals the number of rows or items in the file, and every difference is listed with its reason.
You inspect the reports and the reconciliation and sign off in writing. Payment follows sign-off; applying the change and triggering processing stay with your account holder.
When we would stop or decline
- The report cites an account-level suspension rather than a file or data source error
- The host blocks Google's crawlers deliberately and you do not want to change that
- The file contains personal data that would have to be shared with us
Questions
Is this the same as fixing disapproved products?
No. This job is about Google fetching and reading the file. Disapproved products have separate causes, such as price, availability or images.
My file is on a hosting service I do not control. Can you still help?
We can find the cause and say exactly what the host or file owner must change. We cannot change a service you cannot access.
Can you submit the file for me?
No. Your account holder applies changes and triggers processing; we do not hold your Merchant Center login.
Price and terms
£245 · untested offer price. £245 after the next processed report shows no file-level errors and the agreed item count, and you sign off. No payment before sign-off. Google's processing time is outside our control.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.