A required field is one a destination won't accept a product without: the product is rejected or disapproved and never delivers. A recommended field is optional, so the product is accepted without it, but the destination documents it as worth supplying. Which fields are required depends on the destination, the product's category and the market.
Required vs. Recommended Feed Fields
A required field is one a destination won't accept a product without, and a recommended field is optional. Renable checks seven required fields for every product, and destinations can require more.
Updated November 6, 2026
The seven fields Renable checks#
Renable marks seven fields as required for every product, because Meta, Google and TikTok all require them. They carry an asterisk on the catalog's Mapping tab:
- ID: a unique identifier for the product
- Title: the product name shoppers see
- Description: the product copy
- Link: the link to the product's page
- Image link: the primary product image
- Price: the current price
- Availability: whether the product is in stock
A field with no source counts toward the tab's warning (2 required missing). A field that's mapped but empty for some products shows a note on its row (120 empty). See Mapping your feed to catalog fields.
What Meta, Google and TikTok require#
| Destination | Required |
|---|---|
| The seven. Also an MPN for products without a manufacturer-assigned GTIN, a brand for new products with a clearly associated brand, condition for used or refurbished products, and color, size, age group and gender for apparel targeted to Brazil, France, Germany, Japan, the UK and the US, and for all apparel in its free listings. | |
| Meta | The seven, plus condition, brand and a product category (google_product_category or fb_product_category). Also color, size, age group, gender and item group ID on the products they apply to, such as variants. GTIN and MPN are optional. |
| TikTok | The seven, plus condition and brand, calling the ID sku_id. |
TikTok's list of required fields doesn't include the apparel attributes.
Fill the seven first, then the fields your destinations and categories need. A field that's recommended on one destination may be required on another.
Recommended fields#
Common recommended fields are GTIN, MPN, extra images, a Product type and custom labels. Google recommends a GTIN for every product that has one, and says a product submitted without it may have limited visibility. To add identifiers, see Add missing GTINs, brands, and identifiers.
Destinations with their own rules#
A few destinations, such as the price comparisons, are more relaxed about some of the seven, and a short required list says little about what's worth filling.
- Prisjakt requires six fields: product ID, title, link, price, availability and condition. Renable
calls out a product missing one and still sends it, and what happens next is Prisjakt's decision. Brand, description and the
product image are optional, so Renable marks them recommended there.
Prisjakt matches your offer to the product page other shops are listed on, and documents the barcode (
gtin) as the way to speed that up, withmpnsecond, so thegtinfill rate is the one to watch. - PriceRunner publishes no reject rule. When data is missing it matches the offer by hand and charges extra per click for the work ($0.07 on its UK price list; Sweden and Denmark publish their own figure in local currency). Renable marks five fields required, because there's no listing without them: product ID, name, price, link and stock status. Everything else, the barcode included, is recommended.
- Criteo asks for a barcode or a manufacturer part number on every product. Renable can't mark "one of these two", so both show as recommended: check the fill rate across the pair. Item group ID is also recommended, though Criteo's specification marks it required, because it only matters when your catalog has variants.
Where Renable shows this#
- The catalog's Mapping tab marks the seven with an asterisk and warns when one is unmapped or empty.
- A channel's Fields tab goes further once the channel knows its destinations and what it's for (its Used for setting). Required fields say who asks for them (Required by Meta and Google) and recommended fields carry a muted rec marker. See Working with channels.
What you set the channel up for changes that list:
- Add-ons ask for more. Extra product images or Meta's Multi-image ads ask for a second image per product, Video ads or Product video for a video column, and AI discovery (Google only) for the fields Google's AI shopping surfaces read. A field that's only asked for because of an add-on says so (Recommended by Google (AI discovery)). Not every destination offers every add-on, and each destination's article lists its own. See AI discovery on Google.
- Supplementary feeds ask for less. With Used as set to Supplementary feed, only the product ID stays required. Any other value you send is still checked, and add-ons keep their own requirements.
- Meta's Adaptive designs asks for nothing new. Once it's on, the Image link and Additional image link rows stop being asked for, because the design groups replace them. See Adaptive designs.
Fill or map every field Renable calls out, then Publish. To check the feed side before looking at a campaign, see Check your ads are eligible to deliver.
Or ask Aimée#
Try "which required fields is this product missing?". She can trace it, tell you which fields are empty and where each value came from, then set up the mapping or a rule to fill them and publish once you approve.
FAQ#
Renable says all my required fields are filled, so why did the destination still reject a product?
A destination can require more for that product's category, or disapprove it on a policy rather than a missing field. See Fix products disapproved by Google.