Each channel has its own feed file. Feedsmith keeps it at a feed URL that the channel can fetch, and it can also upload the file to a server for you. You set all of this on the channel's Settings tab.
The Feed URL card shows the address of the feed, e.g. https://…/f/k3J9xQ2b7.xml. Click Copy to copy it, or Open to see the file. Paste the address into the channel's own system, e.g. as a scheduled fetch in Google Merchant Center or a data feed in Meta Commerce Manager.
To stop an old address working, e.g. after a contractor leaves, click Regenerate URL. The current address stops working at once, so update it everywhere you use it.
The address ends with the file type, e.g. .xml or .csv. If you change the channel's format, the ending changes too, so update the address in the channel's system.
You choose the format under General. Each template allows certain formats. See Channels and templates.
| Format | File | What it looks like |
|---|---|---|
| XML (RSS 2.0, Google namespace) | .xml | The standard Google Shopping layout. Each product is an <item>, and fields are written as <g:title>, <g:price> and so on. Empty fields are left out. |
| XML (custom root / item elements) | .xml | A plain XML file, e.g. <products><product><title>…</title></product></products>. Custom channels only. |
| CSV | .csv | One row per product with a header row of field names. |
| TXT (tab separated) | .txt | Like CSV, with a tab between fields. |
| JSON | .json | A list of products. Custom channels only. |
Format options depend on the format:
catalogue and item. The defaults are products and product.Fields with several values from Use every matching rule are written as one element per value in XML, as one cell with values separated by commas in CSV and TXT, and as a list in JSON. In XML (RSS 2.0), shipping values such as NZ::Standard:5.00 NZD are split into country, region, service and price, and you can put several shipping rules in one value, separated by commas.
Feedsmith turns &, <, >, " and ' in your product data back into &, <, >, " and ' before writing the feed. So Lime & Orange from a supplier file comes out as Lime & Orange.
An XML (RSS 2.0) feed starts with a title and a link. By default, the title is the channel's name and the link is the shop's storefront URL. To change them, fill in Feed title and Feed link. Other formats don't use these settings.
Some channels, e.g. some Google Merchant Center setups, fetch feeds from their own server instead of from a URL. Feedsmith can upload the feed there after every build.
uploads.google.com, without ftp:// or a folder. Enter the Port only if the server uses an unusual one. The defaults are 21 for FTP and 22 for SFTP./feeds, or leave it empty for the top folder, and the File name, e.g. kiwi-outdoor-nz.xml. The file name can't contain spaces or folders.The card shows the result of the Last upload, e.g. "OK" with the size of the file, or "Failed" with the error. The Channels tab shows "Last upload failed" next to a channel whose upload failed. A failed upload doesn't stop the feed URL from working.
The password is stored encrypted, and the box shows "Saved — leave blank to keep". If you change the host, port or username, Feedsmith clears the saved password, so enter it again. To remove the password, use Remove saved password.
A host key is the server's digital fingerprint. Feedsmith checks it on every upload to make sure it is talking to the right server, so it never sends your password to a server pretending to be yours. SFTP uploads need it.
SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.If the server's key later changes, uploads fail with "SFTP host key MISMATCH". Only update the key if the server's owner confirms they changed it.