Perimeter Use cases Category

Real turnover, store by store

The national average hides the decision. Perimeter drills down to the store and SKU level to show what to restock, what to move between stores and what to clear out, with weeks to spare before price decides for you.

Ask about your assortment…
Turnover · same line, different zone live
SKU 7712 · North8.6 wks
SKU 7712 · Central5.4 wks
SKU 7712 · South2.1 wks
SKU 7712 · Far South1.2 wks
The same product turns seven times faster in the north. There are 1,400 units sitting idle in the south.
Perimeter agent

Assortment stops being decided by the average

Today

  • Turnover is viewed in aggregate and the average hides the differences.
  • Excess stock shows up when clearance is the only option left.
  • Transfers between stores are proposed late, or not at all.
  • Comparing with last season takes an afternoon of spreadsheets.

With Perimeter

  • Turnover is visible by store and by SKU, which is where decisions are made.
  • Excess is detected with weeks to spare before the markdown.
  • Transfers are suggested with data from both stores in view.
  • Comparing with past seasons takes one question.

What Perimeter does for category management

Assortment

Turnover at the store level

Perimeter compares each SKU’s rate of sale in each store against its own history and against comparable stores, not against the chain average.

  • Rate of sale by SKU and by store
  • Compares against stores of similar size and profile
  • Flags assortment that doesn’t justify its shelf space
Turnover by store · last 8 weeks live
Store 141.2/wk
Store 071.6/wk
Store 221.9/wk
SQL for this answerselect store, sku, sum(units)/8 as wk_rate from store_sales where week >= 28 group by 1,2 having wk_rate < 2
Excess

Overstock spotted before the markdown

Inventory that hasn’t moved in weeks is projected against the coming season. You know how much is left over and how much time remains before clearance is the only option.

  • Projects how many weeks of sales remain by SKU and store
  • Estimates excess at season end
  • Suggests transfers between stores before cutting the price
Non-moving inventory live
Over 90 days$0M+18% vs Q2
Idle SKUs0+24 vs Q2
Transferable0%of excess
AprMayJunJulAugSep
Season

What happened last time, without digging

Every launch is compared against its equivalent season, adjusting for open stores and assortment changes, so the comparison is fair.

  • Compares against equivalent seasons, not the calendar
  • Adjusts for open stores and assortment changes
  • Shows what was excluded from the comparison and why
Launch vs. last season live
Week 1+12%
Week 2+4%
Week 3−7%
Week 4−14%
The drop starts in week 3, the same point where it fell last year.
The real questions

What category management asks on any given Tuesday

Each one is answered in the conversation, with its chart and the SQL behind it. When the number matters, anyone can audit where it came from.

Which products sell well in one zone and poorly in another?
How much of my inventory has gone over 90 days without a sale?
Which transfers between stores would avoid clearance this season?
What happened the last time we launched this category in winter?
Which SKUs don’t justify the shelf space they take up?
Alert me if a new SKU doesn’t reach its target rate of sale within three weeks.

How a transfer gets decided

From the moment excess appears until the team has a concrete proposal to approve.

STEP 01

Measures real turnover

Rate of sale by SKU and store, compared against similar stores.

STEP 02

Projects the excess

Estimates how much will be left at season end if the trend holds.

STEP 03

Matches origin and destination

Finds the store where that SKU does sell and calculates how many units to move.

STEP 04

Proposes and waits for approval

The proposal arrives with details for both stores and waits for a human sign-off.

What changes for the team

8Weeks of lead time before excess forces a clearance.
100%Of season comparisons with their criteria in view.
0Afternoons of spreadsheets to compare against last year.

Connects to what the category team already uses

No exporting spreadsheets or pasting data by hand. Every connection is read-only and can be revoked in one click.

SAP Bsale Falabella Cencosud Mercado Libre Shopify Google Sheets Snowflake

Perimeter across the rest of the business

Your assortment already has
the answer

Tell us what you want to answer and we’ll show you Perimeter on your own sources.