Making changes
How changes get from the console into your ledger, and why a Save can be turned back.
Your ledger only changes in one way: through a Save. That keeps the record clean, and it means every change has a name and a time on it.
Plan, check, Save
- Make your changes. Mark an order shipped, move a card to a new slot, raise a price. Nothing is written yet. The console keeps your changes to one side and shows them on every page, with a count of what’s unsaved.
- Check them. The review page lists each change as old value to new value, so you can see exactly what will happen before it does.
- Save. All your changes go into the ledger together. Either they all land, or none do.
If you change your mind before saving, discard the change and nothing happens.
Owners and staff save changes. Claude, working as an assistant, drafts them for one of you to save. See People and roles.
Editing is being switched on in the cloud console a page at a time. Where a page doesn’t offer it yet, a note at the top says the page is read only for now.
When a Save is turned back
A Save is refused if one of the records you changed was changed by someone else after you started. Say you planned to move a card, and in the meantime a teammate sold it. Rather than overwrite their work, .vault stops and asks you to look again. Reload, check the record, and make your change again if it still makes sense.
Some changes are refused by design, whoever asks:
- A list price can’t go below the card’s break-even floor: the price at which, after eBay’s fees and shipping, you’d get back what it cost you.
- Lowering a price, even above the floor, asks you to confirm the decrease first.
- An order’s shipping status moves forward. Moving it back asks for a clear confirmation, shown in red.
Who changed what
Every change in a Save is logged with the person who made it and when, so the ledger always shows who did what.