Wholesale Bicycle Parts, Ordered From the Bike on the Stand

Compatibility is the catalog, and it runs on standards, not vehicles. A bottom bracket fits a frame shell, not a model year. Park Tool's bottom bracket reference splits the field into two families, threaded and press fit. The English thread alone also answers to BSA, BSC, ISO, British and Euro, and T47 is a larger 47 mm thread. On the press fit side, one 41 mm bore is sold as BB86, BB89.5, BB92, BB107, BB121, BB132, PF24 and Shimano Press-Fit. The number in most of those names is shell width, which has nothing to do with the bearing fit. A catalog keyed on the name printed on the box ships the wrong cups.

The freehub decides which cassette fits. Shimano tells you to pair a MICRO SPLINE cassette with a MICRO SPLINE freehub body. SRAM's XD driver is a separate cassette system, with its lockring hidden inside the cassette stack. The hub must also match the frame: Shimano's FH-TC500 rear hub is built for 148 mm spacing on a 12 mm thru-axle. So a wheelset is four questions at once: spacing, axle, freehub body and rim size, with tire designations set under ISO 5775. Miss one and the dealer finds out with the rider waiting.

The IBD orders from the bike, not from your part numbers. A customer's bike is clamped in the stand. The cassette is worn, the bottom bracket creaks, and the rider wants it back by Saturday. The mechanic knows the model and can read the frame serial. What they do not know is which press fit variant that frame uses or which freehub body the stock wheel shipped with. If your site cannot answer from the bike, they call inside sales or order from whoever can.

Preseason booking pays for the year. Dealers commit to next model year's bikes, groupsets and wheels long before delivery, on booking terms that differ from in-season fill-ins. Payment dating often runs past delivery, and the booked price has to hold while fill-ins price at current rates. Many brands still run the booking on spreadsheets and email, then key it into the ERP.

Warranty runs through the shop, by frame serial. A rider brings a cracked frame or a failed drive unit to the dealer who sold it. The dealer files the claim for the rider with the serial number, the purchase record and photos. The brand needs that unit's history, and the dealer's order history does not hold it. When the serial lives in a warranty inbox and the sale lives in the ERP, every claim becomes a research project.

E-bikes bring a motor class, a wattage and a battery. The Consumer Product Safety Commission's rule, 16 CFR Part 1512, counts a pedal vehicle with a motor under 750 watts as a bicycle. The motor alone must top out below 20 mph. States then sort e-bikes into classes. Washington's statute caps Class 1 and Class 2 assist at 20 mph and lets Class 3 assist to 28 mph with a speedometer. The replacement battery is its own problem. Under 49 CFR 173.185, each lithium battery must be of a type proven to meet UN 38.3 testing. It cannot ship like a tube of grease.

The build starts with compatibility as structured data, because every other decision in wholesale bicycle parts depends on it.

Compatibility modeled on the standard, with the aliases searchable. Every SKU carries its standards as attributes: bottom bracket bore or thread, freehub body, rear spacing and axle, wheel size, speed count, e-bike class. A dealer who searches "BB92" gets the cups that fit a 41 mm bore, because the alias maps to the standard. This model is built during implementation from your own charts and spec sheets, and it belongs in a scope with a price.

The bike on the stand, recorded once. The rider or the shop registers each bike by model and frame serial, with its warranty and service record attached. That registry, parts reorder by serial and the link from each model to its standards are built during implementation from your spec data.

Exploded views for the parts nobody can name. Uncap Diagrams gives clickable hotspots mapped to live SKUs, assembly trees down to the part, and filtering by model, year or assembly. A drive unit breaks down into seals, bearings and bushings, and the mechanic adds the exact part without a part number. Existing exploded views import with callouts mapped. Rebuild kit offers are built during implementation.

Dealer ordering on the dealer's own terms. Uncap Portal gives each IBD a multi-user company account with roles and permissions and its own assortment and pricing. Reorder lists, order history, net terms, invoices and payments sit in one place. Per-variant minimums use Shopify's own B2B quantity rules. Warranty returns, booking windows and dating terms are built during implementation, with terms from the ERP.

Booking proposals and build kits as quotes. Uncap Quotes runs the configure, price, quote workflow inside the Shopify admin. Negotiated prices, tiers and volume breaks apply automatically, exceptions route to the right approver, and branded quotes keep validity windows and a full revision history. An approved preseason proposal becomes a Shopify order in one click. Build kit rules are added during implementation.

Warranty claims tied to the unit. The claim is built during implementation on the registered bike. The shop files for the rider with photos, sees approval status, and gets the replacement.

E-bike class and battery rules on the product. Class, motor wattage and assist speed live on the product record so dealers and riders can filter by them. Battery SKUs carry their lithium classification, and shipping rules send them only to eligible services. Both are configured during implementation.

The ERP stays the system of record. Uncap Connect runs real-time, two-way sync of inventory, orders, customers and pricing, including customer-specific pricing, credit terms and tax rules. It runs inside Shopify with an audit trail and no separate middleware platform to maintain. Each integration is delivered through an owned Uncap Connect app or a managed iPaaS integration, depending on the ERP.

Where the platform question lands. The usual objection is that Shopify needs more custom work for a dealer program than a B2B-first platform. The dealer account itself is native: company accounts with their own payment terms, catalogs with custom pricing, volume price breaks and quantity rules. What stays custom is compatibility across standards, warranty by frame serial and MAP enforcement, and those are built during implementation. MAP is a policy with monitoring; the storefront carries only the advertised price. The real test is the integration: it has to write dealer accounts, catalogs and price lists to Shopify's B2B model, not to a retail customer record.

Proof, at its true distance. No cycling case study is published yet. The closest builds are adjacent. For KBS Golf Shafts, a golf shaft manufacturer, Uncap delivered D2C, B2B and POS on one platform with direct integration to Oracle ERP. That is the same one catalog, several channels problem a component brand has. On the e-mobility side, fluidfreeride is an electric scooter store with collection filters and product comparison. It is a consumer build, not a dealer program.

Standards-based compatibility filtering. Bottom bracket bore and thread, freehub body, spacing and axle, wheel size and speed count as attributes, with aliases like BB92 and PF30 resolving to the right standard.

Parts from the frame serial. Bikes registered by model and frame serial, with a warranty and service record and reorder by serial. Built during implementation.

Exploded views for hubs, forks and drive units. Clickable hotspots mapped to live SKUs and imported schematics, so a mechanic orders the exact part without a part number.

Preseason booking with in-season fill-in. Booked quantity held against delivery windows and dating terms, fill-ins priced at current rates on the same account. Built during implementation.

Dealer-filed warranty claims. The shop submits for the rider against the registered bike, with photos, status and replacement routed back. Built during implementation.

Dealer accounts for IBDs. Each dealer sees its own assortment and pricing, with multi-user roles and net terms, invoices and payments in the portal.

E-bike class and battery handling. Class, wattage and assist speed on every e-bike SKU, with lithium batteries routed to eligible shipping services.

Honest about what ships and what gets built. This page names the published capabilities of each product. Compatibility modeling, booking logic, warranty claims and battery rules are named as implementation work, so you see them in the scope, not in week six.

A long record on Shopify. Uncap is a Shopify Platinum Partner, on Shopify since 2013, with 380+ unified storefronts launched on Shopify.

Scoped before it is built. An Uncap Blueprint is a fixed-price, four-week engagement covering solution architecture, an ERP integration audit and total cost of ownership before any build begins. The plan is yours to keep, with Uncap or without.

This page sits under Sporting Goods, which covers dealer authorization, MAP and preseason booking across the category. This page goes deeper on what cycling does not share with it: compatibility across standards and the bike on the stand. Brands with serialized warranty across outdoor hard goods should also read Outdoor Recreation. If your catalog runs to motorized machines beyond those e-bike limits, Powersports covers that trade. Brands on Business Central should read the Dynamics 365 Business Central integration page, and every ERP is listed on Uncap integrations.

Bring your compatibility chart and last season's booking sheet. Between them they hold the standards your catalog must encode and the terms your dealers actually buy on.

Book a strategy session with Uncap, or start with a Blueprint if what you need first is the compatibility model and the booking workflow written down and costed.