Sizes and Colours in a Store: How the Catalog Should Be Built
31 Oct 2026
An item in three colours and four sizes is neither twelve unrelated products nor one product with no stock. How you model the differences decides whether a customer can choose what exists, and whether you know what sold out. This guide settles that before data entry.
A clothing, shoe or home store usually stumbles in the first week because size was implemented as a picture, not as a choice that reduces a quantity. The customer orders “black / L” and the branch receives “black”, or they are blocked because quantity sat on the parent product and every size disappeared together.
A parent product and its variants
The parent is what the customer sees in the list: the name, the shared description, the general photos. The variant is what is purchased: colour, size, sometimes material. Quantity and any extra price live on the variant, not on the parent. If each colour has its own price, store it on the variant. If the price is shared, do not retype it twelve times in different texts so it drifts later by mistake.
What is not a variant?
- A marketing line such as “relaxed fit”. That is copy, not a stock choice.
- A gift or packaging. That may be a cart add-on, not a size.
- Which branch has it. That is a stock-and-place question, handled in the branch link, not inside the colour name.
Mixing these makes the option list long and useless, and the customer leaves. Show only what changes what will be shipped.
Photos
A colour photo is not decoration. When you have one, it should change as the customer picks a colour, so they do not buy from a black photo while selecting beige. If you do not have a photo per colour, do not imply a colour that is not shown. One photo plus the written colour name is more honest than a colour grid with no source.
Entering and maintaining data
Who adds a new size a month later? If the answer is a developer for every size, the panel does not fit a catalog that changes. Ask for adding a variant from the panel to be part of delivery, with a test your own staff perform. The online sales system we built for Morsh D lets customers order directly from a clothing brand, with support after launch. That does not mean every size in your brand is copied from that project. It means running orders after the build is part of the agreement, and entering sizes will remain your daily work.
Stock-outs
A variant that is gone is hidden or marked unavailable. The parent is not deleted while other colours remain. Deleting the parent loses the ad link. A customer from an old ad should see the alternatives, not an error page. Write this into the test: buy the last piece of one size and confirm the rest can still be bought.
A naming table before the rows grow
An extra column in the first week is cheaper than renaming a thousand variants a month later. Agree colour names as the customer will read them, not as a supplier invoice spells them when those differ. Write whether size is a number or a letter. Different names across branches create two codes for one piece, so available stock sits in one place and the page shows none.
Before you fill hundreds of rows
Start with ten items that represent every kind of difference you sell: size only, colour only, both, and an item with no variant. If the path works on the ten, repeat it. Filling a thousand rows and then discovering the unit is wrong means entering them again. Prepare a table with columns: parent code, variant code, colour, size, quantity, price, image file name.
The store build is e-commerce development, and the on-screen choice is UI/UX design. A clothing brand where customers order directly: Morsh D.
Send a sample of ten items in their current form from start your project. A photo of the table is enough on WhatsApp from the button on this article if the file is heavy.
