Save & Deploy logic (unified publishing)

Understand how Save & Deploy works across Recommendations and Merchandising, including draft logic, deployment lifecycle, and unified statuses.

What’s Save & Deploy logic

We now have a real 2-step status model across Recommendations & Merchandising.

• Step 1: Save changes: edits are stored as a draft without impacting the live version.

• Step 2: Deploy: once the user is ready, they intentionally push the new version live.

This separation makes the workflow clear, safe, and predictable.

Why this matters

• You always know what is live and what is still being edited.

• Users avoid accidental deployments or overwritten strategies.

• Deployment is now a deliberate action, not an automatic side effect.

• We gain better control over synchronizations (catalog sync, rules propagation, API consumption, etc.).

• The system can safely handle drafts, concurrent edits, and deployment queues.

Statuses

• Draft → changes saved, not deployed

• Deployed → live version

• Draft waiting → deployed version exists + new edits pending

• Deploying → deployment job in progress

• Failed → deployment error, draft preserved

In short

• Save = work in progress

• Deploy = push live

A clean, controlled, two-step publishing workflow that secures updates and stabilizes synchronization.

---