Support > Technical support
Open Shop 1.6 Incoherency
Amigamerlin:
Ciao Datahell,
I'm facing a little probelm with e-shop.
Scenario:
I've 1 piece of the Object A (physical object) in stock;
User A buy Object A using Paypal but don't do the payment.
In the order status I've Waiting for payment;
The warehouse report 0 as availability;
IMHO It should report 1 since no pyament is done.
This because if another user (User B) buy it and do the payment he has the right to get the last object in warehouse.
Shortly ...stock quantity should be updated ONLY if /when payment is done .
Let me know.
Amigamerlin:
Datahell,
Open Shop 2.0 now is out.
I didn't have done the update yet, just a question:
In Open Shop 2.0 the order are managed in the same way of Release 1.6? Have the same incoherency managing order?
Let me know.
Thank you .
datahell:
No, stock quantity should be updated on order regardless the payment status because if the stock is left as is and an other user makes a second order he will have no product to get if there is only 1 product in stock. Then you will have 2 users having purchased the same product! When you make an order the products are reserved for you. If the order is cancelled/deleted the reserved products are released and become available again for other users (this requires stock to be enabled in Open Shop). Open Shop v1.x and v2.x works the same way in this.
Amigamerlin:
--- Quote from: datahell on January 10, 2017, 10:04:52 ---No, stock quantity should be updated on order regardless the payment status because if the stock is left as is and an other user makes a second order he will have no product to get if there is only 1 product in stock. Then you will have 2 users having purchased the same product! When you make an order the products are reserved for you. If the order is cancelled/deleted the reserved products are released and become available again for other users (this requires stock to be enabled in Open Shop). Open Shop v1.x and v2.x works the same way in this.
--- End quote ---
No Datahell IMHO can't work that way. Say me why user B should not get the last product if payment is not done by user A. In the current condition even If I have 10 pieces of one item and User A get all the 10 pieces without doing the payment I loose the opportunity to sell 10 pieces until I remove the order ?
At least provide an automatic option that provide to cancel the not paid orders after XX days. As remainder An e-mail should be sent to the user that don't do the payment about the order cancellation in xx days.
Anyway IMHO a solution must be found because in this condition I can have hundred of product blocked waiting for payment !!!
Let me know.
datahell:
I totally disagree. You can create a mess if you don't reserve the purchased products after an order. Consider this: You have 5 items of product A. Customer X buys all of them, the order is saved and selects as payment bank deposit. This is an offline payment method, the administrator will be notified about the deposit even 2 days later. After some hours customer Z orders 1 product A he makes an online payment and gets the product. Now the next day, or after a few hours, customer X makes the payment and waits you to send them 5 A products but you have only 4 in stock! He has placed a legal order, paid for the products and you have no product to give him. Is this right? I strongly believe it is not. You can't convince me for the opposite. Except if you want to play boxing with your customers... This is a simple case, I can make you more complex examples.
Open Shop has cron jobs for various tasks but not for the task you want. But you can use Elxis cron jobs for that task.
Put your custom PHP code in a .php file (any name) and place it in folder repository/cronjobs/
Enable cron jobs in Elxis configuration and you will have automatic deletion of unpaid orders.
Elxis will execute any php file will find in folder "cronjobs" periodically.
I believe most administrators want to delete orders by themselves and not use an automatic deletion mechanism because some orders may be delayed on purpose (eg waiting for a customer to reply, waiting for products to arrive, problems with the payment gateway, etc).
Navigation
[0] Message Index
[#] Next page
Go to full version