A feed is a product data file Koongo builds for a channel (you may also hear "channel" or "channel profile"). The channel then downloads it - or, for some channels, Koongo submits it directly. This guide creates a feed, fills it in, and generates the file.
Just ask
Create a Google Shopping feed for my store, help me map the required attributes, then generate the file and check it looks right.
Other examples: "What feed templates are available for Germany?" · "Only include in-stock products in this feed." · "Re-generate the feed and tell me when it's ready."
How it goes, step by step
Pick a template. The assistant lists feed templates; you choose the channel/country/format you want.
Create the feed. If the channel needs category mapping, the assistant flags it - do Category Mapping next.
Map the attributes. Fill every required output attribute - see Attribute Mapping.
Optional settings & filters: stock/shipping output, and which products to include (in-stock only, by category, or by attribute conditions).
Export. The assistant generates the file (this runs in the background) and waits until it's ready.
Verify. Ask for a quick check of the generated file - missing values, empty columns, spec problems - fix, and re-export.
Submit (only for channels Koongo pushes to via an API). File feeds that the channel pulls don't need submitting - you just share the feed URL.
Settings, filters and mapping are all saved first and only appear in the file after you export. So the usual rhythm is: change things → export → check.
Tip: ask "verify the feed and show me a small sample" before you hand the feed to the channel. It's the fastest way to catch an empty required column.
Behind the scenes (for the curious)
Behind the scenes (for the curious)
Flow: list_feed_templates → create_feed → (if categoryMappingNeeded) category mapping → get_feed + map_feed_attribute per attribute → optional set_feed_settings (stock/shipping), set_feed_filter (common flags + categories), set_feed_attribute_filter (attribute conditions) → export_feed → get_feed_status (poll to generated) → verify_feed_attributes → submit_feed (API channels only; file channels return "not submittable"). Lifecycle helpers: pause_feed / resume_feed, update_feed (rename/enable), delete_feed / restore_feed.
