Merchant Center Disapproval Triage and Feed Rebuild

Where we start: Most accounts we open carry six to twelve distinct disapproval reasons, and two or three of them account for the large majority of affected SKUs. We rank that list by revenue at risk rather than by item count, because eleven hundred disapproved clearance items matter less than forty core SKUs failing on a price mismatch. The first thing you receive is that ranked list with a named cause behind each line, traced back to the system that produced the value. Why the errors are there: Feed syntax is almost never the reason. What we find instead, roughly in this order: prices submitted without IVA while the landing page shows the tax-inclusive figure, which Google reads as a mismatch because displayed prices in Mexico must include tax; availability written from a nightly ERP export while the product page renders stock from a live call, so the crawler and the feed disagree by design; Googlebot or Google-InspectionTool blocked by a Cloudflare bot-fight rule or a WAF managed ruleset, which turns thousands of items page-not-crawlable overnight; GTINs keyed by hand that fail the check digit, or that carry a 750 prefix belonging to a company which is not the manufacturer; and identifier_exists set to false on products that plainly have manufacturer identifiers, usually because somebody set it once to clear a warning. Account-level suspensions are separate work. Misrepresentation strikes are resolved by changing what the site does, returns policy, contact information, checkout disclosure, price parity between feed and cart, before anything goes back for review. We write the reinstatement request only once the site can survive it. We fix values where they are created: The correction goes into the PIM, the ERP export or the product page template. We change the feed only when the source genuinely cannot carry the field. Supplemental feeds are for merchandising data, custom labels, promotion IDs, exclusion flags, and never for overwriting a wrong price or a wrong stock number. That kind of override goes stale in silence and the same failure returns a quarter later wearing a different error code. Mexico specifics: Shipping configured per estado rather than as one national rate, so the destination surcharge stops contradicting checkout. Free-shipping thresholds expressed in shipping settings instead of in a banner the crawler cannot read. Marketplace-fulfilled items separated from own-warehouse items, because their delivery promises are not the same and one bad promise drags the whole account's shipping trust down with it. What you get: A rebuilt primary feed, the Merchant API integration in place of the Content API for Shopping, automatic item updates configured and tested against a known price change, item-issue alerting with thresholds that fire on movement rather than on every warning, and a runbook naming the owner of each recurring failure mode. Named, because unowned failure modes come back. Not included: Campaign structure, bidding or budget work. Landing page development, we specify and your team ships. Product photography or background removal for image quality rejections. Translation of product copy. Marketplace listings, which are a different engagement. Who this is not for: Retailers whose catalog lives in spreadsheets exported by hand each week. The fix there is a catalog system and we will say so rather than take the work. Anyone who wants the disapproval count moved without changing the source data, which is a supplemental-feed exercise other shops are happy to sell. Accounts under an active policy suspension where the underlying site issue is not going to be fixed.