Glossary

StoreHome task

A to-do created where a POS or state system has no write surface: 'change it in your POS, then confirm.' BudAlly verifies from the next sync.

Every POS API has holes. A tool that degrades into a clear task for a person is usable, while a tool that silently does nothing is worse than no tool. A StoreHome task is that clear task.

Which changes become tasks depends on the connection. On some POS systems price and product changes become StoreHome tasks; on a store connected by nightly CSV export plus the state system, everything does. BudAlly writes to the POS only where the POS allows it, only after a named person approves, under the store's own credential; a repricing draft becomes a POS draft where a write surface exists, else a StoreHome task.

State systems produce them too. In New Mexico, each step of receiving an NMS2S manifest is a StoreHome task with a "done in NMS2S, confirm" check, or a draft for approval where the API allows it. Metrc receiving works the same way: BudAlly prepares the accepted quantities and hands the user a task with the right screen.