Feed ManagementKnow exactly what your feed tool did

Fix, join, and reshape messy product feeds with ordered rules and lookups — no IT ticket, no changes to the source. See every change on your own products before it ships, then retire the upstream feed tool and the guesswork with it.

Every value explains itselfSee every change before it shipsWorks with the feed you have

Start free Book a demo

Catalogsportgear.com

Imported 12 min ago48,113 rows

12 mapped3 required missing

FieldValueSampleFill

TitletitleTrail Runner 30099%

Price$price$8997%

GTINgtin—82%

TitleTrail Runner 300Set by Normalize titles

Fix the feed you have — not the one you wish you had

Every fix happens on Renable’s side of the feed, never in your store. No export to re-spec, no IT ticket, no waiting on a developer to change what your platform sends. Connect the feed you already have and reshape it entirely inside Renable.

Runs on the feed you already have

Feed URL

XML, CSV or TSV

Google Merchant Center

Meta catalog

Shopify

via third-party plugin

WooCommerce

via third-party plugin

Magento

via third-party plugin

BigCommerce

via third-party plugin

Google Sheets

File upload

CSV, TSV or XML

Fix anything in your feed — no code, no consultant

Aimée does the cumbersome part: she reads your feed, works out what’s wrong, writes the rules, maps the fields, and cleans up the mess. You describe the problem in plain language and approve the result — no becoming a feed expert to fix your feed. And every rule she writes is one you can open and hand-edit, because the full visual workspace is right there.

Catalogsportgear.com · en-GB

Unpublished changesPublish

Aimée

The titles from some of our suppliers are a mess — ALL CAPS, leftover HTML tags. Clean them up?

Created rule: Normalize supplier titles

Title Case, and strip HTML tags

TRAIL RUNNER 300Trail Runner 300

Drafted it — nothing’s live yet. On a preview run it matched 12,880 of 48,113 products. Publish it?

PublishNot yet

What do you need?

ActivityData sourcesRulesMappingSettings

Imported 12 min ago48,113 rows

Import now

Flag clearance items

When tag is SALE, set availability to clearance

Matched 4,201 of 48,113 last import

Normalize supplier titles

Matched 12,880 of 48,113 last import

When

brand is Acmeorbrand is Peakform

Then

Title → Title Case, strip HTML

Split variants by sizenever matched

One product per size · deterministic IDs

Rules you can read like a sentence

“Brand is Acme or Peakform, and price is above 50” — built by clicking, not by writing code, and every rule shows how many products it hit on the last import.

Value transforms for messy data

Replace text, apply regular expressions, change casing, strip HTML, trim, round, do math, and work with lists — split, join, filter, deduplicate. Each transform shows its effect on real values from your feed before you keep it.

Field mapping with fallbacks and coverage

Map any feed column to any output field, and stack fallbacks for when the first source is empty. A coverage indicator on every field shows how many products actually fill it — so gaps are visible before the ad network finds them.

Clean up the catalog itself

Drop the columns you never want downstream, and exclude products that shouldn’t be advertised at all. Excluded products never reach your channels — and never count toward your bill.

Meet Aimée

You shouldn’t have to guess what your feed tool did

Feed tools are black boxes: rules go in, a feed comes out, and when a value looks wrong you dig through exports to find out why. Renable shows its work at every step.

Trace a product

Road Racer Tee

Rules

Flag clearanceapplied

status: active → clearance

Exclude out of stockdidn’t apply

Clearance priceapplied

price: $45 → $35

Catalog output

TitleRoad Racer Teefrom mapping

Price$35Set by Clearance price

AvailabilityclearanceSet by Flag clearance

Publish configuration?

Publishing changes 8,012 of 48,113 products.

Fields changing

Availability8,012 of 48,113activeclearance

Price8,012 of 48,113$45$35

Title3,110 of 48,113TRAIL RUNNER 300Trail Runner 300

Publish

214 products have an invalid GTIN

Deduplicated from 214 warnings into one line · last import 12 min ago

View products

Live preview before you publish

See the effect of every rule on real rows from your feed before anything goes live. Not sample data — your data.

Every value tells you where it came from

Click any field on any product and see who wrote it: this title came from the “Normalize titles” rule, this stock level from the supplier feed. No exports, no guessing.

“Why is this product missing?” — answered in seconds

Follow one product from your feed to your channels: every rule that touched it, every lookup it hit, and the exact step where it dropped out. No support ticket.

Every import tells you what it did

What was imported, skipped, excluded, and warned about — with 214 products sharing one problem rolled into one line, not 214 alerts, and a click through to the exact products.

See exactly what changes before you publish

Before a rule goes live, see which products and fields it will change, before and after. No more publishing an edit and hoping.

Hand any warning to Aimée

Every warning and error an import raises comes with an “Ask Aimée to investigate” button. She reads the run events, traces the affected products back through the rules, and tells you what caused it.

And for the hours you’re not looking: monitors watch every import and every feed update, email whoever needs to know, and can hold a channel’s publish so a broken feed never reaches your ads at all.

Know before your client does

Set the rules once. It keeps itself fresh

Renable re-fetches your feeds roughly every hour and reprocesses only what changed — a new price, a product back in stock, a title you just fixed. AI copy is rewritten and images redone only where they need it, and the channels that depend on them regenerate right away. Changes go live automatically, without you opening the app.

Last run

Automatic

Fetched

12 min ago

62 products changed

price · stock · titles

Refreshed

copy rewritten · 14 images redone

6 channels regenerated

every destination you publish to

Content flows by exception

New and changed products get their copy written, images fixed and ads rendered as they arrive. Aimée runs her own quality checks, ships what she’s confident in, and flags only the exceptions for a human — so a routine price change never sits in a queue.

Configuration stays gated

Rules, mappings and templates are a different story. A change to any of them — yours or Aimée’s — lands as a draft and goes live only when a human publishes. The feed keeps itself fresh; the machinery changes only when you say so.

Goes as deep as your messiest catalog needs

Most catalogs live in more than one place: the product feed, a stock file, a supplier price list, a spreadsheet someone maintains by hand. Renable joins them into one catalog and keeps the seams visible.

Product feed

48,113 rows

Stock file

supplier SFTP

Supplier price list

Google Sheet

Renable

join on SKU

One catalog

ready to publish

Stock lookup · last import

98% match

SKU	Product	Stock	Lookup
SG-4471	Trail Runner 300	128	Matched
SG-2210	Road Racer Tee	54	Matched
SG-9002	Alpine Down Jacket	—	No match

Lookups into a second feed

Pull stock levels, supplier prices, or extra attributes from another feed by matching on a key column. Matched values flow into your products, and the match rate is reported on every run — with a drill-down to the products that didn’t match.

Mapping tables

Convert many values in one place — your category names to Google’s product taxonomy, size codes to a standard scale. Tables are seeded with the values found in your own feed, and when new values appear later, Renable flags the drift instead of letting them fall through silently.

Google Sheets and file uploads

Use a Google Sheet or an uploaded CSV, TSV or XML file as a feed source. Perfect for the price list a colleague keeps current, or the attribute file your supplier sends by email.

Split into variants, group them back — or filter down to what pays

Split into variants

Trail Runner 300

one row · sizes 38–42

Trail Runner 300 · 38SG-4471-38

Trail Runner 300 · 39SG-4471-39

Trail Runner 300 · 40SG-4471-40

Trail Runner 300 · 41SG-4471-41

Trail Runner 300 · 42SG-4471-42

Each variant keeps a stable ID across re-imports.

Group into one

Road Racer Tee · Black$35

Road Racer Tee · Navy$39

Road Racer Tee · Sand$45

+ 5 more colors

Road Racer Tee

from $358 colors

one product · master row

Aggregate fields are built from the family: the cheapest variant’s price, the colors that exist, the master’s image.

Split rows into variants

One feed row carrying five sizes becomes five products, each with a stable, deterministic ID that survives re-imports — so ad history and learning don’t reset every time your feed refreshes.

Or group them back into one

Go the other way and collapse a variant family onto a single row — the cheapest variant as “from $35”, the range as “8 colors”, one master product where you had eight. Because feed items are counted after your rules run, the collapsed family bills as one feed item too.

Or filter down to what matters

Keep only the variants worth advertising. Your rules decide what stays in the catalog, and you pay only for the feed items they keep — filtered feed items never bill.

See how pricing counts feed items

Nothing touches your live feed until you say so

Versions

Unpublished changesPublish

Draft versionSave as version

Changes made to the unpublished draft

Fixed price fallbacksPublished

Published 2 days ago · live now

Restore

Added supplier stock lookup

Published 6 days ago

Restore

Draft first, always

Every edit — yours or Aimée’s — lands on a draft. Your ad networks keep reading the last published catalog while you work.

Versioned and revertible

Every publish is a version. If a change turns out wrong, go back to an earlier version instead of reconstructing what the rules used to say.

Write the rule once. Every catalog that uses it stays in step

Six markets, or forty client accounts, and the same handful of fixes belongs in every one: brand names spelled three ways, promo words in titles, the category map that has to match. A ruleset is a rule library that lives at the organization level — build it once, apply it to every catalog that needs it, and stop maintaining the same logic in parallel.

Rulesets

Organization

Brand normalization6 catalogs

Edit

Promo words out of titles6 catalogs

Edit

Size scale → EU3 catalogs

Edit

Legacy category maparchived · not applied

Restore

Editing · Size scale → EU

Unpublished changesPublish

Preview with catalogsportgear.com · DEChange

Publishing applies to 3 catalogs

sportgear.com · DEwill reprocess

sportgear.com · FRwill reprocess

sportgear.com · NLwill reprocess

Every catalog that uses the ruleset is reprocessed when you publish — and the confirm lists them by name, so nothing updates that you didn’t expect.

One library, every catalog

Rulesets live above your catalogs, not inside one of them. A multi-market retailer applies the same brand and title rules to every market; an agency applies its house hygiene rules to every client, and still keeps per-client rules where they belong.

Preview on real products first

Try the edit against any catalog that uses the ruleset and watch it change live products before anything is published — the same before-and-after you get on a single catalog.

Forty accounts, one publish

Fix the ruleset once and the fix lands in every catalog that uses it — six markets or forty client accounts — instead of the same edit forty times, with forty chances to miss one.

Already paying for a feed tool?

See what switching involves, and how to run Renable side by side with your current setup until the output matches. Two things disappear: the upstream feed-tool subscription, and the guesswork that came with a black box.

See how switching works

One subscription fewer, one black box fewer

Connect your feed and rebuild your rules in an afternoon. Start free — 30 days on the 500-feed-item plan.

Start free Book a demo