
How We Work · Private Label & OEM
A defined path from feasibility to replenishment.
Every program moves through the same six stages, whether it is a first sock or a transferred tech pack.
This page covers how a program moves through Runway Knitting: the six stages from feasibility through development, sampling, approval, production, and replenishment. It is written for private label and OEM buyers who want to know what is expected of them at each stage. Every stage runs in our Rainsville, Alabama facility.
Process
The six-stage program process
Each stage has a defined output. A program does not advance until that output exists.
- 01
Feasibility
We review what you want knit against what the equipment, yarn, and finishing can actually hold. This is where construction, size run, and end use get pressure-tested before anyone commits time or tooling. If something in the brief will not knit the way it is drawn, you hear it here rather than after sampling.
- 02
Development
Construction decisions get written down: gauge, yarn selection, zone placement, cuff and toe treatment, finishing method. Where a spec is missing we propose an option and explain the trade-off it carries. The output is a build sheet the floor can run from. Programs are built in Lonati's ORION software, and you can review the design in 3D on a shared call before a sample is knit.
- 03
Sampling
Samples are knit on machines on the knitting floor, and the R&D office opens straight onto that floor, so what you hold is representative rather than a mock-up. Sample rounds and acceptance criteria are agreed before development.

- 04
Approval
An approved sample and a written spec become the reference for the program. Packaging, labeling, and origin wording are confirmed at this point alongside the product itself. Nothing enters production scheduling until the approval record is complete.
- 05
Production
Production runs only after samples are made, expectations are set, and you agree to them. Knitting, wet processing, boarding, inspection, and packing all happen in the same building.
- 06
Replenishment
Repeat runs work from the approved spec, so the second order is not a new development cycle. Share a forecast and we plan yarn and scheduling against it. Changes to a running program are handled as controlled revisions, not silent substitutions.



New Brand
Launching a new brand
For founders and teams bringing a first sock program to market. You do not need a finished tech pack to start; you do need a clear picture of who the product is for and what you are prepared to invest to develop it.
Readiness checklist
- Intended user and price position
- Initial quantity estimate
- Target launch window
- Reference products
- Artwork
- Budget for sampling and first production

Full-custom development
Every element is developed to your spec: construction, yarn, zones, finish, and packaging. It produces a product nobody else sells, and it asks for more sampling rounds, more decisions from you, and a longer runway before first production.
What a usable brief contains
Who wears it, what it has to do, one or two reference products, the height and size run you want, your artwork in a workable file, and an honest quantity and timing estimate. That is enough for us to review feasibility and come back with real questions.
If parts of that are still open, send what you have. Most first programs arrive incomplete, and the feasibility conversation exists to close the gaps rather than to screen you out.

Established
Established brand or medical program
For brands moving an existing product, adding capacity, or running a program with defined documentation requirements.
Tech-pack transfer
You send the existing pack; we read it against our equipment and flag anything that translates differently on our machines.
Spec validation
Measurements, yarn callouts, and tolerances are confirmed against a knit sample rather than assumed from paper.
Forecast review
Expected volume and cadence are reviewed so yarn and machine time can be planned against real demand.
Pre-production approval
Samples are made and expectations are set, and production runs only after you agree to them.
Replenishment
Repeat orders run from the approved spec on a known setup, which is what keeps repeat product consistent.
Supply continuity
Yarn sourcing, substitutions, and revision control are handled as documented changes so a program does not drift over time.
Quality
Quality as process
Quality requirements are defined per program and confirmed during technical review before production begins, rather than published as a general sequence.
Reference samples and program records for every style, new and old, are kept in the QC room, a separate room where testing is done on a stretch tester, a lab oven, and a light box.


Request for quotation
Start with a feasibility review.
Send your product, quantity, timing, and development status. We review manufacturing fit first and come back with the questions that move the program forward.
Start an RFQPrivate label and OEM only