How to Manage Colour and Size Variants Without Excel

Garment and footwear wholesalers can manage colour and size variants without Excel by storing one product with a separate SKU for every sellable combination. The common name, item code, HSN and GST remain at product level, while each colour-size SKU keeps its own quantity, location, price, cost, image and barcode.

The purpose is not simply to move spreadsheet rows onto a phone. It is to replace disconnected cells with inventory identities and stock movements that remain useful during restocking, transfers, billing, returns, search and reporting.

This guide explains why common spreadsheet layouts become difficult, how the structured model works and how to move current opening stock into My Local Shops Inventory Manager without pretending that every old Excel row can be imported safely.

At a glance

Inventory task	Typical Excel approach	Structured inventory approach
One design in many types	Repeated rows or colour-size matrix	One product with separate SKUs
Stock at several locations	Separate columns, sheets or files	Quantity by shop and godown under each SKU
Identify exact packet	Manually typed code	Protected system-generated SKU and barcode
Different variant prices	Extra columns or manual notes	Selling price stored on every SKU
Variant photos	File links or separate folders	Product image plus individual SKU images
Restock	Replace or add a cell value	Recorded restock with cost history
Transfer	Reduce one cell and increase another	One connected source-to-destination movement
Sale	Someone must update the sheet	Connected invoice reduces exact SKU stock
Return	Manual reverse entry	Invoice-linked credit note restores eligible stock
Concurrent users	Conflicting files or last saved value	Transactional writes against current stock
Low stock	Formula and filter maintenance	Positive-stock threshold view
Sold-out history	Often mixed into working sheet	Separate Out of stock filter

Why Excel feels suitable at the beginning

Excel is flexible. An owner can create columns immediately, copy formulas, colour cells and send the file to another person. For ten products in one location, the sheet may feel completely adequate.

The difficulty appears when the business asks the spreadsheet to behave like an inventory system:

• several people must update it;
• one design contains many colours and sizes;
• the same SKU exists at several locations;
• sales should reduce stock automatically;
• restocks arrive at different costs;
• images and barcodes must follow exact SKUs;
• old sold-out designs must remain searchable without crowding daily work; and
• the owner needs to know why a quantity changed.

Excel can represent all of these with enough sheets, formulas and discipline. The owner then becomes responsible for designing, protecting and maintaining a custom inventory application inside a spreadsheet.

The two common spreadsheet layouts—and their limits

Layout 1: one row per product

An early stock sheet may look like this:

Item	Code	Quantity	Price
Printed T-shirt	6120	48	₹250

This is compact but cannot answer:

• how many Blue · M pieces exist;
• whether Red · XL is sold out;
• which colour has a different price;
• what is available at Shop 2; or
• which exact packet a barcode should open.

The number 48 is mathematically correct and operationally incomplete.

Layout 2: one row per colour-size type

A more detailed sheet may contain:

Product	Code	Colour	Size	Shop A	Shop B	Godown	Price
Printed T-shirt	6120	Red	S	3	0	2	₹240
Printed T-shirt	6120	Red	M	4	1	0	₹245
Printed T-shirt	6120	Blue	S	0	2	3	₹235

This can describe exact stock, but it creates another set of problems:

• the common name and code are repeatedly typed;
• HSN or GST changes must be copied across many rows;
• duplicate Red · M rows can appear;
• a new location requires new columns or another sheet;
• images need external file references;
• formulas can exclude newly inserted rows;
• two users may edit from older copies; and
• billing still needs someone or another system to reduce each row.

The detailed sheet contains good information. The problem is that its relationships and rules depend on human discipline rather than being enforced by the data model.

Use one product with exact sellable SKUs

The correct non-Excel structure starts with two levels.

Product

The product is the common design recognised by staff and buyers.

Example:

Mickey Mouse Printed T-shirt
Item code 6120

It normally keeps:

• product name;
• supplier item code;
• category;
• HSN code;
• GST rate;
• brand and description; and
• My Local Shops listing and price-visibility controls.

SKU

The SKU is one exact sellable combination.

Examples:

Red / Small
Red / Medium
Blue / Small
Blue / Medium

Every SKU can keep its own:

• protected stock code;
• colour and size;
• quantity at every location;
• average and latest purchase cost;
• selling price;
• image;
• barcode label; and
• low-stock threshold.

This structure keeps the catalogue clean without sacrificing exact stock.

Example: three colours and three sizes

Suppose one design arrives in Red, Green and Blue, with S, M and L sizes. There are three pieces of every combination.

Colour	S	M	L	Total
Red	3	3	3	9
Green	3	3	3	9
Blue	3	3	3	9
Total	9	9	9	27

Inventory Manager stores:

• one grouped product;
• nine underlying SKU records; and
• 27 total pieces.

The Products page shows one product card with nine variants. Opening the item shows the exact list. The owner does not scroll past nine repeated “Mickey Mouse Printed T-shirt” cards merely to find another size.

When a retailer buys three pieces from every type, the product can be opened once during billing. The selected types are added together for speed, while the invoice still preserves nine lines and reduces all nine SKU quantities correctly.

Why the SKU should not be an editable Excel cell

In a spreadsheet, an SKU is often typed, copied or reformatted manually. That allows subtle identity failures:

• BLUE-M becomes BLU-M in one row;
• a leading zero disappears;
• a copied row keeps the previous SKU;
• the code changes after labels are printed; or
• two products receive the same code.

Inventory Manager generates one shared SKU base for the product and adds the applicable colour and size. A simplified family may be:

MLS-7K3F9Q-RED-S
MLS-7K3F9Q-RED-M
MLS-7K3F9Q-BLUE-L

The exact value will differ. The important rule is that the user cannot casually replace it during creation or restocking.

The protected identity keeps printed labels, exact search, stock movements and invoice deductions connected even when the product name, quantity, price or photo later changes.

Keep each SKU's price, cost and image independent

A matrix often encourages one price for the whole design. Wholesale reality may differ.

For example:

Variant	Average cost	Latest cost	Selling price
Red · S	₹180	₹190	₹240
Red · XL	₹195	₹205	₹260
Blue · M	₹175	₹185	₹235

The larger size or a separately sourced colour may cost and sell differently.

Inventory Manager stores cost and price per SKU. It distinguishes weighted average cost from the latest purchase cost so a new expensive restock does not remain hidden behind an older average.

Each SKU can also keep its own photo and thumbnail. A grouped product retains a representative image for list browsing, while SKU details and billing can show the image that identifies the exact colour or type.

Store location quantity as data, not spreadsheet tabs

Separate Excel files such as Shop-A.xlsx, Shop-B.xlsx and Godown.xlsx make each location easy to view but difficult to reconcile. One transfer requires two files to remain consistent.

A single file with location columns improves totals but becomes wider whenever a location is added and still depends on two manual edits for a transfer.

Inventory Manager keeps one SKU identity with quantities under each location. A transfer records:

1. source location;
2. destination location;
3. quantity moved; and
4. the connected reduction and addition.

Business-wide total stays the same while the physical position changes.

For example, moving five Blue · M pieces from the Bhiwandi godown to the Borivali shop should not increase total inventory by five. It should subtract five at the godown and add five at the shop as one protected operation.

Replace overwritten cells with stock movements

If an Excel quantity changes from 20 to 16, the owner may not know whether four pieces were:

• sold;
• transferred;
• damaged;
• lost;
• returned to a supplier; or
• removed as a correction.

A stock-management workflow should record the business reason.

My Local Shops distinguishes:

• product creation;
• restock;
• transfer;
• invoice sale;
• customer return;
• adjustment; and
• damage, loss or other write-off.

The current number remains important, but movement history explains how it was reached.

Read How to Restock, Transfer, Adjust and Write Off Inventory Safely.

Let billing update inventory instead of maintaining two files

Some businesses keep a detailed stock sheet and create bills in another app. After each invoice, someone must remember to update every sold colour-size row.

This creates two competing truths:

• the invoice says what was sold; and
• the spreadsheet says what staff remembered to deduct.

Order Manager and Staff Bill use the connected Inventory Manager stock. During a wholesale invoice, the user selects the grouped product and enters quantity and price for each required SKU. Saving the invoice validates current stock and reduces the selected billing location.

If the same SKU changes from another device before save, protected Firestore transactions evaluate the operation against current data instead of allowing an old screen value to overwrite the newer quantity.

Returns use invoice-linked credit notes and restore eligible stock rather than asking someone to add the cell manually.

Search without remembering the spreadsheet row

A growing Excel sheet often depends on filters, exact spellings and column knowledge. Inventory Manager supports several lookup behaviours:

• product name search;
• supplier item-code search;
• shared SKU-base search;
• exact SKU resolution;
• category filter;
• location filter;
• name or recently stocked sorting; and
• barcode scanning.

The main catalogue is paginated and grouped. It does not need to load every SKU row just to display the first product page.

When the physical packet is available, scanning its Code 128 label finds the exact system SKU. When the user only knows “6120,” item-code search finds the grouped product.

Keep low stock useful when old styles sell out

An Excel formula such as quantity < 5 also matches every zero-stock item. Over time, a fast-fashion wholesaler's warning sheet may become dominated by products that will never be restocked.

Inventory Manager separates:

• In stock — the normal operational catalogue;
• Low stock — positive quantity below its threshold; and
• Out of stock — zero-quantity history available through a deliberate filter.

This preserves old designs without making them daily noise.

The owner can set a default low-stock threshold and override it for a product group or an individual SKU where necessary.

A safe opening-stock transition from Excel

Inventory Manager does not currently provide a generic Excel or CSV bulk-product importer. This is deliberate information to consider when planning the move: opening stock must be entered through the supported product workflows rather than assuming any spreadsheet layout can be uploaded directly.

An old workbook may contain duplicate variants, stale quantities, merged cells, hidden formulas, inconsistent codes and products that no longer exist. Automatically copying all of it would move those problems into the new system.

Use this controlled cutover.

Step 1: choose a start date

Pick a date after which every sale, transfer, restock, return and write-off will be recorded in the apps. Avoid running two “current” stock systems indefinitely.

Step 2: preserve the old workbook as history

Make a read-only archival copy. Do not destroy historical spreadsheets merely because the new system begins. They may still be needed to understand old transactions.

Step 3: perform a physical count

Count what actually exists at each shop and godown. Do not assume the last spreadsheet quantity is correct without checking the physical stock.

Step 4: clean the product structure

For every active design, decide:

• common product name;
• item code;
• category;
• HSN and GST rate;
• actual colours and sizes;
• current cost and selling price; and
• location quantity for every SKU.

Combine duplicate rows that represent the same type. Keep sold-out history only when it has future operational value.

Step 5: enter opening products manually

Use Add Product Manually for opening stock that has no connected Trade Manager record. Create the product once and add all current variants in the same planned entry.

The cost entered becomes the inventory-cost basis used by stock worth and later invoice-profit calculations, so use the truthful available value instead of zero merely to finish setup.

Step 6: use the connected route for newly received trades

After cutover, goods whose purchase and receipt are tracked in Trade Manager should move through the Trade Manager-to-Inventory Manager handoff. That preserves received quantity and costing context instead of retyping them as manual stock.

Step 7: add and verify photos

Set a useful representative product image and add individual SKU photos where colour or type identification matters. Confirm thumbnails and full images appear on the item page.

Step 8: print labels where useful

Print the generated SKU barcode for physical packets or footwear boxes. Verify that the label is attached to the matching colour and size before printing a large batch.

Step 9: compare totals

Check:

• total units;
• in-stock SKU count;
• stock worth;
• product quantity by location; and
• several randomly selected physical SKUs.

Do not compare only one grand total. Two location mistakes can cancel each other mathematically while remaining operationally wrong.

Step 10: begin connected billing

Create all new wholesale invoices through Order Manager or Staff Bill so exact SKU stock starts updating from the agreed cutover point.

What should remain in Excel?

Moving current inventory does not mean Excel becomes forbidden.

It can remain useful for:

• old archived records;
• one-off analysis;
• temporary supplier comparisons;
• external files requested in spreadsheet form; and
• calculations unrelated to live SKU stock.

The boundary should be clear: Excel may analyse or archive information, but it should not remain a second editable source of current quantity after the connected inventory becomes operational.

What the owner sees after the transition

Instead of opening sheets and rebuilding totals, the owner can use Inventory Manager to see:

View	Result
Dashboard	Stock Worth, Total Units and in-stock SKU count
Products	Grouped paginated catalogue with filters and search
Product detail	Shared design information and every SKU
SKU detail	Exact price, cost, photos, quantities and movements
Location catalogue	Products relevant to one shop or godown
Low Stock	Positive-stock types below their threshold
Out of stock	Historical zero-stock items when deliberately selected
Scan	Exact SKU lookup from printed label

The owner still needs to record real-world events. The system does not know that a packet left the shop unless a supported sale, transfer, adjustment or write-off is entered.

What staff sees during billing

Billing staff do not maintain a second spreadsheet. Invited staff use Staff Bill with the owner's connected catalogue.

They can:

• search a grouped product;
• open its available variants;
• view SKU image and available quantity at the billing location;
• enter quantity and negotiated selling price;
• scan an exact label; and
• create the invoice through the protected stock workflow.

Staff Bill's screens do not display the owner's cost, profit or reports. The owner can later see who created the invoice in Order Manager.

A realistic footwear example

Suppose a wholesaler stocks one sneaker design in:

• Black and White; and
• sizes 6, 7, 8, 9 and 10.

That is one product with ten SKUs.

The old workbook uses one row per size and separate columns for two shops. A staff member sells White · 8 from Shop A but updates the Black · 8 row by mistake. The total changes, so the error is not immediately obvious.

With the structured workflow:

1. White · 8 has its own generated SKU and image.
2. Its physical box can carry that SKU's barcode.
3. Scanning during billing resolves the exact type.
4. The save validates Shop A's current White · 8 quantity.
5. The invoice reduces that SKU at Shop A.
6. If the pair is returned through a credit note, the eligible quantity is restored.
7. Shop B's White · 8 remains unchanged.

The benefit is not that a phone displays a nicer table. The physical pair, stock identity, location and invoice line remain connected.

Common mistakes when leaving spreadsheets

Avoid these transition errors:

• creating each size as an unrelated product;
• combining every variant into one quantity;
• typing old spreadsheet row codes into product names;
• assigning stock to the future selling shop instead of its current physical location;
• entering zero cost when the real opening cost is known;
• recreating sold-out catalogue noise that has no operational value;
• printing labels before checking colour and size;
• continuing to update the Excel quantity after app cutover;
• recording new Trade Manager receipts again as unrelated manual products; or
• allowing staff to share one account instead of using the supported billing role.

Frequently asked questions

Can I upload my complete Excel inventory file directly?

Inventory Manager does not currently provide a generic Excel/CSV product importer. Opening stock is entered through supported manual product creation, while new received trades can use the Trade Manager handoff.

Should every colour and size become a separate product?

No. Create one common product and separate SKUs for the sellable colour-size combinations. The catalogue remains grouped while quantity stays exact.

What if only size matters and colour does not?

Create separate size SKUs without inventing a colour. The same model also supports colour-only or standalone products.

Can each size have a different price?

Yes. Selling price and cost belong to the SKU, so one size or colour can differ from the others.

How should opening stock cost be entered?

Use the truthful cost basis available for the current stock. That value affects stock worth and later invoice profit. Consult the business's records or adviser if the correct opening valuation is uncertain.

Can the same SKU exist at two shops?

Yes. One SKU can have quantities at several locations. A transfer moves quantity between them without changing business-wide units.

Will a sale automatically reduce inventory?

An inventory-linked invoice created in Order Manager or Staff Bill reduces the exact selected SKU at the billing location through the protected save workflow. A custom invoice line does not create or reduce inventory.

Can I keep Excel after moving?

Yes, for archives and one-off analysis. Avoid maintaining the same live quantity in both places, because the two records will eventually diverge.

Replace the fragile relationship, not only the file

The biggest limitation of Excel is not the grid. It is that product identity, location, movement, invoice and user rules must be maintained manually around the grid.

A structured inventory system makes those relationships explicit. One design stays one product. Every colour-size combination becomes an exact SKU. Each location keeps its own quantity. Restocks, transfers, sales, returns and write-offs update stock through their proper workflows. Search, barcodes and images continue using the same identity.

Move from Excel with a physical opening count and a clear cutover date, not by copying every historical mistake into a new database. Keep the old workbook as history, then let the connected apps become the source of current stock truth.

Read How to Create a Product with Colours, Sizes, SKUs, Images, HSN and GST, explore the Inventory Manager complete guide, or review the business apps.