A
new order is created as soon as you add something to the basket
(assuming there isn't an existing order), but if the customer does not
make an order, that order number is "wasted" and the next customer gets a
subsequent order number. The result is non-sequential completed order
numbers.
For each order number, the order line numbers are also
strangely numbered. At the moment, while I am doing some testing I am
getting order line numbers of 144, 145, etc as the first and second line
on an order. The next order will have line numbers 146 and so on.
Although these are pretty much internal - is there a reason for the
numbering scheme? Why can't each order have order lines starting from 1?
The
Order number issue is more of a problem though - the site owner cannot
use the order number as any indication of how many "actual" orders they
have had. Having gaps is hard to explain to the site owner!
It
would be great if you could build a "cart" system that uses a random
numbering scheme, until the final step when an actual order (number) is
created. That way, the order numbers would (should?!) be consecutive.
After all, items in a shopping cart does not consitute an order ...
until it is paid for :-)
Yes you are on to something there. The reason is that all orders and orderlines use integer identifiers.
The plan is to change that in Tea Commerce 2.0, which we are working on now. Here all identifiers will be guid's and order id's will be assigned when the order is sent to payment. My guess is that laps will still occur when the order is cloned due to the use case in the other forum post you created
We still have to bend to the payment gateways demands.
Order and order line numbering
This is kind of linked to this post http://our.umbraco.org/projects/website-utilities/tea-commerce/tea-commerce-support/34140-New-order-being-created-during-checkout-phase
A new order is created as soon as you add something to the basket (assuming there isn't an existing order), but if the customer does not make an order, that order number is "wasted" and the next customer gets a subsequent order number. The result is non-sequential completed order numbers.
For each order number, the order line numbers are also strangely numbered. At the moment, while I am doing some testing I am getting order line numbers of 144, 145, etc as the first and second line on an order. The next order will have line numbers 146 and so on. Although these are pretty much internal - is there a reason for the numbering scheme? Why can't each order have order lines starting from 1?
The Order number issue is more of a problem though - the site owner cannot use the order number as any indication of how many "actual" orders they have had. Having gaps is hard to explain to the site owner!
It would be great if you could build a "cart" system that uses a random numbering scheme, until the final step when an actual order (number) is created. That way, the order numbers would (should?!) be consecutive. After all, items in a shopping cart does not consitute an order ... until it is paid for :-)
Hi Gordon,
Yes you are on to something there. The reason is that all orders and orderlines use integer identifiers.
The plan is to change that in Tea Commerce 2.0, which we are working on now. Here all identifiers will be guid's and order id's will be assigned when the order is sent to payment. My guess is that laps will still occur when the order is cloned due to the use case in the other forum post you created
We still have to bend to the payment gateways demands.
/Rune
That sounds like a plan!! So, when is TC 2.0 due ? ;-)
is working on a reply...