Keeping your catalog clean is hard when it’s built from multiple upstream sources—products can disappear upstream but still linger in Constructor. Whitelist Action gives you a fast way to clean up stale catalog data by telling Constructor what to keep.

With this update:

• Upload a keep-list of item, variation, and/or item group IDs.
• Anything not on the list is removed, so you can do a “keep this set, drop the rest” cleanup without a full feed re-upload.
• Supports CSV, JSON, JSONL, and .tar bundles containing any mix of supported files (items, variations, item groups).
• Includes built-in safety checks to help prevent accidental large deletions (override available for intentional large cleanups).

How to get started

• Supported entity types: items, variations, and item groups.
• File formats: CSV, JSON, JSONL, or a .tar bundle containing any mix of supported files.
• Built-in deletion safeguards: by default, Whitelist Action won’t delete more than 50% of a catalog in a single run (override available).
• Cascade rules: deleting items also deletes their variations; deleting item groups validates that the tree structure won’t break.
• Payload requirement: whitelist payloads must include only ID fields; extra fields will error.
• Override option: override the failsafe threshold with the forcewhitelist keyword (use with caution).

📓 Links to additional documentation

- Public Docs -

Constructor DocumentationCatalog upload operations,

Constructor DocumentationCreate or replace catalog