A True Story
On June 25, 2026, the first staging sync ran end to end: 96 ready products created, zero errors, zero deletions.
Curated Sync Guide · How It Works
Curated Sync Guide · How It Works
A small connector on each website reads the library with its own key. It only takes what belongs to that site.
This guide explains the connection between Curated Sync and your eight WordPress websites, including the connector plugin. No technical background needed. Five minutes to read.
CURRENT AS OF JULY 16, 2026Each website runs one small connector plugin. That plugin is how the site and the library talk.
Every one of your eight websites runs a connector. It asks the library, "what products belong to me, and what changed since I last asked?" Then it updates the site's own product pages to match.
After the first big pull, the connector only fetches changes. A quiet night means a tiny, fast update. The site never rebuilds everything from scratch.
On June 25, 2026, the first staging sync ran end to end: 96 ready products created, zero errors, zero deletions.
One plugin per site keeps that site's catalog matched to the library, fetching only what changed.
A site's key is its library card. The card decides what it can see.
Each website has its own access key. The key maps the site to its market, its warehouse, and any narrowing rules. Raleigh's key returns Raleigh inventory. Charleston's key returns Charleston inventory.
Keys are shown exactly once when created. Rotating a key keeps the old one valid for 24 hours, so a website never goes dark in the middle of a swap.
Scoping happens at the key. A site cannot see, or accidentally publish, another market's inventory.
The library is careful about what it serves. The connector is careful about what it applies.
If a feed would wipe too many products off a site, the connector HOLDS the change instead of applying it.
A rental product without a usable price is held back and reported. It is never listed wrong and never deleted.
Every product carries a permanent id. Even if IntelliEvent renumbers a product, the site heals it in place instead of duplicating it.
Both ends check the handoff. A bad feed stops at the connector, not on your storefront.
The connection carries more than product text.
Product photos are hosted and served by Curated Sync itself, full size. The websites simply point at them. One photo, added once in IntelliEvent, powers every site. The full journey is in the photos guide.
The cart works in reverse. When a customer requests a quote, the website sends it straight back to the library's queue. It lands instantly, is recorded safely, and is never duplicated even if the site retries.
The same connection carries photos out and quote requests back. See: How your product photos get to your websites.
Honesty about the current state.
The connector has been proven end to end on an exact staging copy of a live site: products created, photos attached, cart wired, zero errors. The full production run across your real sites is built and switched off until you say go.
That order is deliberate. Nothing touches a live storefront until the staging proof is repeated and reviewed with your team.
Staging is proven. Production rollout is one deliberate, reviewed step away, never an accident.
The library refreshes at 2:00 AM. The connector picks the change up on its next pull. Overnight edits are live by morning.
No. Scope lives on the key, and the library filters before it serves. The wrong products never leave the library.
Per-site visibility rules, driven by fields your team sets in IntelliEvent. They are off by default and preview before they activate. See the Visibility screen guide.
Nothing is lost. The quote sits safely in the queue, and pushing onward retries later. The queue is the safety net.
Keyed, scoped, guarded, and proven in staging. The connection moves the catalog out and the quotes back without losing either.