Delivery zones and service areas
Delivery zones and service-area checks for NZ websites
Delivery zones help answer one practical question after a user selects an address: do we deliver or service this address? StreetKit can combine selected NZ address data with radius rules, branch rules, local geography rules, and managed road-aware Drive Zones.
What it does
A delivery-zone or service-area check starts with a selected StreetKit address. Your site can then classify the address using customer-owned rules and show an explicit result such as available, paid local delivery, quote required, nearest team, or outside standard area.
Feature status: Radius is available now for estimated straight-line checks. Drive Zones are a managed setup for teams with fixed depots, branches, clinics, warehouses, or service bases that need bounded road-aware eligibility checks.
Supported rule styles
Radius rules
Use estimated straight-line distance from selected address coordinates when a simple local radius is good enough.
Nearest branch
Compare the selected address with configured depots, branches, clinics, warehouses, or field teams.
Suburb, city, or TA rules
Use structured address fields for simple customer-owned suburb, city, or territorial-authority service rules.
Managed Drive Zones
Use bounded road-aware service areas for fixed origins where the same eligibility check runs many times.
How managed Drive Zones work
Drive Zones are best for repeated checks from known origins. A delivery company might need checkout eligibility from one depot; a clinic network might need the nearest branch; a field-service team might need standard, extended, and quote-required coverage.
StreetKit helps define practical limits before anything is enabled: max drive time, max distance, regions, number of origins, update frequency, customer messaging, and fallback behaviour for unknown results.
The result is designed for fast website workflows such as delivery availability, nearest-team hints, service-area checks, and quote-required messaging. Flexible address-to-address routing remains a better fit when every request has different start and end points.
Example use cases
- Free delivery zone for addresses inside a configured area.
- Paid local delivery for nearby addresses outside the free tier.
- Quote required when the result is outside standard coverage or unknown.
- Nearest branch or team selection after address capture.
- Franchise or service-territory routing for fixed areas.
What we need to know
- Origin addresses for depots, branches, service bases, or teams.
- Coverage thresholds such as standard, extended, and quote-required areas.
- Whether the workflow is checkout-grade, reporting-only, or internal-use only.
- How often coverage should be reviewed or refreshed.
- What the website should show when an address is outside coverage or unknown.
Drive Zones need sensible limits so they stay fast, affordable, and clear for customers. Contact us if you want road-aware delivery or field-service eligibility checks.
Limitations
- StreetKit delivery-zone checks are not courier certification.
- They are not NZ Post delivery certification.
- They do not use live traffic.
- Drive Zones are managed fixed-origin checks, not arbitrary address-to-address routing.
- Road-aware estimates can differ from courier networks, local restrictions, and real-time conditions.
- Service-area rules and customer messaging remain owned by the business using StreetKit.