What to Check in Carsharing Software: Qualification, Fees, and a Driver
Carsharing software is a phrase that hides a fork in the road. Some products are self-drive keyless networks. The documented product line discussed here is a car-plus-driver service: a driver collects the car, serves the passenger, and returns it. If you buy against the wrong fork, you will ask the vendor for in-vehicle hardware they have not documented, or you will miss the qualification and return steps that this service actually runs on.
Ptaxi's carsharing system documentation describes a passenger client, a driver app, and a PC admin. Passengers complete a use-qualification review, may pay a violation prepaid deposit, search for a car by location and time, and pay a stack that includes a base fee, a service fee, an insurance fee, and a driver fee. An unpaid booking can auto-cancel after half an hour. Drivers complete a driving-qualification review, then work from an order hall: collect the car, reach the passenger, run the trip, and return the vehicle for inspection. Payment should be briefed as configured in-app payment methods and account balance. Do not name a card rail or a payment provider.
The contrast with self-drive keyless boxes is already the subject of carsharing: car-plus-driver versus self-drive. This article does not retell that explainer. It is a buyer script: what to force into a demo so you know you are purchasing the car-plus-driver loop, not an unmanned protocol that has not been shown as a confirmed product.
Qualification and the fee stack come before the map
A common vendor meeting starts on a map pin and never returns to who is allowed to use the car. In the documented flow, passenger use qualification sits in front of a completed booking, and driver driving qualification sits in front of the order hall. Driver qualification review is the training card for that split. In a selection demo, bring one passenger account that has not yet been approved, and one driver account that has not yet been approved. Confirm each is blocked from the step that requires review. Then use approved accounts for the happy path. If you only log in as already-approved users, you have not tested the gate that will create support tickets in week one.
The violation prepaid deposit is a separate money step, not a synonym for the booking fare. It should be visible as its own item, and a later violation query is also documented. Do not collapse deposit, fare, and a later violation charge into one unexplained number during the demo.
Then open the fee stack on a test booking and read it out loud: base, service, insurance, and driver fee. Plans can differ for weekdays, weekends, and holidays. Ask what happens if the booking is not paid: the documented rule is a half-hour auto-cancel. That rule is a payment-hygiene feature, not a promise about utilization. A longer treatment already exists in the unpaid-cancel and fee-stack posts. For selection, you only need to see the lines and the cancel behavior once.
Search and filters matter, but they are not the purchase test by themselves. After qualification, confirm a passenger can look for a car by location and time and can place a payable booking. Do not spend the meeting customizing a map style.
Realtime vehicle location is documented on the admin side and is useful after a driver has the car, not as a substitute for the qualification gates. Invoices and driver payouts also exist in the admin, and they should stay as a short pointer unless finance is the reason you are buying. A selection meeting that becomes a ledger review will skip the return inspection, which is where this product actually differs from a simple passenger checkout.
The driver has to close the loop
Because this product is car-plus-driver, a demo that ends when the passenger is dropped off is incomplete. The driver accepts from the order hall, collects the vehicle, serves the trip, and returns it for inspection. An owner or operations confirmation is part of closing the job. If nobody in the meeting can show that return inspection, you do not yet know how condition disputes will be handled.
Keep this part operational and short. You are not retraining the entire trip lifecycle. That already has its own article. You are confirming that the purchasable system includes a driver, a hall, and a return, not only a passenger checkout page. If a condition issue appears only at return, you need to know who records it and who confirms the job is actually closed. Stopping at drop-off hides that argument until the first bad weekend.
Companies, agents, and admin roles are documented and were described in a recent post. If you will run more than one company, or you need agents and role-based permissions, ask to see how an order is attributed to the company that owns the vehicle. That is a follow-on check, not a replacement for qualification and return.
What you will not get from the confirmed lists is a peer-to-peer in-vehicle protocol, a named hardware vendor, or a confirmed per-minute unmanned tariff. If that is the business you actually want, say so early and keep those items unverified or in a different negotiation. Do not let the word carsharing on a brochure close the gap.
If you are evaluating Ptaxi carsharing software, say in the first minute that you are testing the car-plus-driver loop. Then stay on qualification, the fee stack, and a return inspection. Performance claims and hardware commitments stay off the scorecard until they are shown in some other, written form.
A free trial is also not a documented product item. You can still ask for test accounts and refuse to sign until an unapproved user is blocked and a full loop has been closed. Whether a trial is offered, and for how long, remains a commercial answer rather than a product fact.
A car-plus-driver checklist
- State the job in writing: car-plus-driver service, not unmanned self-drive, unless you have a separate, documented offer.
- Fail passenger qualification once, then fail driver qualification once. Confirm the blocks. Continue with approved accounts.
- Open a test booking and read the fee stack: base, service, insurance, and driver fee. Confirm a weekday versus weekend or holiday difference if you will use one. Let an unpaid booking sit until the half-hour cancel, or have the vendor show a recorded example and the setting that controls it.
- Run one complete loop: driver accept, vehicle pickup, trip, and return inspection with an owner or operations confirmation.
- If you need multiple companies or agents, look at role permissions and company attribution as a second pass.
- Leave in-vehicle hardware brands, store-less per-minute billing, and unshown performance claims off the already-included list.
FAQ
Is this carsharing product the same as unmanned, self-drive carsharing? No. The documented carsharing lists describe a car-plus-driver service: a driver accepts the job, collects the vehicle, serves the passenger, and returns the car for inspection. They are not a peer-to-peer in-vehicle hardware protocol list. An earlier explainer covers that contrast in more depth.
What should I see in the fee stack during a demo? The documented stack includes a base fee, a service fee, an insurance fee, and a driver fee. Pricing can differ for weekdays, weekends, and holidays. An unpaid order can auto-cancel after half an hour. Ask to see those lines on a test booking. Do not invent a per-minute unmanned tariff and score the product against it.
Why are there two qualification reviews? Passengers go through a use-qualification review, including personal information and a driving license, and may owe a violation prepaid deposit. Drivers go through a driving-qualification review before they can work in the order hall. In a demo, use one account that is not yet approved and confirm it cannot complete the path you are testing.
Does return inspection belong on the same card as booking? Yes, for selection. The trip is not finished when the passenger is dropped off. The driver returns the vehicle for inspection, and an owner or operations confirmation is part of the documented close. If you stop the demo at payment, you have not accepted the product you are actually buying.
Close
Buy carsharing software only after you have accepted it as a car-plus-driver service, or after you have written a different, unmanned scope as unverified. The selection test is qualification, a readable fee stack, and a driver-run return, not a map pin and a brochure word.
Review that loop on the carsharing system product page. If you want a walkthrough of Ptaxi, bring one unapproved passenger, one unapproved driver, and one complete trip that does not end until the car is inspected and confirmed.
Frequently asked questions
Is this carsharing product the same as unmanned, self-drive carsharing?
No. The documented carsharing lists describe a car-plus-driver service: a driver accepts the job, collects the vehicle, serves the passenger, and returns the car for inspection. They are not a peer-to-peer in-vehicle hardware protocol list. An earlier explainer covers that contrast in more depth.
What should I see in the fee stack during a demo?
The documented stack includes a base fee, a service fee, an insurance fee, and a driver fee. Pricing can differ for weekdays, weekends, and holidays. An unpaid order can auto-cancel after half an hour. Ask to see those lines on a test booking. Do not invent a per-minute unmanned tariff and score the product against it.
Why are there two qualification reviews?
Passengers go through a use-qualification review, including personal information and a driving license, and may owe a violation prepaid deposit. Drivers go through a driving-qualification review before they can work in the order hall. In a demo, use one account that is not yet approved and confirm it cannot complete the path you are testing.
Does return inspection belong on the same card as booking?
Yes, for selection. The trip is not finished when the passenger is dropped off. The driver returns the vehicle for inspection, and an owner or operations confirmation is part of the documented close. If you stop the demo at payment, you have not accepted the product you are actually buying.