Curated Events Curated Sync Guide · Your Control Panel
A Plain-Language Guide · Your Control Panel

The Visibility screen: show and hide, with a safety net

Per-site show/hide rules that preview everything before they touch a storefront.

This guide explains the Visibility screen in the Curated Sync control panel. Written for admins. Four minutes to read.

CURRENT AS OF JULY 16, 2026
What This Screen Is For

Deciding what each website should not show

Some products belong in the warehouse but not on a particular website. Rules handle that.

A visibility rule tells one site to hide certain products. Rules are off by default. Nothing hides anywhere until someone deliberately turns a rule on, and this screen exists to make that step safe.

The screen's core promise: you see exactly what a rule would do before it does anything.

The Bottom Line

Nothing hides by accident. Rules are off until switched on, and previewed before that.

What It Shows You

The dry-run preview: a rehearsal, not a leap

1

Pick a rule

Choose the site and the rule you are considering.

2

Read the rehearsal

The preview shows how many products would hide, how many would show, and the difference from today.

3

Check the safety verdict

The preview includes a safety check and flags orphaned packages: bundles whose pieces would vanish.

4

Activate deliberately

Turning the rule on is a separate step, on the Sites screen. This screen writes nothing to any storefront.

A True Story

On June 24, 2026, the activation guard blocked a test rule that would have hidden too many products at once. Proceeding required an explicit override. The default answer to "hide a lot, suddenly" is no.

The Bottom Line

Preview first, activate second, and an over-aggressive rule gets blocked with a warning.

Where the Rules Come From

Your team drives visibility from IntelliEvent fields

The agreed model: custom fields in IntelliEvent decide location visibility. The middleware reads them.

Your team marks products in IntelliEvent using custom fields: which stores an item should not appear on, and whether it should be hidden from websites entirely. The library reads those fields on every sync. The first pilot products carrying these fields arrived on July 16, 2026.

A nightly safety net backs it all: if a site's visible product count drops sharply overnight, the system raises a flag before customers notice.

The Bottom Line

IntelliEvent stays the steering wheel. The middleware reads, previews, guards, and applies.

Common Questions

What admins usually ask

If we fill the custom fields wrong, what breaks?

Nothing, immediately. Rules are off by default, the preview shows the damage before activation, and the activation guard blocks a rule that hides too much.

What is an orphaned package?

A package whose component products a rule would hide. The preview lists them so a bundle never sells with invisible pieces.

Does this screen change my websites?

No. It is read-only plus rehearsal. Activation happens on the Sites screen, deliberately, after the preview.

The Bottom Line

Visibility is powerful, so it is fenced: off by default, previewed, guarded, and watched nightly.

Keep Reading