Skip to content

Walton Audit: Combined MoM+RAVE Dashboard vs Original

Source verified directly via gog sheets get on both sheet IDs. Original = 33 cols, demo = 21 cols.

1. Deficiencies - columns Noman needs that you removed

Removed col Used for Severity
MOQ Vendor minimum order. Cannot place a PO under MOQ. BLOCKER
Case QTY Case-pack rounding. PO quantities must be multiples of case. BLOCKER
Vendor Who to send the PO to. Without it the row is unactionable. BLOCKER
Lead Time Days from PO send to FBA-ready. Gates Days-Cover math. BLOCKER
Freight days Adds to Lead Time. Sea freight adds 30-45d, air adds 5-7. SIGNIFICANT
Total Lead Time Lead Time + Freight + Order Cycle. The actual reorder trigger horizon. BLOCKER
Order Cycle How often vendor takes orders (some are monthly). PO timing depends on this. SIGNIFICANT
Safety Stock Buffer days above forecast. Drives PO sizing. BLOCKER
Forecast 120D / 150D / 180D Long-cycle SKUs (sea freight + monthly cycle = 180d horizon). SIGNIFICANT
Sales 60D Trend signal vs Sales 30D. Tells you if demand is climbing or fading. SIGNIFICANT
Label Class A/B/Q4-Seasonal/Q1-Seasonal/Bundle/Relaunch - drives buy strategy. Q4 needs landing by Sept; Q1 needs landing by Nov. Without this Noman cannot stage orders by season. BLOCKER
Ace Override Manual override on system PO qty. The whole point of having Ace in the loop. BLOCKER

That is 12 columns removed; 7 are blockers. As designed the demo cannot generate a PO.

2. Things you changed without justification

  • Sales 30D split into "$" and "Units": Useful, keep. Dollar tells you revenue impact, units tells you velocity. Original only had units - your version is an upgrade.
  • "Cost/Unit" rename of "Price": Cosmetic. Fine.
  • "Reorder Need" / "Reorder Value" collapse: NOT fine. See section 5.
  • "Class" column (kept): Good, but you renamed and lost the Label nuance (Q4 Seasonal vs Class B vs Bundle). The seasonality dimension is gone.

3. What you added that helps

  • Brand column - required for combining MoM+RAVE in one sheet. Correct call.
  • Status column (URGENT / REORDER / WATCH / OK) - the original buried this in mental math. Promoting it is a real upgrade. Keep.
  • Section headers (IDENTITY / DEMAND / SUPPLY / ACTION) - improves scanability for a non-buyer reviewer. Keep.
  • Days Cover - derived metric the original lacked. Useful for triage. Keep.
  • Status counter row at top (URGENT: 40, REORDER: 5, etc.) - gives the dashboard a glance-value the original did not have. Keep.
  • Amz Alert + Amz Recs - Amazon-side signal as cross-check. Keep.

The visual layer is genuinely better. The math layer is broken.

4. Missing 3PL inventory breakdown

Original splits inventory across AMZ / TONY / LEO / HIEX / AWD. Demo only shows FBA + AWD.

Operationally this matters because: - TONY, LEO, HIEX are 3PL warehouses holding units NOT yet shipped to Amazon. They are real supply but require an outbound shipment to convert to FBA. - A SKU showing FBA=8 / AWD=0 looks URGENT in the demo, but if TONY=2,000 the real action is "create FBA outbound from TONY," not "send PO to vendor." - Collapsing them hides the difference between needs replenishment (move inventory) and needs procurement (cut PO). Different team, different action, different timeline.

Severity: BLOCKER. You cannot decide PO vs transfer with the demo.

5. PO calculation chain - why your collapse is a downgrade

Original chain: 

Forecast Based on Lead Time → Units Needed → PO Units (case-rounded) → PO Value → Ace Override

Each step is auditable: - Forecast Based on Lead Time = expected demand during the wait window - Units Needed = forecast minus on-hand minus on-order - PO Units = Units Needed rounded UP to MOQ + Case QTY multiple - PO Value = PO Units × Price - Ace Override = manual correction lane

Demo collapses this to Reorder Need → Reorder Value. Two problems: 1. No case-rounding visibility. A "Reorder Need" of 47 with Case QTY 144 should round to 144, not 47. Demo doesn't show the rounding step so Noman can't verify it. 2. No override lane. Ace cannot edit the buy without a dedicated column - he'd be overwriting the formula.

Severity: BLOCKER. The demo's PO column is decorative; the original's is operational.

6. Recommendations

Critical adds (rebuild requirement)

  1. Vendor, MOQ, Case QTY, Lead Time, Freight, Total Lead Time, Safety Stock, Order Cycle - the procurement metadata block. Hide-by-default in a collapsible group, but they must exist.
  2. Forecast 120/150/180D - at minimum 120D for sea-freight SKUs.
  3. Per-3PL inventory: TONY / LEO / HIEX as separate columns alongside FBA + AWD.
  4. PO chain split: Forecast-At-LeadTime, Units Needed, PO Units (case-rounded), PO Value, Ace Override.
  5. Label column restored alongside Class. Seasonality drives staging.
  6. Sales 60D for trend.

Keep from your redesign

  • Status column + counter row.
  • Brand column.
  • Section banners (IDENTITY / DEMAND / SUPPLY / ACTION) - but add a fifth: PROCUREMENT META for vendor/MOQ/lead time block.
  • Sales 30D split into $ and Units.
  • Days Cover.
  • Color-coded Status.

Walton's organization recommendation

Two-tab structure: - Tab 1: Triage - your 21-col view as the morning glance. Renames "Reorder Need" to "Action Hint" so it is clearly directional, not the PO. - Tab 2: PO Builder - full 33-col original layout, filtered to Status = URGENT or REORDER. This is what Noman exports and sends to vendors.

Triage tells you what to look at. PO Builder tells you what to buy. Don't conflate them.

Bottom line: the visual redesign is a real win. The procurement math got gutted. Ship the visual layer; restore the math layer; split into two tabs so neither audience suffers.