01
Versioned builds
Every feed build is a version. When a channel suddenly tanks, diff the feed that ran yesterday against the one running now — and roll back to the version that worked.
// feed syndication
Fix Merchant Center disapprovals automatically.
When Google Merchant Center disapproves a product it stops serving — usually without anyone noticing for days. Magistry audits your Shopify feed continuously: it diagnoses the offending attribute, patches the item, resubmits it, and verifies the fix landed. The same build syndicates to Google, Meta, TikTok, Pinterest, and Bing — versioned, so you can diff yesterday's feed against today's and roll back.
5 channels from one build Versioned & diffable Disapproval auto-fix
Feedv218 · 684 items
0 disapprovals- Google684 / 684synced 12m ago
- Meta684 / 684synced 12m ago
- TikTok671 / 68413 excluded by rule
- Pinterest684 / 684synced 41m ago
- Bing684 / 684synced 1h ago
feed rule
IF margin_tier ≠ A AND channel = tiktok
THEN exclude_item
THEN exclude_item
title a/b arm · google
A · keyword-ledCTR +11%
B · benefit-ledbaseline
// what it does
Feeds as infrastructure, not exports.
A CSV upload is a snapshot that starts rotting the moment you export it. Magistry treats the feed as living infrastructure: built from catalog state, shaped by rules, measured by experiments.
02
Rules per channel
Exclude thin-margin SKUs from expensive channels, rewrite titles per platform, force GPC categories where the auto-mapper is unsure. Rules are declarative and logged.
03
A/B arms on the feed itself
Run keyword-led vs benefit-led titles as feed experiment arms and let click-through decide. The winning arm graduates into the main feed with the evidence attached.
04
GPC category mapping
Google Product Category mapping runs automatically with confidence scores — the long tail of miscategorized products stops silently suppressing your impressions.
05
Merchant Center auto-fix
Health audits run from P0 to P6 severity. Disapprovals trigger a fix loop: diagnose the offending attribute, patch the item, resubmit, verify — before reach quietly bleeds.
06
Provider migration
Moving off Simprosys or another feed app? The cutover runs offer-id parity analysis first, so Google keeps your PMax learning history — gated, resumable, and operator-confirmed at every phase.
// merchant center
Disapprovals fixed while you sleep.
Every Merchant Center disapproval throttles impressions until someone notices — and nobody notices on a Saturday. The audit loop diagnoses, patches, resubmits, and verifies, with every fix landing as a logged decision row.
// 01 · detect
Health audit sweeps run on a schedule, grading issues P0 (account-level threat) to P6 (cosmetic). New disapprovals surface as alerts within the cycle, not at month-end.
// 02 · diagnose
The offending attribute is identified — missing GTIN, image policy, price mismatch, taxonomy conflict — and matched against the fix it needs.
// 03 · fix & resubmit
The item is patched in the feed build, resubmitted to Merchant Center, and re-verified. Fixes that need operator input queue with the diagnosis attached.
gmc_audit · item 9241
issue : image_link disapproved
severity : P2 (item suppressed)
detected_at : 02:14 UTC
diagnosis : promotional overlay on image
fix : swap to variant image #3
(clean, passes policy check)
resubmitted : 02:16 UTC
verified : APPROVED · 03:41 UTC
logged_as : decision_log row · reversible// get started
Put your feeds on autopilot.
Connect Shopify and Merchant Center, and Magistry takes the feed from there — five channels, one source of truth.
Free plan · No credit card · Starts in dry-run