Glossary
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.
Why it matters for reconciliation: a gap in data can be the connection's limit and not the store's error. The manifest says what a connection can read, draft and execute and how often it syncs, so a missing field or a delay is explained before anyone investigates a discrepancy.
Example: one POS can accept an order from the platform and another cannot. The manifest for the first marks an online order as injectable, while the second marks it as a handoff to staff. The match back from receipt to ticket is therefore stricter for the second store.
Where this comes up on budally.com
Related terms
- 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.
- Order handoff
How an online order reaches the register so the state receipt is created there: API-injected where the POS supports it (Treez, Cova, BLAZE); staff handoff with receipt match-back where it doesn't (Dutchie).