Feature Guide
By Andrew Hemphill Β· 2 May 2026
Once a customer has accepted an order in Puree, the quote becomes a contract β they've agreed to the items, pricing, and event details exactly as quoted. But real-world catering jobs change. Guest counts shift, menus get tweaked, delivery times move. Puree's order versioning gives you a way to handle those changes cleanly, with a clear record of what was agreed at each stage.
When you edit an order that's in Accepted state, the order form gives you two save options:
The "Save as new version" button sits just above the regular Save button on the order form, and only appears once an order has been accepted.
We recommend only creating a new version for material changes β the kind of changes a customer would reasonably want to see and re-approve before the event goes ahead. For example:
Because saving as a new version reverts the order back to Pending, the customer will need to re-accept the contract. That's a feature, not a bug β it ensures both sides have agreed to the latest terms β but it does mean a new version triggers another acceptance step. If you create a new version for a tiny tweak the customer didn't ask for, you may end up chasing them for re-acceptance unnecessarily.
For minor internal changes β fixing a typo in a chef instruction, attaching a document, updating a tag, correcting a note β use the standard Save button. The order keeps its current version number and stays Accepted. The customer doesn't need to do anything, and your audit trail still records what changed and when.
Each version is kept as a snapshot. Once an order has been versioned, a Previous Versions dropdown appears at the bottom of the order page, listing the current version plus every prior version (e.g. Quote # 123.1, Quote # 123.2). Clicking an entry reloads the page showing the order exactly as it was at that version.
The snapshot covers everything that makes up the quote: order items and pricing, staff, deliveries, venue reservations, packages (including any "All Items" package selections), every commentary field (introduction, event format, menu, beverages, equipment, miscellaneous, staff, venue), discounts and surcharges, deposit requirements, supplier details, online order information, and scheduled payment requests.
A few things deliberately stay current rather than versioned: deposits actually received, tags, attached documents, notes, and the audit trail. These are operational or admin metadata that aren't really part of the quote, so they always reflect today's state regardless of which version you're viewing.
Saving in place doesn't create a separate snapshot β only changes that bump the version number are kept as history.
For an external long-term record β accounting, legal, or a shared drive archive β we recommend downloading the order PDF before saving a new version. The in-app history is the source of truth, but a PDF gives you something you can store outside Puree, attach to invoices, or hand to a customer in a dispute.
This is especially worthwhile for high-value events, weddings, and corporate jobs.
As always, if you have questions or feedback, reach out to us at email@puree.app.