---
title: "Business delivery zone model"
description: "A DeliveryZone defines delivery availability and pricing for a business."
canonical: https://docs.ordering.co/api-reference/guides/delivery-zone-model/
---

# Business delivery zone model

A `DeliveryZone` defines delivery availability and pricing for a business. A zone can belong directly to one business and can also be shared with other businesses through a separate association.

## Operations

| Action | Method   | Resource                                               |
| ------ | -------- | ------------------------------------------------------ |
| List   | `GET`    | `/business/{business_id}/deliveryzones`                |
| Find   | `GET`    | `/business/{business_id}/deliveryzones/{deliveryzone}` |
| Create | `POST`   | `/business/{business_id}/deliveryzones`                |
| Update | `PUT`    | `/business/{business_id}/deliveryzones/{deliveryzone}` |
| Delete | `DELETE` | `/business/{business_id}/deliveryzones/{deliveryzone}` |

Authentication is required. Business managers should use operations only for businesses associated with their account.

## Shared concepts

Representative model fields include `id`, `business_id`, `name`, `type`, `address`, `data`, `dropdown_option_id`, `price`, `minimum`, `schedule`, `enabled`, `hourly_delivery_times`, `snooze_until`, `price_percentage`, and `recipient`. The `businesses` relation represents sharing.

The documented schema lists zone `type` values `1` through `5`; their meaning and validation depend on the operation. Do not treat the list as a complete enum. On update, verify business IDs before changing sharing associations through the `businesses` array.

This guide provides common context, not a complete request or response schema.