Taxi Dispatch Software

Taxi Cancellation Rules: Passenger Fees, Driver Daily Caps, and Desk Cancels

A late cancel can leave a driver with empty miles. A driver who cancels too often leaves passengers waiting. And sometimes the desk has to void a job before the bill is confirmed. Ptaxi’s taxi dispatch software documents taxi app cancellation rules in three places: a passenger fee after the free-cancellation time, company-scoped driver caps that lock further cancels that day, and a desk cancel before the driver confirms the bill.

This article stays on those taxi-list facts. It is not a rewrite of ride-hailing cancellation rules, which use a different rule shape. The 10-minute unaccepted auto-cancel already has its own post; one pointer is enough.

What a passenger cancel actually costs

In the passenger app, cancel is a tap. A popup asks whether to cancel. That confirm step is the whole passenger-facing contract in the list.

The fee sits in the backend. Staff can view and configure passenger cancellation rules. If a driver has already accepted the order and the rule conditions are met, canceling requires a cancellation fee. The admin wording is the same idea in a different phrase: after the free-cancellation time is exceeded, the passenger must pay a cancellation fee.

The list does not name the default free-cancel window. It does not name the fee amount. Do not brief a short free window or a fixed charge as a product fact. Open the passenger cancellation rules in a demo and write down the values your build actually uses. Until then, brief it as a configurable free window plus a fee when a driver has already accepted and the rule conditions are met.

That is the tradeoff you should say out loud. A late passenger cancel after acceptance is what creates empty miles. A fee after the free window is the documented way to put a cost on that. A tight window protects the driver. A loose window is easier for the passenger and leaves more unpaid deadhead. The list does not sell a packaged policy.

Driver cancels are capped by company, for that day

On a taxi order in progress, the driver also taps to cancel, and a popup asks whether to cancel. After a cancel, a real-time popup reminds both the passenger and the driver.

The backend can set driver cancellation rules. If the cancel count exceeds the limit, the driver cannot cancel again. The admin screen is more specific, and this is the taxi hook: rules are configured by company, and after the driver exceeds the cancel count, the driver cannot cancel again that day.

Do not import ride-hailing wording here. That list uses a different rule shape, including at-fault and no-fault cancels. Do not import designated-driver service-score deductions. This post stays on the taxi cap: company-scoped, same-day, and it locks further cancels once the count is exceeded.

The list does not name the default daily count. Confirm that number in a demo, company by company if you run more than one. A platform that runs several companies should treat this as a per-company setting, not as one global switch. The list says the rules are configured by company. It does not say a cap set for one company automatically applies to the others.

The tradeoff is the same one a fleet manager already feels. A tight cap protects the roster from a driver who cancels too often. It can also strand a driver in a real exception — a breakdown, a blocked road, a passenger who cannot be found — once the day’s count is used up. A loose cap leaves more room for those exceptions and leaves more passengers waiting. The list does not document a grace override or a manager unlock button. Do not invent one.

The desk can cancel before the bill is confirmed

On the admin order list, customer service can cancel the order in the backend before the driver confirms the bill. That is the documented desk path for a job that should not continue, or that should not be billed.

The trigger is the bill-confirm boundary, not a named list of exception types. The list does not say the desk can cancel after bill confirm. Do not brief a post-billing void as a product fact. In a demo, open an accepted job that has not reached bill confirm, cancel it from the desk, and note what the passenger and the driver see. The driver-app path already documents a real-time popup after a driver cancel. The list does not say the same popup fires after a desk cancel. Write down what you see.

Train the desk on that boundary. If the driver has already confirmed the bill, this article does not give you a documented cancel action. Handle that case as an operations question in the demo, not as a feature you can already quote.

Cancellation-reason text is a neighboring config

The rating-tags screen also holds configuration of rating tags, cancellation reasons, complaint reasons, and refund reasons. Mention it as adjacent content configuration. It is not the rule engine, and it is not an audience-tags post.

Do not invent a cancel-reason taxonomy. The list says those reason texts can be configured. It does not publish the default labels. If a buyer wants the wording passengers or drivers pick at cancel time, open that screen in a demo and copy the labels. Then come back to the fee, the daily cap, and the desk cancel. Those are the rules.

A short pointer to unaccepted auto-cancel, then stop

Orders with no driver after more than 10 minutes are auto-canceled. That timeout, and the pool split that sits next to it, already has its own walkthrough on taxi order pool and unaccepted timeout. One sentence is enough here. Do not retell that post. Today’s rules are about cancels after a person acts: a passenger fee, a driver daily cap, and a desk cancel before bill confirm.

What not to promise on taxi cancellation rules

Do not invent the free-cancel minutes or the fee amount. Do not invent the driver’s daily cap. Confirm those values in a demo.

Do not rewrite this as a ride-hailing cancellation article. Do not describe at-fault versus no-fault rules, or service-score deductions, as taxi facts. Do not turn cancellation-reason configuration into a tags training. Do not claim a packaged policy, a grace-period default, or a manager override the list does not describe.

Do not spend this page on the unaccepted-order timer. Link it, then return to the three human cancel paths.

A short ops checklist before you brief the app

Keep this to one page.

  • In the passenger app, start a taxi order, let a driver accept, and cancel. Confirm the popup asks whether to cancel. If the rule conditions are met, note whether a cancellation fee is required. Write down the free-window and fee values you see; do not brief invented numbers.
  • In admin, open passenger cancellation rules. Confirm staff can view and configure them, and that a fee applies after the free-cancellation time is exceeded.
  • In the driver app, cancel a taxi order in progress. Confirm the confirm popup, then confirm the real-time reminder to both sides.
  • In admin, open driver cancellation rules. Confirm they are configured by company. Push a test driver over the cancel count and confirm that driver cannot cancel again that day.
  • On the admin order list, cancel a job before the driver confirms the bill. Do not demo a cancel after bill confirm as a documented action.
  • Open the rating-tags screen only long enough to show that cancellation-reason text is configured there, along with rating tags, complaint reasons, and refund reasons. Then leave it.
  • If a buyer asks about unaccepted jobs, point to the order-pool and timeout post and do not retell it.

If a script starts promising a default free window or a fixed fee, cut it back to configurable passenger rules, a same-day company cap for drivers, and a desk cancel before bill confirm.

Close

Taxi cancellation rules sit in three documented places. A passenger who cancels after a driver has accepted, and after the free-cancellation time, pays a cancellation fee. Drivers are capped by company, and once the count is exceeded they cannot cancel again that day. Customer service can cancel from the order list before the driver confirms the bill. Cancellation-reason text is a neighboring config on the rating-tags screen.

That is enough to brief empty miles, habitual driver cancels, and a desk void. It is not enough to sell a default free window, a fee amount, or a policy pack the list does not describe. Look at the cancel rules on the taxi dispatch software product page. If you want a walkthrough, ask for a demo and bring one passenger cancel after acceptance, one driver who is near the daily cap, and one desk cancel before bill confirm.

Frequently asked questions

When does a passenger pay a cancellation fee on a taxi order?

The passenger taps to cancel, and a popup asks whether to cancel. If a driver has already accepted the order and the passenger cancellation-rule conditions are met, canceling requires a cancellation fee. The admin screen states the same idea another way: after the free-cancellation time is exceeded, the passenger must pay a cancellation fee. The list does not name the default free window or the fee amount. Confirm those values in a demo.

What happens when a taxi driver exceeds the cancel count?

Driver cancellation rules are configured by company. After the driver exceeds the cancel count, the driver cannot cancel again that day. In the driver app, cancel is a tap with a confirm popup, and a real-time popup then reminds both the passenger and the driver. The list does not name the default daily count. Confirm that number in a demo, company by company if you run more than one.

Can customer service cancel a taxi order from the admin desk?

Yes, but only before the driver confirms the bill. On the admin order list, customer service can cancel the order in the backend up to that boundary. The list does not say the desk can cancel after bill confirm. Do not brief a post-billing void as a product fact.

Does this article cover the 10-minute unaccepted auto-cancel, or ride-hailing cancel rules?

Only as a pointer. Orders with no driver after more than 10 minutes are auto-canceled, and that timeout already has its own post on the taxi order pool. Ride-hailing cancellation rules are a different product list, with a different rule shape. This article stays on taxi passenger fees, company-scoped driver daily caps, and desk cancels before bill confirm.

Related articles

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.