Skip to content
Sale Simulation · Readiness report Sample · Example figures
Simulate my sale
This is a sample. Every figure on this page is an example, not a client result.

Full gas on the simulation. Sold out on the real one.

Sale Simulation report

Brand
Example Brand
Sale
Example rosin drop
Window
Staging, 2 h, with notice
Band
Up to 2,500
Target 2,500
Pass
Sold out
3,000
Finish line
Break point
3,400
POS sync
Checkout p95 against concurrency
Checkout p95 against concurrency Baseline 800, Target 2,500, Break point 3,400 concurrent shoppers. Sold out 3,000. SOLD OUT 3,000 BASELINE 800 TARGET 2,500 BREAK POINT 3,400 CONCURRENT SHOPPERS P95 MS
Example curve. Checkout p95 at target: 880 ms. Sold out at 3,000. First failure at 3,400: POS sync writes rejected.

Verdict

The purchase path holds at the target of 2,500 concurrent shoppers with checkout p95 under 1,000 ms and error rate under 0.5 percent at every step except POS sync. The drop sells out at 3,000, before the first failure. That failure is POS sync at 3,400, where the vendor API rejects writes above its rate limit and orders queue without confirmation.

Baseline
800
Target
2,500
Sold out
3,000
Break point
3,400

p95 latency and error rate by step

Example figures · ms and percent
Example p95 latency in milliseconds and error rate in percent for each step of the purchase path at baseline, target and break point
Step Baseline 800Target 2,500Break point 3,400
  p95errp95errp95err
Browse 2100.0%4200.0%1,1000.4%
Add to cart 2600.0%5400.1%1,9002.1%
Checkout 3800.0%8800.2%3,1007.8%
Inventory hold 1200.0%3100.3%2,40011.2%
POS sync 6400.0%1,4500.8%4,20018.5%
Payment 9000.0%1,3000.1%2,1000.9%
SMS burst 3000.0%7000.0%1,6001.2%

Green under 1,000 ms and 0.5 percent. Amber above. Coral marks the failing step at the break point.

Fix list

Fixed by us
  1. 01Inventory hold released on checkout timeout instead of on cart abandon (held units leaked for 15 minutes)
  2. 02Menu page cache set to 0 seconds during the sale; moved to 20 seconds with stale-while-revalidate
  3. 03Checkout retried payment authorization without an idempotency key; added one
For your dev team
  1. 01Order confirmation email rendered synchronously inside the checkout request; move to a queue
  2. 02Add the sale-day runbook checks to the release checklist
Take to your vendor
  1. 01POS sync API rate-limited at 60 writes per minute per location; the sale needs 180. Ticket drafted
  2. 02SMS provider throttled the opening blast to 1 message per second after the first 2,000

Runbook summary

Add-on
  1. T-60 min Go/no-go checklist: storefront, POS, payments, inventory holds, notifications
  2. T-15 min Menu cache warmed, waiting room armed, war-room channel open
  3. T-0 Sale opens. Live dashboard on p95 and error rate per step
  4. Threshold Checkout p95 above 2,000 ms for 60 seconds: waiting room on, POS sync to manual mode
  5. Vendor down POS unreachable for 2 minutes: switch to backup data path, reconcile after close
  6. T+2 h Post-sale report started: what held, what did not, figures, fix list
Re-test scheduled after fixes · one included Sample report · example figures

Your report carries your own figures, your own break point, and the name of the thing that failed.