Critical Scalability Improvement Request – Historical Data Decoupling from Live Inventory

Hello Aronium Team, I am reaching out to highlight a structural limitation that becomes increasingly critical for long-term and enterprise-scale users of Aronium. Currently, inventory quantities are fully dependent on historical documents. This means any deletion of past invoices or transactions directly affects current stock calculations by reversing historical operations. While this approach ensures accounting integrity, it creates a significant limitation in real-world long-term usage scenarios. After extended operational periods (years of transactions), businesses naturally reach a stable state where: Current stock levels already reflect real physical inventory Historical transactions are no longer required for day-to-day operations The database becomes heavily dependent on legacy data that is rarely accessed but continuously impacts system behavior At this stage, maintaining full historical recalculation becomes a scalability constraint rather than a benefit. Core Issue: The system tightly couples historical data integrity with live inventory state, making it impossible to clean or optimize historical records without affecting operational stock accuracy. Proposed Improvement: Introduce an advanced administrative feature that allows: “Decouple historical transaction data from current inventory state” or “Archive or purge historical documents while freezing current stock balances” This feature should include: Strict administrator-only access Mandatory backup confirmation before execution Clear irreversible action warnings Optional archival export before deletion Why this matters: This is not a cosmetic improvement—it is a scalability requirement for real enterprise environments. It would directly benefit: Large warehouses with long operational history Businesses operating multi-year inventory systems Users facing performance degradation due to large databases Companies needing periodic system cleanup or fiscal resets Without this capability, organizations are effectively forced to either: Retain years of unnecessary transactional data indefinitely, or Rebuild systems manually while re-establishing inventory baselines Both approaches are inefficient and not suitable for enterprise-scale operations. Closing: This enhancement would significantly strengthen Aronium’s position as a scalable, long-term inventory solution and make it more suitable for high-volume professional environments. I strongly believe this feature would add substantial value to the platform and resolve a long-standing limitation for advanced users. Thank you for your time and continued development.