Store owners often expect WooCommerce order IDs to increase one by one without gaps. When the numbers do not follow that pattern, it is easy to suspect a failed checkout, a deleted order or a database problem. In many cases, however, the explanation is simpler: WooCommerce assigns IDs to more than orders, so other content can use values between two purchases.
This distinction matters when choosing custom WooCommerce order numbers. A sequential numbering extension can create a clearer, customer-facing reference with a prefix, suffix, padding or date pattern, but it does not replace the underlying order ID. This article explains the difference, shows how to configure Sequential Order Numbers Pro, describes what happens to existing orders and outlines the checks needed for payment, export, invoice, fulfillment and automation workflows.
WooCommerce Order ID vs. Order Number: What Is the Difference?
The internal identifier
The WooCommerce order ID is a unique database-oriented identifier. It is not reserved exclusively for orders: IDs are assigned to multiple types of content. If another type of content is created between two orders, it can consume a number in the sequence. The next order may therefore have a higher ID, leaving a visible gap.
These gaps do not, by themselves, show that an order is missing or duplicated. The internal ID remains important for technical operations. In the documented extension model, WooCommerce lookup and URLs continue to rely on the underlying order ID.
The customer-facing number
A customer-facing order number is a separate presentation layer. Sequential Order Numbers Pro can generate an incrementing number that is easier to quote in customer service, fulfillment or store administration. Supported integrations may also use this formatted number instead of the underlying ID.
The two references can still differ. A formatted number improves the numbering workflow, but it does not turn the database ID into a sequential order number everywhere.
Why WooCommerce Order Numbers Have Gaps
What creates the gaps
WooCommerce assigns unique IDs to different content types, not only orders. When other content is created between purchases, those records take values from the same general ID sequence. The order IDs visible in the store can consequently contain gaps even when the order records themselves are functioning as expected.
For this reason, an administrator should not treat every missing number as evidence of an unsuccessful checkout or a removed order. The ID sequence and the customer-facing order-number sequence answer different operational needs.
When a separate sequence helps
A separate sequence can make order references more consistent for customers and staff. It can be configured to increment independently and can use a readable structure rather than exposing irregular database IDs. This is useful when a store wants a predictable reference in messages, exports or supported external-system communication.
It remains important to retain the original ID as a technical reference. Some integrations, URLs and internal searches may continue to use it, so sequential WooCommerce order numbers should be treated as an additional reference rather than a replacement.
How to Set Up Sequential WooCommerce Order Numbers
Core settings
Before changing a live store, plan the numbering format and test the complete workflow in staging where possible. Install and activate the relevant sequential order-number extension, then open WooCommerce > Settings > General and locate the Order Numbers section.
The documented settings allow you to configure the main numbering behavior:
- Set a starting number for the sequence.
- Use a fixed minimum length with leading zeroes when that format is useful.
- Add a custom prefix or suffix.
- Review the available setting for separate treatment of qualifying free orders.
On a new store, numbering begins at 1 by default according to the documentation. On a store that already contains orders, new numbering follows the largest existing order number unless a higher configured starting number is used. If the goal is to move to a new range, choose a starting value higher than the current largest number.
A controlled rollout
Numbering should not be changed as though it were an isolated visual setting. Test checkout, payment callbacks, refunds, subscriptions, exports, invoices, fulfillment, shipping and automations before relying on the new format. Confirm which reference appears in customer communications and which reference is used by connected systems.
Do not run multiple sequential-order-number extensions at the same time. Overlapping numbering systems can cause settings to behave incorrectly. A controlled rollout should also include a record of the selected format, the starting point and the date or operational point at which the new numbering behavior was introduced.
Prefixes, Dates, Suffixes and Custom Formats
Readable formatting choices
Custom WooCommerce order numbers can include a prefix or suffix around the incrementing value. A prefix can identify the order reference in store workflows, while a suffix can add a consistent ending. Fixed minimum length is also available through leading zeroes, so numbers can follow a uniform visual structure.
These choices affect the formatted reference, not the underlying WooCommerce order ID. They should therefore be selected with both customer readability and integration behavior in mind. A format that is clear to a person may not be interpreted identically by every third-party system.
Date and time tokens
The documented extension supports date and time patterns in prefixes or suffixes. Available values include day, month, two-digit or four-digit year, hour, minute and second tokens. For example, a date-based pattern can use a documented arrangement built from YYYY, MM and DD.
Test the chosen pattern before going live, including the way the store’s timezone affects the displayed result. Do not assume that every gateway, export, invoice tool or automation will parse every custom pattern. The formatted number should be verified in the actual workflows used by the store.
Existing Orders and Numbering Changes
What remains unchanged
Activating the extension on a store with existing orders does not rewrite historical order numbers. Existing order numbers remain unaffected when the extension is activated. The same applies when the configured starting number, prefix or suffix is changed: those changes do not renumber previous orders.
This behavior is important for support and reconciliation. Staff may need to work with older references and newer formatted references at the same time, particularly during a transition period.
Choosing the next range
For existing stores, the next numbering behavior is related to the largest existing order number unless a higher configured starting number is selected. A higher value can be used when the store wants to advance the sequence rather than continue directly from the current range.
Document the transition point and communicate it to people handling exports, fulfillment, customer support and payment reconciliation. Historical orders should remain identifiable by their existing references, while new orders follow the configured behavior.
Compatibility: Payment Gateways, Exports and Automations
Integrations that can use the formatted number
Integration behavior is not universal. Compatible plugins and gateways can use the formatted sequential order number instead of the underlying order ID. The documentation lists examples across selected subscription, pre-order, CSV, payment-gateway and WooCommerce Zapier integrations.
That list is not exhaustive, and the absence of an integration from an incompatible list does not prove compatibility. Check every specific plugin and service used by the store before deployment. Pay particular attention to systems that create invoices, export orders, trigger automation or send fulfillment information.
Integrations that may retain the original ID
The documentation identifies Apple Pay via Stripe, PayU, PayU Turkey and RedSys as gateways that may continue to reference the original order ID because of technical limitations. In those cases, the gateway reference and the WooCommerce display number may not match.
The original ID may also remain relevant for internal lookup, URLs and integrations that do not support formatted order numbers. This is why payment support and reconciliation procedures should record which reference each system uses. Do not assume that every connected system will display, transmit or search by the formatted number.
Before activation, test payment confirmation and callbacks, refunds, subscription actions, exports, invoices, fulfillment, shipping and automations. Compare the gateway reference with the WooCommerce display number where the integration may use the original ID.
Common Pitfalls and Safe Testing Checklist
Pre-launch checks
A reliable rollout starts with a complete test rather than a visual inspection of the order page. Use staging or test mode where possible and verify both customer-facing numbers and technical references.
- Place a test order and confirm the configured prefix, suffix, padding or date pattern.
- Check payment callbacks, refunds and any subscription-related workflow.
- Review exports, invoices, fulfillment, shipping and automation outputs.
- Compare gateway references with the displayed WooCommerce order number.
- Confirm that internal URLs and order lookup still use the expected underlying ID.
- Verify that only one sequential-order-number extension controls the numbering.
Do not describe the selected format as a guarantee of accounting compliance. Local requirements should be checked with appropriate professional advice.
Post-change documentation
After deployment, document the starting point, selected format and behavior of every connected system. Record which workflows use the formatted number and which retain the original ID. This gives support and fulfillment teams a consistent way to investigate apparent mismatches.
Keep the historical transition clear as well. Existing order numbers are not rewritten, so staff should know how to distinguish older references from new ones without assuming that a changed prefix or suffix applies retroactively.
WooCommerce order IDs can contain gaps because the ID sequence is shared across multiple types of content. Sequential Order Numbers Pro provides a separate, configurable customer-facing format with starting values, padding, prefixes, suffixes and documented date and time patterns. It does not replace the internal order ID, and existing order numbers are not rewritten when the extension or its settings change. Compatibility must be checked integration by integration, especially where gateways may retain the original ID. Test the full order lifecycle, document the references used by each system and then Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.