Catalog Drift
Settings → Catalog Drift runs scheduled checks that compare each billing integration's local catalog against the upstream provider (for example Zuora) and trigger an automatic re-sync when they diverge. This keeps your PeakCommerce catalog aligned with the source of truth without anyone having to remember to re-sync after an upstream change.
Why it matters
If a product, rate plan, or charge is added, edited, or removed in Zuora, your local catalog drifts out of sync until the next sync. Buyers could see a plan that no longer exists upstream, or miss one that was just added. The drift watcher closes that gap automatically.
What it shows / the controls
Drift Watcher Schedule — pick the hour of day (server time) the daily check runs for this tenant (default 03:00), and toggle auto re-sync on drift. With auto re-sync on, a detected divergence triggers a re-sync immediately; with it off, drift is detected and reported but the catalog is left as-is for you to re-sync manually.
Recent drift events — each check's result, filterable by integration: the detected differences in product / rate-plan / charge counts and IDs (what's missing locally versus extra locally) and the re-sync outcome (success, partial failure, or failed).
How to read a drift event
Drift is flagged when upstream and local counts differ, or when the sets of product/rate-plan/charge IDs don't match. "Missing locally" means upstream has items your catalog doesn't; "extra locally" means your catalog still lists items upstream dropped. The re-sync summary shows how many products, plans, and charges were synced or deactivated to close the gap.
Gotchas
The check skips a run if the upstream fetch comes back incomplete (e.g. partial provider drops), to avoid triggering a wrong re-sync against a bad snapshot — so an occasional "no event" is expected, not a failure.
Only active Zuora integrations are watched.
The schedule is per-tenant and runs once per day at the chosen hour; changing the hour takes effect on the next eligible tick.
Related
Catalog Sync History — the full run log, including drift-triggered re-syncs.
Last updated
Was this helpful?