For US-facing Shopify apparel and accessories stores with 300–2,500 variants. By Marco Nicola Messina · sources checked October 17, 2026.
First, identify what is actually disapproved
Record the issue wording exactly as Merchant Center displays it, its affected destination and country, and whether it applies to individual products or the account. Save a few affected item IDs and the time of your observation. A store-wide count alone does not explain the cause.
Shopify distinguishes product-data problems from policy and account issues in its disapprovals and warnings guidance. Check the current notice before deciding who should investigate. FeedSteady handles scoped catalog diagnosis; account reinstatement is outside this offer.
Choose the investigation that matches the evidence
| Observed issue | First comparison | Next step |
|---|---|---|
| Price mismatch | Same item, currency, sale period and selected variant | Trace the price discrepancy |
| Availability mismatch | Final Attributes, selected option and purchase availability | Compare stock evidence |
| Missing or invalid identifier | Exact variant and the identifier assigned by its manufacturer | Confirm the product facts and source mapping before editing |
| Variant attributes missing | Source size/color values and the affected exported rows | Inspect titles and variant attributes together |
| Account warning or suspension | Full account notice and stated policy | Use the account-specific guidance; a catalog edit alone may not resolve it |
Trace one affected item back to its source
Choose an item you can reproduce and one similar item without the same issue. Compare their source rows, Merchant Center values and exact destination URLs. The second item is a useful comparison, although it does not prove that the rest of the catalog is correct.
Identify what supplies each disputed field: Shopify product data, the Google channel, another feed app, a transformation rule or an additional data source. Write down the field owner before changing it. A manual downstream correction can be overwritten when its source syncs again.
For identifiers, check Google’s GTIN requirements. Do not fabricate a barcode or borrow one from a different size. Whether an identifier is required depends on the product; missing data and a product without an assigned GTIN are different situations.
A synthetic example: 240 rows, one mapping to investigate
This example is fictional, not a customer result. Imagine 240 apparel variants with an empty exported size field. A sampled medium variant has a size in Shopify, but its feed rule reads a different option. That observation supports investigating the mapping. It does not prove all 240 rows share the cause.
Group the affected rows by product template and option structure. Sample each group, record exceptions, then propose a small repair with a rollback. After approval, verify regenerated rows and the values received by Merchant Center. Keep any unresolved status separate from your own technical checks.
What to prepare before asking for help
- The exact issue label and affected country.
- Three to five affected item IDs and their product URLs.
- Your feed integration and approximate variant count.
- Recent changes to pricing, stock, product options, theme or feed rules.
Start with the store URL and a brief issue description in our request form. Do not send passwords, customer-order records or account tokens. We agree access separately, after confirming that the problem fits our scope.
Get a finding you can act on
For $299, we review up to 2,500 variant rows and manually check 20 product URLs. The deliverable is a prioritized evidence report, the likely owner of each correction, and a proposed repair scope. It is a diagnostic, not 2,500 individually inspected pages or an approval guarantee.
A repair pilot, when appropriate, costs $750 total including the diagnostic, for up to three agreed issue classes and six repair hours. Timing, taxes and access are confirmed before payment.