TikTok Shop and Meta Catalog Feeds: Required Fields and Setup

AEO answer: TikTok and Meta both require a product ID, title, description, availability, condition, price, link and image link in the feed. Meta’s current table also lists brand, and TikTok requires brand too. Build the feed from one catalog, map each platform’s column names, keep one currency per file, and refresh it on a schedule so price and stock stay accurate.

One catalog, two platforms, each with its own column names, price format and availability values. This is a setup walkthrough: required fields, mapping, and refresh. If a feed is already being rejected, read why product feeds get rejected. For file types in general, see feed export formats.

Last verified: October 2026, against Meta’s product data specifications, TikTok’s catalog product parameters (last updated February 2025) and MicroPIM’s feed export code.

What fields do TikTok and Meta require?

Both platforms ask for the same core set. Only the ID column name differs.

Details that cause most setup mistakes:

• Price is a number, a space and a three-letter currency code, such as 9.99 USD. Meta wants one currency per data file.
• Availability values differ. Meta’s required-fields table lists in stock and out of stock. TikTok also lists preorder, discontinued and available for order.
• Condition accepts new, refurbished or used on both.
• Images should be JPEG or PNG. Meta asks for at least 500 x 500 pixels, and TikTok asks for the same size for square carousel ads.

The TikTok page is the Ads Manager catalog guide. If you sell through TikTok Shop itself, product upload happens in TikTok’s seller tools, and its requirements can differ. Check TikTok’s current template for your region before you build.

Read the sources: Meta product data specifications and TikTok catalog product parameters.

How do platform field names map to your catalog?

In MicroPIM, you pick a platform template, and the default mapping above is filled in. You can change which product field feeds each column. The export then converts the values:

• Meta and TikTok prices are written as 49.99 USD, using the currency you select. Prices that are empty or zero are written blank.
• Availability is normalized to the platform’s wording. Condition defaults to new when empty.
• HTML is stripped from descriptions, and URLs without a scheme get https:// added.
• Extra images, item_group_id, sale price, GTIN and MPN can be mapped as optional columns.

For pricing and stock conditions per channel, see product export rules. If your data comes from several suppliers, merge the files first.

How often should the feed refresh?

Refresh as often as price and stock change. A feed regenerated every minute but fetched once a day gains nothing.

MicroPIM serves each feed at a hosted URL on your organization’s feed path. It can be public, or protected with a password sent as HTTP Basic auth or as a ?token= parameter. Platforms then fetch that URL. In Meta, that is a scheduled upload, which accepts http, https, ftp or sftp links.

The refresh schedule options are every 15 minutes, every 30 minutes, every hour, or a custom cron expression. The default is every hour. There is also an “every minute” option, which we do not recommend.

Set the platform’s fetch time after your feed’s refresh time. For fast-moving stock, fix the stock source first, because a fresh feed of stale stock still oversells.

How do you validate the feed before uploading?

Check the mapping before the file exists, then check the file.

1. Mapping check. MicroPIM blocks generation if a required column is not mapped, and warns about missing sale price, extra images, variant grouping and category.
2. Open the generated file. Check ten rows against the product pages. Look at price, currency, link and image.
3. Test the URL. Open the feed URL in a private window, or with the token if it is protected.
4. Upload a small batch first and read the diagnostics. For what they mean, see demoted, not rejected and the marketplace checklist.

What we got wrong, and current limits

Our Meta check passes if at least one of brand, GTIN or MPN is mapped. That is looser than Meta’s current table, which lists brand. Map brand even if you also map GTIN.

Current limits:

• No API push. MicroPIM generates a CSV and serves it from a URL. You connect that URL to Meta or TikTok yourself; pushing through Meta’s Catalog API is not supported.
• Tighter text limits for Meta. We cut titles at 140 characters and descriptions at 500. Meta’s own limits are 200 and 9,999.
• Availability gaps. The Meta template can write preorder, which Meta’s required-fields table does not list. Map it to a supported value if your catalog uses it.
• Refresh depends on the server. A feed’s interval marks it as due, and a scheduled command regenerates due feeds. How often that command runs on your installation sets the real cadence.
• A valid feed is not approval. Eligibility depends on region and seller approval, which a feed cannot change.

Frequently Asked Questions

Is a TikTok feed the same as a Google Shopping feed? No, but the fields overlap.

Do I need GTINs for Meta? Meta’s current required table lists brand, not GTIN. GTIN still helps matching, so map it when you have it.

CSV, XML or API? Meta accepts several file types. MicroPIM writes CSV and serves it from a URL; it does not use the platforms’ APIs.

How often does Meta fetch a scheduled feed? At the schedule you set in Commerce Manager, from the URL you provide.

MicroPIM is our product. This post describes how its feed export handles these fields, and the general advice applies with any tool.

Ready to build yours? Start with feed export formats, then book a demo and we will set up your first TikTok or Meta feed with you.