Taxi Exception Orders: False Report, Penalty, Refund, and Price Adjust
A finished taxi trip can still land on the desk as an argument. The meter closed. The rider questions the fare, or the driver flags a problem, or someone on the phone says the trip should not have been billed that way. If the only tool is a spreadsheet and a chat thread, the same case gets handled twice. Ptaxi’s taxi dispatch software documents an abnormal-order list: staff can view every abnormal order on the platform, open the details, and take a documented action — false report, penalty, reject, refund, or price adjust.
This is not a new fare engine, and it is not the passenger dispute form. Taxi order disputes already covered the rider-facing feedback path for fare, route, or amount paid. Today’s card is the admin list and the five actions.
Why a closed taxi trip still needs an exception desk
Dispatchers close the job. The passenger pays with a configured in-app method or account balance, or settles cash at the curb. None of that automatically settles a later fight about the amount, a wrongly flagged case, or a trip that should be unwound.
The documented admin path is the abnormal-order screen under order management. Staff can view all abnormal orders on the platform, open an abnormal order’s details, and operate on that order. The list names five operations: false report, penalty, reject, refund, and price adjust.
Do not treat a complaint reply, a cancellation, or a billing-details row as this feature. The exception list is a queue of abnormal orders plus the actions above.
The list does not say how an order enters that queue. It does not say a passenger dispute auto-creates a row, or that only supervisors can add one, or that a cash trip is always included. Confirm the entry path in a demo, and write down what you see. Do not brief “every disputed taxi job appears here” as a product fact.
The five actions, and the tradeoff in each one
The actions are short to name and easy to over-promise.
A false report is how staff close a case that should not have been treated as abnormal. That keeps the queue honest. It also means someone has to look at the trip first. The list does not name a required evidence field, a second approver, or a note that is written back to the passenger. In a demo, mark a test row as a false report and write down the status you then see.
A penalty is a staff action on the abnormal order. The list names the operation. It does not say who is penalized, what is deducted, or whether the driver’s service score moves. Do not import a packaged fine schedule from another product line. Open the action in a demo and copy the fields in front of you.
A reject is how staff turn the exception down. Useful when the claim does not hold. The list does not say the passenger is notified, or that a rejected case can be reopened. Confirm both in a demo before a sales brief promises a closed-loop message.
A refund returns money on the abnormal order. The list names refund as an operation. It does not publish a partial-versus-full control, a refund-to-balance-only rule, or a link to a card network. Passenger payment on this line should be described as configured in-app payment methods and account balance. Cash settlement, when it happens, is a curb payment with commission taken from the driver wallet. Confirm in a demo where a refund actually lands.
A price adjust (repricing) changes the amount on the abnormal order. This is the lever when the fare was wrong but the trip was real. The list does not say whether add-on highway, bridge, or parking fees can be edited here, or whether a price adjust can be done only before payout. Open it in a demo and write down which amount fields move.
That is the first tradeoff to say out loud. A desk that can refund and reprice can end a fare fight without rebuilding the job. It can also create informal discounts if no one reviews who used the button. The list does not sell a packaged approval chain. If you need two people on a refund, confirm whether role permissions can express that. Do not invent a maker-checker module the list does not describe.
What you actually look at while you decide
The abnormal-order line says staff can view details. It does not itemize those detail blocks.
Regular order details on the same taxi list are richer. They include order info, order logs, operational data, network-security data, fee details, the trip track, complaint info, push logs, and trip audio recordings. That is the evidence pile a dispatcher already has on a normal order.
Use it as context, not as a claim that the exception screen repeats every block. In a demo, open the same trip from the order list and from the abnormal list. Write down whether the detail view is the same, or whether the exception screen is thinner and you still jump to order details for the track and the recording.
Do not brief “exception orders include built-in audio playback” unless the demo shows that player on that screen. The recording field is documented on order details. The exception line only promises details.
Refund reasons are configured with rating tags, cancellation reasons, and complaint reasons. If you use refund on an abnormal order, check whether a reason from that list is required. The exception line does not say it is. The tag screen does not say it is wired to this queue. Confirm the join in a demo, and do not invent a mandatory reason code.
Neighbors to keep off this card
Passenger order disputes are a rider action on fare calculation, route, or amount paid. That walkthrough already exists. An exception row may follow a dispute. The list does not say it must.
Complaints about a driver’s service, and the admin complaint and feedback queues, are a different path. Do not retell them here.
Cancellation rules, cash settlement and add-on fees, and passenger invoicing already have their own posts. A refund on an exception order is not an invoice credit, and a price adjust is not a new pricing plan.
Order accounts and the payment ledger are finance screens. They are not this queue. Mention them only so a buyer does not treat the exception list as the company’s books.
What not to promise on taxi exception orders
Do not invent the trigger that moves an order onto the abnormal list. Confirm it in a demo.
Do not import the car-rental appeal wording, where store and renter feedback are shown and the platform steps in. That shape is not what this taxi screen is described as.
Do not import ride-hailing exception wording as if it were this list, even if the action names look similar. Brief only the taxi document: view all abnormal orders, view details, and the five operations.
Do not name bank cards, credit cards, or a card processor as the refund rail. Do not claim a tax-authority notice, a packaged SLA, or an automatic SMS to both parties after every action.
Do not say trip audio, the track, or complaint info live on the exception screen unless you have seen them there. Point to order details, then confirm the overlap.
The Chinese source has a wording typo (“并对并单”). Treat the operations as applying to the abnormal order. Do not build a “merge orders” feature out of that typo.
A short ops checklist before you brief the app
Keep this to one page.
- In admin order management, open the abnormal-order list. Confirm you can see abnormal orders for the company in the demo tenant, and that a details view opens.
- On one test row, walk each documented action you are willing to use: false report, penalty, reject, refund, and price adjust. Write down the fields, the resulting status, and whether the passenger or driver app shows a change.
- Open the same trip in regular order details. Note the track, fee details, complaint info, and trip audio. Compare that screen with the exception details.
- Open rating-tag configuration and find refund reasons. See whether a refund on an abnormal order asks for one of those reasons.
- Open role permissions and write down who can see the list and who can refund or reprice. If the demo cannot express a two-person refund, say that in the brief instead of inventing a workflow.
- Create one passenger dispute from the app. Watch whether it appears on the abnormal list, and how long that takes. If it does not appear, do not promise an automatic join.
Close
Taxi exception orders are an admin queue for abnormal jobs, with five documented actions: false report, penalty, reject, refund, and price adjust. The list does not publish the entry rule, the approval chain, or the exact detail blocks. Those are demo items, not brochure items.
If you run a taxi or dispatch company and fare fights still live in a spreadsheet, walk this path in a taxi dispatch software demo. Bring one trip that should be refunded, one that should be repriced, and one that was flagged by mistake. Then decide which of the five actions belong in the launch brief, and who may use them. For the rider-facing dispute path, use the order disputes post, and come back here for the admin queue. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
What can staff do on a taxi exception order?
The taxi list documents an abnormal-order screen where staff can view every abnormal order on the platform, open the details, and mark a false report, apply a penalty, reject, refund, or adjust the price. The list does not say which action is required in which case, or who is allowed to use each one. Confirm the buttons and any permission split in a demo.
How does a taxi order become an exception?
The list does not document the trigger. Do not brief a packaged rule such as ‘every complaint becomes an exception’ or ‘every unpaid cash job is auto-flagged.’ In a demo, create a test dispute or a desk-flagged fare and write down how the order actually appears on the abnormal list, if it appears at all.
Is this the same as the passenger order-dispute tool?
No. Passengers can already submit feedback when they dispute fare calculation, the route, or the amount paid. That path has its own walkthrough. This article is the admin abnormal-order list and the five actions staff can take on it. Keep those rehearsals on separate cards.
Does the exception screen include the trip track and audio?
Regular order details on this line include order info, logs, operational data, network-security data, fee details, the trip track, complaint info, push logs, and trip audio recordings. The abnormal-order line only says staff can view details. Confirm in a demo whether that detail view is the same block or a thinner screen.