The Problem | WTP Pitch
02 / 14 · Why change

Too many systems. Too much re-entry.

“There's thousands of items — things get missed.” — Kelli Bowles on monthly Clover → Invoiss price updates

Daily friction

  • Export Clover → edit spreadsheet → re-upload → hope Invoiss syncs → manual review again
  • Website (Shopify) shows items OOS when they should sell — wasatchtimber.com
  • Multiple Customer Profiles (Kelli 10/27): “TONS of duplicate customers” across Clover and Invoiss; “hidden” records from the January changeover still block clean history
  • Proof exports attached: Clover Customers-20261027 (~2,023 rows) vs Invoiss Clients (~11,578 rows) — two systems, no single customer of record
  • Wholesale accounts: multiple ordering reps, one AP bill-to — order history gets split
  • Customer PO vs WTP internal PO both crammed into one field; delivery address lives in three different places depending on who wrote the ticket
  • Paper tickets, handwritten POs, highlighter marks, multi-signature pickup sheets

Business risk

  • Pricing drift across thousands of SKUs
  • Missed inventory and fulfillment steps
  • No single live view of production + payment + delivery
  • Accounting reconciliation across Clover deposits, AFCU, bill.com, QBO
  • Local delivery portal separate from sales stack
  • Barcode labeling is a third-party bolt-on (Easy Labelz)

Goal Cut paper, stop multi-path order entry, and make every order follow one consistent flow no matter who processes it.