Hey,
I get different Ordernumbers in DIBS payment and in Umbraco Backoffice.
This forces the order number history not to be sequenced, but every other number instead.
Is there a way to ensure order numbers to be sequential?
The trick is to have two Order Number Series. One for the payment reference ( the one assigned to the ordre before the customer arrive at DIBS) and one for the completed order (assign when uCommerce get the DIBS callback). This way only completed orders get the "real" order number, and they will be sequential.
So you would have to create two ordernumber series, one with the "hardcoded" ID for the payment reference, and the other is picked on the store-node (in uCommerce), and will be used as the "real" ordernumber.
Different orderNumber in DIBS as in backoffice
Hey, I get different Ordernumbers in DIBS payment and in Umbraco Backoffice. This forces the order number history not to be sequenced, but every other number instead.
Is there a way to ensure order numbers to be sequential?
The trick is to have two Order Number Series. One for the payment reference ( the one assigned to the ordre before the customer arrive at DIBS) and one for the completed order (assign when uCommerce get the DIBS callback). This way only completed orders get the "real" order number, and they will be sequential.
Cheers,
Actually makes sence, if you look at it!
How do i set order number series for payment reference? Is that in payment config file or?
You can change the ordernumber for dibs with the code Matt Brailsford provides here: http://our.umbraco.org/projects/website-utilities/ucommerce/ucommerce-support/37430-Order-number-series-Default-Payment-Reference-does-not-exist, or just use the default name.
So you would have to create two ordernumber series, one with the "hardcoded" ID for the payment reference, and the other is picked on the store-node (in uCommerce), and will be used as the "real" ordernumber.
Hope that makes sense :)
Cool, thanks
is working on a reply...