BudAlly for BLAZE stores.
Keep BLAZE. Add the layer.
BLAZE stays your register. BudAlly connects through BLAZE's API where your store grants access, or through your BLAZE 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 product batches
- Inventory transfer history
- Transactions and sales
- Members (customers), loyalty and promotions
From BLAZE's endpoint titles; field-level detail, including a Metrc tag on transaction lines, is not yet confirmed — package detail are joined from Metrc receipts
WE DRAFT · YOU APPROVE
Only where BLAZE has a write surface
- Drafted: Online orders: finalize or set to fulfill in BLAZE's transaction queue
- Drafted: Promotions
- Drafted: Products and prices, through product create and update
- Never: Metrc writes through BLAZE, campaigns
Executes under your BLAZE shop key, never a BudAlly one
Known limits, stated plainly
- 01Paid API. BLAZE charges for API access. The fee schedule is not published.
- 02Thin public documentation. The webhook event list and rate limits are not documented, and whether transaction lines carry the Metrc tag is not yet confirmed. BudAlly checks each surface when you connect.
- 03No cash-drawer or employee data documented. Till reconciliation uses Metrc receipts plus your processor's data (Aeropay, CanPay).
IF YOU EVER LEAVE BLAZE
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 BLAZE exports to BudAlly's CSV / SFTP importer. The ledger backfills from Metrc.
STEP 2
Mapping review
Metrc items ↔ BLAZE SKUs ↔ GL accounts, matched automatically where the match is clear, the rest reviewed by you.
STEP 3
Generate the shop key
Your admin generates a developer key and secret for BudAlly in BLAZE, with Expose Sales and Expose Members turned on. Webhooks then replace the import.
FIRST RUN
First overnight run
Variance audit, first briefing, first proposals in the queue. Drafted N · executed 0.