Sales teams renegotiate constantly. A customer asks for a discount, a longer payment term, a swapped product, a different quantity — and the salesperson simply edits the quotation in place. Odoo's native sale.order keeps only the latest state of the document; once a line is edited or deleted, the prior figure is gone. The chatter (mail.thread) logs that "a change was made" but not a structured before-and-after of the whole quote. When a deal closes weeks later and finance, the customer, or an auditor asks "what did version 2 actually say?", there is no clean answer. Managers lose the ability to review how a margin eroded across rounds of negotiation, and disputes over "what we agreed" become he-said-she-said.

This is where Odoo core runs out of road. The standard product gives you order-line tracking on a handful of fields and the chatter feed, but no first-class concept of a quotation revision — an immutable, numbered snapshot of the entire document at a point in time that you can reopen, compare, and print. Rebuilding this from Studio or manual chatter notes is brittle and unenforceable. What ECOSIRE builds for you is a dedicated revision engine: a new sale.order.revision model (models.Model) that stores a deep, serialized snapshot of the order header and every order line each time a revision is cut. Snapshots capture partner, pricelist, payment terms, validity date, notes, and the full line grid (product, description, quantity, unit price, discount, taxes, subtotal), stamped with revision_number, create_uid, and create_date. A revision_count computed field (@api.depends) surfaces on the quotation, and a smart button opens the version list.

Technically, revisions are cut through a controlled action rather than silent edits. We add a "Create Revision" button in the quotation form (XML/OWL view inheritance) that freezes the current state into a snapshot before the user begins the next round of changes — or, where you prefer, an automated action / model override that auto-snapshots on defined triggers (e.g. sending the quote, or any change after it was sent). A side-by-side comparison view renders two selected revisions and highlights field-level and line-level deltas — added lines, removed lines, quantity and price changes, discount movements, and the resulting margin swing. Each revision is printable via a dedicated QWeb report so you can hand the customer, or attach to the deal, the exact document as it stood at any round. Everything is reachable over the standard XML-RPC / JSON-RPC API for downstream reporting or integration, and access is governed by ir.model.access.csv plus record rules so revisions are read-only to salespeople and manageable only by sales managers, with multi-company record rules keeping each company's history isolated.

Because this is built to order, we start from your actual negotiation process rather than a generic template. During scoping we confirm which fields must be snapshotted, what triggers a new revision (manual, on-send, or on-confirm), whether revisions should carry approval, how comparisons and reports should look, and which roles can create versus view them. We then build against your target Odoo line — 17.0, 18.0, or 19.0, Community or Enterprise (Enterprise adds tighter Studio/approvals interplay we account for) — deliver on a staging instance for UAT, and only then install on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company revision isolation, approval workflows on revisions, migration of historical quotes into snapshots, and deeper reporting or API integrations increase the quoted scope.