[seventhfury]

Hey guys!

Lately I've had to make a few manual changes to orders in the LS backend because people have changed their minds on sizes, etc. When I do this, I noticed that I have to manually go in and update the inventory for the items, which means removing the new item and adding back the original item. Thought it would be cool to have a checkbox in the Edit Order area that would say "Update Inventory with New Settings" so that when the order is saved out the inventory will update.

Thanks,

Matt

[Aleksey]

Hi, Matt!

That's a good suggestion. I added it to the to-do list.

But I didn't get this: "Manually go in and update the inventory for the items, which means removing the new item and adding back the original item" - why do you do that? Can you clarify, please?

Thank you

[seventhfury]

Great!

Quote

"Manually go in and update the inventory for the items, which means removing the new item and adding back the original item"

Here's what I meant: Say I start with 2 Medium shirts and 2 Large shirts. I sell a Medium shirt, which brings the inventory count to 1 Medium and 2 Larges, but then the customer emails me back and wants to change the Medium to a Large instead. I then go into the LS backend and edit the order, changing it from a Medium to a Large. After that I go to the Products section in the backend and check the inventory count for Mediums and Larges and they appear to be the same as they were before I made the change in the Edit Order area. The changes made in the Edit Order section should have reflected a +1Medium because it was being swapped/returned, and a -1 Large because it was sold instead. Therefore, I should then have a count of 2 Mediums, 1 Large.

When I do this process, however, I don't see the inventory count change at all, so I'm guessing the Edit Order doesn't communicate with the inventory. I could be wrong, but I've checked on a few occasions and have had to go into the Grouped Products for items and update manually.

Make sense? Kind of lengthy, wanted to be thorough. :D

Thanks!

Matt

[Aleksey]

Hi, Matt!

Yes, this makes sense!

When I do this process, however, I don't see the inventory count change at all, so I'm guessing the Edit Order doesn't communicate with the inventory.

Now LemonStand updates inventory count only when the customer pays the order. Because until the order is paid, the t-shirt does not belong to the customer, and thus the number of t-shirts of this type in stock is not changed. This was the original idea. BTW, with this approach you even don't need to update inventory counts in the existing orders, because inventory has not been updated yet. It will be updated when the customer pay the order.

Does this make sense for you? We can add an option which will force LemonStand to reduce the inventory numbers when somebody places the order (without waiting for the payment), and revert inventory back if you cancel the order. Please let us know what do you think.

Thank you

[seventhfury]

Quote

It will be updated when the customer pay the order.

This does make sense, but the issue usually arises after the customer has paid and before the item has shipped. The scenario I'm describing is more if the customer pays and then an hour later decides to email me about changing their size. So I'm actually talking about finalized orders.

Quote

We can add an option which will force LemonStand to reduce the inventory numbers when somebody places the order (without waiting for the payment), and revert inventory back if you cancel the order. Please let us know what do you think.

This does sound like a good additional item to add, because if you set it up to work as you have stated above and reduce the inventory number when somebody places an order you reduce the risk of running out of stock if two people place an order for the last item in an inventory at the same time. i.e., Bill and Mike both buy the very last Small size shirt at the exact same time but because Bill beat Mike to the final order page before payment he gets the shirt and Mike gets an out of stock notification. I think it would be extremely rare for two people to buy the very last item at the exact same second as one another, but it could happen. I may also be getting a little off track here...

Thoughts?

[Aleksey]

I agree!

I added a task to my to-do list. Thank you!

[seventhfury]

Awesome!! Thanks!

[zone]

Great topic. I think the tweaks suggested here are quite important.

[rtd]

Just scanning through the forum and came across this post. For what it's worth, we also have a similar requirement, but we also had a much bigger inventory tracking requirement (to track inventory levels as the size/variation level), so we decided to have a custom module developed by pnomolos and the module is just about complete.

You can see more of our original requirement here:
http://forum.lemonst...module-request/

Not only does it do a fabulous job in tracking inventory level at the option/variation level, it also is smart enough to know when to add/subtract inventory when order line items change - and it only does that when the order status is set to a specific value. So, if an order is New for example, you can add/subtract/change order line items all you want and it doesn't adjust the inventory. But, once that order is moved into Paid status, the inventory will be adjusted.

Also, if you change the line items of a Paid order, the inventory module will correctly add/subtract the inventory level. Plus, if you cancel Paid orders, it will make the necessary updates to inventory.

Lastly, the module takes care of messaging the shopper when a product variation is out of stock. If I have a small, white, crewneck shirt that has an inventory level of 0, when a consumer tries to buy that variation, they will see a message saying that item is temporarily out of stock.

If you have a need for better inventory tracking functionality, send a message to pnomolos.

[seventhfury]

rtd,

Thanks for sharing! I'll definitely take a look at this. :D

[rtd]

My pleasure seventhfury. who knows, maybe Aleksey will talk with pnomolos and somehow integrate this functionality into LS natively in some future release of LS :)

In the meantime, at least you have an option you can use immediately.

[Aleksey]

Hi, guys!

I will definitely talk to pnomolos. I implemented many API extensions by his request :-)

Thank you

[seventhfury]

Cool! Well, perhaps I'll wait to see if you'll plan on implementing this. Can you post back after you decide? That will let me know if I should pursue this route or wait for your version.

Thanks!

Matt