Built for Washington,
on Washington’s rules.
CCRS-native cannabis POS and back office — written against Washington’s own reporting regime from day one, not ported in from a Metrc state and hoping the reporting lines up.
Open to new stores in Washington.
Most POS vendors treat WA as a checkbox.
Washington doesn’t run on Metrc. It runs on CCRS — the state’s own weekly CSV reporting regime, live since December 2021. Most cannabis software was built around Metrc and treats WA as a checkbox, a stale page, or a state it can’t serve at all. Here’s where the field actually stands, as of July 2026:
Several of the largest national platforms don’t list Washington at all.
Check any vendor’s own published markets page — on more than one, the “Washington” listed is Washington, D.C.
vendor markets pages, as of July 2026
Some vendors’ Washington pages still advertise traceability systems the state retired in December 2021.
Leaf Data Systems or BioTrack-era integrations, in a state that has reported through CCRS ever since.
vendor WA pages, as of July 2026
Most cannabis software is built around Metrc.
CCRS — Washington’s own weekly CSV reporting regime — works nothing like Metrc’s real-time API, and a WA tab bolted onto a Metrc platform is where reporting problems start.
regime live since December 2021
Pull up any vendor’s own Washington page in the demo and read it next to ours. We’re not characterizing anyone — the published pages speak for themselves. Named, dated citations live in the internal sales notes; ask us in a demo and we’ll show you the sources.
The weekly file builds itself.
The weekly CCRS file builds itself from the sales, inventory, and disposal you already recorded. It reconciles your recorded sales, inventory, and disposal against each other and flags gaps or mismatched weeks before you file — so a problem surfaces on your screen, not in a state rejection.
The weekly CCRS CSV export is built.
The week is built, reconciled, and accuracy-checked, not reconstructed from memory on a Friday night.
LCB has granted CannAgent integrator access to CCRS.
Dispensary customers already use it for their weekly CCRS file. For your store, the system builds the weekly CCRS file and checks it before it goes in.
This is software written against Washington’s reporting regime as the starting point — not a national platform’s WA tab.
The receipt, and the CCRS row behind it.
Change the product, the city, the quantity or the medical card. The paper receipt is what your customer takes home. The CCRS panel with it is the row that sale adds to your weekly CCRS file, built by the same code that runs the register. Set the customer under 21 and watch what happens to both.
Total $53.13. Files as RecreationalRetail.
THANK YOU · KEEP THIS RECEIPT
- Quantity
- 3.5
- UnitPrice
- 35.00
- SalesTax
- 5.06
- OtherTax
- 12.95
- SaleType
- RecreationalRetail
- Operation
- Insert
- RCW 69.50.535 — 37% cannabis excise, applied at retail
- Seattle — Seattle (DOR loc 1726) 10.55% = 6.50% state + 4.05% local; B&O retailing 0.342% (2026–2032)
Computed by src/lib/receipt-demo.ts, which emits the same CcrsSaleRow the WSLCB submission is built from and is pinned against the real CCRS validator in CI. Statutory rates shown; a live store computes from its own configured local tables.
The proof is checkable, not claimed.
In a demo we show the weekly CCRS file screen on a sample store and the checks it runs before you upload. The reporting regime that trips up the national platforms is the one this product was written to survive, and the demo is where you can check that for yourself.
Book a demo