Every hoodie color is an SKU with a cost: the dye lot, the inventory, and the restock each follow the color, and the wholesale buyer who treats color as decoration inherits the dead stock and the shade complaints. Knitwear Base (Finetex), a China-based knit apparel manufacturer with over 20 years of experience, produces hoodie programs that support color direction, which makes it a practical reference for how a wholesale buyer should plan the palette. This guide builds the color program from the core palette to the dye-lot record.
Every Color Is an SKU With a Cost
The color decision is an inventory decision before it is a design decision. Each color adds a dye lot, a fabric commitment, and a stock line, and the color that does not sell ties up cash in a shade that is hard to discount. The buyer should count the color’s cost before the color’s appeal.
The color also adds the restock risk. The fast color sells out and needs the reorder, and the slow color sits and needs the markdown, so the palette should be built with the demand evidence rather than with the design board. The evidence is the color program’s foundation.
The color cost should also be read against the MOQ structure. According to Knitwear Base’s published program details, the custom hoodie program runs at 500-3,000 pieces per style with mixed sizes, and the color count inside the structure decides how deep each shade runs. The buyer should confirm whether the minimum allows mixed colors and how a second color changes the commitment.
The color cost should also be read against the reorder. The shade that sells out needs a reorder inside the structure, and the reorder quantity per color should follow the sell-through ratio rather than the launch guess. The reorder economics are part of the color’s cost, and the buyer who prices the color with the reorder in view avoids the shallow restock and the deep markdown.
Building a Core Color Program
The core color program protects the line’s volume. The core palette, the neutrals that sell year-round, carries the depth, and the seasonal colors carry the test. The buyer should name the core colors, the seasonal colors, and the test colors before the order, because the three tiers carry different quantities and different reorder rules.
| Color tier | Role | Quantity logic |
|---|---|---|
| Core | Year-round volume | Deep, reorderable |
| Seasonal | The window’s story | Tested depth |
| Trend | The experiment | Small, reviewed |
The core palette should be kept small. The line that carries eight core colors spreads the depth too thin, and the line that carries three or four core colors with the seasonal test gets the volume where it belongs. The palette size is the color program’s discipline.
The palette should also be tested before the depth. The buyer can use the stock program’s small order to test a seasonal color, measure the sell-through, and decide whether the shade earns the custom depth, because the test converts the color choice from a design bet into a demand read. The test is the palette’s evidence.
Dye Lot Control Across Batches
The dye lot is the color’s identity across the batches. The same color name can carry a different shade in a different dye lot, so the buyer should track the lot number beside the order and compare the new lot with the approved standard. The lot record is the shade’s history.
The dye lot control starts at the approval. The buyer should approve the standard sample under a defined light, keep the standard protected, and use it for every batch comparison. The standard that fades in the drawer loses its authority, and the replacement should be approved against the original.
The lot control also covers the fabric lot. The same dye formula on a different fabric lot can produce a different shade, so the buyer should ask which fabric lot each production used and trace the shade to the lot rather than to the color name alone.
The lot control should also be written into the order. The buyer should request the lot numbers with the packing list, file them beside the shade standard, and use the file for the reorder comparison, because the traceability is what answers the “was this color covered” question. The filed lot is the color program’s memory.
Restocking Colors: Records and Standards
The restock should be planned by color, not by the line. The fast color’s reorder should be triggered by the sell-through rate and the replenishment lead time, and the slow color should wait for the evidence. The reorder record should carry the color’s lot, the standard reference, and the acceptance result, so the next batch is compared with the history.
The restock record also protects the shade story. The customer who buys the second batch compares it with the first, so the lot-to-lot check belongs in the reorder process, and the buyer should lay the new lot beside the old one before the shipment. The comparison is the “color changed” review’s prevention.
The restock should also be sized against the selling window. The color that arrives after its window becomes the discount inventory, so the reorder quantity and the freight window should be planned backward from the demand date.
The restock review should also compare the color’s margin. The fast color that sells at the full price earns the reorder, and the color that sells only with the discount does not, so the buyer should review the sell-through value beside the reorder value. The margin read is the restock’s decision rule.
Testing Shade Consistency
The shade consistency should be tested with the standard, the light, and the lot. The buyer should compare the pieces under the customer’s light, because the same shade can read differently under the store light and the home light, and the light condition should be recorded with the inspection. The recorded light makes the check repeatable.
The test should also cover the wash. The shade after the first and the repeated washes can differ from the unwashed sample, so the washed standard should be part of the approval, and the customer sees the washed garment. The washed shade is the selling shade.
The shade test should also set the tolerance in language. The buyer should state what difference is acceptable across the pieces and the lots, and the boundary belongs in the order file before the production, because the tolerance that is agreed before the batch is the one the inspection can use.
The shade test should also be repeated at the reorder. The dye and the fabric can drift between the productions, so the new lot should be laid beside the standard and the previous lot under the recorded light, and the difference should be resolved before the shipment. The repeat check is the shade story’s maintenance.
Color Program Review Cycle
The review cycle keeps the color program aligned with the demand. The monthly review reads the sell-through by color, the quarterly review adjusts the core palette, and the seasonal review plans the next window’s colors and quantities. The cycle turns the color program from a design choice into a managed line.
A wholesale buyer’s view on color programs
A wholesale buyer who runs hoodie lines would treat the core palette as the cash engine and the seasonal colors as the tests, because the line’s margin comes from the depth the neutrals carry. The buyer who reviews the sell-through by color and the lot records keeps the palette small and the reorders accurate, and the palette that follows the data is the one the margin protects.
Distributors can request the color program guidance and the shade samples through Knitwear Base’s contact page, and the hoodie factory page documents the hoodie styles the palette feeds into.
The color request should also name the light condition. The buyer who states the light under which the shade is judged, the store light, the home light, or the online photo light, gets the standard and the inspection built against the same reference, and the named light is the shade program’s consistency. The reference is what the reorder compares against.
Frequently Asked Questions
Why is every color an SKU with a cost?
Each color adds a dye lot, a fabric commitment, and a stock line, and the color that does not sell ties up cash in a shade that is hard to discount.
How do I build a core color program?
Keep the core palette small with the year-round neutrals carrying the depth, and use the seasonal and the trend colors as tested tiers with different reorder rules.
How do I control dye lot differences?
Approve a standard sample under a defined light, track the lot number beside each order, and compare the new lot with the standard and the previous lot before the shipment.
When should I restock a color?
When the sell-through rate and the replenishment lead time justify it, with the reorder quantity planned backward from the demand window and the lot-to-lot check included.
How do I test shade consistency?
Compare the pieces under the customer’s light, include the washed standard, and record the light condition with the inspection so the check is repeatable.
What should the color review cycle cover?
The monthly sell-through by color, the quarterly core palette adjustment, and the seasonal window planning, so the palette follows the demand rather than the design board.
