What a Cannabis Customer Data Platform Should Do for Independent Dispensaries

First-party data is the operating layer

Cannabis operators need customer data they can trust: who checked in, what they bought, which categories they prefer, how often they return, and which messages influenced a purchase.

Generic CDPs rarely understand cannabis constraints. A practical cannabis CDP needs to support compliance, consent, POS drift, local market context, and campaign approval gates.

The minimum useful dataset

For most stores, the first production layer should include organizations, locations, customers, orders, order items, products, POS connections, sync runs, and spending aggregates.

That is the layer BakedBot is moving toward with Kinde for auth and Neon Postgres for operating data. Firebase and Firestore remain a transition fallback while the production data layer is verified.