How to Sort OEM Trail Running Shoe Samples by Distance

Change the midsole and the last on a trail shoe and you are not editing a sample, you are restarting one. New pattern card, another spec approval, another round of fit comments from three people who each ran the previous pair twice. The first sample becomes a reference on a shelf, and that round's cost buys you nothing you can sell. In sample rooms I keep meeting the same cause: the brief said trail running, all distances, so every band got one card and one set of sign-offs.

A distance-banded range costs more paperwork before the first quote and less rework after it. One all-round sample only looks cheaper because the second round has not been billed yet. A short-race shoe is judged on weight and response; an ultra shoe is judged on protection and cushioning. The spec lines that make the first one work are the lines that make the second one wrong.

One sample for every distance costs real money

The rework lands in three places: the midsole, the last, and the outsole tooling. In most trail constructions those three are tied to the upper pattern, so raising the stack for cushioning and opening the last for a longer-distance foot invalidates the pattern you already approved. Colorways get re-reviewed on a shape that no longer matches. QC reopens comments it had closed. A supplier starts a tooling conversation it thought was finished.

There is a second cost that never shows on an invoice. When one card covers a short-course race shoe and an ultra shoe, the approval line reads approved, and nobody can say what was approved. Two seasons later nobody can point to why a sample was rejected or passed, because the card never carried the band in the first place.

Build the distance matrix before the first quote

Order matters more than the matrix itself. Start by defining the use bands: a distance range plus how often the runner trains per week. Write each band onto its own spec card with the band name in a fixed field. Send the request for quotation and the sample request band by band, not as one bundle. Approve samples band by band. Lock the assortment last.

Reverse the first two steps and every quote comes back as we can make all of these. That sentence is not a quotation, it is a claim, and it makes two suppliers incomparable because each one priced a different reading of your brief. The same factory can answer the same brief two ways in the same week, once with a light race shoe and once with a cushioned trainer, when nothing on the paper says which band is being asked about.

What Salomon's distance guide covers and misses

Salomon's own trail-running selection guide is the cleanest public example of band boundaries. It puts shoes for runs under 15 km in the lightweight and responsive group, points 25 to 50 km at classic all-round models, and says that beyond 50 km and on ultra trails you want built-in protection and cushioning for comfort. Two things are worth taking from that. The boundaries give you something concrete to argue about with a supplier instead of adjectives. The vocabulary, lightweight and responsive, all-round, protected and cushioned, is the same vocabulary that should appear on your spec cards.

What the guide does not do is vouch for anyone's factory. It is a brand's advice to runners about picking a shoe, written for the buying side of the market. It says nothing about minimum order quantities, tooling ownership, monthly capacity, lead times, or test reports, and it does not cover the stretch between 15 and 25 km. Treat it as a way to phrase design questions, not as a performance claim for a bulk order.

Turn each band into lines the factory can answer

Every band needs its own answerable lines. For the light and responsive band, the questions are about the midsole compound and the stack, the last volume, outsole rubber hardness and lug depth, upper material, and how much structure sits in the heel. For the all-round band, ask about outsole abrasion choice, midfoot wrap, toe cap construction, and lining. For the protected and cushioned band, ask about the rock plate or its equivalent, the toe bumper, how the cushioning layer is built, and whether the shoe takes gaiters.

Ask each of those as a question with a reason attached: what do you propose for this band, and what does it do to the other two lines. Leave the values empty. The moment a buyer fills in a number from a different shoe, the supplier quotes to that number and both sides stop thinking. Every value on those cards has to come back confirmed item by item by the supplier you are actually going to use.

What I check in the sample room before approval

I lay the tech pack next to the returned sample and start with the band field. More often than I would like, I find it blank, or I find one card used for all three bands with the construction swapped by hand. So the first check is documentary: does this sample claim a band, and is it the band that was ordered.

Then I check whether the construction matches the claim. A sample ordered as a light race shoe that arrives with a deep lug pattern and a stiff toe bumper has drifted into the ultra band, whatever the label on the box says. I write the mismatch on the card, photograph the card and the shoe together, and send it back with the line that failed. Arguing over email about which band a shoe belongs to wastes a week; a marked card ends it in one message.

What I do not do in that room is judge cushioning or durability by hand. Squeezing a midsole tells me nothing I can defend to a QC file. Those calls wait for whatever test protocol the supplier can actually provide, and until then they stay open questions.

Ask these when the spec sheet comes back blank

When the spec sheet comes back with gaps, the gaps are the agenda. Ask for the minimum order quantity per band and per size run, since those are usually different numbers. Ask what quantity the quoted unit price is based on. Find out who pays for tooling and who owns it after the order ends. Ask for monthly capacity on this specific construction, not for the factory in general. Get the lead time counted from sample approval, not from deposit. Ask which certifications the supplier holds and can put in front of you, and for test reports tied to the exact construction you are ordering.

None of that exists in anything I can hand you today. There is no quote, no capacity audit, no lead-time commitment and no certificate behind this article, so each of those is an open question with a name on it rather than a default you can assume. A supplier who answers four of six in writing is easier to work with than one who answers all six on a call.

Training frequency reshuffles the bands more than price

Weekly mileage moves the band. Price does not.

A runner who goes from two short sessions a week to a long-distance block changes what the shoe has to do. It has to carry more protection and more cushioning, it can afford more weight, and the upper has to survive more hours per outing. The price a buyer is willing to pay inside a band moves far less, so using cost as the first cut pulls every band toward the same target and quietly under-builds the long one.

Suppose a buyer builds a range around one landed cost and lets the bands fall where they may. The light shoe comes out fine, the all-round shoe comes out acceptable, and the ultra shoe comes out as a heavier all-round shoe with a thicker insole. That is not a band, that is a colorway of the same idea. Frequency decides the band. Price decides the order inside it.

Who should not sort trail shoes by distance

One case should skip all of this. If your line is a single short-course race shoe and you replenish once a season from stock, a full distance matrix is paperwork you will never amortize; one solid all-round model, reviewed once, serves you better and lets you spend the attention on fit. The method pays off for buyers carrying more than one distance band at the same time, and for QC teams willing to confirm spec lines one at a time instead of approving a sample because it looks right on the table. If a supplier cannot put the band question on paper, that is your shortlist running short, not a reason to go back to one all-round shoe.