Ride-Hailing Pricing Plans: Base, Distance, Time, Long-Distance, and Waiting Fees
A passenger who is quoted one number at hail and a different logic at drop-off will not trust the next booking. Most of those fights start earlier, when finance never decided whether the first kilometers are bundled into a starting fee, or whether the base is only a flag-drop and distance and time do the rest.
Ptaxi’s ride-hailing app documents an admin Pricing Plan with five price components: base fare, distance fee, time fee, long-distance fee, and waiting fee. Different base fares and unit prices can be set for different time periods. A pricing tier associates the plan with a vehicle tier, and the estimated fare is calculated from the configured rules. A pricing cycle sets whether that plan runs on weekdays, weekends, holidays, or a custom cycle. Passengers can select a pricing tier when they hail.
This is a configuration module, not a surge-pricing engine. Stay on this page for the plan, the periods, the cycle, and the vehicle-tier bind.
Starting fee and base fee are two different base fares
A starting fee lets you set a base price, a base distance, and an optional base duration. Some of the opening distance — and, if you use it, some of the opening time — is already in that base price. The per-kilometer or per-minute fee should not start stacking until those included amounts are used up. Confirm in staging when those fees actually begin, then write it in the fare note you give support.
A base fee sets only the base price. The actual price is then determined by distance and duration. There is no included distance or duration in the type itself. The flag-drop is the flag-drop. Kilometers and minutes price on top of it.
Do not treat these as marketing synonyms. “The first two kilometers are included” is a starting-fee conversation. A fixed open amount plus a clean distance-and-time build is a base-fee conversation. Pick one per plan on purpose. If different vehicle tiers need different logic, create more than one plan.
The module also allows different base fares and unit prices for different time periods. Evening or midday rates can live in those period prices. That is still this module. It is not a separately named “night surcharge” product, and it is not surge pricing. This post stays with the pricing-plan module: components, period unit prices, cycles, and the tier bind.
Distance, time, long-distance, and waiting
After the base, four components do the rest of the documented work.
Distance fee is a price per kilometer, subject to any distance already included in a starting fee.
Time fee is a price per minute. Use it when duration should matter — city traffic, or a trip that is short in kilometers and long in minutes. The product does not say the time fee pauses in motion or only counts while stopped. Watch the build, then write the explanation you will give support.
Long-distance fee lets you set different distance ranges, each calculated separately. That is how you price a longer leg differently from the first stretch, without pretending the per-kilometer rate is flat forever. In a demo, configure at least two ranges and show how a long trip accumulates them. Do not invent a named “airport add-on” inside this module. Airport as a vehicle type or a geofence lives elsewhere.
Waiting fee is the billing rule for waiting time after the driver arrives at the pickup point. It is not a general idling charge for every red light, and it is not a documented fee for waiting at the destination unless your own build shows that. Train staff on the trigger: the driver has arrived at pickup. If you need a grace period, confirm it in staging and write it into policy.
Prepaid versus postpaid belongs with vehicle types and prepaid modes, not in the middle of the plan itself. A plan can be bound to a tier the passenger selects. How and when the passenger is asked to pay is a different configuration area.
Cycles have to match the calendar you actually run
Pricing cycle sets the cycle the plan uses: weekdays, weekends, holidays, or custom cycles.
Finance usually under-briefs this part. A weekday plan that silently runs on a public holiday will look like a bug to the passenger and like a leak to the operator.
Before launch, write down which calendar you mean: which days are weekdays, which holidays you recognize, and who updates that list. The module names the four cycle types. It does not publish a built-in public-holiday calendar for every country. Walk the settings in staging, and assign an owner who keeps holiday cycles current.
Period unit prices and cycles work together, but they are not the same control. A cycle decides when the plan applies. Period prices decide how base fares and unit prices vary by time of day. A Saturday night is both a cycle question and a period-price question. Settle both on paper before you ask a passenger to trust the estimate.
Bind the plan to a vehicle tier, then check the estimate
Vehicle tiers are managed in the backend. Passengers can select a pricing tier when hailing a ride. On the plan, pricing tier sets the vehicle tier associated with the pricing plan. The estimated fare is calculated per the configured rules.
That bind is the difference between a plan that exists in admin and a number the passenger actually sees. If a tier is selectable on hail but is not associated with the plan you think it is, the estimate will follow other rules or look wrong. Do not assume a default bind you have not confirmed.
In a walkthrough, do this in order: open the vehicle tiers you will sell, build one plan, associate it with the correct tier, and set the cycle. Then hail a trip as a passenger, select that tier, and read the estimated fare. Compare it to a hand calculation from the same rules. If they diverge, fix the plan or the bind before you train drivers.
The estimated fare is calculated from the configured rules. That is not a live ticking meter before boarding. Do not promise a pre-boarding meter unless your staging build actually shows one.
What not to hang on this module
Do not call this surge pricing. Period unit prices can express different rates at different times of day; that is not a demand-based surge engine. If you need later-evening rates, use period prices and the right cycle, and name them in your own fare table — not as a module called “night surcharge.” Do not invent an airport add-on inside this plan, and do not add tax lines, tips, or card fees. Payments are not a reason to put a card network into a fare plan. Do not tell the buyer the passenger watches a live meter before they board unless you have seen that meter. This screen is the plan, the period prices, the cycle, and the tier — not vehicle-type rules, prepaid modes, or confirm-bill add-ons.
A short ops checklist before you publish rates
- Each live vehicle tier has a named pricing plan associated with it, and someone has hailed that tier and checked the estimated fare against a hand total.
- Every plan states, in an internal fare sheet, whether the base is a starting fee (base price, base distance, optional base duration) or a base fee (base price only, then distance and duration).
- Distance is per kilometer, time is per minute, long-distance ranges are written with their separate calculations, and waiting is described as wait after the driver arrives at pickup.
- Period unit prices are filled in for the times you actually operate, without calling them surge.
- Cycles are assigned: weekdays, weekends, holidays, or custom. A person owns the holiday list.
- Support scripts use the same component names the admin screen uses. No one quotes an airport fee or a tip line from this module.
- Prepaid or postpaid behavior is checked in the vehicle-type settings, not invented here.
Close
A ride-hailing price the passenger will accept is usually a boring one: a clear base, a per-kilometer and per-minute logic you can explain, a long-distance range that does not surprise people on a longer trip, and a waiting rule that starts when the driver has arrived at pickup. The Pricing Plan is built from those components, with period unit prices, a cycle, and a bind to the vehicle tier the passenger selects.
The estimate is only as honest as that configuration. Look at the plan and tier settings in Ptaxi’s ride-hailing app. If you want a demo, bring the fare table you actually want to run on a weekday and on a holiday, and walk one tier from admin through to the estimated fare. The useful test is whether the number the passenger sees at hail matches the rules you just set.
Frequently asked questions
What is the difference between a starting fee and a base fee?
Both are types of base fare. A starting fee sets a base price, a base distance, and an optional base duration. A base fee sets only the base price; the actual price is then determined by distance and duration. They are not marketing synonyms. Pick one per plan on purpose, and say which you used in the fare sheet you give support.
Is a pricing plan the same thing as surge pricing?
No. A pricing plan is the fare module with base, distance, time, long-distance, and waiting fees, period unit prices, a cycle, and a bind to a vehicle tier. Different base fares and unit prices can be set for different time periods, including later-evening rates, but that is not a demand-based surge engine and this module is not named that way.
How does the passenger see the plan at hail?
Vehicle tiers are managed in the backend, and passengers can select a pricing tier when hailing a ride. The pricing plan is associated with a vehicle tier, and the estimated fare is calculated from the configured rules. The list does not say the passenger sees a live ticking meter before boarding. In a demo, hail the tier and check the estimate against a hand calculation.
What pricing cycles can a plan use?
A pricing cycle can be weekdays, weekends, holidays, or a custom cycle. The product names those four types; it does not publish a built-in public-holiday calendar for every country. Assign an owner who keeps holiday cycles current, and confirm in staging when each cycle actually applies.