Delivery software should reflect what a business is authorized to do, not define its operating model. Before enabling dispatch, purchasing, or inventory storage, map each function to the Massachusetts license and approved activity that supports it
A package transfer exception should be investigated before the transfer is recreated. The original event may be pending, partially processed, rejected because of status, or inconsistent with what the receiving location expects
CBD product setup can create reporting problems when category, tax treatment, unit, SKU, and product name are copied from unrelated cannabis items
A receiving exception occurs whenever what arrived does not match the approved order or expected data. Quantity, cost, package information, condition, and product identity should be reviewed before the product becomes part of sellable retail inventory
Slow inventory consumes cash and shelf space before it becomes an obvious problem. Aging reports help a store identify products that are not moving while there is still time to change replenishment, merchandising, or pricing decisions
Record retention should preserve what the business and law require without turning every system export into permanent storage
Store KPIs are useful when they lead to decisions. Revenue alone cannot show whether the dispensary is protecting margin, turning inventory, using labor efficiently, or relying too heavily on discounts
A pre-migration audit prevents a new POS from inheriting old data problems
Good reminder that regular upkeep saves so much money compared to waiting for something to break
Wholesale receiving and invoice matching protect both inventory and cash. The store should be able to connect an approved purchase order with what physically arrived, what the supplier invoiced, and any credit or discrepancy that followed