Sale Order Auto Archive
Automated Pipeline Decluttering & Data Retention
Stop drowning in old, cancelled, and locked sales records.
Automatically sweep inactive orders out of your main views to keep your sales pipeline clean, fast, and focusedâwithout ever deleting historical data.
The Cost of a Cluttered Sales Pipeline
Over the years, your Odoo database accumulates thousands of cancelled or permanently locked Sales Orders. Leaving them in the active view clutters the interface, distracts sales representatives, and slows down list searches. Manually archiving them takes hours of administrative work. You need a system that automatically hides the noise while keeping the data safely stored for financial audits and reporting.
Smart Archiving Engine
Set your rules once, and let Odoo maintain a pristine sales environment indefinitely.
Time-Based Trigger
Configure exactly how many months an order must remain inactive (based on its last update) before it is safely archived. Runs quietly in the background via a daily scheduled cron action.
Flexible Target States
Total control over what gets cleaned. Choose to archive only Cancelled orders, only permanently Locked orders, or both, depending on your company's operational retention policies.
Transparent Audit Trails
Never wonder where an order went. Every automated action generates a detailed record in the Auto Archive Log, and an automated message is instantly posted to the order's chatter.
Surgical Exception Handling
Have a historic cancelled order you need to keep visible? Simply check the "Exclude from Auto-Archive" flag on that specific document, and the engine will bypass it forever.
Easy 3-Step Configuration
| 1. | Navigate to Sales > Configuration > Settings. |
| 2. | Locate the Auto Archive section and enable "Automatically Archive Old Orders". |
| 3. | Set your inactivity threshold (e.g., 6 months) and select your target states (Cancelled and/or Locked). Click Save. |
| Archived orders are never deleted! You can always find them by typing "Archived" into the search bar filters. |
Configuration & Tracking Interfaces
Simple global settings paired with strict tracking logs for system administrators.
Developed with by SyncSoft LLC
Need assistance optimizing your database size, setting up custom retention rules, or building advanced cron jobs?
We are here to support you!
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Sales (sale_management)
• Discuss (mail) • Invoicing (account) |
| Lines of code | 324 |
| Technical Name |
sale_order_auto_archive |
| License | OPL-1 |
| Website | https://pxfox.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module