Prices or Stock Look Wrong

When prices or availability in your feed don't match your website, it's almost always one of four things: the feed hasn't re-imported yet, the value maps from the wrong column, a number-format mismatch is misreading it, or your live stock lives in a separate feed you haven't joined. Work through them in order — or ask Aimée to trace the product.

The feed hasn't refreshed yet#

The most common reason a price or stock value is out of date is simply that Renable hasn't re-imported since it changed — or you fixed the mapping but haven't published. Renable re-imports your product feed on a regular schedule and reprocesses whatever changed, but a value that just changed on your website won't reach your ads until that next import runs and the affected channels regenerate.

Two things to check:

• The health strip at the top of every catalog page shows "Last import {time ago}". If the last import is much older than you'd expect, run one now with "Import now", or wait for the next scheduled one. See Keep your feed fresh.
• If you edited the catalog to fix the value — remapped a column, changed a setting — remember that nothing takes effect until you Publish, and "Import now" uses your last published configuration, not your draft. Publish first, then import, so your fix is actually applied.

There's also a lag beyond Renable: the ad network re-fetches your finished feed on its own schedule, so even after a correct import, your live ads update only once the network pulls the new feed.

The value maps from the wrong column#

If the price or availability is consistently wrong — not stale, just incorrect — the field is probably drawing from the wrong feed column. A feed can carry several price-like columns (a sale price, a compare-at price, a cost) or more than one stock field, and the Price or Availability field may be mapped to the wrong one.

1. Open the catalog and go to the Mapping tab.
2. Find the Price field (in the Pricing group) or the Availability field (in the Availability group) and check which column feeds it. The live sample on the row shows the value a real product gets.
3. If it's the wrong column, drag the correct one onto the field. To fall back to a second column when the first is empty, stack a fallback in the field's value editor.
4. Publish the catalog so the change goes live.

To see exactly where a single product's value came from, use Trace a product — it walks one product to its final catalog output and labels which column or rule produced each field. Mapping is covered in Mapping your feed fields; tracing in Feed runs, warnings, and tracing a value.

A price is misread because of number format#

A price can map from the right column and still come out wrong when the number's separators are read the wrong way round. Renable reads most values by their own shape, so this is rarer than it used to be: 1.299,50 and 1,299.50 both read as one thousand two hundred ninety-nine and a half, 4490.00 and 12,5 mean what they look like, and 1.234.567 is a million-odd — whatever the catalog is set to. The one shape Renable cannot read on its own is a single separator followed by exactly three digits: 4.490 is four thousand four hundred ninety in Sweden and four and a bit in the US. That case is decided by the column's own Decimal separator, set on its type badge on the Mapping tab. Until you set one, Renable doesn't guess: such a value is not read as a price at all, and the import warns you about the column.

1. On the Mapping tab, check the price column's type badge. If it reads "Inferred — click to declare" and the guess is wrong, click it and declare the correct type so Renable treats the column as a number rather than plain text.
2. Use Trace a product on an affected product to see the raw value the feed sends. If it has the 4.490 shape, click the price column's type badge, choose Number, and set its Decimal separator to match how your feed writes prices: Comma when 4.490 means four thousand four hundred ninety, Dot when it means four and a bit. A warning dot on the badge marks a column with such values, and when the column's other values tell the answer the choice opens on it, marked "Suggested from this column's values". Press Apply to set it.
3. Publish and re-import to see the corrected values.

Prices that import correctly but look wrong in your ads — too many decimals, or the wrong separators — are a different problem: how a number is written in an ad is decided by a Format number step on its placeholder. The step sets the decimals, and the separators too unless it leaves them on their first option, where it takes them from the catalog's language (its Locale, on the Settings tab). To write a price another way, pick the separators in the step; the catalog's language never changes how your feed is read. See Languages and localization.

The same idea applies to any Date column in your feed: it takes an optional parse pattern, and left blank it reads dates in your catalog's locale automatically. If a date is being read in the wrong order, declare its parse pattern on the Mapping tab. See Mapping your feed fields for column types.

Your stock lives in a separate feed you haven't joined#

Sometimes the availability in your product feed is genuinely out of date because the real, up-to-the-minute stock lives somewhere else — a warehouse or supplier system with its own feed. If that feed isn't joined to your catalog, Renable only knows the availability your main feed carries, which may lag reality or be missing entirely.

The fix is a lookup: add the stock feed as an Auxiliary feed on the Data sources tab, then match your products to it on a shared key — a barcode works best — and pull its stock or availability column across. Renable fetches auxiliary feeds at import time, so the join always runs against the latest data from both feeds. See Join a stock or supplier feed for the job, or Joining another feed with a lookup for the full mechanics.

The fastest check: ask Aimée to trace the product#

Rather than checking each cause by hand, ask Aimée why a specific product's price or stock is wrong. She can replay that one product's import and read its history end to end — which column or setting produced the value, and how each field resolved — and tell you exactly where the number came from. She can also fix it for you: remap the field, declare a column type, adjust the catalog's locale, or set up a stock feed join — then publish once you approve.

FAQ#

My website shows the new price but my ads still show the old one — why?

Two schedules sit between your website and your ad: Renable's import, which pulls your feed on its own schedule, and the ad network, which re-fetches your finished feed on its schedule. A change appears in your ads only after both have run, so a short lag is normal. If you edited the catalog to fix it, publish first — draft edits don't apply until you do. See Keep your feed fresh.

Only some products have the wrong price — the rest are fine. Why?

A problem that hits only a slice of products usually points to those products being different in the feed — a subset written in another number format, or missing the primary column so they fall through to a fallback. Open the Mapping tab and read the Fill column to confirm a slice of products is falling through to a fallback, then use Trace a product on one of the affected products to see exactly where its value came from.

My feed says a product is in stock but it's sold out on my site — why?

Either the Availability field is mapping from the wrong column, your live stock lives in a separate feed that isn't joined, or the feed simply hasn't re-imported since it sold out. Work through the causes above in order: a wrong availability value keeps the product delivering because the network still treats it as available. A value that's missing entirely is a different problem — availability is a required field, so the network may leave the product out rather than run it. See Product availability and stock.