A True Story
On July 16, 2026, your team added two pilot packages with photos in IntelliEvent. That night's 2:00 AM run picked them up before anyone asked.
Curated Sync Guide · How It Works
Curated Sync Guide · How It Works
Every night at 2:00 AM, the library refreshes itself. Carefully, in order, with guards.
This guide explains what the sync pulls from IntelliEvent, in what order, and what protects your catalog. No technical background needed. Five minutes to read.
CURRENT AS OF JULY 16, 2026The sync runs on a schedule. Your team can also run it by hand, any time.
The nightly run needs no one awake. It pulls the full catalog from IntelliEvent, compares it to yesterday, and updates only what changed. Most nights, most products are untouched.
Admins have two buttons on the dashboard. Sync Now runs a real sync immediately. Dry Run shows what a sync would do without changing anything.
On July 16, 2026, your team added two pilot packages with photos in IntelliEvent. That night's 2:00 AM run picked them up before anyone asked.
The catalog refreshes itself nightly. Changes your team makes today are on the websites tomorrow morning.
The sync always works in the same careful order. Foundations first, details after.
Offices, warehouses, categories, and market price lists. The map everything else hangs on.
Every product, compared by fingerprint. Only changed products get updated.
Which product has which photos, and which still need downloading.
Products that vanished from IntelliEvent are marked, never silently erased.Guarded
Full descriptions, dimensions, and location lists for anything that changed. Website visibility rules are re-checked here too.
New photos are fetched full size and stored in the library.
Pushing queued quotes into IntelliEvent. Built and switched off until you say go.Switched Off
Same order, every night. Foundations first, so nothing downstream builds on missing pieces.
The sync assumes something will eventually go wrong, and plans for it.
If IntelliEvent returns a suspiciously small catalog, deletions are held. A truncated feed cannot empty your websites.
Any change that would remove too many products at once is stopped and held for a person to review.
If a website's visible product count drops sharply overnight, the system raises a flag.
If a secondary feed lags, the run finishes as "partial" and names the feed. Nothing fails silently.
A run interrupted mid-sweep picks up from its last page. It also skips deletions that pass, for safety.
The library database is backed up every night. The last 14 copies are kept.
On July 6, 2026, a test deliberately fed the sync a truncated catalog. The shrink guard held every deletion. The catalog stayed intact.
Bad data gets held, not applied. Your catalog is protected by five guards and a nightly backup.
Honesty first: here is the one thing the nightly sync cannot fully do today.
Per-market rental prices are temporarily missing while IntelliEvent finishes their price endpoint. The fix is already found. Until it lands, nightly runs finish as "partial" and name the prices feed as the lagging piece.
This is the guard system working as designed. Products without a usable price are held back from rental listings and reported. They are never deleted, and nothing shows a wrong price.
Prices are the one lagging feed. The fix is known, the runs say so plainly, and no product ever shows a wrong price meanwhile.
One glance at the dashboard. The last-run line shows when it ran and how it ended. The attention list below it names anything that needs a person.
The core catalog synced fine, but one secondary feed lagged. The run record names which one. Today that is usually the prices feed.
No. A single-run gate means the schedule and the buttons share one lane. A second request waits its turn.
The Sync screen. Every run is recorded, and clicking one opens the full step-by-step record of that night. See the Sync screen guide.
The sync is scheduled, ordered, guarded, and honest about its one lagging feed. The dashboard tells you everything in one glance.