Shared mobility fleets are bought against a permit, not a product brochure. Before an operator can bid on a city contract, the transport authority has already fixed the governed speed, the lighting visibility distance, the geofencing rules, and the telemetry the vehicles must report. The procurement decision that follows is therefore narrow and technical: which platform can be certified to that permit without aftermarket retrofitting, and what does it cost to run across a three-year deployment.
This guide walks through the specification sequence an OEM-sized sharing scooter is built around — from permit mapping through anti-vandal engineering, battery swap economics, and the pilot-to-scale expansion that most operators get wrong. Every figure below reflects the sharing-fleet platform that EMS-EBIKE builds for docked, dockless, and campus programmes.
What Makes a Sharing Fleet Different From a Retail Fleet
A consumer scooter and a sharing scooter look similar on a spec sheet. They diverge on the five duty conditions that decide whether a fleet survives its first season: who rides it, how often it is dropped, how it is charged, how it is recovered, and what the city demands of it.
| Duty condition | Retail scooter | Sharing fleet scooter |
|---|---|---|
| Rider profile | One owner, familiar with the machine | Many strangers, no familiarity, no care |
| Drop and impact exposure | Occasional, handled by owner | Constant — curb strikes, kerb drops, tandem riding |
| Charging model | Owner charges at home | Central cabinet, swappable packs, depot staff |
| Recovery | Owner retrieves | Field team must locate and collect |
| Regulatory gate | Consumer standard only | City permit spec fixed before bidding |
None of these differences are cosmetic. Each one maps to a specific component decision: sealed bearings rather than open ones, forged aluminium stems rather than cast, tamper-proof fasteners rather than standard hex heads, and an IoT module welded into the frame rather than bolted on where a passer-by can unscrew it.
Permit Mapping Comes Before Component Selection
The most expensive mistake in fleet procurement is choosing a platform and then discovering it cannot be certified to the permit the operator needs. Permit requirements vary by city, but four categories recur in almost every scheme — and each has a hardware consequence.
- Governed top speed. Many city permits cap shared scooters at 20 km/h. This must be enforced in firmware and be reportable, not left as a throttle limit that a rider can defeat.
- Lighting visibility. Front and rear lighting is commonly required to be visible at 150 metres. That is a brightness and reflector specification, not a styling choice.
- Geofenced speed zones. School zones and pedestrian areas require the vehicle to slow automatically when it enters a mapped polygon. This requires a cloud API that can push geofence boundaries to the vehicle, which in turn requires an IoT module with OTA update capability.
- Audible warning. A bell or electronic sounder is mandated in most European and Asian permit frameworks.
The practical consequence is that a sharing platform must be specified against a permit matrix before the first unit is ordered. Retrofitting geofencing into a vehicle that was never designed for a telemetry link is not a firmware update — it is a new vehicle.
Anti-Vandal Engineering: The Five Loss Channels
Every deployed unit is exposed to theft, vandalism, and abuse that no retail customer would inflict on their own property. Standard consumer scooters use Phillips-head and hex fasteners that come off with tools any rider already carries. Fleet-grade construction closes five specific loss channels — the same abuse profile that drives the component choices in our commercial fleet maintenance schedule and the safety feature specification used on these platforms.
| Loss channel | Consumer-grade exposure | Fleet-grade countermeasure |
|---|---|---|
| Fastener removal | Phillips and hex heads, off-the-shelf tools | Tamper-proof Torx security screws throughout |
| Wheel and axle theft | Standard axle nuts | Pin-lock axles |
| Tracker removal | Bolted module, unscrewed in seconds | Welded IoT enclosure; motor immobiliser engages when tracker is disconnected |
| Frame fatigue | Cast stems, light welds — steering-column cracks within months | Six-point reinforced frame, forged aluminium stem |
| Tyre destruction | Standard pneumatics, frequent flats | Solid or puncture-resistant tyres rated 5,000+ km |
The tracker-defeat countermeasure is the one operators most often overlook. If the IoT module is simply bolted on, a thief removes it first and the vehicle becomes invisible. Welding the enclosure into the frame and wiring the motor immobiliser to the tracker's presence turns that into a losing move: the vehicle can no longer be ridden away once the module is disturbed.
Battery Swap Economics: Why the Charging Model Decides the Fleet Size
Charging is where sharing economics are won or lost. Building individual charging docks with dedicated power, networking, and weatherproofing carries a real materials and labour cost per dock — and a large dock deployment is a significant infrastructure bill before the first ride is even taken.
Swappable battery architecture changes that arithmetic, and the pack chemistry and BMS grade behind it matter as much as the swap mechanism — see the battery pack OEM selection guide for how cell grade and BMS tier are specified. One central charging cabinet serves many vehicles, so dock cost scales with cabinets rather than with units. That infrastructure trade-off is covered in detail in the fleet charging guide and the charging dock station planning guide. The operational figures that matter are swap time, swap throughput, and cycle life.
- 8-second swap. A tool-free latch mechanism lets depot staff change a pack in seconds, with no downtime on the vehicle itself.
- 50 swaps per hour per staffer. That throughput is what makes a central-cabinet model viable at fleet scale — the limiting factor stops being charging time and becomes staffing.
- 500 full cycles at 80% capacity retention. Battery replacement becomes a predictable scheduled line item rather than a surprise, and it directly sets the three-year consumable budget.
The consequence for procurement is that the battery specification drives the fleet size, not the other way around. A fleet running 48V 15Ah swappable packs at 50 km real-world range supports a different deployment density than one running 48V 20Ah packs at 65 km, and the two are not interchangeable in a mixed fleet without taking on a second pack SKU.
Reading the Three Fleet Build Tiers
Sharing platforms are typically offered in tiers matched to deployment density and permit requirements. The table below maps the three commonly specified builds to what each is actually for.
| Tier | Motor | Battery | Range | Optional |
|---|---|---|---|---|
| Entry | 350W hub | 36V 10Ah | 30 km | Solid tyres, basic GPS, mechanical brake |
| Core | 500W sealed hub | 48V 15Ah swappable | 50 km | 4G GPS at 2.5 m accuracy, tamper-proof fasteners, puncture-resistant tyres, BLE 5.0 unlock |
| Pro | 500W sealed hub | 48V 20Ah swappable | 65 km | Dual GPS + GLONASS, geofence API, docking rail compatible, per-cell battery telemetry, tamper alarm |
The Entry tier suits first-generation sharing in dense urban grids where trips are short. The Core tier is the workhorse for suburban and campus zones that need swappable packs and app-based unlock. The Pro tier is for fleets that have already committed to a geofenced permit programme and need dual-constellation positioning plus per-cell telemetry for battery health reporting.
The Three Deployment Patterns and What They Demand
Dockless City Rollout
Dockless operation is a permit game before it is a fleet game. The city sets governed speed, lighting, geofencing, and telemetry requirements per permit; the operator bids on volume and service area; and the vehicle spec is then built around that permit. The required configuration is tamper-proof fasteners, a welded IoT enclosure with immobiliser, solid or puncture-resistant tyres, and swappable batteries feeding a single central charging cabinet.
Docked Campus and Compound Programme
Docked programmes at universities, campuses, and gated communities trade vandalism exposure for tighter control. They use docking rails, per-vehicle telemetry, and a fixed station network. Sourcing runs like a campus procurement: the spec is defined by the station and geofence layout, one shared battery pool serves the whole fleet, and a service contract covers station and vehicle maintenance.
Pilot-to-Scale Expansion
Operators who intend to grow should use the pilot batch to validate real-world outcomes rather than to demonstrate the product. The four numbers worth measuring are decommission rate, theft rate, battery swap cadence, and downtime per vehicle. Those figures then justify the scale order, the spares ratio, and the field-operation training plan — and field-swap and depot processes should be designed jointly with the supplier before the larger order ships.
Spares, Service, and the After-Sales Contract
A sharing fleet's after-sales model is built around field-service speed and predictable component replacement cycles, not around warranty claims. Two contractual elements carry most of the weight.
The first is a spare parts SKU catalogue in which every component is identified by SKU, exploded-diagram reference, and recommended replacement interval. High-wear items — brake pads, tyres, grips, throttle — must be stocked for quick dispatch, and each container shipment should include a spares kit sized to the fleet it accompanies.
The second is OTA capability for the IoT module. Over-the-air updates let the operator adjust geofence boundaries, speed-limit maps, the unlock protocol, and battery reporting after deployment — which matters because permit terms are renegotiated and city boundaries change. A fleet that cannot update its telemetry remotely is a fleet that must physically touch every unit whenever a permit changes. Operators weighing how vehicle spec feeds unit economics should also read our shared scooter fleet economics breakdown, and the e-scooter OEM sourcing guide for the platform-level sourcing questions that sit upstream of this one.
Building the Procurement Specification
Because shared platforms are built to order, the specification has to be assembled before the order is placed. The items below are the ones that determine cost and certification more than any other, and each should be settled explicitly rather than left to default.
- Permit matrix. List every city or campus the fleet will operate in, and extract the governed speed, lighting distance, geofence requirement, and telemetry reporting duty from each.
- Battery model. Decide swappable versus fixed, and pick the pack capacity against expected trip length — 36V 10Ah, 48V 15Ah, or 48V 20Ah.
- IoT and positioning grade. Basic GPS is adequate for a pilot; permit programmes generally need 4G positioning, geofence API access, and per-cell telemetry.
- Anti-vandal package. Tamper-proof Torx fasteners, pin-lock axles, welded IoT enclosure, motor immobiliser, and puncture-resistant or solid tyres.
- Certification set. Confirm which of EN 17128, UL 2272, IP67 electronics sealing, ISO 4210 frame, UN 38.3 battery transport, and CE marking each market requires.
- Spares and OTA contract. Agree the SKU catalogue, the spares ratio per shipment, and the OTA update terms before the scale order.
Handled in this order, the specification process produces a fleet that can bid on a permit, survive a season of public use, and scale without a second platform redesign. Handled in the reverse order — platform first, permit second — it produces a fleet that has to be re-specified before it can operate.
EMS-EBIKE builds sharing-fleet e-scooters against operator livery, app branding, and regional certification variants, with the three-tier configuration above available from a minimum order of 50 units. Fleet enquiries are quoted with the permit specification, battery model, and IoT grade already scoped so that the FOB band and lead time are meaningful from the first exchange.
Build the Permit Spec Before the Fleet Order
Send us your operating city or campus, the permit's governed speed and telemetry requirements, and the deployment density you are planning. We will return the matching tier configuration, battery model, IoT grade, and FOB pricing for a fleet order.
