Scheduled product feeds from your store

A data feed is an export that runs on a schedule and lands somewhere a machine can read it: a shopping channel, a marketplace, a warehouse system, a BI tool. Same export engine, same filters — just repeating, and delivered.

What you can publish

• Google Shopping feed — product fields in the shape Google Merchant Center expects.
• XML — for channels and systems that read a structured feed.
• JSON — for anything you are wiring up yourself.
• CSV or Excel — for partners and internal reporting.

Setting one up

1. Build the export you want: pick the data type, filter it, and choose the columns the receiving system needs.
2. Run it once and open the file. Feeds fail on small mismatches — check it before automating it.
3. Save it as a schedule and pick the frequency: hourly for stock, daily for catalog, weekly for reporting.
4. Choose the destination — FTP/SFTP, Amazon S3, Google Drive, Google Sheets or email.

Keeping a feed honest

• Filter to the products you actually want listed — usually Active status, and in stock.
• Include the identifiers the channel matches on (SKU, barcode, MPN) or your items will not be recognised.
• Match the refresh rate to how fast the data changes: hourly stock, daily prices.
• Watch the job history. A feed that silently stopped updating is worse than no feed.

Every scheduled run keeps its own file and results, so when a channel complains about last Tuesday's feed you can open exactly what was sent.

Feeding a warehouse or ERP

The same mechanism works in reverse: a scheduled import can pick a file up from FTP or S3 on a timetable, so a supplier's nightly stock file becomes tonight's inventory update without anyone touching it.