Delivery areas and vicinity

Vicinity delivery lets Tradar operations define how far each physical supermarket branch will deliver from its own location. When enforcement is enabled, Tradar checks the straight-line distance between the branch pin and the shopper's confirmed delivery pin before the shopper can pay.

This is branch-specific. If a supermarket has more than one location, each branch needs its own confirmed location and delivery radius.

The supermarket confirms the branch location

The supermarket confirms its physical branch during onboarding. It can later correct the pin from Settings → Storefront → Store Location.

1. Search for the branch by address, estate, business, or nearby landmark.
2. Choose the correct Google Maps suggestion.
3. Check the address and map preview. Use Change if the pin is not the physical pickup branch.
4. Save the onboarding step or Store Location setting.

The dashboard does not ask staff to type latitude or longitude. Tradar resolves and stores those coordinates from the selected Google Maps result. The Google API key remains on Tradar's server rather than in the browser.

The supermarket cannot set or disable its own delivery radius. Its dashboard shows the current coverage as read-only and explains that Tradar operations manages it.

:::warning Confirm the real pickup branch The branch pin is the centre of the delivery circle. A pin placed at a head office, landmark, or different branch will produce incorrect delivery decisions even if the written address looks reasonable. :::

An admin sets delivery coverage

In the admin app, open the supermarket record and find Delivery coverage.

1. Confirm that the branch location is present and looks correct.
2. Set the delivery radius. The platform default is 2.5 km, and admins may choose from 0.5 km to 25 km when operations require an exception.
3. Turn on Enforce vicinity delivery and save.

The admin API rejects enablement when the supermarket has not confirmed valid branch coordinates. The vendor API does not accept delivery-area changes, so hiding the field in the supermarket dashboard is not the only control. Any radius or enablement saved through the older vendor-controlled flow is treated as legacy; enforcement stays off and Tradar uses 2.5 km until an admin explicitly saves a coverage policy.

What shoppers experience

At checkout, a shopper searches for an address, estate, business, or landmark and chooses one of the Google Maps suggestions. Tradar shows a map and formatted address for confirmation; there are no separate city, state, postcode, or coordinate fields to edit.

Once saved, the checkout presents one active Delivering to card. If the address is within range, the card shows the confirmed distance. Other saved addresses stay inside the Change chooser so a long address book does not overwhelm checkout.

If the selected address is outside the radius, Tradar pauses pricing and payment. The shopper sees:

• that the address is outside the delivery area;
• the address-to-branch distance and the branch's configured radius;
• an option to choose another saved address; and
• an option to add a new address.

An older saved address without a confirmed pin is marked Location needed. The shopper must add it again through address search before Tradar can evaluate it.

How enforcement works

Tradar calculates the great-circle distance between the branch and delivery coordinates. In other words, it measures the direct geographic distance between the two pins; it does not currently calculate driving distance, traffic, or road boundaries.

The rule is enforced twice:

1. Checkout quote. Tradar checks the selected address before returning item pricing, delivery fees, and the order total.
2. Order creation. Tradar checks again immediately before creating the payment transaction.

The second check is authoritative. It prevents a shopper from bypassing the rule with a stale checkout page or a direct API request, and it catches a branch location or radius changed after the quote was shown.

When the order is created, Tradar snapshots the delivery address, its coordinates, the measured distance, the radius used, and the branch origin. Later changes to the shopper's saved address or the supermarket's settings therefore do not rewrite the delivery decision recorded on an existing order.

Enforcement states

State	Checkout behaviour
Enforcement off	Delivery continues without a radius gate.
Address within radius	Pricing and payment continue.
Address outside radius	Pricing and payment pause until another address is selected.
Address has no confirmed coordinates	The shopper is asked to add it again using address search.
Branch has no confirmed coordinates	Delivery is temporarily unavailable until the supermarket fixes its Store Location.
Pickup-only store	The delivery-radius gate is skipped.

All supermarkets use a 2.5 km radius unless a Tradar admin explicitly saves another value. Vicinity enforcement remains off for new supermarkets until the branch confirms its location and an admin enables it.

Operational guidance

Admins should keep the 2.5 km default unless operations evidence supports an exception. Use a radius the branch can serve reliably during ordinary traffic, not the furthest trip a rider could theoretically make. Watch failed address attempts, late deliveries, and rider turnaround times before widening it.

Changing the radius affects new quotes and new orders immediately. Orders already created keep the distance and radius snapshot captured when they were placed.