Etsy Statistics: Set Three Zones Before Your Shop Goes Dark

Six out of ten Etsy shops ever opened have gone dark.

That number didn't have to be so high. Some of those shops might still be open if their owners had known, early and plainly, which problem could end them. With a control system, the count could look different.

Now picture your own Tuesday. A slow week of orders. A three-star review. A supplier email about new prices. All three land before lunch, and you fix whichever one shouted last.

Here is the irony. The shop pings you for every new favourite. Nothing pings when the cash drops below one month of costs.

The problem isn't effort. It's the order of the work.

Etsy statistics need a gauge, not a verdict

Look at an engine temperature gauge. Three coloured sectors. Green: drive on. Yellow: pay attention. Red: stop. You don't strip the engine. You look at the sector.

Run your shop the same way. For each goal, subtract the goal from today's value: actual minus goal. That gap is the error. It is the main signal for every decision you make.

A gap alone doesn't say whether to act. You need lines drawn in advance.

Set the zones in one calm evening

This is the tool. About 15 minutes, one sheet. Here it is with the numbers of Andrew, who runs a coffee shop called "The Corner".

1. Write each goal next to today's value. Andrew's reserve: goal 2.0 months, now 0.5. Margin: goal 15%, now 9%.

2. Set three zones for every row. Andrew did it that same evening, while his head was clear.

3. Draw the red line where damage gets hard to reverse. Andrew put the reserve's red line at one month. A month gives him time to negotiate a deferral, find money and decide. Under a month, there is no time for any of that.

4. Make no zone narrower than your measuring error. If your margin records drift by a point, a green zone half a point wide is noise.

5. Subtract and sort. Andrew's errors: reserve minus 1.5 months, red. Margin minus 6 points, yellow. Regular customers minus 15 points, yellow. Complaints plus 3, yellow. Hours plus 25, yellow.

6. Write the lines down and leave them. Moving a threshold mid-crisis bends the ruler to fit the result.

One red row and four yellow ones. Now Andrew knew where to look first.

Online store tips for a short life: the red protocol

The typical online store lives about six months.

Six months didn't have to be the whole story. Some of those stores might have reached a second year if their owners had seen the red row early and dropped the rest. With a written order for bad days, the number could look different.

When a row turns red, follow four steps.

1. Check for a direct threat. People, safety, mandatory payments, the law. If there is one, protect and escalate first.
2. Freeze secondary work. Anything that doesn't help the red row waits.
3. Put time, money and attention on the red row. And on the levers that act on it.
4. If several rows are red, start with the nearest irreversible damage. Then, other things equal, save the goal you would give up last.

Andrew's first thought at that table was loyalty cards, to win customers back. The table said no. Cards cost money: printing, discounts, setting up the till. That money would come out of a reserve already under a month.

"But you wanted loyalty cards," Sara said that evening.

"I did," Andrew replied. "But the reserve is in the red zone."

Regular customers drift away slowly. A red reserve can end everything quickly. He put the cards aside and, for the first time, felt no guilt. The order he chose with a clear head made the call, not his fatigue.

The Jirgenson Model is new. It is scientifically proven to work (doi.org/10.5281/zenodo.23964934). Because it is new, it could not help the shops and stores behind these numbers. Now it can help yours.

Ecommerce failure rate in year one: priority, not a queue

Two out of three Shopify stores vanish within their first year.

Some of those owners might have kept going with one habit. Sort problems by priority, not by arrival, and the year-one count could look different.

A queue of incoming problems is run by chance. A queue of decisions is run by priority. When a new problem lands, put three questions to it before you touch it:

1. Which goal does it belong to?
2. Which zone is that row in now?
3. Is it more important than what I'm doing right now?

Elena, a freelance designer, shows why. One client brings her 70% of her income. Her goal is no more than 30%, and above 50% is her emergency line. That row is red. Then the tax authority freezes her account. Two reds at once.

Income is her goal number one, and the frozen account hits it directly. So she puts the client problem on hold and turns everything to the account.

Here is the same morning both ways. Illustration from her story.

When everything is urgent, nothing is managed.

Ecommerce mistakes the green zone prevents

The green zone guards against a costly habit: fixing what works.

Suppose that a few months later Andrew's complaints drop below two a week. He is tempted to fine-tune the service. It could always be better. But the row is green. Correcting it costs effort and buys nothing.

So leave green rows alone.

The yellow zone asks for the opposite. Nothing is on fire, so it is easy to wait. Don't. Find the cause while it is still cheap. Ask: what has changed since last time? Since when? Which lever affects it? Andrew wrote for his margin: waste and unprofitable menu items. For regular customers he had no cause yet, so he wrote "find out" in his task list.

Ecommerce margin: what the error costs in money

Turn the gaps into money and the zones stop being abstract.

Andrew's monthly expenses are €27,300. His reserve error of 1.5 months equals €40,950 missing from the cushion. His margin error of 6 points on €30,000 of revenue is €1,800 of profit lost every month: €2,700 instead of €4,500. Six more months like that cost €10,800.

The gap also decides how hard one bad day hits. A broken coffee machine is a nuisance for a shop with two months of reserve. For a shop with two weeks, it is an emergency.

The human cost fits in one sentence. Every new problem gets decided by whoever is loudest that day, and the owner goes home with all of it.

"Zones are too much for a small shop"

They take about 15 minutes.

Alex, a boy saving for a bicycle, keeps three zones for his savings. By 1 July his schedule says €170. He has €140. The gap is minus €30. Up to €10 behind is normal for him, 11 to 40 is acceptable, more than 40 is an emergency. So he is in yellow. No panic. He knows the cause: the scooter isn't sold yet.

If a schoolboy can run three zones on a piggy bank, a shop can run them on five rows.

Where the zones stop

The zones treat a symptom: you stop answering problems in the order they arrive.

The cause is still in place. You know the reserve is red. You don't yet know which action will move it, how fast, or whether you can undo it. And the zones show today, not the month after next.

Two steps close that gap.

• Levers. What you can change by your own decision, with three questions asked before you pull. Chapter 5.
• Two forecasts. "If nothing changes" against "if the plan works", so you see a red row coming. Chapter 8.

The zones are the third step of one loop: goal, state, error, levers, plan, forecast. Etsy statistics describe thousands of shops. The zones describe yours.

For the levers an online store can pull, with a price test in numbers, see shopify statistics.

Fifteen minutes or another Tuesday like this one

You have two choices. Close this tab and let tomorrow's loudest email set your order again. Or draw three zones for your five rows tonight and see what is red.

Next Tuesday three problems land before lunch, and you already know which one goes first.

The zones tell you where to look. The levers and the forecasts tell you what to move, and what happens if you don't.

Start free: Chapter 1, with the refusal test, sets the order the red protocol relies on. The whole control system comes as a book on Kindle: get it on Amazon.

Published research

It is scientifically proven that the Jirgenson Model works. The published experiment, its record and its data:

• Zenodo (DOI): 10.5281/zenodo.23964934
• Hugging Face: E5 Jirgenson Model blind test
• Kaggle: E5 blind test dataset
• GitHub: experiment folder
• Wikidata: dataset Q142022866, author Q141981336
• ORCID: 0009-0001-3034-3552