Job merchant-center-feed-file-fetch-processing-errors · revised 11 October 2026
Get your product file fetched and processed by Merchant Center without errors
Merchant Center fetches your named product file on schedule and processes it, with file-level errors in the data source report cleared or explained and the item count matching your file.
You might be seeing
- The data source shows a failed or stale fetch, or processing errors affecting many items at once
- Merchant Center lists far fewer products than the file contains, or none
No passwords, keys, card details or admin invites needed to start.
What usually happened
Google cannot fetch the product file, or can fetch it but cannot read it. The address redirects to a page instead of the file, is blocked by access rules or a login, the file has the wrong extension or compression, the text file has an extra or missing tab, the XML contains an unescaped character or wrong-case tag, or the file's encoding is not one Google reads. The data source report shows file-level errors rather than item problems.
Who it’s for: Merchant or developer whose Merchant Center data source shows a failed fetch, a processing error or far fewer products than the file contains.
Usually starts when: 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.
Check whether this job fits
Answer these without sharing logins. Nothing is submitted unless you choose to contact us.
Checks you can run yourself
Read the file's first lines
Open a copy of the file in a plain text editor and look at the first three lines, or the first item if it is XML.
Look for: For text, a header row of attribute names separated by tabs, and the same number of tabs on each line. For XML, an rss or feed root element with the Google namespace declared, and escaped ampersands.
What you get
- 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
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
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
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
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.
Evidence: The request record showing status, redirects, final address and type, with any login 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.
Evidence: Redacted before and after report screenshots with dates.
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.
Evidence: A reconciliation table of file rows against processed items.
Sign-off. 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.
If it fails. If the report still shows file-level errors after the agreed changes and a reasonable processing time, you do not pay for this fixed scope. We hand over our findings and agree whether to stop or re-quote.
When it fits, and when we stop
It fits when
- The file is produced by a script, export or feed rules that you control or can ask someone to change
- You can send redacted screenshots of the data source report and the first lines of the file with invented values
- The file address can be opened by a visitor without a login, or the login is stored in your Merchant Center settings
We stop and tell you if
- 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
What could go wrong
Keep the previous generator rule and host settings. The handover lists each change and its reverse. We do not change your live file, host or account; you apply the change and can restore the earlier version.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A fix to the file hides a hosting or access problem that returns later. | The cause statement names whether the fault was the address, the access or the file, and the change list covers each. |
| Google's reports lag, so a correct change looks like it failed. | The acceptance check is the next processed report, with the wait stated up front, and we do not promise Google's timing. |
| Pasting a login or token into an email. | The first enquiry asks for the address with any token removed and redacted screenshots only. |
An independent reviewer checks that the cause is supported by the report and the address behaviour, and that no personal data or credentials appear in the evidence. Your account holder or host administrator applies the change.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the data source, the file address and the reports to be used in writing
- Read the report and request the file address as Google would, recording redirects, status and type
- Check the file's structure, encoding, extension and size against Google's published file requirements
- Correct the generator on a copy, or prepare a change list for the host or schedule
- Independent review of the cause statement and the change, then hand over for your account holder to apply
- After the next processing run, compare the report with the file and record the result
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access and any needed permissions are in place. Hosting, supplier and platform charges are excluded unless the written quote includes them. An enquiry creates no charge or booking.
Need to keep it working?
Discuss a standing watch on the data source's fetch and processing status.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Google's troubleshooting page for data sources lists the usual file creation, configuration, formatting and upload problems and their fixes. Work through it first if you can. support.google.com
- Google's file requirements page describes the accepted formats, header row and XML layout; compare a copy of your file against its examples. support.google.com
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.
Send an enquiry
Send us
- 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
Later, once you agree
- Diagnostics and data source report access at the least level that lets us read them, or redacted exports from you
- The file-generating rule or export through an agreed company-controlled route
- A named person who can change the host, schedule or generator
You keep your Merchant Center account, hosting and feed generator. We work from redacted reports and a copy of the generator, and return a corrected rule and a change list. Your account holder or host administrator applies changes and triggers processing; we never hold advertising or billing access.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “merchant-center-feed-file-fetch-processing-errors” as the subject.