How Litecart handles Stops when they are prod?

Hello, greetings. This is my first post. I've been using Prestashop for some years now, but it's getting more and more difficult to maintain a store with this platform, so I decided to look for an easier and more functional CMS without the need of third party libraries, or unnecessary requirements, and I came across this marvel, congratulations to the founder of this project and thanks for sharing it. That said, I've been in the learning curve, "playing" between its functions and alternatives, and I've run into something that I don't understand how it works. I am looking for how to configure so that when a customer selects a color and a size, the system tells him that there is not available in Stop. So, my doubts are:

[b]1.- [/b]Where do I change this value that I mark in red? Where does this 4999 come from if I have not added stop? All the attributes below say "0".

[b]2.- [/b]And my other doubt is, why if the attribute that is marked in blue says 200 in Stop and when I go to the frontend it tells me that there is not enough stop? I don't understand how Litecart handles this function.

[b]3.- [/b]And another doubt is, what is this field (the one marked in green) for?

[b]NOTE: [/b]Sorry for the screenshots in Spanish language. They should indicate that new users cannot post links. I uploaded some images to a server, to post them in post 1.- 2.- 3.- and the forum told me: To avoid spam, new forum users are not allowed to post links. So I uploaded them as attachments.

Thank you for your guidance.

Sorry, in point 3, it refers to the Sku code. The Spanish translation was wrong. I have already cast my vote on the correct translation (SKU).

Hi deimar, thank you for those kind words. I am the founder of this project and I am always happy to see new faces.

I understand a new platform is a bit of a learning curve. And LiteCart might not be that everyday conventional platform you are used to.

Indeed the options and stock options part is very complex. That's why it will be replaced in 3.0 with what will be called stock items instead. It is unfortunate that this is one of the first components you have to dig into. The have during the years cost a lot of unnecessary time due to the complexity.

1. It looks like an inconsistency here. 4999 should be the total of all stock options beneath. Did you set quantities directly to the database? Or maybe saved a quantity of 5000 before assigning any stock options.

All quantity adjustments can all be found how they operate here:
https://github.com/litecart/litecart/search?q=adjust_quantity

Is there a way to reproduce this if this was not inserted directly to the database?

2. We don't immediately display quantities per stock option. Because the current make requires a combination of options to refer to a stock option. But it sounds like [url=https://www.litecart.net/en/addons/305/product-options-stock-notice]Product Options Stock Notice[/url] is the addon you are looking for. It's been reported to have compatibility issues with the latest version and I would like to rewrite it. But I haven't had time to do so yet.

The validation of quantities is made during add to cart.
https://github.com/litecart/litecart/blob/dev/public_html/includes/library/lib_cart.inc.php#L342-L369

3. Indeed it's sku an not article number. Thank you for upvoting the right translation. It was the right thing to do. 👍

Hi Tim, nice to meet you! Thanks for your answer.

1.- I was able to solve the 4999, indeed, I searched in the database and there it was, I set it to 0.0000 and now it takes the total amount of all attributes. I don't know where that amount 4.999 came from.

2.- Here if I can not do anything. 95% of the articles of my small company, contain at least 2 attributes and many combinations:

• Colors and Diameters
• Colors and Sizes

You can not hide those attributes that do not have stop.

Yes, this part needs a lot of polishing, I think it is one of the most important parts for a comfortable shopping experience for customers.

I will be watching the development of this CMS, which I see a lot of future. Successes!

2. There is no current feature that hides options that are part of sold out stock options. This is a hen and the egg dilemma. To know which ones to hide we need to generate and test all combinations. That's why this will be different in 3.0.

Check back after summer to see where we are at.