Skip to content

StickyMetrics - Product Roadmap

Current State (v1)

  • Single-tenant (ecomhd_us)
  • Local Mac Mini deployment
  • Nightly batch pipeline (no real-time)
  • Output: Google Sheets dashboards
  • Forecast: Chronos-Bolt-mini (365d horizon, lifecycle-aware)
  • PO recommendations: per-ASIN, MOQ-gated
  • Settlement accounting: clean eComHD journals automatically post to QBO; exceptions are held and verified through readback

Active 10-Day Product Slice

StickyBooks is the active August 26–September 5 build. The committed boundary is a complete eComHD monthly-close cockpit: exception-first settlements, a controlled inventory roll-forward, reviewer-approved inventory journal, QBO readback, close signoff/lock, and Financial Call Report package export (re-anchored per issue #49 — the brand managers' report, not the Google "Accounting Sheet Template").

See StickyBooks: 10-Day Product Plan for the observed A2X and ConnectBooks findings, the Financial Call Report anchoring, scope, wireframes, architecture, acceptance gates, and execution sequence.

Known Gaps (from Walton Dashboard Audit)

The audit's 12-column deficit was answered in May: build_po_dashboard_xlsx.py ships the full operational set (MOQ, Case QTY, Vendor, lead-time columns, Safety Stock, forecasts, Ace Override, PO chain) at per-ASIN grain. Remaining: - per-vendor lead-time/freight/cycle/safety data (columns run on one default) — needs ops sourcing - TONY/LEO 3PL split — one ops answer decides feed gap vs stale - console parity — purchasing-v2 stays a thin decision lens by design; product call parked behind forecast dial-in - See product/dashboard-audit.md (status header) for the full reconciliation

Open Questions

  • Cloud deployment vs keep on Mac Mini?
  • Multi-tenant pricing model?
  • Real-time vs batch? (current: batch is fine for daily inventory decisions)
  • Integration with Karim's FRIDAY system? (complementary architectures)