Designated Driver Fixed Price vs Metered: Backend Toggle, Fare Stack, Preferential Tiers

Bars want a shouted number. Drivers want traffic and sidewalk time paid. Designated-driver platforms that only ship one religion lose half the night. Fixed-price (一口价) versus metered pricing—with a full component stack and optional preferential mileage tiers—is how you choose the argument you can actually staff.

On Ptaxi’s designated driver app, business modules include a fixed-price order setting: orders priced from estimated distance and duration. Pricing plans document base, distance, time, long-distance, and waiting components, pricing cycles, and preferential pricing by mileage stage (admin switch). Passengers see estimated price, preferential price, and pricing details when confirming. This piece separates those knobs so night leads stop treating them as synonyms. For curb delay pricing specifically, see designated driver waiting fees at pickup. For multi-driver booking and preferential stage math in venue flows, see multi-driver and preferential pricing.

Two pains, two pricing religions

Fixed-price pain: the guest is drunk, the venue is loud, and nobody wants a surprise meter. A clear up-front number closes the booking.

Metered pain: downtown traffic, long highway tails, and fifteen minutes of “he’s coming down” at the door. A pure fixed quote either banks the risk into every fare (riders feel overcharged on empty streets) or underprices bad nights (drivers churn).

Your job is not to moralize. It is to pick which religion owns which city, which hours, and which SKUs—and to label the admin switches so support tells the truth.

What fixed-price mode documents

Business modules: 一口价计价 / fixed-price — order priced by estimated mileage and duration. That is an up-front quote path, not a “meter plus vibes” hybrid unless you configure the rest of the stack for other modes.

Launch implications:

• Estimates must be credible or fixed price becomes a complaint machine.
• Minimum mileage limits (when enabled) still gate whether a trip can be placed at all—fixed price does not mean “any two-block freebie.”
• Bill confirm and pay methods (passenger pay, driver advance, cash with uploaded collection QR when enabled) still matter after the quote; fixed price is not a payment method.

What metered mode documents

Pricing plan components:

1. Base fare — starting fee (base price + base distance, optional base duration) or base fee (base price only; distance/time decide the rest).
2. Distance fee — per kilometer.
3. Time fee — per minute.
4. Long-distance fee — bands with separate calculation.
5. Waiting fee — rules after the driver arrives at pickup.
6. Pricing cycle — weekdays, weekends, holidays, or custom; different unit prices by time stage.

Metered is how you pay for the night the map lied. It needs rider-facing detail screens so “why did it climb?” is answered with lines, not insults.

Preferential tiers are a third knob

Preferential pricing (admin switch) can set mileage fees per stage and a maximum charge for that stage. Passengers may see both estimated and preferential options with rule breakdowns.

Do not call preferential “fixed price.” Preferential is stage-capped metered kindness. Fixed-price is estimate-locked 一口价. Mixing the words in agent macros creates refund fights you cannot win.

Ops tradeoffs to say out loud

• Fixed-price citywide: venue sales love it; drivers hate bad traffic nights unless you raise the estimate buffer (then short trips feel expensive).
• Metered citywide: fair to drivers on gridlock; venues complain about surprise totals unless waiting and long-distance lines are explained before hail.
• Fixed for short urban, metered for long/suburban: common sense—but only if product labeling and agent scripts match the admin toggle state.
• Preferential stages without training: riders pick the cheap badge, drivers see thinned mileage bands, night leads blame “the algorithm.”

Also keep minimum mileage, acceptance range, and scheduled-order rules in the same workshop. Pricing mode does not replace those gates.

What riders and drivers must see

Riders: estimate / preferential / rule details before confirm; clear cancel rules; order dispute path for fare/route/pay disagreements.

Drivers: order broadcasts that still carry origin, destination, and distance context; bill confirm surfaces that match enabled pay methods; waiting behavior that matches the live pricing mode.

If fixed price is on, do not let drivers invent sidewalk surcharges. If metered is on, do not hide waiting fee lines and expect drivers to “just wait.”

Launch sequence sales can repeat

1. Show pricing plan with base/distance/time/long-distance/waiting and a weekday vs weekend cycle.
2. Enable preferential stages on a demo plan; show passenger estimate vs preferential.
3. Flip fixed-price business setting; place a booking; show the estimate-locked quote.
4. Flip back to metered; show waiting fee behavior at pickup on stage.
5. Walk bill confirm with an enabled pay method—without inventing card brands.

Buyers who want “Uber-simple one number forever” still need to hear the driver retention cost. Put both quotes on one slide.

Choosing modes by city and hour

Many fleets do not need a philosophical forever choice. They need a calendar:

• Dense downtown bar belts on weekend nights → fixed-price for speed of booking and fewer sidewalk debates.
• Suburban long returns and highway-heavy corridors → metered with long-distance bands and waiting fees.
• Corporate daytime transfers → often fixed for purchase-order clarity.

Whatever you pick, publish it. Drivers and merchants should not learn the mode from the first disputed bill.

Bill confirm still matters after the quote

Fixed price answers “what is the trip price?” It does not erase pay-method choices at confirm. Documented options can include passenger pay, driver advance, and cash with collection QR upload when enabled. Go-online reserve rules and income freeze remain separate money controls.

Train drivers: arguing for extra cash on a fixed booking is a policy violation, not entrepreneurship. Train riders: fixed price still requires completing pay on the enabled method.

Preferential stages in merchant venues

Hotels and bars that book through merchant-assisted flows care about a preferential badge they can explain to guests. Stage caps (“this band maxes at X”) are easier to shout across a lobby than a full meter lecture—if agents know preferential is not 一口价.

Keep merchant commission reconciliation on its own finance track. Pricing mode changes do not redefine merchant cut math.

QA script before you flip production

1. Metered plan with waiting fee: driver arrives, wait, confirm waiting line appears as configured.
2. Preferential on: passenger sees both prices + rules.
3. Fixed-price on: same OD shows estimate-locked quote; no live wait creep mid-trip for that mode.
4. Minimum mileage on: too-short OD blocked before pay theater.
5. Dispute path: rider can open order dispute on fare/route/amount.

If any step surprises night leads, rewrite the laminated card before marketing “simple pricing.”

What this is not

• Not tips, Stripe, or bank cards.
• Not WeChat-only packaging for overseas App buyers.
• Not a claim that fixed price auto-includes every highway add-on—bill confirm add-on habits remain a separate ops topic when you use them.
• Not SOS/110 theater. Keep emergency claims out unless you are documenting a real confirmed control elsewhere.

Soft next step

Decide which nights are shouted-number nights and which nights are meter nights. Configure the fixed-price toggle and the metered plan—including waiting and preferential stages—on the same admin tour. When venue managers and drivers can repeat the same definitions, designated driver app pricing stops being a nightly debate and becomes a switch you can staff.