Glossary
Adapter
The connector between BudAlly's ledger and one external system (Dutchie, Treez, Flowhub, Cova, BLAZE, Metrc, NMS2S, Headset, QuickBooks). Each has a capability manifest and a kill switch.
Why it matters for reconciliation: every comparison starts with getting data out of another system, and each system exposes different things. The adapter is the part that knows what a given POS or state system can read, how often, and under whose credential, so a gap in the data is traced to a specific connection.
Example: the adapter for a POS with webhooks receives events as sales happen, while the one for a POS without them polls on a schedule. A daily match reads both through the same ledger, but a timing difference on the polled one is expected and is classed as timing before anyone investigates.
Where this comes up on budally.com
Related terms
- Capability manifest
Per-adapter declaration of what a POS or state-system connection can read, draft and execute, its sync cadence and its data-use rules. It decides, for example, whether an online order is API-injected or handed to staff.
- Kill switch
A per-connector and per-user control that stops a sync or a credential immediately. Revoking a POS or state-system key ends reads within one sync.