He Had the Same Product Entered Four Times Under Four Names

Duplicate entries, vague names and inconsistent units make stock counts wrong and reports useless. Here is how to set a catalogue up so it stays clean.

Vasanth could not work out why his best-selling cooking oil showed poor sales in every report. It turned out he had entered it four times — once when he set up, once when a staff member could not find it, and twice more when the pack size changed.

Each entry held a fraction of the sales. Each showed a stock level that was wrong. Every report that touched that product was quietly meaningless.

Why Catalogue Mess Matters More Than It Sounds

A messy catalogue does not announce itself. Billing still works, sales still record, and nothing visibly breaks. What breaks is everything downstream.

• Stock levels split across duplicates, so nothing is ever accurate
• Low-stock alerts firing for one entry while another has plenty
• Sales reports understating your actual best sellers
• Margin analysis wrong wherever cost price was entered on only one duplicate
• Physical counts that never reconcile, which then get blamed on shrinkage

That last one is worth noting. A significant share of unexplained stock gaps in small shops are catalogue problems, not loss — the units exist, they are just recorded against a different entry.

I spent a month looking for missing stock that was sitting in my own system under a different name.

A Naming Convention You Can Actually Follow

The goal is that two different people, on two different days, would create the same name for the same product.

• Brand, then product, then variant, then size — in that order, every time
• ‘Aashirvaad Atta Whole Wheat 5kg’, not ‘5kg atta aashirvad’
• Write sizes the same way throughout — 500g, not 0.5kg or ½ kg
• Never use a personal shorthand that only you understand
• Never let pack size live only in the name if the system has a unit field

Barcode scanning solves most of this on its own, because the code is the identity. Where a product has no barcode — loose goods, repacked items — the convention is what prevents duplicates.

Almost every duplicate is created by someone who could not find an existing product and made a new one rather than interrupt the queue. Train anyone who adds products to search two ways — brand first, then product name — before creating anything. That one habit prevents most catalogue mess.

Units Are Where Counts Go Wrong

Unit confusion is the single largest cause of stock gaps that are not damage or theft.

• A case of 24 entered as one unit rather than 24
• A 500g and a 1kg pack sharing one product entry
• Goods bought by the sack and sold by the kilo with no conversion recorded
• A ‘dozen’ that is 10 in one supplier’s invoice and 12 in another’s

Decide the selling unit for each product and record purchases converted into it. If you sell by the kilo, buy in kilos in your records however the supplier invoices it.

Categories: Fewer Than You Think

Categories exist so you can count and analyse in manageable groups, not to build a perfect taxonomy. Fifteen to twenty-five is plenty for most shops.

• Make them match how you would physically count the shop, section by section
• Avoid categories with three items — they add navigation cost and tell you nothing
• Avoid a catch-all ‘Others’ that grows to hundreds of products
• Keep them stable; renaming categories breaks comparison with last year

Cleaning Up an Existing Mess

Do not attempt the whole catalogue. Work where the consequences are.

• Start with your top fifty products by sales — the ones your decisions depend on
• Search each for near-duplicates and merge them
• Fix units before names, since units cause the count errors
• Then set the convention, so the mess does not rebuild
• Review new additions once a month for a while

Arali supports barcode-based product identity, per-product units and category grouping, which prevents most duplication at the point of entry. Where it cannot — loose and repacked goods — a written naming rule taped near the counter does the rest.

Frequently asked questions

Why do duplicate product entries cause problems?

Because stock levels split across the duplicates, so nothing is accurate. Low-stock alerts fire for one entry while another has plenty, sales reports understate your real best sellers, margin analysis is wrong where cost price was only entered on one, and physical counts never reconcile — which then gets blamed on shrinkage rather than on the catalogue.

How should I name products in my inventory system?

Brand, then product, then variant, then size, in that order every time — 'Aashirvaad Atta Whole Wheat 5kg', not '5kg atta aashirvad'. Write sizes consistently, avoid personal shorthand, and let the unit field hold pack size rather than the name. The test is whether two people on two days would create the same name.

What causes stock counts to be wrong even without theft?

Unit confusion, most often: a case of 24 entered as one unit, a 500g and 1kg pack sharing an entry, goods bought by the sack and sold by the kilo without a conversion, or a 'dozen' that is 10 on one invoice and 12 on another. Decide a selling unit per product and convert purchases into it.

How many product categories should a small shop have?

Fifteen to twenty-five is enough for most shops. Make them match how you would physically count the shop section by section, avoid categories holding only two or three items, avoid a catch-all 'Others' that grows unchecked, and keep them stable — renaming categories breaks year-on-year comparison.