Catalog & Store Data Reviewjarscannabis.com · independent review by Mousa Batarseh
Plan · first 30 days

One record per store. One rule per ladder.

Nothing here needs a new platform; it needs rules at the point data goes in.

30days
Week 1

Stop the wrong numbers

  • Replace 800-222-1222 in the homepage schema; add the 19 Arizona stores
  • Fix the three phone mismatches and El Mirage's hours
  • Retire one of each same-quantity deal pair (7/$80 vs 7/$90, 7/$60 vs 7/$69)
Weeks 2–3

Rules at intake

  • Deal sheet row requires a real end date or an explicit “evergreen” flag — no year-4200 stand-ins
  • Ladder check: each tier cheaper per unit than the one below
  • Store pages render schema from the store record; fill the 13 map IDs
Week 4

Weekly report

  • Deals submitted, cleared first pass, blocked, and which check fired
  • Store-record drift: any page whose phone, hours or city differs from the record
  • Orphan deals attached to closed stores, and duplicate deal slugs

What I'd ask first

Whether the storefront already suppresses one of two conflicting deals at checkout (that changes finding 1 from a pricing problem to a display one). Who owns deal entry — Dutchie at the store, or a central team — because the ladder rule belongs wherever the deal is typed. And whether the 4200 end date is a platform default or a habit; one is a setting, the other is a checklist line.