--- title: Doudlah Farms — Amazon Inventory Management System type: article created: '2026-04-05' updated: '2026-04-05' source_docs: - raw/2026-02-02-doudlah-call-amazon-inventory-beanvivo-119082342.md tags: - client/doudlah-farms - amazon - inventory-management - ecommerce-strategy - supply-chain - packing-operations layer: 2 client_source: null industry_context: null transferable: true --- # Doudlah Farms — Amazon Inventory Management System ## Overview Doudlah Farms' Amazon channel has grown faster than its operational infrastructure can support. January 2026 sales hit **$136,000** (~$6,100 peak single day), and the current system — manual inventory tracking, garage-based packing, and reactive shipment preparation — is creating stockout risk that directly damages search rankings and long-term revenue. This article documents the diagnosed problems, the proposed system redesign, and the infrastructure decisions needed to support continued growth. --- ## The Core Problem: Pack-to-Ship vs. Pack-for-Inventory The current model is **reactive**: Karly calculates what's needed, sends Jason a packing list, Jason packs it, and it ships. At $20k/month this was manageable. At $136k/month — trending toward a truckload per week — it creates compounding failures: - Jason can pack **4–5 pallets/week** (~4 man-hours per pallet), which is insufficient to keep pace with demand - Packing happens in a **2-car garage** that is at capacity for both packing and staging - Shipment prep is a **multi-hour weekly exercise** involving manual data export, spreadsheet manipulation, and frequent Amazon support cases - Jason's availability will be **severely limited by fieldwork** starting in spring The proposed model is **proactive**: pack continuously for inventory, maintain a **2–3 month buffer** of packed product, and fulfill orders by pulling from that buffer rather than packing to order. > *"We shouldn't be packing to ship. We should be packing for inventory... somebody ought to be packing every day, five days, seven days a week."* > — Mark Hope --- ## Stockout Impact on Amazon Rankings Running out of stock is not a temporary sales gap — it triggers algorithmic demotion that takes weeks to recover from: | Product | Pre-Stockout Rank | Post-Stockout Rank | Recovery Status | |---|---|---|---| | Organic Black Beans | #1–2 | #30 | Partially recovered (~#5) | | Yellow Cornmeal | Top position | Major drop | Recovering | This makes inventory continuity a **ranking protection strategy**, not just a fulfillment concern. A 2–3 month packed buffer is the minimum needed to absorb demand spikes and shipping delays without going out of stock. --- ## Shipping Strategy: Why AWD Is Off the Table Amazon Warehousing & Distribution (AWD) was trialed but rejected due to: - Inventory delays and items sitting idle during peak season - Amazon incorrectly flagging products as expired (no expiration date on packaging) - AWD closed to new inbound shipments during Q4 without warning, stranding inventory - Higher cost than the current multi-shipment approach **Current approach:** Split each order into 10+ smaller shipments directed to different Amazon fulfillment centers. This saves roughly **$4,000 per shipment cycle** ($4k vs. $8k) but is labor-intensive and will become unmanageable at higher volumes. The shipping strategy should be revisited as volume grows, but AWD is not the near-term solution. --- ## Proposed System Components ### 1. Inventory Planning & Monitoring - Export Amazon inventory data weekly; automate calculation of days-of-supply by SKU - Factor in: inventory in transit, inventory already scheduled, packed-but-not-shipped buffer - Build a rolling 90-day demand forecast using trailing sales velocity by SKU - Flag reorder points before stockout risk, not after ### 2. Packing Operations - Shift from order-driven packing to **continuous inventory packing** - Target: pallets packed and labeled in advance, ready to pull and ship on demand - Current capacity: 4–5 pallets/week with existing labor (neighbor, 4 days/week + weekend help) - To support a truckload/week, packing capacity needs to scale — either more labor hours or a dedicated packing facility - Pack pallets so at least one face of every box is visible, reducing label-application time at shipment ### 3. Packaging Materials Management - Establish reorder triggers for boxes, bags, labels, and shrink wrap - Prevent packing stoppages due to materials stockouts (currently an untracked risk) ### 4. Shipment Preparation - Standardize the weekly shipment workflow: inventory pull → Amazon shipment creation → label generation → pallet staging → truck loading - Reduce manual spreadsheet manipulation by building a repeatable template or lightweight tool - Track open cases with Amazon (expiration flags, receiving discrepancies) in a shared log ### 5. Product Line Simplification Consider **dropping 25 lb bags from Amazon**: - Lower margin per pound (~$4/lb) vs. 5 lb bags (~$6/lb) and 1 lb bags (highest margin) - Slower velocity and harder to pack/stage - Focusing on 1 lb and 5 lb SKUs concentrates packing effort on highest-return products --- ## Infrastructure Requirements ### Immediate Need: Packing & Staging Space The 2-car garage cannot support current volume. A dedicated space is needed for: - Continuous packing operations - Staging 40–60 pallets of finished inventory - Loading dock access for outbound truck shipments **Priority 1 — Edgerton Warehouse Rental** Doudlah Farms already stores grain at the Edgerton warehouse. The goal is to negotiate a dedicated section with: - 40–60 pallet positions - Access to existing dock doors (doors 19 and 20 are current Doudlah positions) - Space for a packing setup (low power requirement) *Note: Another company has rented half the Edgerton warehouse, so available space needs to be confirmed. Jason to scout and arrange a walkthrough with Eric (warehouse manager) on Friday.* **Priority 2 — New Building Phasing** An 8,000 sq ft building is planned on the farm property but delayed until ~June due to financing (concrete pour pushed to late March). The recommendation is to **phase construction** so the packing area comes online first, before the full build is complete. See also: [[clients/doudlah-farms/_index]] for full infrastructure timeline. --- ## Channel Strategy Context The inventory system decisions are downstream of a deliberate channel prioritization: | Channel | Margin | Notes | |---|---|---| | Amazon (1 lb / 5 lb bags) | ~35% | Premium price position; ~$2/bag profit | | Retail (e.g., Woodman's) | 4–5% | Plus slotting fees; not core business | | BeanVIVO / Valley Foods (bulk) | Near break-even at $1.10/lb | Useful for clearing surplus; not a growth channel | Amazon's margin advantage is significant enough that **protecting Amazon inventory takes priority** over fulfilling bulk wholesale orders. The 77,000 lb Amazon holdback on black beans is a direct expression of this strategy. For the KAHI/Wild Oats private-label opportunity (meeting Feb 19), the same logic applies: the deal only makes sense if it clears margin targets. See [[knowledge/ecommerce-strategy/channel-strategy-amazon-vs-retail]] for the broader framework. --- ## Action Items - [ ] **Mark Hope** — Draft full inventory/packing/shipping proposal; share with Mark Doudlah, Lucy, Jason, and Karly - [ ] **Jason Doudlah** — Scout Edgerton warehouse space; confirm Friday walkthrough with Eric; schedule 1-hour review with Mark Hope - [ ] **Mark Doudlah** — Re-verify Amazon holdback assumptions (77k lb black bean figure); update Mark Hope - [ ] **Sherry Lucy Doudlah** — Send KAHI/Wild Oats Zoom link (Feb 19) to Mark Hope --- ## Related - [[clients/doudlah-farms/_index]] - [[knowledge/ecommerce-strategy/beanvivo-valley-foods-order-conflict]] - [[knowledge/ecommerce-strategy/channel-strategy-amazon-vs-retail]]