FARE STRATEGY

Fare-Filter Settings: Worked Examples

Understand reject, wait, and accept thresholds, then build rules from your own trip costs.

What a Fare Filter Does

A fare filter compares a recognised request amount with rules you configure. Rope can use these rules before attempting an action on a supported request. It does not set platform prices, predict the next request, or determine profit. Review the selected mode: a minimum fare rule and a steady-mode wait range are different.

Start with the Cost of a Trip

Include pickup travel, trip distance, waiting, fees, fuel or charging, maintenance, and the return journey. Divide the payout you actually retain by total working time when reviewing a shift. A large displayed fare can still represent an unsuitable trip. This guide has no measured claim that filters raise earnings.

A Worked Threshold Example

Illustrative values only: suppose you configure a reject threshold of ₹120 and an accept threshold of ₹220 in steady mode. A ₹100 request is below the reject line. A ₹180 request is in the wait band. A ₹250 request is above the accept line, subject to other rules passing. Check how your current version treats exact boundary values.

These are teaching inputs, not city fare averages or recommended rates. There is no verified universal threshold for Mumbai, Delhi, Bangalore, Hyderabad, Pune, or Chennai. Replace the example with a rule justified by your own vehicle costs.

Review Rules Between Shifts

Demand and waiting can vary through the day. Compare your own records before changing a threshold; increasing it may leave fewer eligible requests. Pause automation and change settings while parked. Do not assume scheduled changes are available in every release: verify the controls actually present in your version.

Read the Offered Payout

Platforms may display pricing and incentives differently. Check the actual driver offer, deductions, and incentive conditions rather than inferring a payout from a passenger surge label. This guide does not establish a surge multiplier filter or a guaranteed premium in Rope. A higher displayed amount still needs a cost check.

Understand Which Distance Is Used

Pickup distance, paid trip distance, and total travel are different. For example, ₹200 divided by a 20 km paid trip is ₹10 per paid kilometre, but adding a 5 km pickup makes it ₹8 per travelled kilometre before costs. This is hypothetical arithmetic, not a platform rate. Check which fields the app recognises, especially when a card is incomplete.

Check Area Rules Carefully

If your current release provides include or exclude areas, keep the list understandable and review actual matches while parked. Similar place names, changed labels, and missing locations can affect recognition. A fare threshold should not override an area you cannot serve. Read the Rope filter walkthrough for the available controls.

Common Configuration Mistakes

After an app update, recheck supported layouts and rule behaviour. Pause if the outcome is unclear.

Fare-Filter Questions

Do filters guarantee profitable rides?

No. The available request fields cannot capture every cost or outcome.

Can filtering affect platform metrics?

Review the platform's current rules. This page cannot guarantee an acceptance rate, rating, or account outcome.

Where should I start?

Read the auto-accept overview, installation guide, and current features; verify a simple configuration while safely parked.

Further reading

Review your setup.
Explore Rope.

Review the current release, supported workflows, and plan terms before enabling a driver utility.

Download Rope
Free to try•2-minute setup•All ride apps