Ride-Hailing Coupons: Discount vs Reduction, Issuance, and the Passenger List
A promo that nobody can find in the app, or a coupon staff issued with no distribution record, is how ride-hailing marketing loses the plot. Ptaxi’s ride-hailing app documents coupons as an admin-issued instrument: discount or reduction types, a marketing-center screen to add, edit, and delete them and to view distribution status, a grant from the passenger list, and a passenger My Discounts list of available and expired coupons.
This is not a fare-plan article, and it is not a rewrite of reward campaigns. Ride-hailing reward campaigns already cover spending and order-count campaigns, including a coupon as one reward type. Today’s card is the coupon object itself.
Why a coupon needs a list and a distribution record
Operators often start with a spreadsheet and a verbal promise. A rider hears they have a discount. The driver cannot see it. Support cannot tell whether the coupon was issued, already used, or already expired.
The documented answer is two lists. In the passenger app, My Discounts shows the coupon list, including available and expired coupons. In admin, the marketing-center coupon screen lets staff view coupon details and distribution status, after they add, edit, or delete a coupon.
That pairing is the operational hook. A coupon that exists only in a campaign brief, with no distribution status and no passenger list row, is not a product fact you can train. A coupon that appears under My Discounts, and that staff can find again on the distribution record, is.
Do not invent a usage report with conversion rates, a city filter, or a fraud score. The list says details and distribution status. Open those screens in a demo and write down the columns you actually see.
Discount versus reduction — two types, confirm the math in a demo
The coupon screen divides coupons into discount coupons and reduction coupons. That is the documented type split. It is also as far as the list goes on the math.
Do not brief a 10 percent example, a “$5 off $20” threshold, a maximum discount cap, or a stacking rule as a product fact. The names are in the list. The formulas are not. In a demo, create one coupon of each type, read the fields on the form, and copy the labels. Then say those labels in the sales conversation, not a rule you assumed from another product line.
The tradeoff sits in how you explain the two types to dispatch and to finance. A discount coupon is usually easier to describe as a rate off the fare. A reduction coupon is usually easier to describe as an amount off. Until the demo form confirms the fields, treat those as ordinary language, not as documented calculations. If your build shows a threshold, a cap, or a valid-until date, write those down. If it does not, do not put them in the proposal.
Creating, editing, and deleting live on the same screen. A deleted coupon is not described further. Confirm in a demo what a passenger still sees under My Discounts after staff delete or edit a coupon that was already issued. Do not invent a clawback or a grandfather rule.
What the passenger actually sees: available and expired
My Discounts is the passenger-facing list. It includes available coupons and expired coupons. That is the whole passenger contract in the list.
The list does not document a confirm-order checkbox, an auto-apply toggle, a promo-code field, or a share button. If your demo lets a rider apply a coupon when they select a vehicle type or confirm the order, write down that step. If it does not, do not brief a checkout picker as a product fact. Train what is documented: the passenger can view the coupon list, and can tell available from expired.
That is a real tradeoff. A list without a documented apply step can still be useful as a wallet of grants the rider can see. It can also confuse a rider who expects to tap a coupon onto the fare estimate. Do not fill that gap with a sentence the list does not support. Show the list in a demo, complete a test trip, and note whether a coupon was applied, and where.
Expired coupons staying visible is useful for support (“you had one, it lapsed”). It can also clutter the screen if old grants pile up. The list does not describe a hide-expired control. Confirm the behavior by issuing a coupon, letting it expire or setting it expired in the demo, and opening My Discounts again.
Admin issuance, and granting a coupon from the passenger list
Day-to-day issuance has two documented staff paths.
The first is the marketing-center coupon screen: add, edit, delete, view details, and view distribution status. Use this when you are defining the coupon itself. Distribution status is how you later answer “did this coupon actually go out?”
The second is the passenger list. Staff can view all passengers, open passenger details, and perform coupon distribution, along with top-up, account suspension or reinstatement, and push notifications. Those other actions belong on other cards. Here, the point is that a grant can be aimed at a passenger record, not only at a campaign of people who later qualify.
The tradeoff is control versus speed. A named grant from the passenger list is slower and easier to explain to a complaining rider. A coupon that exists in the marketing center, with a distribution status you can reopen, still needs a clear story for who received it. The list does not describe a bulk-upload of passenger IDs, a tag-based audience, or an automatic expiry job. If the demo form includes a recipient picker or a quantity, copy it. Do not assume it.
When you rehearse, issue one coupon from the passenger list, then find that grant in distribution status and under that passenger’s My Discounts. If any of those three places disagrees, you have an operations issue to resolve before launch, not a missing feature to invent in the brief.
A short pointer to campaign-granted coupons, then stop
Passenger reward campaigns can grant a reward automatically when a spending threshold or a completed-order count is met. The reward type can be balance or coupons. That setup, including the campaign types, already has its own walkthrough. One sentence is enough here.
Do not retell spending campaigns, order-count campaigns, or driver marketing. If a coupon in My Discounts arrived from a campaign rather than from a passenger-list grant, say so in the demo notes. Then come back to the coupon types, the list, and distribution status. Those are today’s objects.
What not to promise on ride-hailing coupons
Do not invent the discount math, a reduction threshold, stacking, or a default expiry. Confirm those on the coupon form in a demo.
Do not brief a checkout apply control, an auto-apply toggle, or a shareable promo code unless the demo actually shows it. The documented passenger screen is a list of available and expired coupons.
Do not turn this into a reward-campaign article. Campaigns can grant coupons. They are a related source, not this screen.
Do not claim targeting by city, vehicle type, or passenger tag. Do not claim click reports, redemption-rate dashboards, or a third-party coupon network. The list gives you types, details, distribution status, a passenger-list grant, and My Discounts.
Do not name a card rail or a payment provider. If a coupon changes what the rider pays, describe payment as configured in-app payment methods and account balance.
A short ops checklist before you brief the app
Keep this to one page.
- In admin, open the marketing-center coupon screen. Create one discount coupon and one reduction coupon. Copy the form fields. Do not brief formulas the form does not show.
- View coupon details and distribution status on that same screen. Write down the columns.
- On the passenger list, distribute a test coupon to one passenger. Leave top-up, suspension, and push for other rehearsals.
- In the passenger app, open My Discounts. Confirm the grant appears as available. After it lapses, or after you expire it in the demo, confirm it appears as expired.
- Complete one test trip and note whether a coupon was applied, and where. If the list and the demo disagree, record the demo behavior. Do not upgrade it into a documented checkout feature in the proposal.
- Open a campaign only long enough to see that a coupon can be a reward type. Do not rebuild the campaign card here.
Close
Ride-hailing coupons are a typed object staff can create, edit, and delete, with a distribution record and a passenger list of available and expired grants. A passenger-list grant is the support path when one rider should receive a coupon now. Discount versus reduction is the documented type split; the math belongs in a demo, not in a guessed example.
If you run a ride-hailing company and marketing still tracks coupons in a spreadsheet, walk this path in a ride-hailing app demo. Create both types, issue one from the passenger list, and check My Discounts plus distribution status. If you also need spending or order-count campaigns that grant a coupon automatically, use the reward campaigns post, then come back to this card for the coupon itself. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
What coupon types can a ride-hailing admin create?
The marketing-center coupon screen divides coupons into discount coupons and reduction coupons. Staff can add, edit, and delete coupons, and can view coupon details and distribution status. The list does not define the math behind each type, the stacking rules, or an expiry default. Confirm those values in a demo.
Where does a passenger see ride-hailing coupons?
Under My Discounts in the passenger personal center. That screen is a coupon list, including available and expired coupons. The list does not document a checkout picker, an auto-apply toggle, or a share-a-code flow. In a demo, issue a test coupon, open My Discounts, and write down how a coupon moves from available to expired.
Can staff give a coupon to one passenger?
Yes. On the admin passenger list, staff can distribute a coupon, along with neighboring actions such as top-up, account suspension or reinstatement, and push notifications. Those other actions are not this card. The coupon screen’s distribution status is the place to see whether issuance was recorded.
Are reward-campaign coupons the same as marketing-center coupons?
They can land in the same passenger list, but they are not the same setup. Passenger reward campaigns can grant a balance reward or a coupon when a spending or completed-order threshold is met. That campaign setup already has its own post. This article stays on coupon types, the My Discounts list, admin add/edit/delete, distribution status, and a grant from the passenger list.