Car Rental Vehicle Brands, Series, and Versions
Stores type brand names inconsistently. Renters cannot tell a model from a trim. Pricing already has a home — vehicle grade — but merchandising still needs a catalog the store can actually pick from when a car is uploaded. Ptaxi’s car rental software documents an admin catalog of vehicle brands, series, and versions, and those brand and series values travel with the store’s cars into the list a renter shops.
This article stays on that catalog. It is not a rewrite of vehicle grades and fee rules. Grades handle price. Brands, series, and versions handle what the car is called.
What the catalog actually stores
Under vehicle management, vehicle brands let staff view or add brand, series, and version information. That is the documented catalog: three layers, view or add. The list does not describe edit-versus-delete in a separate sentence, and it does not describe a merge tool for duplicate brand names. In a demo, add one brand with a series and a version, then try a second close spelling and see whether the list prevents the duplicate. Do not promise a forced pick-list or a merge tool unless the build shows one, and even then, label it as a demo observation.
A catalog only helps if stores pick the same records when they upload a car. If one store types a brand as free text in a different field, or picks a near-duplicate name, the renter-facing list will still look messy. The list does not say the upload form forces a pick from this catalog. Confirm that binding in a demo, especially when you walk store vehicle upload and review.
This is the tradeoff to say out loud. The capability is a maintained brand, series, and version list. The pain it is meant to solve is inconsistent naming, and renters who cannot tell a model from a trim. The catalog does not, by itself, clean up a store that keeps inventing new spellings. Without a documented merge tool, someone still has to police the list.
Do not invent an OEM catalog API or an automatic model-year import. Staff view or add the records. That is a catalog you maintain, not a manufacturer feed that arrives overnight.
Version is the layer people argue about, because “series” already sounds like a model to most staff. Use the three names as the list uses them: brand, series, and version. A version is the trim-like record in this catalog, not a software release, and not a pricing tier. If your team currently types a trim into a notes field, move that conversation onto the version record and confirm in a demo how it shows up on the car. Year is already a separate field on the store vehicle list, so do not collapse year into version just to make the catalog smaller.
Keep grades, and their prices, on a different layer
Vehicle grades are a different admin screen. Staff can view grades, see the count of vehicles linked to each grade, edit grade names, and bind vehicles to a grade. Mention that screen only to keep the layers apart. Pricing plans are configured on vehicle grades: deposit, violation deposit, base service fee, weekday, weekend, and holiday bases, over-mileage, overtime, chauffeur fee, and delivery fee. Do not retell that post here. Do not say price is bound to brand, series, or version. The list binds pricing to grade.
If a buyer asks “what does this model cost,” the honest answer is split. The catalog tells you it is that brand, series, and version. The grade tells you which fee plan applies. Mixing those answers on one slide is how merchandising and pricing get tangled, and how a store ends up creating a new “brand” just to charge a different rate.
How brand and series show up on a store car
On the admin store list, staff can open view vehicles for a store. That page shows store name, vehicle brand, series, year, plate, last six of the VIN, last six of the engine number, photos, status, and actions (detail, suspend). The detail includes vehicle information and vehicle pricing information.
So the merchandising fields that travel with the car, on this list, include brand and series, plus year and the identity fields. Version is documented on the catalog screen. The store vehicle list wording names brand and series. In a demo, open a car detail and confirm whether version appears there too. Do not invent a column the list does not name, and do not hide version from the catalog just because the store-list sentence names brand and series.
Those identity fields are also a reminder that this list is an operations view, not a marketing page. Last six of the VIN and last six of the engine number are there for staff who need to tell two similar cars apart. The renter is shopping a store’s available cars, not auditing a VIN. Keep those audiences straight when you brief the screen.
What the renter actually does
The passenger flow is: choose a city, choose a store, choose dates, then go choose a car. The system queries vehicles at that store that match the request, and the renter picks a car.
That is a store-scoped choice, not a marketplace-wide model search. Do not copy carsharing filter chips into this product. The carsharing product has rich filters; this car-rental list does not document renter-facing filter chips for brand or series. If the build shows a filter in a demo, write it down as a demo observation, not as a feature-list fact.
The catalog still matters on this path, because the cars the store uploaded are the cars the renter sees. If brand and series were entered cleanly, the renter can tell one car from another at that store. If they were not, no amount of grade configuration will make the names consistent. Train the upload and the catalog together, then finish on the renter’s “go choose a car” step so buyers see where the merchandising lands.
Because the query is store-scoped, a clean catalog still will not let a renter start with a brand and shop every store at once. If a buyer wants that marketplace behavior, say it is not how this flow is written. The renter picks a store first, then a car at that store. That is a slower start for brand shoppers, and a clearer inventory promise for a store that only wants to show its own cars.
What not to promise on the brand catalog
Do not promise an OEM feed, an automatic model-year import, or a merge tool for duplicate names. Do not say the upload form forces a pick-list unless you have confirmed that in the build and labeled it as a demo note. Do not bind price to brand, series, or version. Do not invent renter-facing filter chips, and do not import carsharing search behavior into this product. Do not write a third-party login into the renter flow. The documented path is city, store, dates, then choose a car at that store.
A short ops checklist before you brief the catalog
Keep this to one page.
- In admin, open vehicle brands. Add one brand, one series, and one version. View the records you just added.
- Try a close-spelling duplicate and write down whether the list prevents it. If it does not, note that there is no documented merge tool.
- Open vehicle grades only long enough to show the linked-vehicle count and to say that pricing plans are bound to grade, not to brand. Then close that screen.
- On the store list, open view vehicles. Point to brand, series, year, plate, last six of the VIN, last six of the engine number, photos, and status. Open a detail and look for vehicle information and vehicle pricing information, and check whether version appears.
- Walk a test renter through city, store, dates, and go choose a car. Confirm the cars shown belong to that store. Do not demo platform-wide brand chips the list does not document.
- When you discuss upload, keep the review path on its own card and only confirm that stores are picking catalog records, not inventing new spellings.
If a script starts promising a manufacturer catalog or a price tied to a trim name, cut it back to view-or-add records, store-level car choice, and grade-based pricing.
Close
A car-rental brand catalog is a merchandising layer, not a price list. Admin can view or add brands, series, and versions. Store cars carry brand and series into the vehicle list, and a renter who has chosen a city, a store, and dates then goes to choose a car at that store. Vehicle grade remains the layer that holds the fee plan.
That is enough to stop stores from inventing a new spelling for every upload, if they actually pick the same records. It is not enough to sell an OEM feed, a merge tool, or renter-facing filters the list does not describe. Look at vehicle brands on the car rental software product page. If you want a walkthrough, ask for a demo and bring two stores that would otherwise type the same model differently, then follow one car from the catalog, through the store list, to the renter’s choice screen.
Frequently asked questions
What can admin add on the vehicle brands screen?
Staff can view or add brand, series, and version information. That is the documented catalog: three layers, view or add. The list does not describe a merge tool for duplicate brand names, and it does not describe a forced pick-list in a separate sentence. In a demo, add one brand with a series and a version, then try a close spelling and see whether the list prevents the duplicate.
Is the rental price bound to the brand, the series, or the version?
No. Pricing plans are configured on vehicle grades, which are a different admin screen. Grades have their own post, covering deposit, violation deposit, base service fee, weekday, weekend, and holiday bases, over-mileage, overtime, chauffeur fee, and delivery fee. The catalog tells you what the car is called. The grade tells you which fee plan applies. Do not retell the whole pricing post here, and do not say price is bound to brand.
Which brand fields appear on a store’s vehicle list?
The admin store list has a view-vehicles page that shows store name, vehicle brand, series, year, plate, last six of the VIN, last six of the engine number, photos, status, and actions for detail and suspend. The detail includes vehicle information and vehicle pricing information. Version is documented on the catalog screen. In a demo, open a car detail and confirm whether version appears there too.
Can a renter filter the catalog by brand or series across the whole platform?
The documented passenger flow is choose a city, choose a store, choose dates, then go choose a car. The system queries vehicles at that store that match the request, and the renter picks a car. This is a store-scoped choice. The list does not document renter-facing filter chips for brand or series. Do not copy carsharing filters into this product, and do not invent an OEM catalog API or an automatic model-year import.