Car Rental Chauffeur Add-On: Checkout Return Mode, Store Fees, Wedding Lock

Self-drive rental sells weekends. VIP transfers, corporate hosts, and wedding fleets sell a driver with the car. If checkout only offers “pick up at store,” those customers invent WhatsApp side deals—or walk. Configure chauffeur as a return/fulfillment mode, with store-set chauffeur fees and a wedding lock to chauffeur return, keeps that revenue inside the platform ledger.

On Ptaxi’s car rental software, confirm-order return methods include store pickup, paid door-to-door delivery/return (store-set fee), and configure chauffeur (store provides the driver; chauffeur fee set by the store). Wedding hire documents that return method can only be chauffeur. Store dispatch for delivery/chauffeur orders must assign a driver. Pricing plans include chauffeur fee among grade components. For the broader corporate + wedding story, see corporate car rental approval and wedding hire. For how over-mileage and overtime still settle at return, see over-mileage and overtime fees.

The add-on problem self-drive checkout ignores

Typical failures without chauffeur mode:

1. Wedding coordinator needs a decorated fleet with drivers; staff tell them to “rent and find drivers yourself.”
2. Hotel VIP wants a car plus driver for a half-day host circuit; ops quotes on chat, never on order lines.
3. Store turns on chauffeur verbally but never assigns a driver at dispatch—status says ready, curb stays empty.
4. Finance cannot find chauffeur revenue because it lived in a personal transfer.

Configure chauffeur is not a tip field. It is a return method that changes fulfillment: store must supply the driver and price it.

What checkout actually offers

Documented return methods at confirm order:

1. Store pickup — customer takes and returns at the store.
2. Door-to-door (customer-paid) — store delivers and collects; fee set by store.
3. Configure chauffeur — store provides chauffeur; fee set by store.

Payments documented at checkout: balance, WeChat, Alipay (plus coupons). Do not invent card brands or Stripe for overseas decks—say local methods you enable.

Store service switches can advertise whether a store supports door-to-door, one-way return, deposit-free, and chauffeur. Hide the SKU if the store cannot staff drivers.

Wedding hire forces the chauffeur path

Documented rule: wedding orders can only choose chauffeur return. That is a product lock, not a suggestion. Decorated cars, timed ceremonies, and multi-stop photo loops are liability-heavy; self-return piles are how bumpers and timelines die.

Train wedding sales on the lock before they promise a cheaper self-drive package. If a couple wants self-drive leisure cars, that is a normal rental—not wedding SKU theater.

Store dispatch obligations

On dispatch confirmation, stores upload odometer, condition photos, notes. For door-to-door or chauffeur orders, the store must set the driver. Only then does status move to awaiting customer pickup.

Return confirmation still allows condition upload and extra fees with secondary payment—chauffeur mode does not erase over-mileage, overtime, or damage lines. Keep those paths separate so Friday returns stay auditable.

Remote lock/unlock and lights/horn helpers support handover checks; they do not replace assigning the chauffeur.

Pricing plan fields that back the fee

Admin pricing by vehicle grade documents: vehicle deposit, violation deposit, basic service guarantee, starting fees (weekday / weekend / holiday), over-mileage, overtime, chauffeur fee, and door-to-door fee.

Tradeoffs:

• Chauffeur fee too low: stores refuse to enable the service switch; VIP demand leaks to chat.
• Chauffeur fee opaque at checkout: customers feel bait-and-switch when the driver appears as a verbal add-on.
• Fee clear + driver assigned at dispatch: boring in the best way—ceremonial fleets show up with a name attached.

Ops tradeoffs to say out loud

• Enable chauffeur only on stores that actually roster drivers.
• Keep wedding on chauffeur-only; do not “special case” self-return for friends of the owner.
• Align door-to-door vs chauffeur scripts: delivery without a staying driver is not the same product as configure chauffeur.
• Pair chauffeur orders with the same deposit and return-photo discipline as self-drive—VIP does not mean skip condition evidence.

Launch sequence sales can repeat

1. Toggle store service: chauffeur supported.
2. Show checkout return method configure chauffeur with store fee visible.
3. Place a wedding demo order; show return method locked to chauffeur.
4. On store app, dispatch with condition photos and driver assignment.
5. Walk return with optional extra fee + second payment—without inventing tip culture.

Chauffeur vs door-to-door vs store pickup

These are three products, not three synonyms:

• Store pickup — customer drives (or is driven by their own party); store hands over keys/condition.
• Door-to-door — store staff deliver and collect the car; customer still may self-drive during the rental window; delivery fee is store-set.
• Configure chauffeur — store supplies the driver as part of fulfillment; chauffeur fee is store-set.

Wedding locks to chauffeur because ceremonial fleets need a responsible driver through the timeline. Treating door-to-door as “close enough” for weddings is how decorated cars end up abandoned in hotel circulars.

Corporate hosts and VIP desks

Corporate and hotel desks often need chauffeur even when wedding SKU is irrelevant. Keep configure chauffeur available on ordinary rentals for stores that roster drivers. Tie the service switch to real staffing: a store that enables chauffeur with nobody on shift creates guaranteed SLA failures.

Enterprise approval flows (pre/post) still apply when you use corporate accounts—chauffeur is a fulfillment mode, not a bypass of approval.

Condition photos stay mandatory

VIP does not mean skip odometer and photos. Dispatch uploads and return uploads protect both the store and the customer when bumpers meet parking pillars. Secondary payment for return extras remains available; chauffeur bookings can still incur over-mileage or overtime when those rules apply.

Remote unlock / lights / horn help handover; they do not assign the human chauffeur. Checklists should list driver assignment as a blocking step, not a footnote.

Packaging the fee without awkward silence

Show chauffeur fee beside the return method at checkout. Mirror it in grade pricing plans so store managers are not inventing WhatsApp prices. If a store needs a holiday chauffeur premium, change the plan—do not whisper a second invoice.

Coupons, when enabled, should have a clear policy: do they apply to chauffeur lines or only base rent? Decide before the first wedding Saturday.

Training store staff in ten minutes

Hand stores a short checklist, not a PDF novel:

1. Service switch: chauffeur on only if a driver can be assigned today.
2. Checkout: show configure-chauffeur fee before pay.
3. Wedding: never promise self-return.
4. Dispatch: photos + odometer + named driver before “awaiting pickup.”
5. Return: condition evidence first; extras via secondary payment second.

Mystery skip of step 4 is the #1 VIP no-show pattern. Mystery skip of step 5 is the #1 deposit fight pattern.

Soft bundling without inventing features

You can market “car + driver packages” as long as the underlying order still uses documented return mode and fee fields. Do not invent tip jars, card pre-auth, or flight meets. If a hotel wants a meet-and-greet, that is staffing and SLA—not a fake flight API line item.

What this is not

• Not P2P keyless carsharing protocol claims—this is store rental with optional chauffeur.
• Not tips, Stripe, or bank cards beyond documented pay methods.
• Not flight tracking.
• Not a claim that chauffeur fee replaces deposits or over-mileage lines.

Soft next step

If VIP and wedding revenue still lives in chat, turn on configure chauffeur, publish the store fee, lock wedding to chauffeur return, and force driver assignment at dispatch. When the order line matches the person at the curb, car rental software is doing the commercial job self-drive-only checkout cannot.