How Do Delivery Zones, Minimums and Fees Work?

What should a delivery zone control?

A delivery zone tells the customer and branch whether an address can be served and under what terms. On a restaurant ordering site, the customer enters an address during checkout. The site checks the branch and delivery area before the order is placed.

Nexara supports three ways to describe the area: a radius, named areas, or a polygon drawn around the streets you serve. A polygon can follow a practical boundary when roads, bridges, hills or branch boundaries make distance alone misleading.

• A radius can cover a simple circle around one branch.
• Area-based zones can group neighbourhoods or districts with the same rule.
• Polygon zones can follow a practical boundary instead of a perfect circle.
• A branch can use its own delivery coverage rather than sharing one company-wide map.

The customer should see the delivery charge and any minimum order before confirming payment or cash on delivery. Your call-center agent sees the same customer address and order record when someone prefers to phone.

How do minimum orders and fees work together?

A minimum order sets the smallest basket a zone will accept. A delivery fee covers the trip. Keep both rules visible at checkout so the customer can see why an order is accepted and what it costs.

Use the minimum order when the basket is too small for the route. Use the fee when the route is serviceable but costs more to cover. If you offer free delivery through a promotion, set that campaign separately from the underlying zone rule. Nexara supports free-shipping and minimum-order promotion types on the restaurant's own channels.

Your storefront supports cash on delivery or pickup, card payment online through HyperPay when enabled, and pay at the counter for dine-in. CliQ is not a storefront checkout method.

What does the customer see at checkout?

The customer chooses delivery, enters a phone number and address, and receives the applicable delivery result. Nexara can verify the phone with a one-time SMS code at checkout, then attach the order to the restaurant's customer record.

1. The customer opens your branded ordering website or installable browser app.
2. They add menu items and select delivery.
3. They enter the delivery address and phone number.
4. The site checks the branch's delivery zone.
5. The customer sees the minimum order requirement and delivery fee.
6. They choose an available payment method and place the order.
7. The order appears on the live order board and prints for the kitchen.

If the basket is below the zone minimum, the site tells the customer what is missing instead of sending an incomplete order to the branch. If the address is outside the zone, the customer receives a boundary message before the order reaches your team.

How does this work with your drivers?

You can use the rules with your own drivers or send the delivery to a connected dispatch provider. Nexara's delivery module supports dispatch through Careem Express, TopDeliver and Nashmi. A driver role is also available for a restaurant's own fleet.

For an own-driver operation, the branch can accept the order, assign it to a driver and track its delivery status from the order workflow. For a connected provider, the order can be quoted, booked and tracked through the provider connection, subject to the provider and plan available to that branch.

The zone rule defines whether the address is serviceable and what the customer pays. The restaurant still needs a driver, courier provider and operating process for the order to reach the door.

For an honest comparison of the two operating choices, see own delivery versus aggregators. Aggregator commissions remain separate from your own-site delivery fee. Nexara charges 0% commission on orders through your own website, app and call center, while Talabat and Careem retain their own commissions on orders they bring.

How should a branch set its rules?

Use the streets your branch can serve during its busiest shift. Check routes where drivers lose time, then set the boundary around a repeatable service area.

1. List the neighbourhoods currently served by the branch.
2. Mark streets that regularly create long or difficult routes.
3. Choose a radius, area-based rule or polygon for the boundary.
4. Set a minimum order for each zone.
5. Set a delivery fee that covers the route under your chosen driver model.
6. Place a test order from inside, near the edge and outside the boundary.
7. Check that the order reaches the board and prints the correct ticket.

Run the test from a customer phone, not only from an administrator account. Check the wording, total, payment options and address shown to the branch. If the dashboard and checkout show different information, customers will call the branch.

The dashboard and storefront work in Arabic and English, and prices are configured in Jordanian dinar. For a broader setup guide, read how to set delivery zones and fees.

How does Nexara fit into the order workflow?

Nexara is the order and operations layer beside the till. Website, app, phone, table QR, Talabat and Careem orders arrive in one live queue. Delivery rules are part of the own-channel order path, while the cashier can record the day's net sale at close for reconciliation.

The same platform keeps customer addresses and order history with the restaurant. When a customer calls about a previous delivery or orders again from the same area, the branch can search the record instead of asking for every detail again.

Delivery provider access varies by plan, with Growth allowing 1 provider and Pro allowing unlimited providers.

See the Nexara features page for the wider order, menu, delivery and printing scope. You can also review the restaurant ordering website guide before choosing your domain and checkout rules.