How to Manage Multiple SKUs Without Chaos
Complexity grows faster than SKU count, because every SKU multiplies records, minimums and decisions. A structure set up at five SKUs holds at twenty. One improvised at five collapses at twelve.
Why Complexity Compounds
This guide is for growing supplement, Ayurvedic and herbal brands in India.
Each additional SKU adds a specification, a stability study, an artwork file, a packaging minimum, a batch record stream, a set of certificates of analysis, a listing on each channel, and a share of attention. None of that is difficult individually, and together it compounds.
The practical result is familiar: by around a dozen SKUs, nobody is certain which artwork version is current, certificates of analysis are filed inconsistently, some products have not been reviewed in a year, and two SKUs are quietly loss-making.
Setting up structure early costs little. Retrofitting it across twenty SKUs is a project.
The Structure Worth Setting Up
Six elements, each simple.
- A consistent SKU naming and coding convention, covering product, variant and pack size, used everywhere including with your manufacturer.
- A product file per SKU with the same four sections: regulatory, product, evidence, commercial.
- A single master list of all SKUs with status, pack size, current artwork version, current specification version and manufacturer.
- A batch log per SKU recording key assay and quality values over time.
- A shared component register: which containers, closures and cartons are used across which SKUs.
- A review cadence: every SKU looked at on a schedule, not only when something goes wrong.
Share Components Deliberately
This is the single most effective complexity reducer.
| Shared Element | Benefit |
|---|---|
| Same container across SKUs with different labels | One packaging minimum serves several products |
| Same closure and liner | Fewer components to stock and specify |
| Same outer carton size | Simpler shipping and lower minimums |
| Same pack sizes across the range | Consistent duration logic and reorder rhythm |
| Same capsule size and shell | Fewer variables in production and specification |
| Same testing panel structure | Easier certificate review and batch logging |
Component sharing also reduces write-off risk, because a container used by four SKUs is unlikely to become obsolete when one of them is discontinued.
Reviewing and Discontinuing
The part most brands avoid.
Review on a Schedule
Look at every SKU at least annually: sales, reorder rate, contribution, complaint rate and whether its documentation is current.
Judge on Contribution and Reorders
A SKU with low volume but strong reorders may be worth keeping. One with volume and no reorders usually is not.
Count the Hidden Cost
Each SKU consumes packaging minimums, stability work, listing maintenance and attention. A marginal SKU is more expensive than its margin suggests.
Discontinue Properly
Run down stock, remove listings, archive the product file rather than deleting it, and keep records for the shelf life of units still in the market.
Archiving rather than deleting matters: you may receive a complaint about a discontinued product within its shelf life and will need the batch records.
Checklist
Set this up before it is urgent.
- Define a consistent SKU naming and coding convention.
- Use the same codes with your manufacturer and on every channel.
- Create a product file per SKU with four consistent sections.
- Build a master SKU list with status and current versions.
- Record artwork and specification version numbers centrally.
- Keep a batch log per SKU of key values.
- Maintain a shared component register.
- Plan new SKUs to share containers and closures where possible.
- Standardise pack sizes and capsule formats across the range.
- Review every SKU at least annually on reorders and contribution.
- Discontinue marginal SKUs deliberately rather than letting them linger.
- Archive rather than delete files for discontinued products.
- Run the fifteen-minute test on a random SKU twice a year.
Planning a Range Rather Than a Product?
Share your intended range and our team will advise on shared components and minimums across SKUs.
Frequently Asked Questions
Why does SKU complexity compound?
Because each one adds a specification, stability study, artwork file, packaging minimum, batch record stream, certificates of analysis, channel listings and a share of attention. Individually manageable, collectively it overwhelms an improvised system.
What is the most effective way to reduce complexity?
Sharing components: the same container across SKUs with different labels, the same closure, carton, pack sizes and capsule format. It cuts packaging minimums, simplifies specification and reduces write-off risk when a SKU is discontinued.
How do I know my structure is adequate?
Pick a SKU at random and try to produce its current specification, current artwork, latest certificate of analysis and twelve months of sales within fifteen minutes. If you cannot, the structure needs work.
How should I decide whether to discontinue a SKU?
On reorder rate and contribution rather than revenue, and counting the hidden cost: packaging minimums, stability work, listing maintenance and attention. A SKU with volume but no reorders is usually worth discontinuing.
Should I delete files for discontinued products?
No, archive them. You may receive a complaint about a discontinued product while units remain within shelf life in the market, and you will need the batch records, certificates and specification to respond.