OEM Bike Parts RFQ: Anchor Every Spec to the Assembled Bike

I checked a draft OEM bike parts RFQ for a US private-label program last month. The drawing package was the strong part: dimensions tight, tolerances called out, materials and finishes named. The only line about the bicycle itself asked the supplier to attach a compliance certificate, and nothing in the document said which bike these parts were going on, or how the finished units would reach the retailer.

That gap gets expensive in a predictable order. The supplier quotes to the part on the drawing, the buyer approves a sample against the same drawing, and the mismatch surfaces at final assembly or at the first retail shipment, when a change order costs money and the season is already booked. The fix is document order, not more paperwork. The assembled bicycle configuration belongs above every part dimension, because the rule governing these products attaches to the bicycle as offered for sale, not to a lever or a chainring standing alone.

Where OEM Bike Parts RFQs Usually Break

The pattern repeats. A buyer opens with part number, drawing revision, finish and packing count, then closes with a request for a compliance certificate. No host bike. No assembly state. That omission survives the quoting stage, which is why it keeps happening.

The supplier is not being careless when it quotes to the drawing. It answers what was asked. The quote comes back clean, priced to the material and finish on the sheet, and the buyer reads that as confirmation of a specification nobody wrote down. What was needed was a statement of the assembled configuration the part belongs to. I noticed this on a second read of the same draft: four pages of part data, not one word about brake family or drivetrain.

Every later question inherits the defect. Sample approval criteria get written at part level, so a lever that passes its dimension checks can still end up somewhere a rider cannot reach in a normal riding position. Then someone adds a line asking the supplier to confirm the parts are compliant, which is a question the supplier cannot answer about a bicycle it has never seen.

Name the Bike Before the Part

Build a header block ahead of the part table, and make the first fields bicycle fields: host model, model year, frame size, brake type and lever family, drivetrain configuration, and the condition the bikes are offered for sale in, meaning fully assembled, partially assembled, or loose parts on their own.

The reason for putting that block first is in the rule text itself. A bicycle offered to consumers in disassembled or partially assembled condition still has to meet the requirements after assembly according to the manufacturer's instructions. The configuration is therefore not background colour. It is the object being regulated.

Keep the boundary visible in the document too. This is a bicycle-level requirement. It is not a part certificate, and it is not a road-use approval, so no RFQ line should describe a bracket or a crank as certified on the strength of it. What this block does is define what everyone is talking about, so the spec lines that follow have something to attach to.

Turn Lever Position Into a Spec Line

The lever wording is short: hand lever mechanisms have to sit on the handlebars where a rider in a normal riding position can reach them. In an RFQ that sentence is dead weight until you pin down what a normal riding position means for this bike, and on this bike it is the frame geometry, bar width, stem length and sweep you already listed in the header.

Write it as a line the supplier can answer and you can accept or reject. Ask where the levers are set on that specific host configuration, and require the declaration to name the host model and model year. Then make it a sample-approval criterion: the sample is checked on the specified bar and stem, with the levers in the delivered position, against a rider position you define in the document rather than one someone eyeballs at the bench.

I re-read a supplier declaration last quarter and found it said the lever was compliant, with nothing else attached. There was nothing to accept and nothing to reject. A declaration that does not name the bicycle is a sentence, not a specification. What you want is a written statement plus a sample check, and you should not invent reach numbers to fill the space; those figures come from the specific model data and from whatever both sides sign off at sample approval.

Write the Chain Check on the Assembled Bike

The chain requirement is one sentence: the drive chain shall operate over the sprockets without catching or binding. Read what condition it describes. A chain over sprockets only exists on an assembled bike. Put the check in those terms in the RFQ: chain fitted to the specified chainring and cog combination, on the host bike's rear spacing, run through the gears.

A part-level tolerance sheet does not discharge that line. Chainline, cog spacing and hanger alignment can each sit inside its own allowance and still bind once they are combined. So ask the supplier to state which chainring and cog combination it intends to supply against, and to confirm the check is made assembled rather than on a bench with the chain lying beside the frame.

Do not convert the sentence into a chainline figure, a tension value or a wear limit. Those numbers are not in hand, and inventing them creates a specification the supplier gets measured against by accident. Ask the question, then record the answer as a question closed, with the model it applies to written beside it.

Put the Assembly State in the PO

Shipping state belongs on the purchase order, not in an email thread that nobody opens at goods-in. Three fields carry it. One records assembled, partially assembled or loose parts. One names whose assembly instructions travel with the goods and which revision. One is the sign-off for who performs the final assembly check on arrival.

Suppose a US buyer takes a partial shipment and only then finds the supplier's instruction sheet is revision C while the RFQ referenced revision A. The assembled-condition lines now point at a document that is not in the carton, and nobody can say whether the lever position in the box matches the one that was approved. That is not a filing annoyance. It is the difference between a configuration you can check and one you cannot.

I put a name against the arrival check, not a department. When the shipping-state field says partially assembled and the sign-off is blank, the goods sit in receiving while the team argues over who owns the assembly step.

Questions to Send Instead of Guessing

Some fields should be sent out blank on purpose. Custom capability and available tooling, minimum order quantity, unit price, lead time, inspection or batch records, and a written statement of the assembled configuration each part is intended for. All of those are questions for the supplier. None of them should be pre-filled with a plausible number, and none should be worded as something the buyer has already verified.

I left those fields empty in the last template I revised, and the replies were more useful than any estimate I could have typed in. Imagine one supplier flagging a mould change for your frame size while another quotes as if your frame fits an existing tool; that difference is worth seeing before any price is quoted. A blank with a question attached is a working document. A guess is a liability that reads like a specification.

Keep the gaps visible in the version you send. If an answer arrives on a call, write it next to the question and note who said it and when. The RFQ is the record, and a record with a visible hole beats one smoothed over.

Check Order Before the RFQ Goes Out

Before the document leaves my desk I run one order over it. First the host bicycle block, complete with model year and frame size. Then the shipped assembly state and the owner of the assembly instructions. After that the lever line and the chain line, each tied back to that host configuration by name. Last, the gap questions, still marked open and still unanswered.

Two signals mean stop. Any line that calls a part certified without naming the bicycle, because that is a claim the document cannot support. And any reference to assembly instructions with no revision attached, because that reference cannot be checked against what actually ships.

If I could confirm only one thing before the PO goes out, it would be the shipping-state line: whether the goods arrive as assembled bicycles, partially assembled, or loose parts, and whose instruction sheet travels with them at which revision. The lever placement criterion and the chain-over-sprocket check only mean what you think they mean once that answer is written down, because a configuration you cannot name is a configuration you cannot accept.