Road and MTB Frame Sourcing Guide for Dealers

Choose the platform before the model

Road, MTB and gravel projects can require different geometry, interfaces, intended-use documentation and supplied parts. Use the Road Bike Frame category, MTB Bike Frame category and Gravel Bike Frame category as separate commercial shortlists.

Frame comparison fields

For each exact model and revision, request:

• geometry chart and size range;
• frame, fork and included-parts scope;
• brake, axle, bottom-bracket, headset and seatpost interfaces;
• wheel and tire requirements;
• routing, suspension or mounting details where applicable;
• material, weight, testing or compliance statements with their definitions;
• sample, finish, branding, packaging and change-control records.

Do not transfer a specification from one platform or visually similar model to another.

Platform comparison for a dealer project

| Platform | Primary project questions | Evidence needed | | — | — | — | | Road frame | What riding brief, geometry, size range and component interfaces define the program? | Current geometry, frame/fork scope and interface documentation. | | MTB frame | Is the project hardtail or suspension-led, and what wheel, fork, shock and routing plan applies? | Exact platform specification, setup limits and included hardware. | | Gravel frame | Is the brief race, all-road, adventure or another documented use case? | Geometry, tire/mounting information and exact-model compatibility evidence. |

The comparison separates project decisions; it does not imply that one frame platform supports another platform’s setup.

Supplier evidence scorecard

For each shortlisted model, record whether the supplier has provided the current specification, geometry, interface drawing, included-parts list, sample criteria, inspection record and change-control contact. Mark missing evidence as an open question. Product photos, generic brochures and another model’s data should not close an exact-model evidence gap.

Evidence before a sample or bulk order

Use the carbon frame compatibility guide to organize interface questions and the carbon frame quality testing guide for evidence review. The carbon bike OEM RFQ template helps buyers prepare a structured enquiry.

Before approval, lock the model, revision, size, finish, frame package, planned components and required documents. Record how later changes will be communicated and approved.

For a repeat dealer program, separate three records: the approved technical configuration, the buyer-facing product data and the commercial packaging or branding brief. This makes later revisions easier to review without silently changing the listing or build plan.

Recommended approval gates

Gate 1: project definition. Record platform, intended use, market, size range, component plan and commercial scope.

Gate 2: technical evidence. Approve geometry, interfaces, frame/fork scope, included hardware and any model-specific documents.

Gate 3: sample review. Check the sample against the approved configuration, finish, packaging and listing data.

Gate 4: production change control. Define how later changes will be documented, reviewed and reflected in buyer-facing content.

These gates help a dealer compare suppliers without turning a generic category description into an unsupported product claim.

FAQ

Can road and MTB frames be compared using the same fields?

Some procurement fields overlap, but geometry, suspension, interfaces and intended use remain platform-specific.

Is a carbon grade or weight number enough to select a frame?

No. Review the exact definition, geometry, interfaces, evidence and project requirements together.

What should a dealer send with an OEM frame enquiry?

Send the target platform, model shortlist, size range, component plan, market, branding, packaging and documentation requirements through the Sunremo B2B project form.