The most common mistake in a custom hiking shoe RFQ is a single line: sturdy for heavy packs, please quote a stiffer outsole. It reads like a specification. It is a mood. One supplier pictures a daypack on a groomed trail, another pictures a multi-day carry with tent and stove, a third designs for scrambling, and three quotes come back priced against three different products nobody can compare line by line. The sample round then approves whichever shoe feels most convincing under a reviewer's thumb.
Put the backpack load band into the RFQ before anyone argues about stiffness, and keep stiffness as a question the supplier answers in writing. A brand's selection guide can tell you that pack weight should influence shoe choice. It cannot hand you a factory acceptance value, and treating it as one is how a sourcing spec turns into fiction.
Start With Backpack Load, Not Sturdy
Load band first. If you change one line this quarter, change this one: swap sturdy for three carrying conditions written in the buyer's own language and tied to the kit the hiker actually carries. That preference has a condition attached, and it only holds when every candidate states its own load assumption and its own check method in writing. Without those statements you have relabeled a vague word, not specified a product.
The three bands stay qualitative on purpose. A light daypack carries water, a shell and lunch, and the trip ends the same day. An overnight pack adds a sleeping bag, a pad and food for one night. A multi-day pack carries the tent, the stove and the food, which is the case where stability stops being a preference and becomes the thing you are buying. You do not need a kilogram figure to make the band usable; the kit list does that work, and the supplier converts it into a build proposal.
I checked two lines from Salomon's hiking-shoe selection guide side by side and noticed that both tie pack weight to shoe choice rather than to a stiffness number. One says the weight of your backpack will influence the choice of your hiking shoes. The other sends a tent, stove and food load toward more sturdy shoes for extra stability. Both are about matching the shoe to the carry, which is exactly the question I want a supplier to answer for its own build.
Turn Backpack Load Into Stiffness Questions
Stiffness becomes answerable only as three written questions. The first asks which load band the proposed shoe is intended for, named in the buyer's bands rather than in the supplier's adjectives. The second asks how the supplier defines or checks flex and stiffness for that band: what it looks at, and which part of the sole unit it evaluates. The third asks what evidence the supplier will put in front of you at sample review, in specific terms instead of a promise of good quality.
The failure mode here is quiet. A buyer treats an adjective as an answered question. Quotes get padded to cover the ambiguity, or the supplier nods at sample review and builds to its own internal standard, and you find out at the port.
On the second pass I looked for anything that behaves like a threshold and came back with a direction of travel: heavier carried kit pushes the design toward stability. So the RFQ keeps the direction and hands the number back to the supplier to state. Whatever it answers becomes a claim you can set against the next candidate's claim, which is all a sourcing spec needs to do at this stage.
Pair Load Bands With Terrain Conditions
Every load band needs a terrain line beside it. The same guide offers light and flexible hiking shoes as an option if the terrain allows, and that conditional does the real work: flexibility is not a global good or a global bad, it is a match to a surface. Ask whether the supplier's recommendation assumes a maintained trail, a rough trail, or something else, and write the answer next to the load band it came with. I saw the terrain condition attached to the flexibility advice, so I would not split those two fields in the RFQ.
Skip that field and the comparison collapses in a predictable way. A supplier recommending a light, flexible build for a fast overnight gets lined up against a supplier recommending a sturdy build for a tent-and-stove carry, and the buyer reads the second as more shoe and the first as underbuilt. Both answered honestly. They answered different questions.
Suppose a buyer is planning a short overnight on an easy trail. That buyer may deliberately accept a lighter, more flexible build and take the stability trade knowingly, which is a legitimate sourcing choice rather than a mistake. Suppose the same buyer later specifies a multi-day carry with tent and stove. Stability moves to the top of the open questions, and the supplier has to say how it checks for it. Neither case is a test result; both are conditions you write down before sampling so the sample review has something to check against.
Put Load Criteria on the Sample Form
A load band that lives only in the RFQ dies at sample review. Move five fields onto one approval line: the agreed load band, the terrain line, the stiffness question you asked, the supplier's stated check method, and the approve or reject decision with reviewer and date. Five fields, one row, no prose.
The consequence of skipping it is slow and expensive. Reviewers pass a sample on feel, pass it confidently, and months later nobody can reconstruct which carrying condition it was passed for. Then nobody can tell whether a production change sits inside or outside that approval, and the argument happens after the tooling is cut. A written row answers the same question in seconds.
In my own review sequence I check the load band and terrain fields before I score stiffness at all, and I have found that a blank field is more useful than a debated adjective. A blank forces the supplier to write something specific. An adjective lets everyone nod and move to the next line.
Separate Brand Guidance From Factory Evidence
Keep the two categories apart on paper. From the manufacturer guidance you can carry three ideas into the spec: pack weight influences shoe choice, a light and flexible option exists where terrain allows, and a tent-stove-food load pushes toward more sturdy shoes for stability. Those are selection principles, and they are worth carrying into the RFQ because they frame good questions.
What the factory owes you is the other column: its recommended load band for the proposed build, a description of how it checks stiffness for that band, whatever sample evidence it will show, MOQ, lead time, capacity evidence for your volume, and certification status for anything it claims. Where a candidate cannot answer, the honest outcome is an open item on the scorecard rather than a filled-in assumption. No quote, MOQ, capacity audit, lead-time commitment or certification report has been verified in what I describe here, and that gap stays visible until a supplier closes it.
I keep the two columns on one sheet: left side what the guide told me to ask, right side what the candidate has actually stated. Anything still blank on the right at RFQ close is a decision about risk, not a detail to sort out later.
Send Vague Sturdy Answers Back
When a supplier replies with only sturdy or reinforced, do not accept it and do not argue about it. Return one clarification that repeats the load band, the terrain assumption, the stiffness question and the sample-check method, then mark that line incomplete until it comes back answered. It is a procurement judgment, not a product test. You are not grading the shoe; you are refusing to grade an undefined one.
The effect shows up in the next round. Either the new quote is attached to the same carrying condition as the others and can be compared, or it is visibly incomplete and drops off the shortlist on a documented basis instead of a hunch. Both outcomes are progress, and neither requires you to invent a pass or fail stiffness number that nobody has evidence for.
Before you send anything today, open the RFQ and add three things: a load-band line defined by the carried kit, a terrain line beside each band, and the three supplier questions about intended band, check method and sample evidence. Then hold the RFQ until each candidate returns those answers, and log every missing MOQ, lead time, capacity figure or certification claim as an open gap rather than a footnote.
Leave a procurement comment