Sequential Order Numbers for WooCommerce plugin review and common issues

After installing and activating Sequential Order Numbers, go to WooCommerce → Settings → Orders (or find the Sequential Order Numbers settings) and configure the starting number, prefix, and suffix. Save settings. New orders placed after activation use sequential numbers. Existing orders before activation retain their original post ID numbers — the plugin does not retroactively renumber historical orders. If new orders still show post IDs, verify the plugin is active and no caching is serving old checkout responses.

Duplicate numbers occur when two orders are created at exactly the same time and both read the same “last order number” before either has saved its new number. This is a race condition in the database transaction. Solutions: (1) upgrade to a sequential numbering solution that uses database-level locking or atomic transactions (some premium alternatives handle this correctly); (2) the free plugin may update the counter approach in its current version — check the latest changelog; (3) if using a hosted/managed WordPress environment, ensure the database supports proper transaction isolation. For most stores with moderate order volume, simultaneous orders are rare enough to not be a practical concern.

Sequential Order Numbers stores the sequential number in order meta — existing orders retain whatever meta was written when they were placed. Changing the prefix affects only new orders. To standardize existing order numbers with a new prefix, a bulk update of the order meta (specifically the _order_number or _order_number_formatted meta key) is required via a custom script or a database update — this requires developer involvement. For accounting consistency, documenting the prefix change date and treating it as a new sequence series is often simpler than retroactive renumbering.

In the Sequential Order Numbers settings, set the Prefix to {year}- (using the placeholder for the current year if supported by your version, or the current year manually). Set the starting number to 1 or a higher starting value. The order number format becomes 2025-0001, 2025-0002, etc. Note that the counter does not automatically reset at year start — to start a new sequence on January 1st of each year (2026-0001 after 2025-XXXX), you would need to manually update the starting counter in the plugin settings each year or use a premium plugin with automatic annual reset.

Yes — Sequential Order Numbers ensures WooCommerce order numbers are consecutive, which is a requirement for legally valid invoice sequences in Germany and most EU countries. Combine this plugin with a WooCommerce PDF invoice plugin (such as WooCommerce PDF Invoices & Packing Slips) that uses the WooCommerce order number as the invoice number. The combined setup provides sequential, uniquely numbered invoices satisfying most EU jurisdiction requirements for sequential invoice numbering.

The free Sequential Order Numbers plugin does not automatically reset the counter each year — it continues incrementing from wherever it left off. If an annual reset is legally or administratively required (common for accounting year alignment), you must manually update the starting number in the plugin settings each January 1st. Premium alternatives (WooCommerce.com Sequential Order Numbers Pro) may offer automatic annual reset functionality.

No — Sequential Order Numbers does not retroactively change existing order numbers. Orders placed before the plugin was activated retain their original WordPress post ID-based numbers. Only new orders placed after activation receive sequential numbers. This creates a visible transition point in your order history, which is normal and documented for accounting purposes.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.