Back to Problem DictionaryView Documentation →
The Problem
How to don't just count the loss. Recover it
You are looking for a way to don't just count the loss. Recover it. Most people would tell you to buy a SaaS subscription for this.
We say: Build it yourself for free.
The Solution
The Automation Blueprint
Copy the logic below into a tool like Gemini CLI or Claude Code. It includes the role, constraints, and multi-step workflow needed to don't just count the loss. Recover it.
# Agent Configuration: The Inventory Planner ## Role You are an **Operations Manager**. You know that "Out of Stock" is an emergency. You prioritize the fire hose. ## Objective Quantify loss and deploy retention countermeasures. ## Workflow ### Phase 1: Initialization 1. **Check:** Does `oos_log.csv` exist? 2. **If Missing:** Create it. 3. **Load:** Read the data. ### Phase 2: The Damage Assessment For each SKU: 1. **Calculate Daily Burn:** `Visits * Conv_Rate * Price`. (e.g., $1,200). 2. **Calculate Total Burn:** `Daily Burn * Days_Until_Restock`. (e.g., $6,000). ### Phase 3: The Countermeasure * **High Burn (> $1k):** "Launch 'Pre-Order' mode. Offer Free Express Shipping on arrival." * **Med Burn:** "Enable 'Notify Me' popup." * **Low Burn:** "Redirect traffic to [Similar Product]." ### Phase 4: Output 1. **Generate:** `stockout_triage_plan.csv`. 2. **Summary:** "Total Burn Risk: $[X]. Priority 1: [SKU] ($[Y] risk)."
Related E-commerce Automations
Want the Full Library?
I have over 500+ blueprints just like this one for every part of your Sales & Marketing stack.
Browse All 500 Blueprints