Carsharing Vehicle Import: Load the Fleet Before Drivers Go Live

A car-plus-driver hall cannot dispatch an empty list. Teams still try. They polish passenger search, they train drivers on pickup and return, and on opening day the vehicle list has three demo plates and a spreadsheet sitting in someone’s email. On Ptaxi’s carsharing system, admins are not supposed to key every car by hand. Vehicle import lets backend staff download an Excel template and bulk-import vehicle information from a local file. The list that results is the fleet drivers will pick up, take to a passenger, and return.

This piece is about loading that fleet. It is not a hardware peer-to-peer car-share protocol story, and it is not a rewrite of trip lifecycle from pickup to return. Import is how cars enter the admin system. The lifecycle is what happens after a passenger actually pays and a driver accepts.

Why launches stall on the vehicle list

Carsharing here means a car plus a driver, not an unlocked hatch the passenger finds alone. Someone still has to collect the vehicle, drive it to the rider, provide the service, and bring it back for inspection. None of that starts if the platform does not know the car exists, which company owns it, which site it belongs to, or which type’s pricing applies.

Typical pains import is meant to blunt:

1. Ops pastes plates into a web form one row at a time while a partner waits with eighty cars.
2. A spreadsheet exists, but nobody downloaded the platform template, so the file will not load.
3. Cars appear in a list and still cannot be priced because they were never bound to a vehicle type.
4. Buyers confuse this import with store-rental vehicle upload or with onboarding a hardware lock.

Import answers *how a batch of vehicle records enters the admin fleet*. The vehicle list answers *what you can inspect after they land*. Type binding and pricing answer *how a passenger sees a bookable price*. Driver qualification answers *who is allowed to pick the car up*. Keep those cards separate.

What the documented import tool includes

Confirmed admin surfaces put vehicle import under vehicle management and describe two pieces:

1. Prepare an Excel template and offer it for download.
2. Provide bulk import so staff can load a large local file of vehicle information.

Say those two sentences in a launch workshop. Do not invent column names the documents do not list. If a buyer asks whether the template includes VIN, color, site code, or insurance expiry, open the actual downloaded file in the demo instead of guessing. The confirmed capability is template plus bulk load of vehicle information—not a published field dictionary.

After import, the vehicle list is where you view added vehicles, site information, models, and vehicle details. That is your sanity check: did the batch land under the right site, with the right model, looking like the partner’s spreadsheet? Realtime location lets you see a vehicle’s current position once the car is actually in the world. Location is not a substitute for import, and import does not by itself prove a tracker is healthy.

Orders later belong to the company that owns the vehicle. That is why company and agent setup is not decorative. Admins can create companies and agents. If you import fifty cars against the wrong company, downstream order attribution and commission follow that mistake. Fix ownership before you celebrate a successful upload count.

Bind types and pricing before you call the fleet live

A second admin list covers vehicle types: view types, bind vehicles to them, and manage pricing. Importing a row without a type is how you create cars that operations can see and passengers cannot honestly book.

Pricing for this line is documented as more than a daily number. Admins set fees by weekday, weekend, and holiday, and they configure service fees, insurance fees, and driver fees. Passengers confirm an order against that stack—base, service, insurance, and driver—and an unpaid hold auto-cancels after about half an hour. That unpaid timer already has its own article. Mention it only so nobody thinks import replaced payment hygiene.

Platform commission is configured as the share taken from company-order driver earnings after the passenger pays. Because orders follow the vehicle’s company, a mis-tagged import flows into the wrong split. Walk one sample order after a test import and show the company on the order detail: basic information, logs, fees, trip track, complaints, and push logs are all on that record. If the company is wrong, stop hiring drivers into that mess and fix the fleet first.

Passenger search will not save you either. Riders look up cars by location—vehicles within a set distance of the use address—and by pickup and return time. They filter by site, model, brand, seats, pickup address, times, distance, rental count, and price. They inspect photos, configuration, and ratings. Empty filters are what an unimported fleet looks like from the app. Pair this with vehicle search filters and ratings once the list actually has cars.

Drivers still need a reviewed qualification

Importing vehicles does not onboard drivers. Drivers submit personal information and driver’s license information for qualification review. Admins approve or reject that file. The trip itself is pick up the car, go to the passenger, start and end the service, return the car, and wait for the owner to confirm inspection. A warehouse full of imported plates with no reviewed drivers is a parking lot, not a hall.

Passenger-side qualification is a separate door: personal information plus driver’s license, then a violation prepaid deposit used after the trip for violations or overtime-style problems. Do not mash passenger certification, driver certification, and vehicle import into one “onboarding” slide. They fail independently.

If you need the human side of driver review, keep driver qualification review next to this article. This page stays on the spreadsheet that loads the cars those drivers will collect.

Ops tradeoffs to say out loud

• No import, typed plates only: fine for a five-car pilot, punishing for a partner drop of eighty vehicles.
• Import without using the official template: fast on Monday, rejected file on Tuesday, and a blaming match about columns you never documented out loud.
• Imported cars, unbound types, missing prices: the admin list looks busy; the passenger app still has nothing honest to sell.
• Imported against the wrong company: order attribution and commission follow the vehicle owner, so you will spend launch week moving cars you already “finished.”
• Template + bulk import + type binding + pricing + driver review: slower than a launch email that says “we’re live,” and the first real booking has a car to collect.

Practical notes that match the surfaces:

• Download the template in the workshop. Fill a few rows from a real partner sheet, then import them.
• Open the vehicle list immediately and check site, model, and details before anyone trains drivers.
• Bind those cars to a type and show weekday, weekend, and holiday prices with service, insurance, and driver fees.
• Create or confirm the owning company first so you are not importing into a holding pen you do not use.
• Check realtime location only after a physical car exists. A row without a vehicle in the world is still just a row.

What this is not

• Not hardware peer-to-peer car sharing, lock vendors, or on-board protocols.
• Not store-rental vehicle upload from a shop counter, even though both involve adding cars.
• Not driver qualification, passenger qualification, or the violation prepaid deposit.
• Not a published dictionary of Excel columns. Use the downloaded template.
• Not WeChat or official-account packaging for overseas App buyers.
• Not named map vendors, tips, bank cards, or card processors.
• Not a rewrite of unpaid-order auto-cancel. Payment still has to happen after the car exists.

Launch sequence sales can repeat

1. Create or select the company that will own the vehicles.
2. Download the Excel template, fill a small batch, and run bulk import.
3. Open the vehicle list and confirm site information, models, and details.
4. Bind the cars to a vehicle type and set weekday, weekend, and holiday pricing plus service, insurance, and driver fees.
5. Only then walk a driver qualification and a passenger search so the imported fleet is something a person can actually book.

If a buyer wants to “train drivers this week and add cars later,” ask who accepts the first hall order against an empty list. The documented answer is that the fleet has to exist first.

Soft next step

If your car-plus-driver launch is waiting on a spreadsheet, download the Excel template, run bulk vehicle import, and bind the cars to types and pricing before you open the hall. When a lead can demo that load without inventing hardware P2P or skipping company ownership, you are ready to run carsharing software with a fleet drivers can actually pick up.