People search “fix my Google Shopping attributes” when titles look fine and Merchant still sulks about colour, size, gender, or material. The wrong answer is another spreadsheet. The right answer is a repeatable scan and push loop with cost ceilings.
Why attributes are a media problem
Shopping filters, free listings quality, and even on-site findability lean on structured facts. “Black / M” as a free-text option string is not the same as typed colour and size. Missing fields look like “Google is broken”. Usually the catalogue is incomplete.
How Ralph approaches it
- Scan engine - suggestions from product content/images into category-relevant fields.
- Tier 0 free - deterministic wins (for example size axes from options) without model spend.
- Tier 1 paid - model-assisted fill with nightly ceilings so a 10k catalogue does not nuke cost in one night.
- Bulk fix runs - durable run records, resume without re-billing finished products, one active run per store, budget checks between products.
- Push - GraphQL batch push to Shopify; pending retry when platforms flake.
If the UI implies unlimited free magic attribute fill for every draft SKU, that UI is lying. Ours should not.
What we do not claim
- We do not silently rewrite your primary Merchant feed file as the default path.
- We do not invent GTINs or policy-safe claims from nothing.
- We do not bill you for scanning dead draft/archived catalogue rows when status filtering is on.
Related systems: GMC supplemental feeds and readiness, free optimisation checklist.
Questions people actually ask
Can Ralph invent perfect attributes for every SKU overnight?
No. Tier 0 is free/deterministic. Paid model tiers have nightly and bulk-run ceilings so a large catalogue amortises. Draft/archived products should not burn budget when status is known.
Does bulk fix write straight to Shopify with no limit?
No. Bulk fix is flag-gated, one active run per store, with hard per-run and per-day pound ceilings. Resume is designed not to re-bill finished products.
Is this the same as fixing the primary Google feed file?
Not exactly. Attributes land on Shopify (and related enrichment). Shopping readiness improves from catalogue truth; GMC supplemental work is a separate surface.
Will this stop all Merchant disapprovals?
No. It targets attribute completeness and related readiness. Policy, GTIN, and account issues still need their own fixes.
If the catalogue is the problem: Ralph maps every Shopify variant to its Meta and Google catalogue item, scans for missing attributes, and drafts the fixes and the feed changes for approval. See Ralph · How Ralph reads the catalogue · Docs