To see what an import did, open a catalog's Activity tab: it lists every import with its counts, and each one expands to a full log, statistics, and the fields that changed. To understand why a single value came out the way it did, use Trace a product — it walks one product through your rules to the final catalog output.
The health strip: your feed's status at a glance#
The health strip sits at the top of every catalog page and is always visible. It's the quickest read on your feed:
- A status light plus, when something's wrong, "Needs attention — N warnings".
- "Last import {time ago}" and the catalog's total "{N} products".
- While an import is running, live progress — "Importing… {stage}" — and an "Import stalled?" prompt if it looks stuck.
- When an import finishes, a one-line summary: "{N} new, {N} updated · {N} excluded · {N} couldn't be read · took {duration}".
- The "Import now" button.
A note on "Import now": it processes your last published configuration, not your draft. If you have unpublished edits, clicking it warns you and offers to publish first. That trap is covered in full in Fixing your feed data with rules and Transforming your feed.
The Activity tab: what each import did#
The Activity tab is the catalog's home view. It lists every import as a row, most recent first, with these columns:
- Started — when the import ran.
- Trigger — what kicked it off.
- Status — how it finished.
- Products — how many products the import covered.
- Changed — how many products' data changed.
- Excluded — how many products a rule dropped.
- Warnings — how many distinct warning types the import raised.
- Duration — how long it took.
The list shows the five most recent imports — the ones you almost always want — with a pager below the table to step back through the older history.
When you publish, Renable also runs a preview to check what your changes would do. Those diff-check runs are hidden by default; a "Show diff checks" toggle brings them into the list when you want to see them, and hides them again to leave only real imports.
Open a run for the full detail#
Click any import in the list to expand it. Inside you get:
- The log — the import's stage-by-stage record, useful when a run failed or behaved oddly.
- Statistics — a row of chips counting exactly what happened: Total rows, Seen, Created, Updated, Output unchanged, Excluded, Soft deleted, Parse failed, and Warnings. Output unchanged is the normal case for a stable feed — those products were re-read and came out identical. Parse failed is the "couldn't be read" count from the summary line: rows the importer couldn't make sense of. Soft deleted is products that were in the feed before but have now dropped out of it.
- Changed fields — a chip per field that changed in this import; open one for a before/after popover so you can see the actual old and new values. This covers the regular product fields, each custom attribute by its own name, and the product's images and reasons to buy (each of those counts as one changed field when anything in the list changes). So when an import updates many products, the chips tell you what moved — even when it's only a single custom attribute or an image link. The popover also has a View products link that opens the products page filtered to the products whose value changed in that import — for very large changes it shows the first 1,000 of them, and says so.
- Products with warnings — the list of products this run raised a warning for, so you can go straight to them.
Warnings: from a message to the exact products#
Below the imports, the Activity tab lists the warnings and errors from your feed. Warnings dedupe on their text — if the same problem hits 500 products, you see one warning that tells you it affected 500 products, not 500 separate lines. From a warning you can drill down to exactly the affected products, so a message becomes a working list instead of a vague alarm.
This covers products the import had to skip, too: a product missing one of the core basics (ID, link, title, or price) can't be imported, and surfaces as a warning that names the missing field and counts the affected products — "14 products are missing price" — rather than disappearing silently. A row the importer couldn't read at all is reported the same way. These warnings clear on their own once an import comes through clean.
Each warning also carries an "Ask Aimée to investigate" action — one click hands the problem to Aimée, who looks into what caused it and what to do about it.
Trace a product: why a value came out the way it did#
When a field on one product looks wrong and you want to know why, use Trace a product. It's on the toolbar of both the Rules tab and the Mapping tab.
- Open Trace a product and pick or search for the product you want to follow.
- Renable shows a vertical pipeline of your rules as step-cards. Each card shows the rule's number, its name, and its one-line summary.
- Every card carries a status chip: "applied" if the rule acted on this product, or "didn't apply" if it didn't. When a rule changed a field, the change is written out as
field: before → after, so you can watch a value move through your rules step by step. - If a rule splits the product into variants, a chip picker lets you switch between the variants and trace each one.
- At the end, a "Catalog output" table shows the final value of every field. Each field a rule changed carries a "set by {rule}" note, so you can see which rule is responsible. Fields that came straight from your mapping, untouched by any rule, simply show their value.
Trace answers two questions at once: which rules touched this product, and what the field ended up as. If a rule you expected to apply shows "didn't apply", its conditions didn't match this product — check the condition against the product's actual values.
To learn how the rules Trace walks through are built, see Fixing your feed data with rules.
Barcodes that fail their check digit#
If you map a value to a GTIN, EAN, or UPC field and its check digit doesn't match, Renable doesn't silently keep a bad barcode, and it doesn't throw the product away. The product imports normally, and the barcode is kept through the import — but it's dropped before the feed reaches any ad network, so Google or Meta never receive an invalid barcode.
You'll see this in two places, describing the same thing:
- In the mapping preview, a hint: "invalid GTIN check digit — will import but be rejected by ad networks."
- After an import, a warning that those barcodes "were dropped downstream."
A failed check digit almost always means a typo or a truncated value in your source feed. Fix it at the source or correct it with a rule, and the valid barcode flows through.
FAQ#
An import ran but the Changed count is low or zero — did it work?
Yes. A feed that hasn't changed upstream produces mostly "Output unchanged" products — they were re-read and came out identical. That's the healthy steady state, not a failed import.
My edits didn't show up in the import — why?
Imports process your last published configuration, not your draft. If you edited rules or mapping and then imported, publish first (or choose Publish & import) so your changes take effect. See Transforming your feed.
A product vanished from the feed after an import — where did it go?
Check the run's Excluded and Soft deleted counts: Excluded means a rule dropped it; Soft deleted means it left the source feed. A product is missing from my feed or ads walks through every cause.
Or ask Aimée#
You don't have to sit and watch an import. Ask Aimée to wait for the import to finish and report back the real counts and warnings when it's done. She can also replay one product's import and read its history end to end — its import state, which fields resolved how, and which rule or setting decided each one — and tell you exactly what happened.