Pinterest Catalog Errors: Diagnostics, codes & feed fixes

Pinterest provides numbered catalog error codes with documented meanings and fixes. Troubleshooting also needs lifecycle checks - ingestion cadence, manual-upload expiry, and domain claims can affect serving without appearing as an item-level data error.

This guide covers both: every code you'll actually meet, and the non-error failures around them. It's the Pinterest spoke of the cross-platform product feed errors pillar; the field-by-field spec lives in Pinterest product feed.

Where Pinterest reports problems

Ads Manager → Catalogs → your data source → Diagnostics shows ingestion status and item-level issues, keyed to numbered error codes. Two habits make it useful:

1. Check ingestion status first - a failed ingestion means item-level counts are stale, and you're debugging yesterday's feed

2. Sort by code, fix by class - one cause (say, a malformed export) usually produces one code across hundreds of items; you're fixing causes, not rows

Whole-feed codes: nothing got in

• Error 100 - the data source couldn't be downloaded. The URL moved, requires auth Pinterest doesn't support, or your host is blocking the fetch. Remember Pinterest's constraints: no password-protected files, no Dropbox links.

• Error 152 - too few lines. Your export produced a near-empty file; the bug is in generation, not ingestion.

• Error 143 - malformed XML. Validate the file; a single unescaped character can kill an RSS feed.

• Error 129 - duplicate column headers. Usually a hand-edited CSV or a template merge gone wrong.

These block everything downstream. If you see one, ignore every item-level count until it's cleared.

Required-field and format codes

• Errors 106 / 107 / 111 / 112 - missing title, description, image_link, or availability. Pinterest requires seven fields; missing ones can fail ingestion rather than just skipping the row, which is why validation before upload matters more here than on platforms that degrade gracefully.

• Error 113 - price formatting. Number plus ISO currency code, no symbols, no comma decimals.

• Error 179 - invalid GTIN. Fix or remove; an empty identifier field is fine on Pinterest (brand and GTIN are optional), a wrong one is not.

Item-level codes: the Pinterest-specific ones

• Error 123 - duplicate items. The same id appears on multiple rows; check variant flattening and your item_group_id structure.

• Error 139 - product link doesn't match your claimed domain. Pinterest's signature rule: every link must live on the website you verified. Common triggers: links through redirect domains, tracking subdomains you never claimed, or a rebrand that moved the store. Claim the domain or fix the links - there's no exemption.

• Errors 1001 / 1007 - image not found or invalid. URLs must resolve directly to the file; check CDN rules and remember additional images only need 75 x 75, but your main images should be 2:3 at 1000 x 1500.

The failures that aren't errors

This is the section that saves Pinterest advertisers the most confusion:

1. The daily ingestion lag - hosted feeds ingest once every 24 hours, no on-demand refresh. A price change at 9am may not reflect until tomorrow. That's not a bug; time your promotions around it.

2. Manual upload decay - manually uploaded feeds need re-uploading every 7 days for organic distribution and stop serving ads entirely after 90 days. "Our products vanished from Pinterest" is very often a forgotten manual upload hitting its cliff. Host the feed at a URL.

3. Merchant guideline currency - Pinterest's merchant guidelines expect price and stock current within 7 days, and require visible shipping and return policies. Drift here risks distribution limits rather than error codes.

4. Error 4042 - the one policy code: a merchant-guidelines violation. Fix the underlying store issue (return policy, availability honesty, prohibited content), then use the one-click appeal.

   
   

The health metric worth adopting

Pinterest gives you a built-in feed-quality KPI: the Verified Merchant Program requires at least 75% of catalog products ingesting successfully, alongside steady tag events. Even if the blue badge isn't your goal, that 75% line is a sensible internal floor - a catalog below it has a systemic problem, not item-level noise.

The Pinterest prevention checklist

1. Host the feed at a URL - never rely on manual uploads past a first test

2. Validate the seven required fields and price format before upload

3. Keep every product link on the claimed domain; claim any subdomains links pass through

4. Serve images at 1000 x 1500 (2:3) from a host that resolves directly

5. Unique id per row; variants grouped under item_group_id

6. Time price changes around the 24-hour ingestion cycle - especially sale starts

7. Keep shipping and return policy pages visible and current

8. Watch the ingestion-success rate against the 75% VMP floor

9. Review diagnostics weekly, sorted by code

Moving Pinterest error prevention upstream

Pinterest's numbered errors make a useful ruleset for preflight. Flow's catalog engine can apply the required mappings and surface catalog-readiness issues before ingestion, while its Pinterest workflow adds reusable templates and creative review.

That can prevent many file and item-level problems, but it cannot claim a domain or resolve policy state on your behalf. Validate the exported dimensions and fields, then use Pinterest diagnostics for the final codes, ingestion rate, domain checks, and promotion timing.

FAQ

Final thoughts

Pinterest catalog troubleshooting combines mechanical code-fixing with lifecycle hygiene for domains, policies, and timing. Run the checklist, allow the documented processing window, and monitor ingestion health above Pinterest's 75% eligibility threshold.