"Zone" gets used loosely in shipping conversations, so it's worth being precise about what it actually means in Shopify, since that's the exact structure Arbyn reads every time it answers a delivery question.
What it does
A shipping zone is a named group of countries (and, inside some of those countries, specific regions) that shares the same set of shipping rates. It lives inside a delivery profile, and a delivery profile can hold several zones. A common pattern is one zone for your home country, another for a handful of nearby countries, and a third, broader zone for everywhere else. Each zone carries its own rates: its own prices, its own free-shipping thresholds, its own carrier-calculated options. That's the whole structure Arbyn is reading from underneath every "do you ship to..." answer.
Where to find it
There's nothing to set up on the Arbyn side. Zones already exist because you configured them in Shopify, under Settings, then Shipping and delivery. To see them the way Arbyn sees them, open Knowledge, then Catalog, then Shipping, pick a profile, and choose View zones & rates.
How it works
A zone is the actual unit that decides cost, not the country by itself. Two customers in different countries can be in the same zone and see identical rates, because the zone is what carries the rate, not the country. A merchant based in the Philippines might have a "Domestic" zone covering just the Philippines, an "ASEAN" zone covering a handful of neighbouring countries at one flat rate, and a "Rest of world" zone that catches everywhere else at a different, usually higher, rate. Ask "how much to ship to Vietnam" and "how much to ship to Thailand" on a store set up like that, and Arbyn gives the same answer for both, because they're both in the ASEAN zone.
A zone's coverage is built from countries, and inside some of those countries, specific regions. The most common shape is a zone that lists a set of countries wholesale, no regions specified, which means the entire country is covered. But a zone can also narrow a country down to specific states, provinces, or territories, most often because a carrier can't reach every corner of it. When that happens, Arbyn reads the exact region list for that country inside that zone. Provinces and regions are covered in full in their own article; this one is about the zone as a container.
Arbyn reads zones the same way whether it's answering live or drafting from stored knowledge. The same underlying data feeds two paths that always agree: a background refresh, roughly every three hours, that stores a summarized version of your zones for fast answers, and a live lookup tool the agent can call mid-conversation for an on-demand check. Both read your delivery profiles directly, so neither one can drift from what your customer is actually charged at checkout.
A shipping zone is not the same thing as a Shopify Market. These are two separate systems that merchants sometimes conflate, because both organize the world into regional groups. A Market controls which products a shopper can see and what currency they're charged in. A shipping zone controls what delivery costs and whether an order can even be shipped to that address at all. A country can be inside a Market's reach and still fall outside every one of your shipping zones, in which case a shopper there could browse and add to bag, but Arbyn would correctly tell them delivery isn't currently available. If you're trying to understand currency or product visibility by country, that's Markets, covered in its own article; this one and the shipping articles beside it are about delivery.
A zone only matters to Arbyn if it has both countries and an active rate. A zone you set up and later emptied out, or one where every rate was switched off, has nothing for Arbyn to quote from a customer asking about it. It's still a zone, structurally, but it's functionally invisible to the agent, in exactly the way an empty shelf is still a shelf. This is one of the things the zones audit flags for you, so a configuration gap doesn't stay hidden until a customer runs into it.
Good to know
Zones inside the same delivery profile don't overlap, by Shopify's own design. A country can only belong to one zone within a given profile, so there's no ambiguity for Arbyn to resolve about which rate applies.
A country can appear in different zones across different delivery profiles, if you run more than one profile (common when a fulfilment app creates its own). Arbyn checks whichever profile actually covers the location the order will ship from.
A zone with no rates configured is the single most common reason Arbyn can't quote a cost. If you've just set up a new zone and haven't attached a rate to it yet, that's exactly what you'll see reflected back at you in the zones audit.
Renaming or restructuring a zone in Shopify is picked up automatically the next time Arbyn's background refresh runs, or immediately the next time the live lookup tool is called.
FAQ
Is a shipping zone the same as a Shopify Market? No. A Market decides which products a shopper can buy and what currency they see. A shipping zone decides what delivery costs and whether it's available at all. They're configured separately and can disagree with each other on purpose, for instance a country you sell into via a Market but genuinely don't ship physical goods to.
Can one zone cover more than one country? Yes, and it's the normal shape for anything beyond a single-country store. A "Europe" zone covering twenty countries at one flat rate is a single zone with twenty countries in it, not twenty zones.
Why did Arbyn quote the same shipping price for two different countries? Because they're in the same zone. That's not a bug, it's exactly what the zone structure means: every country inside one zone shares that zone's rates.
How do I see which zone a specific country is actually in? Open Knowledge, then Catalog, then Shipping, choose your profile, and select View zones & rates. Each zone lists its countries directly, so you can find the one containing the country you're checking.
I deleted a zone in Shopify. Will Arbyn still mention it? No. Arbyn reads your live delivery profiles, so a deleted zone disappears from its answers the next time the data refreshes, at most a few hours later, or immediately via a live lookup.
