SKU Management for E-commerce: The Complete Guide
Master SKU naming conventions, inventory tracking, and batch processing. Learn 5 essential SKU best practices that save time and reduce shipping errors.
Introduction
You're managing inventory across multiple sales channels. Orders come from Amazon, Flipkart, Meesho, your own store. Each platform uses different product identifiers. Tracking which SKU maps to which product becomes a nightmare without a solid system.
A proper SKU (Stock Keeping Unit) management system is the backbone of efficient e-commerce operations. It ensures accurate inventory tracking, reduces fulfillment errors, and streamlines shipping label generation.
Why SKU Systems Matter for Your Business
- Tracks physical inventory accurately across warehouses
- Links orders to correct products automatically
- Prevents overselling and stockouts
- Simplifies return and refund processing
- Enables better sales analytics and forecasting
- Reduces fulfillment errors and customer complaints
- Scales operations without hiring more staff
Understanding SKU Basics
What is a SKU? A unique code that identifies a specific product variant in YOUR inventory. Not assigned by platforms. You create it. SKU vs ASIN SKU is YOUR internal code. ASIN is Amazon's code for the same product. Different platforms use different identifiers. Why You Need Both SKU for internal tracking. ASIN/UPC/Platform IDs for uploading to sales channels. They work together.
SKU Naming Conventions: Best Practices
- Example: SHIRT-RED-M (Shirt, Red, Medium)
- Example: JEANS-BLACK-32 (Jeans, Black, 32-inch)
- Best for: Simple product catalogs
- Drawback: Runs out of codes if you have many variants
- Example: LV-PROD-8734 (LV is manufacturer, 8734 is their code)
- Example: NIKE-BL-MID-12 (Nike Black Mids size 12)
- Best for: Resellers and wholesalers
- Drawback: Depends on supplier consistency
- Example: PRD-001, PRD-002, PRD-003
- Example: SKU-2026-0001, SKU-2026-0002
- Best for: New sellers or when inventory grows
- Drawback: Doesn\t show what product is from code alone,
Best Practice for Indian E-commerce Sellers Use Format 1 (Category-Code) + sequential number. Example: SHIRT-001, SHIRT-002, JEANS-001. Easy to scan, understand, and scale.
Format 1: Category-Color-Size (Simple)
Format 2: Manufacturer-Code (Supplier)
Format 3: Sequential Code (Growing Inventory)
SKU Generation: Manual vs Automated
- Create SKU in a spreadsheet before uploading to platforms
- Best for: <100 products
- Time required: 5-10 minutes per product variant
- Risk: Human error, inconsistent naming
- Use a SKU mapper tool to generate codes in bulk
- Upload your product list (CSV with product names, colors, sizes)
- System generates consistent SKUs automatically
- Best for: 100-1000 products
- Time required: 2 minutes for 100 products
- Connect inventory management system to sales channels
- Platforms auto-generate SKUs based on rules you set
- Best for: 1000+ products or multi-channel sellers
- Tools: Shopify, WooCommerce, Fulfilio, Zoho Inventory
- Time required: Initial setup 2-4 hours, then automatic
Manual SKU Assignment
Batch SKU Generation (Better)
Automated SKU Integration
SKU vs ASIN vs UPC: Know the Difference
- SKU: Internal warehouse and inventory management
- ASIN: Uploading products to Amazon, tracking Amazon sales
- UPC: Selling in retail stores, creating barcodes for products
- Use all three: Large sellers selling across online and offline channels
SKU Your internal code. Created by you. Used for your inventory tracking. ASIN (Amazon) Amazon's code. Auto-assigned. Identifies product on Amazon. Same ASIN = same product. UPC (Barcode) Global barcode. 12 digits. Retail standard. Scanned at checkout.
Inventory Integration: Connecting SKUs to Your System
- Create SKU - Decide naming format and create codes for each product variant
- Upload to your system - Add SKUs to inventory management software (Zoho
- Shopify
- WooCommerce
- manual spreadsheet)
- Stock initial inventory - Enter opening stock quantities for each SKU
- Configure platforms - Link SKUs to Amazon ASIN
- Flipkart product IDs
- etc.
- Set auto-sync - When stock decreases for one SKU
- all channels update automatically
- Monitor stock levels - Get alerts when SKU hits reorder point
- Generate shipping labels - System automatically uses SKU to pull correct product details
- Shopify: Built-in SKU field, sync with all apps
- WooCommerce: SKU support + plugin for multi-channel sync
- Zoho Inventory: SKU + automatic channel inventory updates
- Fulfilio: Specialized for Indian e-commerce (Flipkart, Amazon sync)
- Microsoft Excel: Manual but free for small sellers (<100 SKUs)
Common SKU Management Mistakes
Mistake 1: No System (Using Platform IDs Only)
Mistake 2: Inconsistent Naming
Mistake 3: Too Long or Complex Codes
Mistake 4: Not Syncing with Inventory System
Relying on ASIN or Flipkart product IDs instead of creating your own SKU. Problem: When you sell on multiple platforms, same product has different IDs. You can't track total inventory.
Creating SKUs with different formats. Example: SHIRT-001, ShirtRed02, T-SHIRT_M. Makes tracking impossible. Fix: Decide on one format and stick with it.
Creating SKUs like PROD-2026-APRIL-SHIRT-RED-MEDIUM-VARIANT-3. Hard to remember and type. Keep it under 12 characters.
Creating SKUs in Excel but not in your actual inventory software. Leads to mismatches and overselling. Always sync SKUs with your system of truth.
SKU Management Tools
- SKU Mapper (Free): Generate batch SKU codes from product list
- Zoho Inventory: Full inventory + SKU + multi-channel sync
- Shopify: Built-in SKU field + app marketplace for automation
- Google Sheets + Apps Script: Advanced automation (coding required)
- Fulfilio: Designed for Indian sellers, supports Flipkart + Amazon sync
Implementation Checklist
- Choose SKU format - Decide on naming convention (category-code recommended)
- Create master list - Add all current products with assigned SKUs
- Upload to platforms - Add SKU field to Amazon
- Flipkart
- Meesho listings
- Set up inventory system - Add SKU codes to your inventory management software
- Map platform IDs - Link your SKU to each platforms product ID, Test fulfillment - Process 5 test orders and verify correct products picked, Document and train - Write down your SKU system for team reference, Monitor and refine - Review system monthly and adjust if needed,
SKU Mapper Tool
Use SKU Mapper Tool →FAQ
Q: Can I change SKUs after creating them?
Q: How many SKUs should I have?
Q: What if I sell on platforms that don't support custom SKU field?
Q: Should SKU contain product cost or price?
Not recommended. Changing SKU breaks inventory links. If you must change, do a one-time migration with clear documentation.
One SKU per unique product variant. If you have Red T-Shirt in sizes M, L, XL—that's 3 SKUs. This enables accurate inventory tracking.
Maintain your own mapping file linking your SKU to each platform's product ID. Update when syncing inventory.
No. SKU should only identify the product. Use a separate system for pricing and cost. Keeps data organized and changeable.
Conclusion
"I spent 3 hours creating SKU codes for my 500 products. It saved me 5 hours per week in inventory checking for the next 2 years. Best time investment ever."
SKU management is not complex—it's just a naming and tracking system. But it's critical for scaling. Without it, you're stuck managing inventory manually forever. With it, you can 10x your business without increasing headcount.