Skip to main content
Generating is the moment Rogus reads your catalog and builds the file. Until you generate, a feed is only settings — it has no file and no URL.

​
Generating by hand

Open the feed and press Generate. Rogus works through the run and shows you where it is:
  1. Checking your catalog
  2. Reading products from Shopify
  3. Building feed items
  4. Saving the feed
You can leave the page. The run continues in the background — it does not belong to your browser tab. Come back later and the result is waiting. Large catalogs take a while; reading products from Shopify is nearly all of it. While a run is in progress the feed shows Generating in the feed list, and Generate is unavailable for that feed.

​
Reading the result

When the run finishes you get a summary:
Feed generated — 1,240 items from 380 products.
and then, only where they apply: A run with skipped items is still a successful run. Bad product data never stops a generation — the products Rogus can publish, it publishes, and the rest are reported.

​
Automatic sync

On a paid plan, Rogus watches for catalog changes and rebuilds the feed for you. How it works: when you add, change or delete a product, or stock moves, Shopify tells Rogus and the feed is marked out of date. Rogus then rebuilds it at your plan’s next slot — not instantly, because rebuilding on every single product edit would be wasteful for you and hard on Shopify’s limits. Two details:
  • A feed is only synced automatically after you have generated it once. A feed you have never generated is treated as still being set up.
  • Changing feed settings does not mark it out of date. After editing a mapping or the product selection, press Generate to publish the change.

​
Feed statuses

In the Feeds list:

​
When a run fails

A failure is shown on the feed with the reason. The most common causes: Permissions. Rogus could not read your catalog. Reinstall or reopen the app so Shopify re-grants access. Shopify rate limits. Rogus waits and retries automatically, using the wait Shopify itself asks for. You do not need to do anything. Configuration errors. Something in the feed makes an empty or broken file for every product — a required field with no source, for instance. Rogus catches these before reading your catalog and tells you which field to fix. A failed run leaves the previous file in place. Your feed URL keeps serving the last good version rather than going empty, so a failure never takes your products offline at the channel.

​
Generating from the Home page

The Home page shows the state of every feed at once — how many are live, how many items are published, and how many products did not make it. Anything needing your attention is listed there with a link to the feed. Below that, Feed templates lets you start another feed straight from Home. For the full list of feeds, with each one’s status and last run, open the Feeds page.