BudAlly for Cova stores.
Keep Cova. Add the layer.
Cova stays your register. BudAlly connects through Cova's API where your store grants access, or through your Cova 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
- Catalog with cannabis package details, stock, pricing and taxes — full or incremental sync
- Completed orders and refund invoices, kept separate
- Customers, searchable by modified date
- Loyalty and promotions
- Rooms and GL
- Reporting API: list and run reports
Metrc receipt id on the order: not documented in Cova's API — it are joined from Metrc receipts
WE DRAFT · YOU APPROVE
Only where Cova has a write surface
- Drafted: Online orders into the register (Cova order API, tax-inclusive or tax-exclusive), tagged with an integrator id
- Drafted: Purchase orders (from the supply plan)
- Task for your team: Prices and new SKUs → StoreHome task: “change it in Cova, then confirm”
- Never: Metrc writes through Cova, campaigns
Executes under your Cova credential, never a BudAlly one
Known limits, stated plainly
- 01No webhooks. Cova documents none, so sync is polling and every screen shows the sync time. Rate limits and a sandbox are not documented.
- 02Report-shaped data. Cova's Reporting API returns a different shape per report, so each report is mapped before it feeds the ledger. Whether tender or cash-drawer reports exist is not documented; till reconciliation uses Metrc receipts plus your processor's data (Aeropay, CanPay).
- 03Data-use terms not documented. Cova's data-use terms for partners are not documented publicly. Cova rows are not pooled into another operator's benchmark without opt-in and at least 8 contributors.
IF YOU EVER LEAVE COVA
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 Cova exports to BudAlly's CSV / SFTP importer. The ledger backfills from Metrc.
STEP 2
Mapping review
Metrc items ↔ Cova SKUs ↔ GL accounts, matched automatically where the match is clear, the rest reviewed by you.
STEP 3
Authorize through iQmetrix
OAuth2 through iQmetrix for your company and locations, with an integrator id. Polling then replaces the import.
FIRST RUN
First overnight run
Variance audit, first briefing, first proposals in the queue. Drafted N · executed 0.