Feeds
A feed keeps a catalogue list in step with an external source. Instead of typing a hundred products by hand, you point a feed at a spreadsheet or a dataset and Klyo imports them, then re-imports cleanly when the source changes.
What works today
All four source types import for real: Google Sheets, uploaded Excel files, BigQuery, and Google Merchant Center. Running a sync by hand works end to end. Automatic scheduled syncs are built but not switched on yet (see the note below).
You manage feeds from the catalogues area: a Feed manager sits beside a catalogue, so a feed always fills a specific list. You do not have to create that list first: connecting a feed can create a brand-new catalogue list for it in the same wizard, naming the list and turning detected columns straight into fields, so you never juggle two screens to set one up.
Where catalogue items come from
| Source | What it reads |
|---|---|
| Google Sheet | A range from a sheet you share with Klyo |
| Excel | An .xlsx file you upload |
| BigQuery | A table or a query result |
| Merchant Center | Your product catalog |
When you set up a feed, Klyo shows the service account to grant access to, and previews the columns it finds so you can map them before the first import.
The column mapping
A feed maps source columns onto catalogue item fields. One column is the external id, the stable key Klyo uses to recognise a row again. Others map to the catalogue item's name, its description, its declared fields, and asset references. Asset references are resolved against your asset library, and a reference that does not resolve is flagged rather than dropped.
Syncs are idempotent
A sync matches rows on their external id, so re-running it updates catalogue items in place and never duplicates. A row that vanishes from the source is tombstoned (soft-deleted), preserving history for any combination package that used it. Your manual edits win: if you edit a feed-imported catalogue item by hand, it is marked manual so a later sync does not overwrite you.
Every run is audited as a sync run with counts of what was created, updated, left unchanged, tombstoned, skipped, and left unresolved (an image reference that matched nothing), plus any per-row errors. You can see the run history for each feed.
A manual sync runs in the background rather than blocking the page: Klyo tells you it is still working and you are free to navigate away, and the feed picks up the finished state on its own once the run settles.
What you can do today
- Create feeds against Sheets, Excel, BigQuery, or Merchant Center.
- Create a brand-new catalogue at the same time, instead of pointing a feed at one you made earlier.
- Check access and preview columns before importing.
- Map columns to catalogue item fields and asset references.
- Run a sync on demand in the background and review its run history.
Scheduled syncs are not switched on
Feeds can run on a schedule, and the schedule settings are there, but the trigger that fires them automatically is not provisioned yet. Until it is, syncs run when you click sync. The feed view tells you when automatic syncing is not active, so you are never guessing.