Product and Property Feed Repair for Meta and TikTok Catalogs

Most catalogs handed to us pass validation and still cannot spend. Commerce Manager shows the green check, the scheduled fetch runs nightly, and item-level diagnostics report that somewhere between 60 and 80 percent of the inventory is ineligible to serve: availability says in stock while the landing page returns a 404, the price currency disagrees with the ad account currency, or no content_id in the catalog has ever matched an event fired by the pixel. Dynamic ads then serve from whatever fraction survives, which is why delivery hits a ceiling nobody on the account can explain. How the work runs: We begin with the diagnostics endpoint and the pixel event payloads side by side, because the failure is almost always a mismatch between two systems that each look correct alone. Typical first-week findings: retailer_id generated from the VTEX SKU while the pixel fires the parent product ID; Loja Integrada exporting price as a string with a comma decimal; a supplementary feed overwriting the primary on custom_label_0; availability refreshed every 24 hours on a store that sells out in four. We fix the source of truth where we can and add feed rules where we cannot, then hold both against a reconciliation we run daily for the first 30 days. Manufacturing catalogs: Industrial inventory breaks the catalog spec in a specific way: no consumer price, no GTIN, configure-to-order variants, and a distributor who owns the transaction. Zero price is rejected, list price is misleading, and a category page as the landing URL kills the item match. We build these as quote-intent catalogs, with price carrying a published list figure or the item leaving the catalog entirely, custom labels carrying the specification fields your sales team actually filters on such as material, tolerance class and lead-time band, and a landing page per item that exists. Where the SKU set is too shallow to justify any of it, we say so and you spend the money on creative instead. Real estate feeds: Home listing catalogs are a separate vertical inside Meta, not a product catalog with different fields, and exports from Vista, Jetimob and Ingaia rarely arrive shaped for it. We handle listing status decay, the neighborhood and address fields that decide whether the ad renders a map, image ordering, and the removal discipline that keeps sold units from serving. A stale property feed does more damage than no feed at all: the lead arrives, the unit is gone, and your broker stops trusting the channel. Not included: We do not build or rewrite your ecommerce platform, and we do not author product copy or shoot product imagery. Google Merchant Center is a different rulebook and a different practice, and we will tell you who to call. We do not run media against a catalog we have only repaired unless you have separately engaged us to. Who this is not for: A store under roughly 200 live items with flat inventory does not need this, and a static campaign will outperform anything dynamic at that depth. If your catalog is rejected on a Commerce policy ground rather than a format one, that is an appeal question before it is a feed question, and the wrong engagement to book here. What you receive: The repaired feed specification, the field mapping, the reconciliation script, and a written account of every rejection reason we closed and how. All of it lives in your Business Portfolio and your repository. We are a partner on your assets, and you can remove us in one click.