Academy
Ecommerce product feeds: start with the source
A grounded guide to building an ecommerce product feed from the shop data you already maintain.
Checked against the sources on 7 October 20267 min read
An ecommerce product feed is a controlled export of what a shop sells. It should carry the information a channel needs while continuing to take price, stock and product facts from the ecommerce platform where the team actually manages them.
Why this matters now
Many merchants begin with a download because it feels tangible. That can work for a one-off audit, but it becomes brittle when stock moves throughout the day. A dependable feed is less about a clever file and more about a clear link back to the live catalogue, with a way to spot when the connection has gone stale.
What to check first
| Check | What good looks like | What to do if it is missing |
|---|---|---|
| Shop platform | Owns sellable catalogue facts | Use it as the live source |
| Feed | Packages selected facts for a channel | Validate its rows and links |
| Checker | Shows gaps and patterns | Use it before manual rework |
A practical way to do it
- Choose the live shop or a maintained source file as the catalogue authority.
- Decide whether products and variants need distinct rows for the channel.
- Check the public URL, image and price for a representative sample.
- Map missing store-level information once instead of typing it repeatedly.
- Refresh after source changes and investigate any new validation errors.
Common mistakes
- Mixing product facts from a staging store with live prices from production.
- Using internal image paths that a shopper or channel cannot open.
- Trying to solve a feed problem by changing unrelated theme copy.
What this does not mean
A clean product feed makes your catalogue understandable to a receiving platform. It does not guarantee approval, inclusion, ranking, sales or a particular checkout experience. Those decisions and customer-facing flows remain with the platform and the merchant.
The useful habit is simple: correct the source data, then validate the exported feed. Do not patch a one-off file and assume the next shop sync will remember your fix. That is how a tidy launch turns into a slow drift a fortnight later.
See the missing fields in a public shop catalogue before you spend time formatting a feed by hand.
Run a free store checkQuestions
Can a small CSV be an ecommerce product feed?
Yes, if it is current, structured for the target and maintained as products change.
Should I export stock manually?
Only if the catalogue rarely changes and you have a reliable process to update it.