Direct answer
Use stock shades to move fast on first drops; use custom dye when brand colour continuity matters. Stock usually lowers fabric friction; custom raises lab-dip time and fabric MOQ. Garment programmes still need a clear style/colour MOQ — at ELEVIA typically from 150 pieces per style per colour — plus dye-lot tolerance on the PO. For procurement: freeze the measurable checks (GSM or construction, wash protocol, branding method, MOQ from 150 pieces per style per colour, remake timing approximately 7–9 working days after confirmation, and Incoterm preference) on one commercial sheet before deposit. Adjective-only briefs reopen sampling. Sample-led OEM means no shelf stock pretending to be development — remake, approve, then open colour. That sequence protects both calendar and claim risk across UK, EU, US and AU programmes. If marketing pressure asks to skip a gate, record the refusal in writing; the season review will thank you when shade, fit or documentation holds.
Programme figures: Company facts · Service page · Citation map.
| Topic | Stock shade | Custom dye |
|---|---|---|
| Speed | Faster to sample | Lab dips + longer lead |
| Colour control | Mill running shade | Brand-owned standard |
| Fabric MOQ | Often lower | Often higher |
| Best when | First drop / library | Signature brand colour |
Stock colour path
Stock or running shades move faster and often clear lower fabric MOQ. Ideal for first drops and library styles when brand colour can flex. Garment MOQ at ELEVIA still starts from 150 pieces per style per colour once fabric is locked.
Custom dye path
Custom dye protects brand colour and season continuity, but adds lab-dip rounds, higher fabric MOQ and longer lead. Use when shade is a brand asset — not a preference.
Risk trade-off
Stock is faster but shade can drift across seasons. Custom is slower but controllable. Write dye-lot tolerance into either path.
Buyer decision rule
If the brand sells on exact colour match across categories, budget custom dye. If speed-to-sample matters more, start stock and migrate later.
Two MOQs that buyers keep conflating
Fabric MOQ and garment MOQ are different commercial floors. Stock or running shades often reduce fabric friction and speed sampling; custom dye raises lab-dip rounds and fabric MOQ to protect brand colour. At ELEVIA, garment programmes still typically start from 150 pieces per style per colour once fabric and block are locked. Writing “low MOQ” without saying which floor you mean is how quotes disappoint both sides.
When stock shade is the rational choice
First drops, library styles, and programmes where brand colour can flex within a family benefit from stock. Speed to remake sample and faster bulk booking matter more than perfect pantone continuity. Accept that mill running shades can drift across seasons — write dye-lot tolerance into the PO and keep a sealed reference if you reorder. Stock does not mean zero shade risk; it means faster risk with different controls.
When custom dye is worth the calendar
Signature brand colours, multi-category continuity (tee, short, layer in one drop) and retailers who reject visible lot drift need custom dye. Budget lab dips, longer lead and higher fabric MOQ. Seal a physical standard. Do not open custom dye to “fix” a weak fabric platform — recovery and pilling problems survive any dye path. Fix the platform first, then own the shade.
Sampling, QC and migration paths
Library remake (approximately 7–9 working days after confirmation) can run on stock while you decide whether season two needs custom. Migrating later is a new colour approval — never assume continuity. QC should check crocking and wash on darks regardless of path. For EU-bound programmes, scope chemical docs per order; dye path does not replace compliance language.
RFQ language that prevents rework
State stock vs custom preference, target colour or pantone, quantity band, whether shade continuity across seasons is required, and garment MOQ expectations separately from fabric MOQ. Attach a sealed standard if custom. If you are actually comparing finished stock garment platforms versus private-label OEM, that is a different insight — do not bury it inside a dye-path decision.
Worked example for a first gym drop
A first men’s tee + short drop often runs stock shades on library blocks to clear sampling and 150 pieces per style per colour colour quickly, then migrates the hero brand colour to custom dye in season two once sell-through justifies fabric MOQ. That sequence beats opening custom dye on every SKU before the athlete has touched a remake sample. Write the migration plan into the seasonal brief so finance and brand share one expectation. Document dye-lot tolerance on both seasons so QC is not arguing from memory when the second lot arrives slightly warmer or cooler under store lighting.
Common mistakes
- Assuming stock has zero shade risk
- Opening custom dye without a sealed standard
- Confusing fabric MOQ with garment MOQ
Buyer advice
- State stock vs custom on the first RFQ
- Keep a physical shade standard for custom programmes
- Align fabric MOQ and garment MOQ on one commercial sheet
- Separate fabric MOQ from garment MOQ on every quote
- Seal a physical shade standard for custom programmes
- Treat stock-to-custom migration as a new colour approval
- Do not use custom dye to mask a weak fabric platform
Buyer FAQ
Questions procurement usually asks next
Can I start stock and switch to custom later?
Yes. Treat the switch as a new colour approval — do not assume continuity.
Does custom dye fix poor fabric quality?
No. Dye path does not repair weak recovery or pilling. Fix the platform first.
What should the RFQ include?
Target colour (or pantone), quantity band, stock-vs-custom preference, and whether shade continuity across seasons is required.
Evaluate styles
From this insight → library products
Open a sample path on a live block — then confirm fabric platform and MOQ on the RFQ.
Downloadable library summary: Lookbook PDF. Lab formats: QC specimens hub · Legal entity: Guangzhou Elevia Apparel Technology Co., Ltd.


