BudAlly for Treez stores.
Keep Treez. Add the layer.
Treez stays your register. BudAlly connects through Treez's API where your store grants access, or through your Treez exports (CSV / SFTP) plus Metrc. Either way it reconciles them into one package-level ledger and drafts the work for your approval — no migration, no re-tagging.
Connection at a glance
WE READ
What BudAlly reads
- Products and catalog, collections, tags
- Stock by location, grouped by package on request, with lab results
- Tickets (orders) by id, order number and status
- Customers, including caregivers — for matching, within Treez's storage limits
- Vendor invoices, synced to Metrc packages
- Discounts
Package tag on ticket lines and the Metrc receipt id are not documented in Treez's API — both are joined from Metrc receipts
WE DRAFT · YOU APPROVE
Only where Treez has a write surface
- Drafted: Online orders into the register (Treez ticket API, paid in full by a separate call)
- Drafted: Discounts
- Drafted: Purchase orders and vendor invoices
- Task for your team: Prices and new SKUs → StoreHome task: “change it in Treez, then confirm”
- Never: Metrc writes through Treez, campaigns
Executes under your Treez key, never a BudAlly one
Known limits, stated plainly
- 01Developer terms on competing products. Treez's developer terms bar use of its API in a product that competes with Treez. Where that applies, Treez stores run on CSV import plus Metrc.
- 02Developer terms. The terms also bar using Treez data to enhance third parties' data files, limit storing customer data and PII, and require deleting it when the connection ends. So Treez rows are never pooled into cross-operator benchmarks, customer data is kept only as the terms permit, and your own store's benchmarks use Metrc receipts instead.
- 03A fixed call budget. Treez allows 10 requests per second per location, which it says cannot be raised, and charges $25 per 100,000 calls above 100,000 a month. Agents read BudAlly's copy of the data, not Treez live, so they add no call fees by default.
- 04No cash-drawer, employee or reporting endpoints found. Till reconciliation uses Metrc receipts plus your processor's data (Aeropay, CanPay).
IF YOU EVER LEAVE TREEZ
Your history, loyalty and consent proofs come with you.
Points never lived in the POS. Metrc receipts since opening day are already in the ledger. A migration workspace maps customers, carries the new-customer flag, and needs two approvers to cut over.
How migration works →Setup, start to first briefing
STEP 1
Metrc + CSV export
Connect your Metrc user key and send your Treez exports to BudAlly's CSV / SFTP importer. The ledger backfills from Metrc.
STEP 2
Mapping review
Metrc items ↔ Treez SKUs ↔ GL accounts, matched automatically where the match is clear, the rest reviewed by you.
STEP 3
Request the location key
Treez certifies partners before keys are issued; your store then requests a per-location key for BudAlly, and webhooks replace the import.
FIRST RUN
First overnight run
Variance audit, first briefing, first proposals in the queue. Drafted N · executed 0.