Bike and duty cycle
- City, trekking, road, trail, MTB or cargo category
- Target market, route, gradient and total load
- Expected riding behavior and service environment
OEM Drive Architecture Guide
Choose mid-drive or hub-drive from the complete eBike program
A useful comparison starts with the target bike, duty cycle, integration constraints, service model and validation plan. It does not start and end with one peak specification.
Start with the platform requirements
The right architecture is the one that fits the complete OEM program and can be validated, serviced and supplied consistently.
Integration envelope
- Frame, bottom-bracket, wheel and dropout constraints
- Battery, controller, HMI, sensor and cable scope
- Voltage, torque, protocol and packaging targets
Program conditions
- Sample quantity and validation responsibility
- Service model and spare-parts planning
- Annual volume, launch timing and production RFQ route
Compare the engineering work, not only the motor type
Both architectures require a complete system review. The main integration questions are different.
Mid-drive evaluation route
A mid-drive places the drive unit at the bicycle drivetrain and should be reviewed with the frame interface, chain line, gearing, shifting under load, cooling, ride calibration and drivetrain service strategy. It is a relevant route when central mass and use of the bicycle gearing are important to the platform.
Hub-drive evaluation route
A hub-drive places the motor at the wheel and should be reviewed with wheel construction, axle and dropout interface, cable exit, connector protection, wheel removal and service procedures. It is a relevant route when direct wheel drive and a simpler main-frame architecture suit the product plan.
Complete component alignment
Motor selection cannot be separated from battery voltage and capacity, controller behavior, HMI and controls, sensors, protocol, charger and wiring. Confirm which party owns each component and interface before samples are built.
Validation and change control
Record the exact hardware, firmware and parameter configuration for every sample. Use the same reference during bench checks, bike integration, ride evaluation, issue closure and production RFQ preparation.
KingClean discussion routes
A80 and W200B provide two concrete starting points for a requirements-led OEM conversation.
A80 Mid-Drive System Review the KingClean mid-drive route for OEM platform discussions.
W200B Hub-Drive System Review the KingClean hub-drive route for OEM platform discussions.
eBike System Integration Checklist Prepare the interfaces, files and validation gates before sampling.
OEM Sample and RFQ Process Send the information needed for sample, engineering-file and production discussions.
Questions OEM teams should resolve
Use these answers to frame the first internal review and supplier discussion.
Is one architecture universally better?
No. The decision should reflect the bike category, duty cycle, integration envelope, ride target, service model, component scope and validation plan.
What should be ready before samples?
Prepare the target market and bike category, expected load and route, frame and wheel constraints, performance target, component requirements, protocol, sample quantity, annual volume and launch timing.
Can KingClean help compare the routes?
OEM buyers can discuss A80 mid-drive, W200B hub-drive and broader Lexy eBike system routes. Final fit, sample configuration, file availability and commercial conditions are confirmed for the specific program.
Send the platform requirements
Email echo.li@kingclean.com with the bike category, market, load and route, frame and wheel constraints, voltage and torque target, battery/HMI/protocol needs, sample quantity, annual volume and launch timeline.
Email the eBike Team