Product feed delivery errors vs data errors
First determine whether the receiver obtained the file. Delivery failure, parsing failure and product-data failure require different evidence. A successful local audit does not test SFTP or API delivery.
Start with the failed stage
Record the failure time, exporter version and a safe technical error code. For delivery, check the destination's own status and authorized transport configuration. Keep credentials, private URLs and customer data out of tickets and logs. Do not weaken authentication or make a private feed public as a troubleshooting shortcut.
Inspect the same exported artifact
If delivery succeeded but parsing failed, inspect the actual exported format, encoding and compression. Validate the XML or CSV structure before interpreting product findings. A successful audit of yesterday's file cannot explain a malformed file uploaded today.
Confirm recovery without overclaiming
After a source fix, scan the new artifact and separately confirm destination processing. Controlled encoding recovery produces explicit warnings and replacement counts; it is not a permanent repair of the exporter. Fix source encoding even when isolated damaged bytes can be recovered for an audit.
Practical example
Synthetic incident: the local CSV audit succeeds while delivery reports an authentication error. Changing product titles will not fix transport credentials. Conversely, a delivered file can still fail parsing because its XML is malformed.
What Product Feed Scan checks
Product Feed Scan fetches supported public URLs or accepts temporary XML/CSV uploads with bounded parsing and visible encoding diagnostics. It does not connect to your SFTP server, call a merchant API or inspect delivery-account credentials.
Open the relevant checker See a sample report