How staged changes work
The approval model behind every write.
Nothing your AI stages touches Amazon until you approve it. The lifecycle:
- Stage. The assistant proposes a change - bids, budgets, negatives, listing copy - and AMZ Vault saves it as a reviewable diff with the reasoning attached.
- Review. You see before and after values, per line. In chat you can approve wholly or partially; in the app, the approval queue shows the same diff with checkboxes and editable values.
- Execute. On approval the change goes to Amazon, and the result - applied, partially applied, or rejected by Amazon with per-item errors - is recorded on the proposal permanently.
Guarantees
- Expiry: chat-staged proposals expire in 60 minutes; workforce-staged ones wait 72 hours for you. Expired proposals never execute.
- No double-execution: an approved proposal is consumed; approving twice is refused.
- Honest receipts: a change Amazon rejected is marked failed, never quietly counted as done. If Amazon's response is ambiguous (a network timeout), the outcome is marked unknown and verified against live values before it is settled either way.
- Everything is kept: approved, rejected, failed, and expired proposals all stay in the changelog with who approved them and why.