Integrations
Every POS in.
Draft tools only out.
BudAlly reads from the systems you already run and writes back only through your approval queue — under your own credential, never ours. Read-only is the default for every connector.
HOW A CONNECTOR IS SCOPED
- read:
- products · inventory · receipts · customers
- draft:
- purchase orders · prices · campaigns · bills
- execute:
- anything
// kill switch per connector · freshness chip on every screen
Point of sale
What BudAlly can read and what it can draft, per POS. Where a POS has no write surface, the draft becomes a task in StoreHome: “change it in your POS, then confirm.”
| POS | We read | We draft (you approve) | Connection |
|---|---|---|---|
| Dutchie POS → | Products, inventory & lab results, register transactions, customers, discounts, employees, deliveries, POs | Purchase orders, customer tags & notes, delivery routes. Prices: StoreHome task | API key per location, or Secure Data Share |
| Flowhub → | Products, inventory, orders, customers (no med-card expiry in API) | POs, price tasks via StoreHome | Client id + key per integration; MCP under retailer login |
| Cova → | Catalog, packages, orders & refunds, customers, promotions, reporting | Orders (API-injected), POs, price tasks | OAuth2 via iQmetrix + integrator id |
| Treez → | Products, stock by package, tickets, customers; webhooks for live updates | Orders, discounts, POs | Partner id + per-location key (2-hour token) |
| BLAZE → | Products, inventory, transactions, customers; partner webhooks | Orders, products, prices, discounts (write surface: confirming) | Partner key + per-shop key |
| Any other POS | Nightly CSV / SFTP export + the state system (Metrc, or NMS2S in New Mexico) as the spine | Everything as StoreHome tasks | Generic importer |
Compliance, data, money, people
TRACK & TRACE
Metrc · NMS2S
The spine of the ledger: packages, transfers, manifests, lab results, receipts. Metrc: read under your own user key. New Mexico's NMS2S: per-location token, with state exports and your POS alongside. Writes stay in Approvals under the approver's key.
- Metrc
- your own user key
- NMS2S
- per-location token
- 10 operations stay manual in the state's web app
BioTrack states: on request · NMS2S details
MARKET DATA
Headset
Licensed benchmarks and demand signal for price intelligence and supply plans. Internal analysis only; never syndicated, never re-exported.
Add-on per state
ACCOUNTING
QuickBooks Online · NetSuite
Journals, bills and inventory valuation reconciled to Metrc before they post. Medical / adult-use split carried through.
Close plan and up
MENUS & MAPS
Menu sites · Google Maps
Listings on menu and marketplace sites can be integrated on request. Google Maps routes self-delivery.
Close plan and up
PAYMENTS
Aeropay · CanPay · others
Tender reconciliation for cash vs non-cash. We don't block any processor.
MAILBOX
Google Workspace · Microsoft 365
Read-only on the invoice inbox and “vendor-deals” threads. No send scope, ever.
PAYROLL
Your payroll provider · export
Time and tips flow out of the People module to the payroll provider you already use, by export.
YOUR AGENTS
BudAlly MCP
Claude, ChatGPT or your own automation get read and draft tools at mcp.budally.com. Every draft lands in the approval queue.
What BudAlly never does with a connection
- Scrape Weedmaps, Leafly, Dutchie or any menu. Uploads with scraper provenance are rejected and not stored.
- Execute a price change, send a campaign, or write to Metrc without a named approver.
- Pool your rows into another operator's benchmark without opt-in and at least 8 contributors. Dutchie-connector rows are never used in benchmarks.
- Sell, share or train on your data. Model providers are held to 30-day-or-less retention.
- Keep a connection you turned off. Each connector has a kill switch; revoking the key ends the read within one sync.
Don't see your POS? Connect it with CSV + Metrc, and we'll build the adapter.
Request an adapter© 2026 BudAlly, Inc. · POS names are trademarks of their owners; BudAlly is an independent product.