Sourcing and range planning
Planning Your First Shoe Collection: Styles, Colors, Sizes and Scope
There is no fixed number of styles that makes a first footwear collection right for every startup. One brand may need a focused test of one direction; another may already have evidence for different customer needs. Begin with the role of each product, then review colors, sizes, construction, samples and launch information. A folder of reference images is not a release plan.
This guide concerns first-launch scope. It does not provide universal MOQ, manufacturing prices or sales promises. Use the shared quantity and cost guides for those separate questions.
Give every proposed style a job
Write one sentence explaining the user, use case and necessary difference from the other candidates. If two styles have no distinct job, assess whether they can become one direction. A new color still needs review of materials, artwork, samples and stock management; it should not be assumed to have no operational impact.
Visual consistency does not establish that lasts, soles or materials can be shared. Any reuse depends on the actual development, availability and permissions. Similar reference images are not proof of common tooling or production conditions.
Make the style-color-size matrix visible
The following arithmetic is illustrative, not a recommended release, size range, MOQ or available VyloxStep program. A combination means a saleable style-color-size variant, not a production quantity.
| Illustrative scope | Styles | Colors per style | Sizes per color | Combinations |
|---|---|---|---|---|
| Option A | 1 | 2 | 5 | 1 × 2 × 5 = 10 |
| Option B | 2 | 2 | 5 | 2 × 2 × 5 = 20 |
More combinations create more quantity, labeling, data and inventory decisions. The table does not mean development cost automatically doubles. Actual technical inputs and reuse opportunities need review. Its purpose is to expose tasks that can be hidden by a small headline style count.
Use a scope review table
| Area | Question | Decision record |
|---|---|---|
| Product role | Is the use clear and supported by relevant evidence? | Initial release, validate or defer |
| Construction | What is new, reusable or still unknown? | Owner and missing input |
| Variants | What supports each color and size range? | Estimate versus confirmed condition |
| Samples | Which differences require review? | Sample objective and approver |
| Channel handover | Who prepares labels, sizing, packaging and product data? | Dependencies and open tasks |
Choose the first round using evidence
Collect relevant research, audience feedback, reference comparisons and channel requirements. Likes or informal preferences are not purchase commitments. If evidence is limited, identify the question to answer through samples or appropriate research before treating a candidate as essential.
Place defined core directions in the first review, worthwhile but independent extensions in a later list, and unclear ideas in validation. Deferral should include a condition for reconsideration, not simply disappear into a forgotten folder.
An illustrative choice between two directions
Imagine everyday casual footwear with a clear brief alongside a light-outdoor idea whose use and performance requirements remain undefined. The brand could review the first while validating the second. This is a hypothetical decision method, not a recommendation that all brands begin with casual shoes or a claim that one category is faster or cheaper.
If evidence supports both needs, compare the technical inputs, sample-review workload and cash commitments for simultaneous development. The decision should fit the team's capacity, not a desire to make the website look full.
Freeze the first-round scope and control changes
- Version the matrix and identify included styles, colors, sizes and open fields.
- Put new ideas in a change register with affected decisions and files.
- Review feasibility, quantity conditions, cost and timing with relevant contacts.
- Approve and distribute an updated matrix, identifying superseded versions.
- Keep later extensions separate with clear entry conditions.
Before review, confirm that each style has a necessary role, combinations can be counted, unknowns have owners and launch-data tasks match the scope. Prepare the first-product brief, then check commitments with first-order budget preparation. Read the shared MOQ and order-mixing guide for quantity questions. Return to the startup footwear workflow with a clear release matrix.