Skip to main content
GullySystem
Automotive

Price Lists and Schemes for Airport taxi services

Apply dated price lists and promotional rules to eligible transactions.

Sales and Distribution

Does this function belong in your operation?

Use when prices vary by customer group, channel, quantity or promotion.

A price or commercial offer changes.

Review an actual selling or distribution arrangement associated with “Airport pickup with flight tracking”. Dealer, commission and credit functions apply only when that arrangement exists in your business.

Bring the records the workflow depends on.

  • Item prices
  • Customer eligibility
  • Validity and combination rules

Outputs to check

  • Effective-dated pricing register
  • Offer eligibility and application record
  • Discount-exception report

Follow the price lists and schemes workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Create the price basis

    Record items, buyer groups and effective dates.

  2. 2. Define offer rules

    Set eligibility, limits and whether offers combine.

  3. 3. Approve publication

    Review exceptions and release the authorised version.

  4. 4. Apply to transactions

    Select the correct terms during quoting or billing.

  5. 5. Review overrides

    Retain manual discounts and preserve historical transaction prices.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Billing clerk

Checks the selected customer terms and raises any requested override through the discount approval rule.

Sales executive

Quotes from the list the customer is on, and knows what the running scheme allows a promise of.

Owner

Sets the lists, approves what goes below them, and sees the discount given this month against last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Two offers overlap

Apply the defined precedence or require review instead of stacking them by accident.

Customer group changes

Use the agreed transaction date and preserve earlier billed prices.

Manual discount requested

Route the exception under the approval limit and record the final authorised rate.

Can this work independently?

Pricing can be maintained independently, but quoting or billing must use the approved selection rules for consistent application. Customer groups and item codes provide eligibility. The price module does not establish stock availability, contractual acceptance or whether a promotion is legally permitted.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Dealer portal: Partner identities, submitted orders and permitted account information.

Configure, test and introduce the workflow.

  • Hand over price sheets, scheme letters and the discount habits of the counter. A note groups them into lists.
  • Decide who sits on which list and how far each role may go. Bills that pick the right rate come back. Try them. Staff raise sample bills from several lists. Corrections return as an adjusted set of lists.
  • Billing clerks and sales staff practise approvals. A reference sheet for the counter follows. The next offer is entered with its dates. A review after it ends checks what each party paid.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Expired offers stop applying.
  • Eligibility rules select the intended buyers.
  • Old transactions retain their original rates.
Airport taxi services

How the business operates.

An airport taxi operator takes advance bookings, counter requests or travel-desk orders and allocates suitable cars and drivers to pickup times. The passenger, the person booking and the paying organisation can be different people. Flight changes, terminal instructions and waiting charges affect dispatch and billing. This illustrative operating model fits an operator managing bookings and trips; a marketplace matching independent drivers requires a different commercial and technical scope.

Booking desk and account service

Record passenger and booker contacts separately, alongside flight, terminal, destination, vehicle class and fare agreement. A hotel or corporate account needs its billing reference and the person authorised to change a booking.

Dispatch and holding-lot coordination

Allocate a driver and car against pickup time and availability. Where the operator runs a holding-lot queue, keep entry and release decisions visible. A revised arrival time needs acknowledgement rather than an assumed change.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking number, booker, passenger and payer contacts
  • Flight, terminal, pickup point, destination and vehicle class
  • Fare rule, waiting allowance and approved extra charges
  • Driver allocation, vehicle assignment and acknowledgement

Operational bottlenecks to check

The flight changes but dispatch does not

A new arrival time is useful only if the dispatcher and assigned driver receive and acknowledge it. Define how the desk responds when a feed or message is unavailable.

Booker and passenger receive different information

A family member or travel desk can hold the booking while the traveller's phone is offline. Specify which details reach each contact and who is authorised to request a change.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Capture and confirm the booking

    Record who is travelling, who booked and who pays. Confirm the pickup instructions and fare basis before treating the car request as accepted.

  2. 2. Review arrival changes

    Update the expected arrival through the agreed manual process or supported feed. Record who acknowledged the changed pickup time and whether the original car and driver remain available.

  3. 3. Allocate the car and driver

    Check availability and the operator's readiness criteria before dispatch. A reassignment needs a recorded reason and updated information for the people relying on the earlier confirmation.

  4. 4. Perform and record the trip

    Capture pickup, destination and completion against the same trip number. Waiting, tolls and other extras need the agreed evidence and approval treatment rather than an unlabelled amount added at settlement.

  5. 5. Reconcile the shift

    Compare trip records with coupons, collected fares and approved expenses. Keep an unexplained difference visible with an owner instead of changing the fare retrospectively to make the cash total fit.

  6. 6. Bill accounts and resolve exceptions

    Prepare corporate or hotel statements from the agreed trip records. Follow disputed charges, cancellation adjustments and missing trip evidence before marking the account period complete.

Industry reports to connect with

  • Bookings and completed trips by pickup period, destination and vehicle class
  • Unassigned, reassigned, cancelled and missed-pickup bookings
  • Driver and vehicle availability against committed trips
  • Shift settlement differences and unapproved extra charges

Questions before implementation.

When should airport taxi services consider price lists and schemes?

Use when prices vary by customer group, channel, quantity or promotion. A price or commercial offer changes.

What should we bring to the requirements discussion?

Bring anonymised examples of Item prices; Customer eligibility; Validity and combination rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Apply dated price lists and promotional rules to eligible transactions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Commercial policy and permitted promotional terms must be approved by your business.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Expired offers stop applying. Use this check when reviewing the first working version.

Talk to us

Discuss price lists and schemes for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements