Skip to content

Pincode Analysis every delivery figure, worked out

Pincode Analysis folds every pincode check in the date range into one read of delivery: how fast Amazon promises to deliver your products, where it will not deliver at all, and how you compare with your competitors at the same pincodes on the same day.

In the app: /product-monitoring/pincode-analysis/ Last updated: 31 October 2026

Where the figures come from

Every figure is measured from the pincode checks your Pincode Monitoring jobs stored for the date range. The page reads the whole range once and works everything out from it; nothing is estimated.

Reading
One day's delivery promise for one ASIN at one pincode. A pincode checked more than once in a day keeps the last check of that day.
Days
The promise as a number of days: Amazon's fastest delivery when it offers one, otherwise its standard delivery. 0 is today, 1 is tomorrow.
Non-serviceable
Amazon says it cannot deliver there. It is never averaged with days; it is counted on its own.
Pair
One of your products at one of its pincodes. Most figures count pairs.
Measured pair
A pair with at least one reading in the range. Most figures use its latest reading.
Competitors
The competitor ASINs mapped to the product in Manage Product Data, read by the same pincode jobs.

A reading with no day count, such as "No delivery date" or "Out of stock" at that pincode, counts as no reading: neither as days nor as non-serviceable.

The top of Pincode Analysis, drawn with sample data.

  1. The date range: a ready-made range from the dropdown, or a range of your own.
  2. Product group, state and search narrow which products and pincodes are read.
  3. Whom you are judged against: the fastest competitor, or the competitors' average.
  4. Nine stat cards; click one to list the rows behind it.

Date range and filters

  • Date range is the last 7 days unless you pick another: a ready-made range from the dropdown (Last 24 hours up to Last 12 months, or All time) or a range of your own. The longest is 92 days: a longer range, Last 6 months, Last 12 months and All time read the last 92 days.
  • Product group, State and the search box (ASIN, SKU, title, nickname or pincode) narrow which pairs are read.
  • vs fastest competitor, the default, judges you against the quickest competitor read at that pincode that day. vs competitor average judges you against the average of their days.

Stat cards

Nine cards sit along the top. Four count what is in the filters, three measure delivery across the measured pairs, and two split the products by their score. Each uses a pair's latest reading in the date range, and every percentage is rounded to one decimal place.

Every card is a button: click it to list the rows behind its number, and click it again to close the list. The list always totals the card. Product cards list products; the others list the competitors, pincodes or pairs they count.

Products monitored

Your products with at least one pincode in the filters: their mapped pincodes, narrowed by product group, state and search.

Products monitored = distinct products across the pairs
Line under it
with readings: how many of them have at least one pincode reading in the date range.
Click it
Lists the rows behind the number, lowest product score first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Pincodes, You Faster, Comp Faster, Tomorrow, Avg Days, Status, Priority.

Competitors seen

Competitor ASINs read at least once in the range at a pincode of a product they are mapped to.

Competitors seen = competitors with a reading at one of their product's pincodes
Line under it
mapped: every competitor mapped to the products in the filters, read or not. The gap between the two is competitors no pincode job has read in the range.
Click it
Lists the rows behind the number, the one faster most often first, in the columns ASIN, Competitor Of, Pincodes Seen, Faster In, Avg Lead, Trend.

Unique pincodes

Distinct pincodes across the pairs.

Unique pincodes = distinct pincodes across the pairs
Line under it
cities: the distinct cities those pincodes are in, from India's postal directory.
Click it
Lists the rows behind the number, where competitors win most often first, in the columns Pincode, City, State, Products, Comp Faster, Avg Gap, Avg Days, Serviceability.

Product x pincode

The pairs: each product counted once at each of its pincodes, however many workspaces list it.

Product x pincode = Σ pincodes of each product
Line under it
measured: the pairs with at least one reading in the date range. They are what the three delivery cards divide by.
Click it
Lists the rows behind the number, competitor faster by 2+ days first, then the largest gap, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Pincode, You, Competitor, Standing, Gap, Checks.

Serviceability

The share of measured pairs where Amazon delivers, by each pair's latest reading.

Serviceability = pairs whose latest reading has days ÷ measured pairs × 100
Line under it
deliverable: the pairs on top of that division.
Click it
Lists the rows behind the number, least serviceable product first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Measured, Deliverable, Non-serviceable, Serviceability, Avg Days.
Example
860 of 912 measured pairs deliver: 860 ÷ 912 × 100 = 94.3%.

Tomorrow coverage

The share of measured pairs whose latest promise is today or tomorrow (1 day or less). Non-serviceable pairs count in the measured total, so they lower it.

Tomorrow coverage = pairs at 1 day or less ÷ measured pairs × 100
Line under it
within 1 day: the pairs on top of that division.
Click it
Lists the rows behind the number, least covered product first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Measured, Within 1 Day, Tomorrow, Avg Days.
Example
534 of 912 measured pairs: 534 ÷ 912 × 100 = 58.6%.

Delivery stability

Of the pairs read on two or more days, the share whose promise was the same on every one of them. A pair read once is left out of both sides, so a one-day range has nothing to measure.

Delivery stability = pairs with one promise all range ÷ pairs read on 2+ days × 100
Line under it
never moved: the pairs on top of that division.
Click it
Lists the rows behind the number, least stable product first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Checked 2+ Days, Never Moved, 3+ Promises, Stability.
Example
860 pairs read on 2 or more days, 612 of them never moved: 612 ÷ 860 × 100 = 71.2%.

Good performing

Products with a reading whose product score is 55 or more: Strong or Good. The score is explained under Good and poor performing products, below.

Product score = (win rate + tomorrow coverage % + serviceability %) ÷ 3Good performing = products with a reading and a score of 55 or more
Line under it
Always "score 55 or more": the line the products are split at.
Click it
Lists the rows behind the number, best score first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Score, Pincodes, You Faster, Comp Faster, Tomorrow, Serviceability, Avg Days, Status.

Poor performing

Products with a reading whose product score is under 55: Watch or Attention. Good and Poor performing always add up to the products "with readings".

Poor performing = products with a reading and a score under 55
Line under it
Always "score under 55".
Click it
Lists the rows behind the number, worst score first, in the columns ASIN, SKU, Nickname, Group, Units Ordered, Score, Pincodes, You Faster, Comp Faster, Tomorrow, Serviceability, Avg Days, Status.
Example
40 products with readings: 27 good performing and 13 poor performing.

How you are compared with a competitor

A comparison only counts when you and a competitor were read at the same pincode on the same day. A competitor's figure from another day would flatter or punish you unfairly, so a pair with no shared day is No comparison and stays out of every competitive figure.

For each pair, the page takes the latest day with both readings and gives the pair a standing:

StandingWhen
You fasterYour days are fewer than the competitor's, or they are non-serviceable and you are not.
Same speedThe same days, or both non-serviceable.
Competitor faster (1+ day)The competitor is quicker, by less than 2 days.
Competitor faster (2+ days)The competitor is quicker by 2 days or more, or you are non-serviceable and they are not.

Competitive Position counts the pairs in each standing, as shares of the pairs judged, and its foot gives the win rate:

Win rate = (You faster + ½ × Same speed) ÷ pairs judged × 100

Example: A win rate

  1. 40 pairs judged: 18 you faster, 6 same speed, 10 competitor faster by 1+ day and 6 by 2+ days.
  2. (18 + ½ × 6) ÷ 40 × 100 = 52.5

"You match or beat the competition in 52.5% of judged pincodes."

Gap = competitor days − your days
  • Positive is your lead; negative is how far behind you are.
  • Your latest days against the competitor's on the latest day you were both read.

Delivery Competitiveness Score

The score and the cards beside it, drawn with sample data.

  1. The score out of 100 and its grade.
  2. The four measures, each with the weight it was given.
  3. Competitive Position: the pairs in each standing, and the win rate.
  4. Average Delivery Time: yours, the competitors', and the gap.

One score from 0 to 100 for everything in the filters, weighted across four measures:

MeasureWeightIts value
Competitive Advantage35the win rate
Tomorrow Coverage25the Tomorrow coverage card
Serviceability20the Serviceability card
Delivery Stability20the Delivery stability card
Score = (35 × Advantage + 25 × Tomorrow + 20 × Serviceability + 20 × Stability) ÷ 100
  • Rounded to a whole number.

A measure with nothing behind it has no value: Competitive Advantage when no competitor was read on the same day, Delivery Stability when no pair was read on two days (a one-day range). Its weight is shared out among the measured ones in proportion, so a measure that could not be taken never drags the score to zero. The card shows each weight as it was used.

Example: No competitor mapped

  1. Tomorrow coverage 60%, serviceability 95%, stability 80%; Competitive Advantage has no value.
  2. The weights left are 25 + 20 + 20 = 65, used as 38%, 31% and 31%.
  3. (25 × 60 + 20 × 95 + 20 × 80) ÷ 65 = 76.9

Score 77: Good.

ScoreGrade
80 to 100Excellent
65 to 79Good
50 to 64Fair
Under 50Needs work

Good and poor performing products

Each product gets a score of its own from 0 to 100, from its own pairs:

Product score = (win rate + tomorrow coverage % + serviceability %) ÷ 3
  • A product with no competitor read on the same day has no win rate, and its score is the average of the other two.
ScoreStatusCounted as
75 to 100StrongGood performing
55 to 74GoodGood performing
35 to 54WatchPoor performing
Under 35AttentionPoor performing

A product with no comparison shows No competitor as its status, and still falls on the good or poor side by its score. Priority in the Product Performance table is 100 − score, so the products that need you most come first.

Example: The page's own example

  1. Faster than competitors at 40% of pincodes and level at 20%: win rate 40 + ½ × 20 = 50.
  2. Tomorrow coverage 10%, serviceability 100%.
  3. (50 + 10 + 100) ÷ 3 = 53

Score 53: Watch, a poor performer.

Delivery time, speed and trend

CardHow it is worked out
Average Delivery Time, yoursThe average days of every measured pair's latest reading. Non-serviceable readings are left out.
Average Delivery Time, competitorsThe average competitor figure (fastest or average, as picked) on each pair's latest shared day.
GapThe competitors' average less yours: positive means you are faster.
Delivery SpeedEach measured pair's latest reading in a band: Today (0 days), Tomorrow (up to 1), 2 Days, 3 Days, 4+ Days or Non-serviceable. One chart for you and one for the competitors.
Delivery TrendFor each day of the range: the average days of every reading that day, yours and the competitors', and the share of your readings that day that were deliverable.

Since the previous check, and persistent issues

Each measured pair's latest reading against the one before it, from its previous day with a reading:

CardCounts the pairs that
Pincodes improvedare now fewer days than before
Pincodes deterioratedare now more days than before
Pincodes held the same speedhave the same days
Became non-serviceablehad days and are now non-serviceable
Became serviceablewere non-serviceable and now have days
Gained tomorrow deliverywere more than 1 day and are now 1 day or less
Lost tomorrow deliverywere 1 day or less and are now more than 1

A pair that gained or lost tomorrow delivery also improved or deteriorated, so it counts in both cards. The pill on a card counts the products behind its pairs.

Persistent issues look across the whole range. A check is one day with a reading.

IssueCounts the pairs where
Competitor faster for 3+ checksthe latest 3 or more comparisons in a row went to a competitor; days with no competitor reading are skipped
Non-serviceable for 3+ checksthe latest 3 or more readings in a row were non-serviceable
Unstable delivery3 or more different promises were read in the range
Never faster than 4 daysthe quickest reading of the range was 4 days or more

Where you are losing the most shows the 12 pairs a competitor wins by the most days, from the latest shared reading.

Top competitor threats

One row per competitor, built from every day it and the product it competes with were read at the same pincode, not only the latest:

ColumnHow it is worked out
Competitor Ofthe products it is mapped to
Pincodes Seenthe pincodes where the two were compared
Faster Indays it was faster ÷ days compared × 100
Avg Leadhow many days ahead it was, on average, on the days it was ahead
Trendits average days in the second half of the range against the first half: getting faster (the threat is growing), getting slower, or steady when they are within 0.05 days

Rows are ordered by Faster In, highest first; 60% or more is shown in red.

Region insights and the India map

The India Delivery Map and Region Insights, drawn with sample data.

  1. One dot per pincode, coloured by the worst standing there.
  2. Region Insights by state, city or pincode.
  3. Comp Faster: how often a competitor wins the region.
ColumnHow it is worked out
Products, Pincodesthe products and pincodes with pairs in the region
Comp Fasterpairs where a competitor is faster ÷ pairs judged, from the latest shared reading
Avg Gapthe average gap (competitor days − yours) of the pairs judged
Avg Daysthe average latest days of the region's deliverable pairs
Serviceabilitydeliverable pairs ÷ measured pairs, on the Pincodes tab

Regions are sorted by Comp Faster, highest first, so the places you lose come first.

The map has one dot per pincode with a reading. Its colour is the worst standing among the products there: a pincode a competitor wins for one product is worth seeing even if you win it for the others. A dot with no comparison is red when the latest reading of every product there was non-serviceable, and grey otherwise. Click a dot for every product at that pincode.

A pincode is placed from India's postal directory. Coordinates entered the wrong way round are swapped back, points outside India are dropped, and where a pincode has several post offices the one nearest the centre of its region (its first three digits) is used. A pincode with no usable location is left off the map but still counts in every figure.

Good to know

  • Figures are kept for five minutes for each set of filters. A check that finished in the last few minutes can take up to five minutes to show.
  • Daily grid, the highlighted button in the header, opens the same readings one cell per day.

A figure still does not add up?

Tell us which page and which number, and we will walk you through it.