BudAlly for Dutchie stores.
Keep Dutchie. Add the layer.
Dutchie stays your register and your Metrc system of record. BudAlly reads your inventory, transactions and customers, reconciles them to Metrc, and drafts the work — without asking you to migrate, re-tag or re-train.
Connection at a glance
WE READ
Everything the ledger needs
- Products, brands, strains, pricing tiers, tax categories
- Inventory with package IDs, snapshots, lab results
- Register transactions with line package IDs, taxes, returns
- Customers, types, tags, journal, segments
- Discounts (v1 and v2), employees
- Deliveries and drivers
- Purchase orders
Metrc receipt id: joined through Metrc's external receipt number when Dutchie doesn't expose it
WE DRAFT · YOU APPROVE
Only where Dutchie has a write surface
- Drafted: Purchase orders (from the supply plan)
- Drafted: Customer tags and journal notes (loyalty and consent flags)
- Drafted: Delivery route details
- Task for your team: Prices and new SKUs → StoreHome task: “change it in Dutchie, then confirm”
- Task for your team: Online orders → staff handoff + receipt match-back (no create-order API)
- Never: Inventory adjustments, Metrc writes, campaigns
Executes under your Dutchie credential, never a BudAlly one
Known limits, stated plainly
- 01No webhooks. Dutchie POS is poll-only, so “live” means about 15 minutes at the rate limit. Every screen shows the sync time.
- 02No product or price write. Price changes become tasks your team applies in Dutchie; BudAlly confirms from the next sync.
- 03No cash-drawer or timeclock endpoints. Till reconciliation uses Metrc receipts plus your processor's data (Aeropay, CanPay).
- 04Developer terms. Dutchie rows are never pooled into cross-operator benchmarks. Your own store's benchmarks use Metrc receipts and licensed data instead.
IF YOU EVER LEAVE DUTCHIE
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
DAY 0 · 10 MIN
Request the key
Your admin requests a BudAlly key per location at Dutchie's API-key page. We send the exact text to paste.
DAY 0–3
Metrc + Data Share meanwhile
Connect your Metrc user key and, if you have it, Secure Data Share. The ledger backfills while Dutchie approves.
DAY 3–4
Mapping review
Metrc items ↔ Dutchie SKUs ↔ GL accounts, auto-accepted at 90% confidence, the rest reviewed by you.
DAY 5
First overnight run
Variance audit, first briefing at 06:30, first proposals in the queue. Drafted N · executed 0.