Set next order number

[adb34]

Can you use coding for the month and/or year this or does it have to be a physical number?

[lat9]

Can you use coding for the month and/or year this or does it have to be a physical number?

The next-order number you enter in Tools->Store Manager, Set next order number, must be an integer.

[adb34]

The next-order number you enter in Tools->Store Manager, Set next order number, must be an integer.

dam, Thanks.

[lat9]

Of course, 2015070000 is a number ... and you'd start creating order IDs like 2015070000, 2015070001, etc. Just adjust the lower digits (0000) to reflect the maximum number of orders you expect to receive in a month (0000 => 9999).

[DrByte]

Keep in mind that since the order_id field is INTEGER, its maximum allowed value is 2147483647.
To use numbers higher than that you'd need to change the table schema definition for the order-id in all related tables to be BIGINT.


For v2 we will have customizable order-numbers (for the customer to see), with the old order-id field simply being a private internal sequential tracker for audit/integrity purposes, and the configurable order-number being something you configure for yourself, such as date-based or a random hash value or UUID or store-name-plus-some-value, etc.

Unfortunately there are a LOT of places in the code where the order-id is output directly so changing it there is a bit challenging in the current version.

[adb34]

What I was hoping to do was 'layer' the receipt number for example;

receipt number | month | Year and make all the element automatic. Just for ease really.