A messy product catalog is the silent killer of inventory accuracy. Duplicate SKUs, inconsistent naming, missing units of measure, and untracked variants lead to stockouts, overselling, and hours of manual cleanup. This guide shows SMB owners and warehouse managers how to structure a clean product catalog from scratch—covering SKU logic, product variants, units of measure, reorder points, and supplier linking—so your inventory data actually reflects reality.
It's 11 PM on a Friday and your biggest wholesale client just sent a purchase order for 200 units of "the blue one." You know what they mean—probably—but when you open your inventory system, you find three products named "Blue Hoodie," two labeled "Hoodie Blue," and one simply called "BH-Fleece-V2." Stock levels contradict each other. One record hasn't been updated since March. You have no idea which SKU the client actually orders from you.
This isn't a technology problem. It's a catalog problem.
A messy product catalog doesn't just slow you down during crises—it quietly bleeds you every single day through duplicate counts, missed reorders, and supplier miscommunications. The fix isn't complicated, but it requires intentional setup from the start (or a disciplined cleanup if you're already in the weeds). This guide walks you through exactly how to do it.
Build a SKU Structure That Means Something
A SKU (Stock Keeping Unit) is only useful if anyone on your team can decode it without calling you. The moment you invent codes like "PROD-001" or "NEW-ITEM-3," you've created a system that lives entirely in your head.
A functional SKU has three to four components: a category prefix, a product identifier, and a variant code. For example:
| Component | Example | Purpose |
|---|---|---|
| Category prefix | APR | Apparel |
| Product name code | HOD | Hoodie |
| Color/size variant | BLU-L | Blue, Large |
| Full SKU | APR-HOD-BLU-L | Immediately readable |
Keep it short enough to type quickly, long enough to be unambiguous. Avoid spaces, special characters, and anything that looks like a letter-number confusion (no "O" next to "0," no "I" next to "1"). Once you define the logic, document it somewhere your whole team can access—a shared Google Doc, a pinned note inside Pleelo, anywhere. The rule needs to be written down or it doesn't exist.
Enter Products Completely the First Time
The biggest source of catalog rot is incomplete data at the entry stage. Someone adds a product quickly, skips the supplier field, leaves the unit cost blank, and moves on. That incomplete record becomes a quiet landmine.
When you create a product entry, fill in every relevant field before saving it:
- Product name (consistent naming convention—always "Color + Product Type" or always "Product Type + Color," never both)
- SKU (following the structure you defined above)
- Unit cost and selling price
- Primary supplier and supplier SKU (their code for your product, which you'll need for purchase orders)
- Unit of measure (each, pack of 12, kilogram—be explicit)
- Reorder point and reorder quantity
- Storage location (shelf, bin, warehouse zone)
- Product category and any relevant tags
Yes, this takes five extra minutes per product. Those five minutes save you hours during every inventory count, supplier call, and order fulfillment run that follows.
Handle Variants Without Creating Chaos
Variants—size, color, material, flavor—are where catalogs fall apart fastest. If you sell a t-shirt in four colors and five sizes, that's 20 SKUs. Done wrong, you end up with 20 disconnected product records with no relationship to each other. Done right, you have one parent product with 20 child variants, each tracked independently but grouped logically.
The Parent-Child Model
In Pleelo's inventory module, you can create a parent product (e.g., "Classic Crewneck T-Shirt") and attach variants beneath it. Each variant carries its own SKU, its own stock count, and its own cost—but they're all visible together when you search for the parent.
This matters more than it sounds. When a client asks "how many crewnecks do you have in stock?" you want to see all variants in one view, not hunt through 20 individual records. When you run a low-stock report, variants that hit their reorder point surface automatically, linked to the right supplier.
The rule: if two items share the same base product but differ only by a single attribute, they're variants—not separate products. If they differ in function, material, or supplier, they probably deserve their own parent entry.
Set Reorder Points Based on Real Data, Not Gut Feeling
Most small businesses set reorder points once, at setup, and never touch them again. Then they're surprised when they stock out in November despite "having a system."
A reorder point should reflect: your average daily sales velocity × your supplier lead time + a safety buffer. If you sell 10 units per day and your supplier takes 7 days to deliver, your reorder point is at minimum 70 units—plus whatever buffer gives you peace of mind.
Revisit reorder points every quarter, or whenever you notice a meaningful shift in sales patterns. A product that moved 5 units a week in January might move 50 in October. Your catalog needs to reflect the current reality of your business, not the reality you had when you first set it up.
In Pleelo, you can set reorder points per SKU and configure automated alerts so you're notified the moment stock dips below threshold—no manual checking required.
Link Every Product to Its Supplier (and Keep That Link Current)
Carlos runs a small electronics accessories business in Monterrey. For two years, his catalog had products listed without supplier information because "everyone knew" which supplier handled what. Then his warehouse manager left. Suddenly, nobody knew. Reordering a batch of cables turned into a two-day investigation.
Don't rely on institutional memory. Every product in your catalog should have at least one linked supplier, including the supplier's product code, lead time, minimum order quantity, and last purchase price. If you have backup suppliers for critical SKUs, link those too and mark them as secondary.
This data pays off in three ways: faster purchase order creation, easier price comparison when renegotiating, and business continuity when your primary contact goes on vacation or leaves the company.
Audit Your Catalog on a Schedule
A clean catalog isn't a one-time achievement—it's an ongoing habit. Set a recurring task (monthly works for most SMBs) to audit for:
- Duplicate entries for the same product
- Products with zero movement in the past 90 days (candidates for discontinuation or promotion)
- Missing supplier links or unit costs
- SKUs that don't follow your naming convention (usually added in a rush)
- Reorder points that haven't been updated in over six months
A 30-minute audit every month prevents the kind of Friday-night chaos described at the top of this article.
How Pleelo Solves This
Pleelo's inventory module is built specifically for the catalog challenges SMBs face: variant management, supplier linking, automated reorder alerts, and a SKU system that scales with your business without requiring an IT team to maintain it.
"Before Pleelo, our product catalog was honestly embarrassing—duplicates everywhere, no logic to our SKUs, and reorder points that were basically guesses. We spent a weekend doing a full migration into Pleelo and set up everything properly using their template. Three months later, we haven't had a single stockout on our top 20 SKUs. The supplier linking feature alone saved us a day of work on our last big purchase order run." — Operations Manager, consumer goods distributor, Guadalajara
The structure is already there. You just need to fill it in correctly.
Get Started Today
Your inventory is only as reliable as the catalog behind it. Build it right, keep it clean, and your entire operation runs smoother—from purchase orders to fulfillment to year-end counts.
