Multi-Entity (MEO/MSO) Support in SellStack 365 Cannabis Print

  • SellStack
  • 0

Overview

SellStack 365 Cannabis supports Multi-State Operators (MSOs) and other multi-entity businesses (MEOs) by allowing multiple licences, jurisdictions, and Business storefronts to operate within a unified administrative environment. This ensures regional compliance while preserving a central management model.

What Is a “Business” in SellStack?

Each entity (e.g., retail licence, distribution centre, brand division) is represented as a Business in SellStack. Businesses are synced from customer cards in Business Central 365 Cannabis, and are used to scope user access, pricing, tax rules, and order visibility.

Core Concepts

  • Licences: Each Business is assigned a licence (or multiple), which controls storefront eligibility, purchase limits, and jurisdiction rules.
  • Users: A user may be linked to one or more Businesses. At checkout, they select which Business they are ordering for.
  • Inventory: Product and Lot visibility is scoped to each Business by inventory channel and product tagging rules.
  • Tax and Pricing: Determined per Business via assigned ERP tax settings and price group mappings.

Supported MSO/MEO Configurations

SellStack supports common MSO/MEO structures, including:

  • Multi-State / Multi-Province / Multi-Entity Business: Separate storefront logic and compliance by jurisdiction or business line
  • Multi-Licence Retail and Wholesale: Different product views and tax logic per entity
  • Brand Umbrella: Central admin can manage multiple regional stores or verticals

Admin Tools for Multi-Entity Environments

Admins can:

  • View orders per Business in the Admin Panel
  • Assign users to multiple Businesses
  • Configure storefront branding and product access per Business
  • Manage Lots across shared or exclusive inventory pools

Limitations and Considerations

  • Each Business must have valid licensing data and pricing configuration
  • Cross-Business inventory visibility is not supported by default — it must be explicitly configured
  • Storefront UI will always scope to a single Business per session/cart

Best Practices

  • Ensure customer and contact records in the ERP are clearly segmented by Business and location
  • Use standardized taxonomies across Businesses for easier cross-entity reporting
  • Coordinate Lot visibility and pricing overrides carefully to avoid duplication or mismatch

Was this answer helpful?

« Back