Revindex Storefront

Why do order numbers skip?

Last updated on 2021-04-21 2 mins. to read

Starting with v6.5, Revindex Storefront maintains its own sequence ensuring order numbers are sequential and continuous. This improvement is especially important to ensure compliance with tax regulations (e.g. UK VAT laws and New York tax laws require that order numbers be serially continuous and any skipped numbers must be justified to the auditor or be subjected to penalties).

For older Storefront versions (v6.4 and under), on rare occasion, you may notice that your order numbers may have skipped some numbers (e.g. 1,2,3,5...). This is perfectly normal and does not indicate a lost of order. Revindex Storefront makes extensive use of SQL transactions to maintain database integrity. SQL server guarantees an identity sequence column to be unique but is allowed to skip a number when the transaction is rolled back or cancelled.

Furthermore, as of SQL Server 2012 and newer, order numbers may skip by as large as 1000 when the database server is restarted due to the new identity seeding algorithm used in Microsoft SQL Server. This behavior affects any database table and is not limited to Revindex Storefront tables. Because Revindex Storefront 6.5 and newer generates its own order number, it is immune from this problem. For older versions of Revindex Storefront, you can configure SQL Server to use the old method of allocating identity numbers by following the steps below:

  1. Open SQL Server Configuration Manager.
  2. Click SQL Server Services on the left pane.
  3. Right-click on your SQL Server instance name on the right pane to open the Properties window. The default instance is "SQL Server(MSSQLSERVER)".
  4. Click Startup Parameters.
  5. On the "Specify a startup parameter" textbox, type "-T272"
  6. Click Add.
  7. Confirm the changes.


Powered by Revindex Wiki