Car Rental Store Service Switches: Delivery, One-Way, Deposit Waiver, and Chauffeur

Homepages love absolute language: “delivery everywhere,” “deposit-free,” “chauffeur available.” Counters hate absolute language. The fix is not a louder slogan. It is per-store service switches that decide what each location actually sells—then let the passenger catalog follow those flags.

On Ptaxi’s car rental software, store-side store services document toggles for delivery / pickup at customer, one-way (off-site) return, deposit waiver, and chauffeur. Passenger store selection follows city plus store service requirements. Platform store lists expose service fields for oversight. This piece is about teaching ops to flip switches with an owner—not about re-litigating smart lock self-pickup or deposit waiver economics in full.

The catalog problem switches actually solve

A city page that promises delivery while half the stores never staffed a delivery driver creates refunds, not growth. Same for one-way return and chauffeur.

Typical pains store service switches are meant to blunt:

1. Marketing enables “delivery” globally; three franchise stores never could run it.
2. Passengers pick a store that cannot waive deposit, then fight the counter about a homepage badge.
3. Chauffeur orders land on stores with no driver roster; dispatch improvises in chat.
4. Platform leads cannot see which stores flipped which flags without a private spreadsheet.

Switches answer *what this store sells*. Fee tables still answer *how much*. Handoff tools still answer *how keys move*.

What the documented surfaces actually say

Store app store services: set whether the store supports delivery/pickup at customer, one-way return, deposit waiver (dual waiver), and chauffeur.

Passenger select store: based on chosen city and store service requirements, show matching stores.

Passenger flows also document that enrolled stores can set support for one-way return, delivery, and deposit-free service as store-level choices—consistent with the switch surface.

Admin store list: includes store service fields among store profile columns for oversight.

Say those sentences in workshops. Do not invent Stripe, bank-card rails, or named map vendors—confirmed rental lists document balance and local online wallets as passenger pay methods, plus these service flags.

Walk the demo in order:

1. Open a store profile and show the four service toggles.
2. Disable delivery; search as a passenger who requires delivery; show the store drop out of matching results.
3. Re-enable delivery; show it return.
4. Repeat a shorter pass for one-way, waiver, and chauffeur.
5. Open admin store list and point at the service fields so franchise leads know oversight is not a screenshot hunt.

If any step feels like theater, fix role permissions for who may flip waiver/chauffeur before you print city ads.

Four switches, four different failure modes

Treat each flag as its own SOP line:

1. Delivery / pickup at customer: needs staffed drivers, delivery fees in the store plan, and dispatch habits when confirming orders that require a driver assignment.
2. One-way return: needs receiving-store agreements and fee rules; do not enable as a vanity badge.
3. Deposit waiver: needs finance appetite and clear risk policy—see the dedicated waiver post for economics; the switch is only the on/off for that store.
4. Chauffeur: needs a driver roster at confirm time for chauffeur/delivery-style orders; fee lines for chauffeur belong in pricing, not in a chat bargain.

Order confirm still requires vehicle-condition upload; delivery/chauffeur orders still need driver assignment on confirm. Switches do not delete those steps—they decide whether the store should have received the order shape at all.

Passenger selection must follow flags

The product story only works if the passenger store picker filters by service requirements. Training that “drivers will explain at the counter” is how you buy one-star reviews.

Launch checklist:

• City ads only claim services at least one live store can toggle on.
• Passenger requirement chips (delivery, one-way, waiver, chauffeur) map to the same flags stores set.
• Mystery-shop a disabled flag weekly during ramp—broken filters are silent until social media is not.

Soft-link readers who need fee depth to vehicle grades and fee rules, over-mileage / overtime, and chauffeur add-on. Keep this article on the switches themselves.

Ops tradeoffs to say out loud

• All switches on, weak staffing: catalog looks complete; counters fail; refunds rise.
• Switches honest, ads oversell: passengers arrive expecting a badge the store never enabled.
• Switches correct, filters broken: wrong stores still appear; the feature might as well be off.
• Switches + filters + fee plans + confirm discipline: passengers only see runnable offers; desk mediation drops.

Practical notes that match the surfaces:

• Assign who may flip waiver and chauffeur (store manager vs platform admin).
• Re-audit flags when a store loses delivery staff or chauffeur contractors.
• Keep smart unlock / flash-horn / scan-to-order training separate—those are handoff tools, not commercial service flags.
• Deposit records and return settlement stay on finance surfaces; a waiver switch is not a refund button.

Franchise oversight without spreadsheet religion

Admin store lists already show service fields. Use them in a weekly franchise call:

• Which stores enabled chauffeur but have zero chauffeured completes?
• Which stores advertise delivery in local ads while the toggle is off?
• Which stores flipped waiver on after a competitor promo without finance sign-off?

The point is not punishment theater. The point is catching lies early while the passenger filter still matches reality. When list fields and store toggles disagree, fix sync or permissions before you print another city banner.

Pricing plans still sit beside switches

Delivery fees, chauffeur fees, one-way fees, and deposit amounts live in pricing / order money lines. A switch only says the store *offers* the shape. If delivery is on and delivery fee is zero with no policy, you trained passengers to expect free courier cars forever. Align fee plans the same week you flip flags—not a month later when finance notices.

Return settlement, extra fees, and deposit refund paths stay on their own posts. Do not let a service-switch workshop become an accidental refund policy rewrite.

What this is not

• Not smart-lock theology, scan-to-order, or remote door demos (related, but different posts).
• Not wedding-only packaging—wedding hire has its own constraints elsewhere; do not collapse it into the four toggles.
• Not WeChat mini-program packaging for overseas App buyers. Demo store app + passenger App/PC admin.
• Not tips, bank cards, Stripe, or named map vendors.
• Not SOS fiction.

Launch sequence sales can repeat

1. Open store services and name the four toggles.
2. Mystery-shop passenger selection with delivery required while the store has delivery off.
3. Flip delivery on and show the store reappear.
4. Point at admin store-list service fields for franchise oversight.
5. Close with “advertise only what a store can toggle,” then walk car rental software.

If a buyer wants every store to show every badge on day one, ask which roster covers chauffeur at 06:00 on a holiday Monday. The switch is the honest answer; the badge is not.

Soft next step

If city pages promise services counters cannot run, open store service switches, align passenger store filters, and assign owners for waiver and chauffeur flips. When a lead can show a store disappear from delivery search after a toggle—without editing a homepage banner—you are ready to run car rental software catalogs without inventing per-store lies in marketing.