Glossary

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).

For a store, the sale happens in the POS, not in BudAlly. BudAlly's menu takes the order and hands it to the register, which is what the state expects.

Which path a store is on is set by its adapter's capability manifest, and each store sees which path it is on. The difference comes down to whether the POS has a create-order API. Every write to the POS runs only after a named person approves it, under the store's own credential, and only where that POS's API allows it.

The storefront does not depend on the path. The menu, the domain, the app and the customer accounts sit in BudAlly, so switching POS changes the adapter underneath, not the storefront. At cutover, the storefront's stock source flips to the new connector and drafts pause during the window.