Car Rental Store Vehicle Upload: List the Car, Bind Pricing, and Wait for Review
A newly certified rental store often looks ready from the street: keys on a board, cars on the lot, a phone that already rings. Online, it is still empty until each car has been entered, priced, and approved. Ptaxi’s car rental software treats that as a store workflow, not a spreadsheet import you hope is right. After store onboarding and certification, staff upload a vehicle, configure its pricing standard, and submit it for platform review. Admin vehicle review is the gate. Only then does store vehicle management — under review, rented, unrented, and listing status — become an operational board instead of a waiting room.
This is not a second store-certification article, and it is not a full replay of vehicle grades and fee rules. Grades and plans should already exist before a store starts typing plate numbers. The useful work here is the handoff: one car, one pricing standard, one review.
Certification gets you a store. Upload gets you a fleet.
Store certification is about the location: name, license, address, phone, then a wait for approval. That approval does not list a single car.
The next step on the store side is upload vehicle. Staff enter vehicle information, configure a pricing standard, and submit the record to the platform. The pricing step has a documented choice: the store can use a platform pricing template, or it can adjust the pricing itself. That choice is the usual fork in a multi-store network.
If you want every airport branch on the same weekend rate, push templates and tell stores to use them. If a downtown branch needs a different weekday base, let that store adjust, and accept that review will take longer because someone has to read the change. Do not leave the choice implicit. Stores that think “template” means “already approved” will call support an hour after submit and ask why the car is not on the renter app.
The list does not say an uploaded vehicle is bookable on submit. It does not say the store can skip review for a template-only car. Treat review as required unless you have confirmed a shortcut in your own build. In a demo, upload one car, show the under-review state, and only then approve it from admin.
What vehicle review is for
Admin authentication review includes store review, vehicle review, and enterprise review. They are three queues.
Vehicle review is where platform staff view the vehicle’s detailed information and approve or reject the submission after a store has uploaded the car. That is the quality gate for plates, photos, and the pricing standard attached to that car. It is not a second pass over the store’s business license, and it is not an enterprise-account approval.
Staff the queue like a desk, not like a folder. If vehicle review sits overnight at the start of a holiday weekend, you will have certified stores and an empty catalog. Write a service target in your own SOP. The list does not publish one.
Rejection needs a process you invent carefully. The list says staff can review and approve or reject. It does not prescribe a comment template, a resubmit button label, or an automatic renter-facing message. Train reviewers to say what was wrong. Train stores to edit and send the car back through the same upload-and-review path, rather than creating a duplicate record “to be safe.”
Admin store lists also let staff view vehicles under a store: brand, series, year, plate, partial VIN and engine identifiers, photos, and status, with detail pages that include vehicle information and vehicle pricing information. Use that when a renter-facing price looks wrong. Look at the car’s attached pricing, not only the global plan.
After approval: review, rented, unrented, and listing status
Store vehicle management shows vehicles under review, rented vehicles, and unrented vehicles. On unrented cars, staff can adjust listing status and can remotely control the doors where that capability is in play.
Those states are easy to flatten into “online” and “offline.” Don’t. Under review is not unrented. A car waiting for platform approval should not be toggled as if it were already in the catalog. Rented is a live job, not a listing switch. Unrented is where listing status and door control belong.
Remote door control, including the broader lock, flash, and horn tools described in self pickup, is not a substitute for review. A reviewer should not “just unlock it and see” as an approval method. Finish vehicle review, then use door control on an approved, listed car.
Listing status is also not pricing. Turning a car off for a maintenance day should not require a new pricing submission. If your team currently does that in a spreadsheet, the store board is the place to stop.
Configure plans first, then attach them to cars
Admin pricing plans are still the backbone. They can include vehicle deposit, violation deposit, a basic service-guarantee fee, weekday, weekend, and holiday base rates, over-mileage and overtime fees, chauffeur fees, and delivery fees, bound to vehicle grades.
The store upload step does not replace that work. It attaches a standard to a specific vehicle, either by using a template or by adjusting it, and then asks the platform to review the result. If plans are incomplete, stores will improvise, reviewers will hesitate, and renter-facing amounts will drift between branches.
A practical launch order looks like this:
- Finish store certification for the branches you are actually opening.
- Set vehicle grades and pricing plans in admin, including the deposits and add-on fees you intend to honor.
- Let each store upload a first batch of cars, using templates unless a branch has a written reason to adjust.
- Clear vehicle review before you advertise availability.
- Teach store staff the three vehicle boards — under review, rented, unrented — and when listing status is allowed to change.
Skip a step and you will debug the wrong screen. A missing deposit is a plan problem. A car that renters cannot see is often a review or listing-status problem.
What not to promise
The list does not say how many photos are required, which identity fields are mandatory, or how long review takes. Do not invent a two-hour SLA or a “five photos minimum” in a brochure.
The list does not say a store can publish a car without platform review, even when it uses a template.
The list does not turn vehicle upload into a hardware protocol catalog or a peer-to-peer marketplace. This is store-fleet rental: the branch lists the car, the platform reviews it, the renter books it.
Payment methods, invoices, and coupons are neighboring finance tools. They do not approve a vehicle. Do not tell a store that a successful test payment means the new car is listed.
Close
The gap between a certified store and a bookable fleet is one disciplined loop: enter the car, attach a pricing standard, submit it, and wait for vehicle review. Ptaxi’s car rental software already has that loop on the store app and in admin. Your job is to decide when stores may adjust a template, and to staff the review queue like it is part of opening the branch — because it is.
If you want a walkthrough, bring one real car and one pricing template to a demo. Ask to upload it as a store, see it land under review, approve it in admin, and only then change its listing status. That sequence is the product. Everything before review is still a draft.
Frequently asked questions
What does a car rental store submit when it uploads a vehicle?
Store staff fill in the vehicle information, configure a pricing standard, and submit the vehicle for platform review. The pricing step can use a platform pricing template, or the store can adjust the pricing itself. The list does not treat an uploaded car as immediately bookable.
Who approves a store-uploaded vehicle?
After a store uploads a vehicle, platform administrators can view the vehicle’s details and approve or reject the submission in vehicle review. This is separate from store certification review and from enterprise review. Do not tell a store manager that pricing is live the moment they tap submit.
What vehicle states can the store see after upload?
Store vehicle management shows vehicles under review, rented vehicles, and unrented vehicles. For unrented cars, staff can adjust the listing status and can use remote door controls where that feature is enabled. A car that is still under review is not in the same bucket as a car you can simply switch on.
Is vehicle upload the same as setting platform pricing plans?
No. Admin pricing plans configure deposits, a basic service fee, weekday, weekend, and holiday base rates, overtime and over-mileage fees, chauffeur fees, and delivery fees, bound to vehicle grades. The store upload step attaches a pricing standard to a specific car, using a template or an adjustment, and then waits for vehicle review. Configure the plans first, then upload the cars.