Regional pricing without a regional pricing team

You already run regional pricing and did not decide to

Somebody asks in a planning meeting whether the brand should try regional pricing. The answer is usually that it sounds complicated, needs a pricing analyst, and is probably a Series B problem.

Then the meeting moves on, and the store carries on charging different amounts to different parts of the country, as it has since launch.

The free shipping threshold was set once for a metro basket. The cash on delivery fee was added after a bad quarter of returns. The flat shipping rate for non-metro pincodes came from a courier rate card.

None of those three decisions was framed as pricing. All three change what a customer pays.

The question is therefore not whether to introduce regional pricing. It is whether to keep running the accidental version or replace it with one somebody chose.

Effective price by zone before any discount

Effective price is what leaves the customer’s account, not what appears on the product page. The gap between the two is where the accidental pricing lives.

The table below is modelled on a Rs 1,800 list price with a shipping threshold that metro baskets clear and remote ones do not, plus a Rs 30 cash on delivery fee in remote zones.

Zone	List	Shipping charged	COD fee	Effective price
Metro core	Rs 1,800	Rs 0	Rs 0	Rs 1,800
Metro outer	Rs 1,800	Rs 0	Rs 0	Rs 1,800
Tier 2	Rs 1,800	Rs 49	Rs 0	Rs 1,849
Tier 3 and remote	Rs 1,800	Rs 99	Rs 30	Rs 1,929

A 7.2% spread, produced by three settings nobody thinks of as pricing.

Note the direction. The customer paying most is the one in the zone where you have the least penetration, the longest delivery and the weakest brand presence.

That is regressive, and it is the default outcome of setting shipping rules from a courier rate card. The rate card is a cost document, and applying it directly to the customer converts your cost structure into your price structure without anyone deciding that was the goal.

Run this table on your own numbers before reading further. Most brands are surprised by the spread and more surprised by which zone sits at the top.

What a zone-gated discount does to that gradient

Now add the mechanic the rest of this cluster is about. A discount live in one pincode at a time, at a depth that concentrates a national budget into a small number of postcodes.

At the modelled budget-equivalent depth of 24.2% in the metro core, the metro customer pays Rs 1,364 and the remote customer still pays Rs 1,929.

The spread goes from 7.2% to 41.4%.

Said from the customer’s side, the remote customer pays 7.2% above list while the metro customer pays 24.2% below it, for the same product on the same day.

That is real regional pricing, achieved without a pricing team, a price table or a single change to a product page. The mechanism is a discount rule.

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.

Because the discount rotates, no single zone holds the low price permanently, which is the difference between this and a standing regional price cut. The zone selection logic sits on the order density work in pincode marketing as a geo lever.

Why the variation belongs in discounts, not price tables

Brands that decide to do regional pricing properly usually reach for the wrong instrument. They build zone-specific price lists, and then discover why pricing teams exist.

Price tables break four things at once. Comparison shoppers screenshot two prices and post them. Marketplace listings and your own site diverge. Every campaign asset needs a price caveat. And somebody has to maintain the tables forever.

A discount rule breaks none of those. The list price stays national and visible, the variation is explicitly temporary, and the whole structure lives in one rule rather than in a table with a row per zone.

There is a second argument that matters more. A price is a statement about what something is worth. A discount is a statement about a window, which is a much easier thing to change your mind about when the numbers come back wrong.

Keep the list price national and put every rupee of regional variation into shipping settings and discount rules. That is the entire operating model, and it needs nobody’s full time attention.

The fairness caveat, stated plainly

This mechanic makes an existing regressive gradient steeper, and any honest account of it has to say so.

The customer in a tier 3 pincode was already paying 7.2% more than the metro customer. After a metro-weighted discount they are paying 41% more. Nothing about their situation changed except that somebody else got cheaper.

Two defences are commonly offered and only one of them holds.

The weak defence is that the discount is temporary and rotates, so every zone gets a turn. In practice rotation lists are built from order density, so dense metro pincodes get many turns and thin remote ones get none.

The stronger defence is that the discount is buying something specific: density, referral concentration, or a demand test in a candidate city. If the discount is buying one of those, it is an investment aimed at a zone for a reason. If it is simply applied to your best zones because they are your best zones, it is a reward for being easy to serve, and there is no defence available.

Framing matters too, and it should be used honestly rather than as cover. A discount reads differently from a surcharge even when the arithmetic is identical, and that asymmetry is real. It is not a reason to pretend the gradient is not there.

The practical test: could you explain your zone selection to a customer in a zone that never qualifies. If the answer is no, change the selection rather than the explanation.

How to decide which zones qualify

Density alone is the wrong criterion, for the reason above. Three better ones, used together.

Zones where you are testing demand. A candidate city with no order history is a zone where a discount is buying information you do not have. This is the most defensible use of the mechanic.

Zones where referral density can compound. A pincode with enough existing customers to forward an offer to people who can use it is buying word of mouth rather than just volume.

Zones where delivery economics are strong enough to absorb the depth. Discount depth and freight cost come out of the same margin, and a deep offer into a high return to origin zone loses money twice.

Measurement has to separate the zone effect from everything else happening that week, because a geo offer, a creator post and a paid campaign will all touch the same buyer.

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.

Compare each live zone against its own previous four weeks rather than against other zones, which is the measurement design in a hyperlocal flash sale without a physical store.

When regional pricing is the wrong answer

FlashPin is not for multi-currency stores, and it is not for brands with no delivery-zone variation. The multi-currency limit bites hard here specifically, because a brand already varying price across currencies has a pricing surface and probably needs the price table approach this article argues against.

Uniform delivery is the other disqualifier. If every pincode costs the same to serve and arrives at the same speed, a zone gradient has no cost basis underneath it, and you are simply charging different people different amounts for reasons you cannot explain.

Low volume disqualifies separately. A brand with 60 orders a month cannot measure whether a zone discount did anything, so the pricing decision would be made on faith.

The limitation worth sitting with is that this mechanic makes a real distributional choice while looking like a marketing tactic. A discount rule is easy to ship, easy to reverse and easy to justify internally, and none of that changes the fact that it decides which customers pay more. Brands that adopt it without ever writing down why a zone qualifies end up with a pricing structure that reflects nothing except which postcodes were already convenient, and that structure will be legible to customers long before it is legible to the team that built it.