// E-commerce

Merchant Feed Rejection Triage

Reconcile product-feed, Merchant Center diagnostic, and landing-page snapshot exports to prioritize the conflicts most likely to block product eligibility.

Get it on Agensi Find another skill $19 one-time

What problem does Merchant Feed Rejection Triage solve?

Merchant Center can stop showing products because the feed, product page, structured data, variants, or identifiers disagree, while the storefront itself still appears healthy.

Use it to

Prioritize product disapprovals before requesting Merchant Center review
Reconcile feed values with captured product-page observations after a migration
Find stale diagnostic rows and repeated catalog-wide root causes
Create a client-ready evidence ledger without granting account access

What it returns

Priority-ranked item findings CSV
Per-item BLOCK, REVIEW, or CLEAR summary
JSON readiness recommendation and severity totals
Root-cause review memo tied to the supplied exports

A representative input and result

fixture-backed sample

input Feed: sku-900 at 199.00 USD, preorder, invalid GTIN. Diagnostics: price_mismatch, disapproved, lost-click potential 82. Snapshot: HTTP 404, 209.00 USD, out_of_stock, old URL and different canonical.

result Recommendation: REJECT_REVIEW_REQUEST Critical: landing page unreachable, price mismatch, availability mismatch. High: invalid GTIN, URL and canonical mismatch, Merchant Center rejection. Priority: fix the source-of-truth conflict before requesting review.

Access and approval boundaries

Read access to user-supplied CSV product, diagnostics, and snapshot exports.
Write access only to the selected local triage output directory.
No Google account, Merchant Center, browser, storefront, API, credential, or network access is required.

Known limitations

The helper supports documented CSV schemas and does not directly ingest every XML, API, supplemental-feed, or platform-specific export format.
A missing snapshot row is unknown, not proof that a landing page is unreachable.
A clear local result does not prove live crawl success, policy eligibility, country-specific approval, impressions, traffic, or sales.

// choose with context

Is Merchant Feed Rejection Triage the right skill?

Best fit

Merchant Center can stop showing products because the feed, product page, structured data, variants, or identifiers disagree, while the storefront itself still appears healthy.

It returns

Priority-ranked item findings CSV. Per-item BLOCK, REVIEW, or CLEAR summary.

Do not use it as

It does not sign in to Merchant Center, crawl the storefront, edit products, submit a feed, or request review.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: merchant-feed-input/**, merchant-triage-output/**, *.csv, *.json.
Compatibility: Google Merchant Center product-feed CSV exports or normalized feed tables. Optional Merchant Center item diagnostics and landing-page snapshot CSVs using the documented schemas. Python 3 for the included deterministic local triage helper.
Version: 1.0.0
Licence: Review the package licence and seller terms at the linked destination.

What happens next

The Agensi listing opens at the current offer. Complete purchase there, inspect SKILL.md and its bundled files, then add the complete folder to your agent.

Questions

Does it connect to Google Merchant Center?

No. It works from local CSV exports and requires no Google login, API token, browser, or network access.

Will it fix or resubmit my product feed?

No. It reports conflicts and prioritizes review. You decide which source is correct and make changes in the responsible system.

Does a clear result guarantee product approval?

No. Merchant Center can apply live-crawl, account, country, shipping, tax, policy, and eligibility checks outside the supplied evidence.

Which mismatches does it detect?

It covers price, currency, availability, landing URL, canonical, HTTP status, required fields, common identifier logic, and supplied diagnostics.

Can it prioritize the largest issue clusters?

Yes. It groups repeated diagnostic codes and combines severity with supplied lost-click potential as a triage score, not a revenue forecast.

Does it crawl every product page?

No. Supply an optional local snapshot from your authorized crawler or platform export when feed-to-page reconciliation is needed.