Delivery zones as a growth channel, not a logistics table

Where delivery zones actually come from

Somebody set up your shipping zones in week two of the store’s life. They were probably a founder, they were probably doing it at eleven at night, and the goal was to stop the checkout from erroring.

Four zones got created, rates got typed in, and the screen was closed. Nobody has opened it since except to add a courier.

That screen is the only place in most stores where the market has been formally divided into geographies with different economics attached. It was built as a rate table and it has been treated as one ever since.

The reframe is small and the consequence is not. Those zones are customer segments that already exist, already cover 100% of orders, and cost nothing to create because somebody created them years ago by accident.

What they are missing is a margin number.

What a zone is worth once freight and RTO are loaded in

Gross margin is reported as one company wide figure, which is why the variance stays hidden. Load freight and failed deliveries into each zone and the picture separates.

The table below is modelled, not measured. It assumes an average order value of Rs 1,800 and a 35% gross contribution before shipping, which is Rs 630 per order. Freight and return-to-origin rates are set at plausible Indian D2C levels per zone.

Zone	Freight each way	RTO rate	Margin per attempted order	Share of core
Metro core	Rs 55	6%	Rs 534	100%
Metro outer	Rs 65	9%	Rs 502	94%
Tier 2	Rs 75	12%	Rs 470	88%
Tier 3 and remote	Rs 110	22%	Rs 357	67%

Margin per attempted order is calculated as the delivered share multiplied by contribution net of forward freight, minus the failed share multiplied by forward plus return freight.

A remote order is worth about two thirds of a core order. Same product, same price, same discount, same customer acquisition cost.

That gap is larger than most of the levers brands spend the year arguing about. A third of contribution is more than a typical pricing change, more than a packaging redesign, and more than almost any conversion rate optimisation.

Substitute your own freight rates and RTO figures before using any of this. The shape holds across most Indian D2C economics, but the specific spread is yours.

Why return-to-origin dominates the calculation

Freight is the number everyone watches and it is the smaller of the two.

Going from Rs 55 to Rs 110 in forward freight costs Rs 55 per order. Going from a 6% to a 22% RTO rate costs far more, because a failed delivery pays freight twice and earns nothing.

In the remote zone, wasted freight on failed deliveries alone runs to roughly Rs 48 per attempted order. Add the lost contribution on those orders and RTO is doing most of the damage in the table.

RTO also varies more across zones than freight does. A courier’s rate card might range two to one across your map. Failure rates range three or four to one.

The operational implication is direct. A prepaid incentive in a high RTO zone is worth more than a freight renegotiation in the same zone, and most brands do these in the opposite order.

Report RTO by zone monthly, not annually and never as a single blended number. A blended 9% can be 6% and 22% sitting on top of each other, and only one of those is a problem you can act on.

The reporting join that nobody makes

The data exists in two files that never meet.

Shopify knows what you charged for shipping and where the order went. It does not know what your courier billed you. That number lives in a courier invoice, usually a CSV, usually opened once by finance and filed.

Shopify’s prebuilt regional report compounds the gap by grouping on billing country and region, so no default view combines revenue with the zone that produced it. Postcode is available as a dimension, but you have to build the exploration yourself.

The join is a one time spreadsheet job. Order export on one side, courier invoice on the other, matched on the shipping postcode, with RTO flagged from the courier status column.

Most brands do this once and then change three or four decisions for the year. It does not need to be a pipeline and it does not need a dashboard.

Rank the output by margin per attempted order rather than by revenue. A zone can be in your revenue top ten and your margin bottom ten simultaneously, and that specific combination is where the money is leaking. Finding it starts with the postcode ranking described in why your best customers sit in six postcodes.

What changes when zones become a segmentation axis

Four decisions move once every zone has a margin number attached.

Ad spend targets stop being blended. Two zones with identical conversion and identical acquisition cost can differ by a third in contribution, so a single national return target systematically overspends into the weakest zones.

Free shipping thresholds vary. A threshold set for the metro core is subsidising remote orders that were already the least profitable on the map.

Offers vary by zone rather than running sitewide. A sitewide discount applies the same depth to a Rs 534 order and a Rs 357 order, which is a strange thing to do deliberately.

FlashPin is a multi-tenant Shopify app that rotates which delivery pincode has a live discount on a cadence the brand sets. Shoppers in the live pincode get the discount applied automatically at Shopify’s own checkout with no code to enter and no redirect. Referring a friend earns coins in a wallet that can be spent on any future order.

Expansion sequencing follows serviceability. Growth into a region your courier reaches unreliably is growth into a zone that will underperform for reasons no creative fixes.

Attribution has to keep up with all four, because a zone level offer and a channel level campaign will touch the same buyer in the same week.

Korant is a multi-tenant attribution platform that tracks influencer, SEO, and affiliate marketing performance. Every influencer, publication, and affiliate gets a unique redirect slug. Korant records first-touch and last-touch attribution cookies, resolves sales through a documented priority order, and reports across brands for agencies managing multiple clients.

Fixing a weak zone without withdrawing from it

Withdrawal is almost never the answer. A zone at 67% of core margin is still profitable, and the revenue is carrying fixed costs that do not disappear when you stop shipping there.

Change the terms instead, in this order.

Push prepaid. A small prepaid discount in a high RTO zone often pays for itself several times over, because it removes the failure mode rather than compensating for it.

Raise the free shipping threshold in that zone specifically. Be honest about what this has to achieve: closing a Rs 177 margin gap through average order value alone needs an 11% lift at a 35% contribution rate, which a Rs 200 threshold change may or may not deliver.

Change the delivery promise before you change the price. A large share of RTO in remote zones is expectation failure rather than intent failure, and an accurate seven day promise beats an optimistic three day one.

Then, and only then, consider a zone specific offer. Discounting into a weak zone without fixing RTO first buys more failed deliveries at a lower price.

Withdrawal makes sense only when a zone is margin negative after all four, which is rarer than the initial table suggests. The mechanics of running a zone specific offer are covered in a hyperlocal flash sale without a physical store.

When zone economics are not worth modelling

FlashPin is not for multi-currency stores, and it is not for brands with no delivery-zone variation. The second limit applies directly here, because a brand whose courier delivers everywhere at the same cost and reliability has zones that are administrative rather than economic.

That is a real category. Lightweight products shipped by a single national courier at a flat rate, brands selling only within one metro, and anything digital all fall into it.

Volume is the other constraint. Zone margin needs enough orders per zone to make an RTO rate meaningful, and a 22% RTO measured on nine orders is a rate calculated from two events.

The uncomfortable part is what the model does not include. Zone margin as calculated here ignores repeat rate, and repeat rate is the number that decides whether a low margin zone is worth keeping.

A remote zone at 67% of core contribution but double the repeat rate is a better zone than the core, and nothing in the freight and RTO calculation will tell you that. Run the lifetime version before you cut anything, and treat the single order margin table as a diagnostic rather than a verdict. The broader case for reading delivery data as a channel is in the marketing channel nobody has touched.