How to Plan Distance-Based and Zone-Based Delivery Pricing

Choose a pricing model that matches how jobs are charged

Use distance pricing when journey length is central to the charge and you can define how that length is measured. Use zones when geographic bands make quotes easier to explain and administer; choose a hybrid when neither approach alone reflects how you price jobs. A simple flat rate may still be sufficient for a limited service area or a narrow range of deliveries.

The right model depends on the jobs you accept and how you want customers and staff to get a quote. Compare not only how each price is calculated, but also what the booking process must ask, what staff need to check and how exceptions will be handled.

Before choosing, review a sample of recent jobs with the people who quote, book and dispatch them. For each job, note the addresses, the service requested, how the current charge was decided and where staff had to make a judgement call. The aim is to find a model that produces understandable quotes for routine work without leaving frequent exceptions to be resolved by hand.

Turn the selected model into booking or dispatch requirements with a short checklist:

• Inputs: List the information needed to calculate a quote, such as pickup and delivery addresses, the selected service and any other pricing inputs the business has agreed.
• Calculation: State the distance measure or zone rules, how the relevant charge is selected, and whether staff can review or amend a calculated quote.
• Exceptions: Define what the booking process should do when an address cannot be placed, a route cannot be assessed, a journey crosses zones or job details change.
• Customer explanation: Decide what the customer sees before confirming, including the locations and pricing basis used, and how a quote requiring staff review is presented.
• Staff workflow: Specify who reviews an exception, what information they need, and how the approved charge is recorded so dispatch and customer service staff see the same decision.
• Scope: Identify whether the rules cover every service and area or only particular job types. Keep a simpler flat rate where it remains adequate rather than adding rules that staff and customers do not need.

These decisions can be documented before selecting or changing software. If you later commission a booking or dispatch system, the written rules give the supplier a practical basis for configuring quotes and handling the cases that need human review.

Decide which job details affect the price

Once you have chosen a pricing model, decide which details of a job actually change the charge. A booking form can collect many useful details, but collecting information does not mean every detail needs to become a pricing rule.

Use this checklist to define the inputs before asking staff or a booking system to apply them:

• Starting charge: Decide whether a job has an initial charge before distance, zone or other additions are applied. State which services and areas it covers, and whether it applies once per booking or to each leg of a job.
• Distance or zone: Specify how this affects the price under the model you have chosen. If distance is included within a starting charge for some work, say where that applies; if the charge depends on a zone, state which parts of the journey determine the relevant zone or zones.
• Service level: Decide whether options such as a scheduled delivery or a more urgent service change the charge. If they do, identify which selectable service options map to which pricing rule. If staff need to confirm availability before quoting, mark those bookings for review rather than implying that every option can be priced automatically.
• Vehicle type: Include this only if selecting a different vehicle changes the charge. Define which vehicle choices trigger a different price or require a manual quote. If vehicle choice is recorded only to help dispatch assign a suitable driver, keep it out of the pricing formula.
• Waiting time: Decide whether waiting is included, charged separately or referred for review. If a separate charge applies, specify the event that starts and ends the charge and how staff record it. Without a clear rule, customers and staff may interpret the same delay differently.
• Additional stops: State whether a booking with more than one collection or delivery point changes the price. Clarify whether the rule applies to each extra stop, to the route as a whole, or only to particular job types. If the route needs staff assessment, make that a quote-review condition.
• Minimum charge: Decide whether the business needs a minimum and define the job types and service areas it covers. Make clear how it interacts with other components: for example, whether it is the lowest total charge or an amount added to another charge. Do not apply it to jobs outside its stated scope.
• Manual-quote conditions: List the situations in which the available inputs do not produce a reliable price. These might include a service the business assesses individually, missing journey details or a combination of options not covered by the rules. Decide who reviews the booking and what they need to confirm before sending a quote.

For each input, record one of three outcomes: it changes the charge, it is included in another component, or it requires a manual quote. This prevents staff from making informal additions and gives whoever configures the booking process a clear instruction.

Keep pricing inputs separate from dispatch information. Access instructions, contact details, parcel description and a preferred collection time may help staff arrange the job without changing its price. Collect those details where they support the operation, but do not make them pricing conditions unless the business has deliberately defined a rule for them.

Finally, keep the rule set as small as it can be while covering the services you actually sell. For each proposed input, check that staff can explain when it applies and that a customer can provide the information needed to receive a quote. If neither condition is met, simplify the rule or leave the job for review.

Make distance measures and zone boundaries unambiguous

Make the geography rule precise enough that two staff members entering the same job would apply it in the same way. Record how distance is measured, where the distance information comes from, what happens when it is missing, and how zone boundaries affect the fare.

• Define the journey measure. State which distance the price uses: for example, the route distance selected under your rules, rather than leaving staff to decide whether to use a direct measurement or a road journey. If the route matters, specify how a route is selected when there is more than one plausible option, such as using the option your business has chosen as its standard. Make the same definition available to the person quoting and to the customer receiving the price.
• Choose and check the distance source. Identify the source the booking process will use and test whether it supports the jobs you handle. A business taking individual bookings may have different needs from one that must price a batch of origin-and-destination pairs. Check the kinds of addresses and journeys that commonly appear in your work, and decide how staff will confirm a result that looks unsuitable. Assess any source against your requirements; no provider is required.
• Set a rule for missing or unusable routes. Decide what the booking process should do if it cannot obtain a distance, or if the result cannot be used to calculate a clear charge. It could stop the customer from receiving an automatic price and flag the job for staff review. Tell staff what to check, such as whether the addresses are complete, and what information they should give the customer while the price is being confirmed. Avoid silently substituting a different measure, as that can make similar jobs appear to be priced inconsistently.
• Make zone boundaries identifiable. Use boundaries staff can apply when taking an order and customers can understand when checking a quote. Document how an address is assigned if it sits on, or close to, a boundary. If zones adjoin, state whether the boundary belongs to one zone, the other, or is handled through a review rule. Keep the boundary description consistent in staff guidance and any customer-facing explanation.
• Choose how journeys across zones are charged. Set out whether the fare follows the destination zone, the zones crossed, or another rule that fits your operation. A destination-based rule can be straightforward to explain, but may not represent every route in the same way. Charging for zones crossed may reflect the journey differently, but staff and customers need to understand how the route determines those zones. Decide how the rule applies to a return journey or a route that crosses a zone without stopping, if those jobs occur in your service.
• Check that the rule can be followed end to end. Walk through a sample booking with the person taking the order: enter the collection and delivery details, review the route or zone result, show the price to the customer, and pass the job information to dispatch. Confirm that staff can see why the geography produced that price and can identify when to refer a job for review. If the same journey could be treated differently depending on who enters it, clarify the rule before configuring the system.

Write rules for exceptions, customer quotes and staff review

Write down how each exception changes the charge and what happens next in the booking process. Customers should be able to tell whether they have a confirmed price or need staff to review the job; staff should be able to explain any change without relying on informal workarounds.

• Out-of-area jobs: Decide whether the booking form should refuse the journey, invite the customer to request a quote, or pass the details to staff for review. Specify what information staff need, such as the collection and delivery locations and requested service, and who is responsible for responding. Do not let an ordinary price appear final if the job is outside the area covered by the pricing rules.
• Multi-drop work: State whether the price covers the full sequence of collections and deliveries or whether each additional stop changes the charge. Define what counts as a stop and what details the customer must provide. If the route or number of stops needs staff assessment, make that a manual-quote case rather than leaving staff to interpret the standard rate differently.
• Cancellations and waiting: Decide which event triggers a charge, how staff record what happened, and what the customer is told before confirming a booking. For waiting, specify how the start and end of the waiting period are established and whether the charge is calculated automatically or reviewed by staff. If the business cannot determine the charge from booking information alone, say so in the process.
• Other exceptional circumstances: Name the cases that need review, such as a change to the job after booking or information that is incomplete. For each, define whether staff can amend the quote, must request more information, or should decline the booking. Keep the list limited: repeated exceptions may mean a missing pricing rule needs to be considered in the underlying model.
• When to show a price: Specify the inputs required for an automatic quote and the conditions that prevent one, such as an unsupported route or a job type that needs assessment. Choose clear customer-facing wording for a calculated price awaiting staff confirmation. Do not label it as final if staff still need to check the details.
• How to explain the charge: Tell customers which details shape the quote, such as the locations, service selected and any declared stops or waiting requirement. Show the charge alongside what it covers, and make clear when an exception may change it. If staff revise a quote, give them a way to explain what changed and why before asking the customer to accept the updated amount.
• Staff review and overrides: Decide who may change a calculated quote and what reason they must record, using clear options such as correcting a job detail, applying an agreed exception or referring an unusual job for review. Keep the original calculation and the revised quote distinguishable in the booking record, so dispatch and customer-service staff can see which amount was communicated and accepted. Set out when the customer must be notified and when their agreement is needed before the booking proceeds.

Use these decisions to write the booking and dispatch requirements. If staff routinely have to bypass the rules for the same kind of job, revisit the pricing model rather than adding another informal exception.

Test the rules before putting them into a booking system

Before configuring software, run the proposed rules against real types of jobs your business handles. The aim is to find unclear inputs and inconsistent outcomes while the rules are still easy to change, rather than discovering them during live bookings.

Build a small set of representative test jobs: a straightforward local delivery, a longer journey, a pickup or drop-off near a zone boundary, a job crossing several zones, a job with an additional stop and an out-of-area request. Include the service and vehicle choices your customers can make. For each case, write down the addresses and other inputs the booking process would collect, then calculate the expected charge using the draft rules. If the job should not receive an instant price, record that it needs a manual quote and why.

Record the customer-facing result as well as the calculation. Note what price or price status the customer would see, which charge components need explaining, and what action staff must take next. For example, an out-of-area request might be sent to dispatch for review rather than shown as a confirmed price. The test should make clear what the customer can do and what information staff need to continue.

Ask dispatch staff to price the same sample jobs independently, using only the written rules. Compare their results and explanations with the expected outcomes. Where staff interpret a boundary, stop or exception differently, clarify the rule and update the test case before it is configured. Keep the original and revised outcomes so the supplier can see what changed and why.

Use this checklist to turn the agreed approach into booking-system requirements:

• Pricing model: State whether charges are distance-based, zone-based or combined, and describe the calculation or decision sequence.
• Charge components: List each input that changes the price, such as the selected service or vehicle, and identify what is included in the main charge.
• Distance measure: Specify how distance is measured, which data source should be used, and what the booking flow should do when a route cannot be calculated.
• Zone map: Provide the intended coverage areas and define how addresses on a boundary, journeys across zones and out-of-area destinations are handled.
• Service and vehicle options: Name the options customers can select and explain which affect the charge or require staff confirmation.
• Minimum charge and exceptions: Document the minimum charge, any exclusions and the conditions that change the normal calculation.
• Manual quotes: Set out which requests must be referred to staff, what information the customer should provide and what status they see while a quote is pending.
• Overrides: Specify who may change a calculated price, what reason they must record and whether the customer sees an explanation.
• Customer quote details: Define what the customer receives, including the price status, charge explanation and any assumptions that need to be clear.
• Test cases: Include the sample jobs, expected outcomes, customer messages and staff actions, so the configured system can be checked against the agreed rules.

Mark each requirement as automatic or requiring human review. Keep the list tied to your actual booking and dispatch process: adding rules that staff do not need can make quotes harder to maintain without improving the service.

Check whether existing tools are enough

Choose the simplest approach that lets staff apply the rules consistently and gives customers a clear price or an honest indication that a quote needs review. A new system is only worth considering if the current process cannot represent the rules that matter to the business.

• Check the tools already in use. Map a typical booking from the customer’s enquiry through quote, dispatch and invoicing. Confirm whether the platform can capture the pricing inputs, apply the agreed rules and flag the exceptions that need staff attention. Test real examples rather than relying on a supplier’s general description.
• Keep manual quoting if it remains manageable. This may suit a business with limited job volumes or few pricing variations, provided staff can find the same information, follow the same rules and explain quotes consistently. Record who can approve a price change and where the final agreed charge is stored.
• Simplify if the rules are hard to use. If customers struggle to understand the quote or staff often need to interpret several overlapping rules, consider whether a clearer distance, zone or combined model would meet the business need. Additional software may not resolve unclear pricing rules or make them easier to administer.
• Consider a tailored booking or dispatch process only where there is a clear gap. It may be worth discussing when established pricing rules and important exceptions cannot be represented clearly in the tools already available. Compare that option with adapting the existing process or using a simpler model.
• Take evidence into supplier discussions. Use the requirements and test cases prepared earlier to show how representative jobs should be priced, what needs manual review and what staff and customers should see. Ask suppliers to explain how their proposed approach handles those cases, then compare it with the current workflow before deciding.