BudAlly for Flowhub stores.
Keep Flowhub. Add the layer.
Flowhub stays your register and your Metrc system of record. BudAlly connects through Flowhub's API where your store grants access, or through your Flowhub 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
- Orders by location
- Locations
- Products and inventory (field detail not yet confirmed)
- Customers — without ID or medical-card expiry, which Flowhub's API omits
Metrc receipt id and line package tags: not documented in Flowhub's API — they are joined from Metrc receipts
WE DRAFT · YOU APPROVE
Only where Flowhub has a write surface
- Drafted: Purchase orders (from the supply plan)
- Task for your team: Prices and new SKUs → StoreHome task: “change it in Flowhub, then confirm”
- Task for your team: Online orders → staff handoff (no create-order API documented)
- Never: Metrc writes through Flowhub, campaigns
Executes under your Flowhub credential, never a BudAlly one
Known limits, stated plainly
- 01Thin public documentation. Webhooks, rate limits and a sandbox are not documented, and field-level detail is not yet confirmed. Public-API writes beyond purchase orders are not documented. So BudAlly polls, and checks each surface when you connect.
- 02No ID or medical-card expiry. Flowhub's API leaves both out, so BudAlly cannot read them from Flowhub.
- 03Flowhub MCP is user-scoped. Flowhub's MCP connector (July 2026) can change prices, deals, room transfers, catalog and fees under each user's own login and role, and confirms destructive changes. Whether a third-party layer may act through it is not yet confirmed, so price changes stay tasks. Data reached through it is used only in that user's sessions and not passed to other AI clients.
IF YOU EVER LEAVE FLOWHUB
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 Flowhub exports to BudAlly's CSV / SFTP importer. The ledger backfills from Metrc.
STEP 2
Mapping review
Metrc items ↔ Flowhub SKUs ↔ GL accounts, matched automatically where the match is clear, the rest reviewed by you.
STEP 3
File the integration request
Your store files Flowhub's API Integration Request naming BudAlly; Flowhub issues the client id and key. Polling then replaces the import.
FIRST RUN
First overnight run
Variance audit, first briefing, first proposals in the queue. Drafted N · executed 0.