You may already know what the webbing will be used for and have a few requirements in mind. Maybe the width and material are already decided. Maybe you have artwork, dimensions, or a reference sample. Or you may only have part of this information. That is a normal starting point for custom webbing development, and it raises an important question: how much do you actually need to know before discussing the project with a manufacturer?
Start with the product information and requirements you already know. Share the application, what the webbing needs to do, any known dimensions or performance requirements, and whatever artwork, drawings, or reference samples are already available. Specifications such as material, construction, thickness, or stretch can stay open when you are not yet sure what will work best. These are decisions that can be developed with the manufacturer rather than guessed in advance.
Read on to see what is useful to bring into the first discussion, what can stay open, and where manufacturer input can help move the webbing development forward.
You do not need every webbing specification confirmed before starting development. At this stage, the goal is not to complete the specification sheet. It is to separate what is already confirmed from what is still open for development.
Some requirements may already come from the product design, while others cannot be decided properly until the webbing construction is considered. Material, thickness, stretch, and construction can affect one another, so filling every blank too early can create specifications that later need to be changed.
For example, a ski goggle developer may already have several decisions in place:
Confirmed
Still Open
This is already enough to begin development. The confirmed requirements give the manufacturer a clear starting point, while the open specifications can be discussed and adjusted around the actual product application.
At this stage, don’t try to fill every blank. Mark what is confirmed, keep uncertain specifications open, and let those open points become part of the development discussion.
You do not need to create new specifications for this step. Start by looking at the information your product development has already produced and organize what is useful for the webbing discussion.
Most projects already have some useful information, even when the webbing itself has not been fully developed. This information usually falls into four areas:
Product application
Identify the finished product and where the webbing will be used in it. A product drawing, rendering, photo, or short description can already provide useful context at this stage.
Known dimensions or restrictions
Include dimensions or limitations already coming from the product design. This might be a required webbing width, available space, buckle or slot size, attachment point, or finished strap length. If a dimension is only an estimate, keep it as an estimate rather than treating it as fixed.
Performance or appearance requirements
Describe what the webbing needs to achieve rather than trying to convert every requirement into a technical specification. Softness, support, grip, stretch, water exposure, logo visibility, or a particular surface appearance can all be useful development requirements.
Existing development materials
Bring in what the project already has. Artwork, drawings, product renderings, reference photos, and physical samples can communicate the intended direction without requiring a finished webbing specification.
For example, a sports bra developer may already have the following:
The exact yarn, thickness, stretch percentage, and elastic construction may still be unknown. Those missing specifications do not make the existing information less useful.
Start with what the product development has already given you. Organize those known requirements and references first; the technical specifications that are still open can be developed with the manufacturer later.
When a webbing specification is still uncertain, start by describing what the webbing needs to achieve in the product. The technical value or construction can stay open until there is enough information to evaluate it properly.
A product requirement and a webbing specification are not the same thing. For example, “the strap needs to stay secure during movement without feeling too tight” describes the required result. The stretch level, thickness, and elastic construction are specifications that may be used to achieve that result. They do not need to be decided before the right construction has been evaluated.
For example, a headlamp developer may know that the strap needs to hold the lamp securely during running while remaining comfortable around the head. The developer may not know what stretch level or elastic construction will provide the right balance.
Instead of guessing, the project can be described as:
Known requirement:
The strap needs enough elastic movement for comfort while maintaining stable support during running.
Open specification:
The stretch level and elastic construction have not yet been decided.
The same method can be used for other unknown specifications:
This gives the manufacturer something meaningful to evaluate without locking the project into an unsupported technical choice.
When you do not know a specification, describe the requirement behind it. Keep the technical solution open until there is enough information to make that decision.
Naming the application is useful, but it does not fully explain what the webbing will experience in the product. Give the manufacturer enough context to understand where the webbing sits, what it interacts with, and what happens to it during normal use.
For example, saying “40 mm elastic webbing for ski goggles” identifies the product, but leaves many use conditions unclear.
A more useful description would be:
The 40 mm elastic strap wraps around a ski helmet, needs to stay in position during movement, and will be exposed to snow, moisture, cold temperatures, and sunlight.
Now the manufacturer has more information to evaluate the open specifications. The way the strap fits around the helmet may affect stretch and recovery decisions. Movement can make grip and stability relevant, while outdoor exposure needs to be considered when selecting the material and construction.
The same principle applies to other products. “Sports bra strap” is an application name. Describing it as a shoulder strap that sits against the skin, stretches repeatedly during movement, and goes through regular washing provides much more useful development information.
You can build a useful application description by answering three questions:
Where will the webbing be used?
Describe its position and role in the finished product.
What will it interact with?
Include skin, hardware, other fabrics, helmets, equipment, or other components that affect how the webbing needs to work.
What will happen to it during normal use?
Describe relevant conditions such as stretching, repeated loading, washing, sweat, water, sunlight, cold, or regular movement.
You do not need to decide what each condition means for the final specification. Describe the real use conditions first. The manufacturer can then use that information to judge which webbing specifications need attention during development.
Not every specification already in a project has the same meaning. Some choices are fixed because the product depends on them. Others are the current preferred direction and can still be reconsidered during development.
A requirement does not have to be a technical specification. “The collar needs to feel soft against the neck” can be a firm product requirement even when the material, thickness, and construction needed to achieve that feel have not yet been decided.
To separate requirements from preferences, ask two questions about each existing decision:
Why was this chosen?
Identify whether it comes from a product constraint, performance need, branding requirement, reference sample, or simply the current design direction.
What happens if it changes?
If changing it creates a problem with fit, function, performance, branding, or the intended product design, it should normally be treated as a requirement. If another solution could still achieve the same result, there may be room to treat the current choice as a preference.
For example, a pet collar developer may currently have 25 mm width, polyester, 1.5 mm thickness, a woven logo, and a soft hand feel in the project brief. After checking the reason behind each decision, the project might look like this:
Requirements
Preferences / Current Direction
This distinction gives the manufacturer a much clearer development boundary. The requirements show what the final webbing must preserve, while the preferences show where alternative materials, constructions, or specifications can still be considered.
For each existing decision, ask why it is there and what happens if it changes. Keep the true product constraints fixed, and leave room to evaluate better solutions where the current choice is only a preference.
Your current design gives the webbing project a direction, but it does not need to define every detail of the final webbing. Drawings, artwork, reference samples, and initial specifications can all be used as development inputs rather than final production instructions.
This is especially important when the design was created before the webbing construction was evaluated. A width may come from the finished product design. A material may have been selected from a reference sample. Logo artwork may have been created before considering how it will reproduce in woven webbing. These decisions are useful because they show the intended result, but they do not all need to remain unchanged.
For example, a developer submits artwork for a 50 mm elastic jacquard waistband with a three-color logo. The 50 mm width may be fixed by the garment design, and the three brand colors may need to stay. During manufacturing review, however, very small logo details may need to be simplified, while the elastic construction may need adjustment to balance stretch with logo clarity.
In this case, the development direction becomes clearer:
What should stay?
What can be adjusted?
What still needs to be confirmed?
The original design has not failed. It has simply moved from a design concept into manufacturing development.
Use the same three questions when reviewing your own current design: what should stay, what can be adjusted, and what still needs to be confirmed? This gives the manufacturer a clear target while leaving enough room to develop a workable webbing solution around the requirements that actually need to remain fixed.
Have your product requirements, specifications, or artwork ready? Share your project with us to discuss the next step in development.
We will contact you within 1 working day, please pay attention to the email with the suffix “@anmyda.com”.