Shared E-Scooters and Rider Vehicles: Ride, Rent, and Battery Swap
A city that wants shared e-scooters, rented vehicles for food-delivery riders, and battery swap usually ends up with three systems and three wallets. The scope here is one base. It keeps the person, the vehicle, the order, and the money on the current Ptaxi mobility platform, and it adds two domains: shared electric two-wheelers for short city trips, and energy top-up through swap cabinets and centralized charging cabinets. The same account, wallet, pricing, and risk tools sit under all three jobs, so a trip, a rental, and a swap can settle on one bill.
The public carsharing system is a different product. Customers book a car with a driver, and that page says hardware locks and device protocols are not on its feature list. This article does not add e-scooters, cabinets, or remote locks to that page. It is also not store self-drive rental, and it is not a four-wheel charging project. The scope drops four-wheel piles, car chargers, and adapters on purpose. Read it as the two-wheel ride, rent, and swap scope, and stop there.
One chain: vehicle, person, order, battery, money
The business the scope describes is a single chain. Vehicles and batteries are bought or leased, placed at stations or rented to riders, used for trips or deliveries, swapped at a cabinet, and paid for as ride fees, rent, and energy. If any link drops its data, the fleet stops being controllable.
Four claims hold that chain together.
Asset control comes before a public fleet. The scope wants a live answer to where the vehicle is, who is riding it, how far it has gone, how much charge is left, and whether it is parked outside the rules. A two-wheel IoT controller and a battery management system are treated as required infrastructure for the shared fleet, not as an add-on.
The swap business is slot turnover and battery assets, not the cabinet shell. Cabinets and packs can be purchased. What the platform has to count is station density, how often a slot turns, the cost of a kilowatt-hour, and the work of keeping the site running. The scope asks for profit and loss by station and by slot before anyone copies the site.
The user is one person across three jobs. The same rider can take a shared vehicle, rent a delivery vehicle, and swap a battery. One identity check, one credit score, one wallet, and one bill are what make the cross rules possible: earnings can pay rent first, a swap coupon can come off a completed order, and unpaid rent can block the vehicle and the cabinet.
The first closed loop is rider rental plus swap. The product menu ranks public shared riding as the main offer and rider rental as the second. The rollout says the opposite order is the safer start: do not open public scan-to-ride, free-floating return, and solar-storage-charging in the same first release. Prove a weekly or monthly rider rental plus a swap cabinet, then copy stations and vehicle types.
What the scope reuses from the current platform
The scope sorts the current mobility platform into reuse, extend, and build. These are scope claims for this two-wheel project. They are not a second feature list for the car-plus-driver page. Confirm each reused channel in a demo before a sales script names it.
Account and sign-in are marked reusable as they stand. The scope names phone number plus a one-time code, Facebook login, WhatsApp verification codes, and language and calling-code selection. A shared-ride user, a delivery rider, and a swap user would keep that same account and would not register again.
Geofences and hot zones are marked reusable. The same tools cover an operating area and a return area for shared vehicles, and a service area for a swap station. The scope also keeps city, district, and zone as the place dimensions, plus an alert when a vehicle leaves the operating area.
Coupons and campaigns are marked reusable. The scope names coupons, euro-denominated issue, triggers on registration, first order, and the Nth order, and audience selection. The cross-domain uses it wants are a ride that grants swap credits, and swap spend that can offset rent.
The pricing engine is marked reusable as a rule engine, then extended. The scope says that engine already includes vehicle tariffs, a fixed price or a meter, waiting fees, holiday service fees, geofence pricing, and incremental pricing. The two-wheel work adds three models on top: time plus distance, energy price plus a service fee, and a swap package.
Orders, refunds, cancellation rules, ratings, complaints, and a 90-day ride track are treated as the trunk that already exists. They are not enough, by themselves, for this product. The next section is the gap.
What has to be extended
Wallet and payout need four additions: freeze and release a deposit, debit ride fees and rent, split revenue with a station or a cabinet site, and settle an enterprise on a monthly bill. The scope treats the current wallet as balance, top-up, local QR, SEPA, Alipay international, international bank cards, digital wallets, and rider settlement plus payout. Those channels are the base. The four additions are the work.
Orders need new document types: a shared-ride order, a lease contract, a swap order, a charging order, a return slip, and a repair work order.
Finance needs depreciation, recognition of rent and ride revenue, a station settlement statement, and a place to collect electricity and swap cost. The scope does not say those reports already exist.
Vehicle records are the start of an asset file, not the finished one. The scope says they need title documents, insurance, maintenance, violations, and accident records added.
Dashboards that already count dispatch, accept, complete, cancel, and complaint, by place and time, with a heat map, still need ride frequency, revenue per vehicle per day, cabinet-slot turnover, station utilization, and battery degradation.
None of these extensions is a promise that a named screen already ships. They are the gap the scope writes down so the project does not under-count the change.
Remote control is new, and it has a hard limit
GPS ingest, a two-wheel controller, and battery management data are marked as data access that still has to become remote control. The shared and rental fleet needs lock and unlock, a speed limit, a battery lock, and anti-theft control. The scope recommends that every shared vehicle have an IoT controller and that every battery be able to speak to the platform, with data use and rider responsibility written into the user agreement.
The control model is three layers.
See it. Live location, track replay, mileage, state of charge, lock state, fault codes, and battery temperature. Data goes up over 4G and MQTT. If the network drops, the device caches and sends later.
Hold it. Remote lock and unlock, geofences for the operating area, no-parking zones, and the station, alerts for leaving the area, alerts for a vehicle that sits still when it should not, and an alert if the battery is removed.
Get it back. Unpaid rent or a lost vehicle is handled in steps: first block riding and swapping, then lock it remotely, then recover it through a lawful process. Every step is logged and needs two-person approval.
Do not brief remote lock or a speed limit as the normal way to collect rent. The scope says doing that while someone is riding is a safety and legal problem, and that European rules on remotely controlling a vehicle another person holds are not clear. The lever it wants is the block on riding and swapping, plus contract penalties, plus recovery through legal process. Remote control is for a parked vehicle, for theft and recovery, and it needs its own clause in the contract.
Shared riding, rider rental, and an optional fleet
Shared e-scooters and e-bikes are the main offer on the product menu. Vehicles sit at stations in commercial districts, neighborhoods, campuses, and transport hubs. The user scans to unlock, pays a start fee plus time, and must return inside a station in the operating area. The revenue lines named are ride fees, a ride pass or membership, and swap.
Rider rental is weekly or monthly hire of an electric two-wheeler for food-delivery riders, with a battery and a swap package. The rider scans to take the vehicle and swaps at a cabinet. The money lines are a deposit, rent, and the swap package. Unpaid rent blocks both the vehicle and the swap.
Longer hire and enterprise fleets are optional. The scope describes them for a company, a campus, or a delivery site that takes 10 or more vehicles, with a fleet account, monthly settlement, sub-accounts, and a usage limit. If a finance product is involved, a local licensed institution does the lending. The platform’s role in that case is to introduce the scene and handle the asset, not to be the lender.
On the apps, priority is split. The user app for shared riding is first: scan to unlock, find a vehicle on the map and navigate to it, show the in-ride price with a cap, check the return against the station, prompt for a helmet, report a fault and call for help, and show the bill and invoice. The scope says to add a scan-to-ride entry on the existing app shell. The rider side is second, and the scope prefers H5 or a mini program rather than a second native app: rent and renew, a cabinet map with slot status, scan to swap, battery and range, the rent bill and debit, fault and rescue, and invoices. The ops side is also second, and it can be mobile pages on the admin, not its own app: move and recover vehicles, swap and recharge, move batteries, repair cabinets, and photograph an inspection.
The admin work marked first is the asset file (frame number, model, purchase price, controller id, battery code, insurance, local registration and inspection where the city requires it, the maintenance plan, repair orders, accident records, and retirement), plus stations and stock. Live state is riding, available, in maintenance, or being moved, with transfer, battery stock, and a check that stops overselling. Pricing to add is the start fee plus time, ride passes, daily, weekly, and monthly rent, rider rent tiers, out-of-area and illegal-parking fees, and deposit-waiver rules. Access is real-name and age, a riding-eligibility check, a credit score, a blacklist, and a deposit-waiver list. The scope treats these two-wheelers as not requiring a driving licence. That is an access rule in the document, not a legal opinion, and overseas document checks still depend on a third-party service the scope says must be confirmed. Contracts are multilingual, with e-sign, clause versions, a renewal addendum, and an end-of-lease statement. European e-sign validity and how the record is stored are also still to be confirmed.
Deposits use a freeze or a pre-authorization, a waiver from the credit score, a deposit-pool ledger, and release or deduction, on the same wallet freeze as the rest of the platform. Return checks the vehicle is inside the station, records damage to the vehicle or the battery, sets an amount, assigns liability, and keeps a dispute ticket with evidence. An AI damage pass is a later option, not part of the first cut. Bills generate on a cycle, debit the wallet or a bound card, escalate unpaid rent, add penalties and late fees, and settle when the lease ends. A failed debit needs an explicit fallback. The scope does not name that fallback. Violations, accidents, insurance follow-up, downtime loss, and vehicle recovery are a later cut, and they depend on a local data source that is not named yet.
Rules that tie the contract to the cabinet
These are the links the scope treats as the point of one platform.
The contract has to be active before the rider can take a vehicle or open a swap. Cross a rent threshold and riding and swapping pause. Pay, and they resume. That is the collection lever the scope prefers to a lock.
When rider earnings land in the wallet, an agreed share moves to rent first. The rest can be withdrawn.
Pickup and swap have to match the vehicle on the lease. A change of vehicle goes through approval, so a private sublet does not leave insurance and liability empty.
When state of charge falls under the threshold, the rider is pointed at the nearest swap, and long trips are recommended less often. The point is fewer mid-route cut-outs.
After N completed orders, the rider can receive a swap coupon that works only at the platform’s cabinets. The scope prefers that to a cash subsidy because the subsidy stays inside the cabinet.
The rider’s bill shows rent, swap, and fines in one place.
Two operating rules sit beside those links. A station vehicle is deployed only at 90% charge or more, and a return under the standard is swapped by operations before it is offered again. A rider package can include a set number of swaps per day. The credit score can draw on rent performance, unpaid energy charges, and complaints, then set the deposit-waiver limit. The same site can be a return point, a rider service point, and a battery turnaround point. The scope says the first release only has to ship three of these rules: a vehicle that is usable at pickup, rent taken from earnings, and a full battery with a swap allowance. The rest can wait.
Cabinets, packs, and the swap ledger
Swap is not a software switch. The scope calls it cabinets, battery assets, site operations, and a match between the vehicle and the pack. It uses planning assumptions you should keep labeled as assumptions: one pack on a shared vehicle or a rider vehicle covers about 60–80 km, and a rider swaps about 2–4 times a day. Cabinet count and the battery ratio then set how many vehicles you can place. The ratio it writes down is about one vehicle to 1.2 batteries if peak hours are not to run out. A healthy cabinet, in the same notes, turns a slot about 2–3 times a day and keeps full packs at about 60% of the cabinet. These are sizing rules in the scope, not measured results from a live fleet.
The equipment split is a swap cabinet as the main method, a centralized charging cabinet for overnight top-up, and one battery specification. The swap cabinet is 8–16 slots, aimed at rider gathering points, commercial areas, neighborhoods, and stations, and the scope puts it at about 60% of energy sites. It needs 220 V or 380 V, its own fire separation, and a site contract. The centralized cabinet is 10–20 ports, about 20% of sites, with a lower cost per port and a higher demand: its own charging room, a fire compartment, and timed charging. An on-vehicle charger at 54.6 V / 4 A is the rest, about 15%, as a rental accessory for home or depot top-up, with the electrical safety duty written down. Vehicles are 48 V or 60 V. Packs are 48 V 25 Ah or 60 V 30 Ah, kept to one specification so a cabinet and a vehicle match. The controller is 4G, GPS, and lock control, and the vendor has to open the protocol or the platform cannot control the vehicle. Helmets, a rack, and mirrors are standard equipment, and helmet loss is an operating cost.
The scope also asks for a site bill of materials that is easy to leave out: power upgrade, lightning protection and grounding, base and canopy, fire equipment and smoke detection, cameras and lighting, cabinet-side metering, a 4G SIM, and spares for packs, chargers, locks, and helmets. Do not quote a site price from this article. The scope keeps hardware prices for a separate supplier quote.
Who owns the assets is a choice, not a default. Buy the cabinets and the batteries if the operator has capital, sites, and a team and plans to run them for the long term. Buy the cabinets and lease the batteries if the operator wants a lower first spend and wants battery aging to sit with a battery operator, settled by the month and by the swap. Let a vendor or operator place both and keep only the user and the tariff, sharing revenue per swap, if the first question is whether demand exists. Whichever choice is made, the platform still needs the same ledger: a unique pack id, owner, cycle count, state of charge, state of health, temperature curve, insurance and warranty, and a residual value; swap pricing per swap, per kilowatt-hour, or as a monthly package, on the same wallet as charging; station scheduling that prefers off-peak charging, watches full-pack stock, takes a faulty pack offline, and moves packs between stations; and a safety trail from the battery management system, a thermal-runaway warning, and a lifecycle record.
The swap software marked first is the site and cabinet file, including address, coordinates, the site contract and its term, and a reminder before the contract ends, plus slot records, battery stock, a QR code, and a status board. Monitoring covers online state, slot state, full-pack stock, and alarms for offline, emergency stop, over-temperature, door lock, and short circuit, plus remote restart and a firmware update. Those commands depend on the cabinet vendor opening the protocol and supporting integration. Billing reuses the pricing engine for a start fee and time, ride cards, a per-swap package or an unlimited monthly package, rider rent, out-of-area and parking fees, promotions, and euro and US dollar pricing. The swap flow is scan, assign a slot, check that a full pack is actually there, start a charging cabinet when that is the device, handle a door that should not have opened, write the bill, and issue an e-invoice. Payment channels named for this flow are local QR, SEPA, Alipay international, bank cards, wallet balance, a company or fleet monthly bill, and a revenue share that can be set per site.
Automatic work orders from alarms, dispatch, on-site check-in, repair notes, spare-part use, and an SLA count are a later cut, and the scope says to merge them with the existing work-order center. Roaming, a third-party app scan, an open API, and a fleet API are later still. The scope names OCPI 2.2 as that later roaming item and says the early return is poor. Do not put roaming in a first-release brief.
European constraints in the scope are design work, not certificates this article claims are in hand. Start a site with one or two cabinets and size the power, including room to upgrade. Specify a wide input voltage, lightning protection, water protection at IP54 or better, a raised base, and leakage protection. Lock one battery size and one battery-management protocol, and finish the vehicle-to-cabinet test before stage 0 closes. Ask for EN 15194 on the vehicle, EN 50604 or UN 38.3 on the pack, CE, and the import papers at the point of manufacture, not after the vehicles ship. Meter at the cabinet and keep cycle records, with a calibration check. Cache swaps on the cabinet, keep an offline allow-list, and reconcile when the link returns. Separate energy revenue from ride revenue in reconciliation. Prefer a site lease of three to five years, and confirm fire, power, and insurance duties for the cabinet and for any charging room on their own.
What not to promise
Do not say the carsharing page already does this. Do not sell four-wheel charging, a converter between European and Chinese connectors, or a long-term adapter plan. The scope allows an adapter only as an emergency and rejects it as the lasting design, because the protocol and the safety rules do not line up. Do not promise remote lock or a speed cut while the vehicle is moving. Do not promise a named customer, a locked cabinet vendor, a software price, or a payback period. The source paper includes sample cost models and a commercial quote. They are illustrations for a sales discussion, and this article leaves those numbers out. Do not promise solar-storage-charging, public scan-to-ride, and free-floating return in one first release. Do not promise OCPI roaming, AI damage detection, or a finished overseas identity check. Do not promise that European e-sign is already cleared.
A short ops checklist before you brief the build
Keep this to one page.
- Say which job is first. The product menu leads with scan-to-ride. The rollout leads with rider rental plus one or two swap cabinets. Pick one sequence and write it down.
- List what is reuse, what is an extension, and what is new remote control. Do not brief lock, unlock, and battery lock as features the current data feed already performs.
- Write the collection rule as a block on riding and swapping, then a parked-vehicle lock, then lawful recovery. Take a moving-vehicle lock out of the script.
- Choose an asset model: buy cabinets and packs, buy cabinets and lease packs, or host both with a third party. Leave vendor, protocol, and price for stage 0.
- Use the scope’s planning assumptions only if you accept them: about 60–80 km per pack, about 2–4 rider swaps a day, about 1.2 packs per vehicle, and deploy at 90% charge or more. Replace them with local numbers before you buy.
- Confirm the stage 0 items that are still open: the hardware bill of materials, site power and fire separation, payment merchant setup, European document checks, and e-sign storage.
- Point buyers who want a car with a driver at the carsharing system page, and do not mix that workflow into this brief.
Close
Shared e-scooters, food-delivery rider vehicles, and battery swap are one scope on the Ptaxi mobility platform: scan-to-ride at a station, a weekly or monthly rider lease, and a swap cabinet that shares the account, the wallet, and the bill. The current platform is asked to contribute sign-in, geofences, coupons, and the pricing engine. Deposits, the new order types, station settlement, and remote control are work, not a claim that those screens already ship. The carsharing page stays a car-plus-driver product.
That is enough to brief the chain and the limits. It is not enough to quote a price, a vendor, or a live fleet result. If you want a walkthrough, bring one rider contract, one station, and one cabinet protocol, and match them against this scope before anything is called a first release.
Frequently asked questions
Is this the same product as the carsharing page?
No. The public carsharing system books a car with a driver, and that page says hardware locks are not on its feature list. This article is the separate scope for shared e-scooters and e-bikes, food-delivery rider vehicles, and battery swap. It does not add cabinets or remote locks to the carsharing page.
What should the first closed loop include?
The product menu leads with public scan-to-ride. The rollout says to prove food-delivery rider rental plus battery swap first: a real rider contract, pickup and return, and a paid swap at one or two stations. Public scan-to-ride is the later scale step. Do not open public riding, free-floating return, and solar-storage-charging in the same first release.
Can the platform lock a vehicle while someone is riding?
The scope says not to use remote lock or a speed limit as the normal way to collect rent. Doing that while the vehicle is moving is called out as a safety and legal risk. Unpaid rent should block riding and swapping first. Remote lock is for a parked vehicle, for theft and recovery, with its own contract clause, a log, and two-person approval.
Who owns the cabinets and the batteries?
That is still a choice. The scope lists three options: buy the cabinets and the batteries, buy the cabinets and lease the batteries, or let a vendor place both and share swap revenue. The vendor, the protocol, and the price are locked in stage 0. They are not decided in this article.