B2B vs B2C Implementation in SellStack 365 Cannabis
This document outlines the key distinctions between B2B and B2C implementations of SellStack 365 Cannabis. It addresses integration responsibilities between SellStack and 365 Cannabis ERP, clarifies product data modelling, and identifies storefront services and features specific to B2C operations.
1. Core Integration Distinctions
365 Cannabis ERP Responsibilities
- Shared between B2B and B2C:
- Core product data (SKU, compliance attributes, ERP-side product name)
- Product Lots (availability, expiry dates, Automated FIFO/FEFO selection)
- Pricing baselines (ERP-defined pricing tables and cost data)
- Inventory levels per location
- B2B-specific ERP considerations:
- Contract-based customer pricing agreements
- Credit terms and account balances
- Restricted catalogue visibility tied to business accounts
- B2C-specific ERP considerations:
- Standardized retail pricing tables (single-tier or region-specific)
- Handling of customer awareness for new customer accounts or guest customers
- Regulatory sales caps and customer purchase limits where applicable
- Tax calculation structures tied to consumer-facing sales; alignment with SellStack’s mathematical model required
- Workflow automation for approving Sales Orders and Deliveries
ERP Product Data Modelling
It is important to note that core product data modelling within 365 Cannabis remains largely unchanged between B2B and B2C implementations. SKUs, compliance attributes, Lots, and baseline pricing structures are maintained consistently. What differs is how these data points are consumed and displayed by SellStack in the storefront context, particularly in relation to pricing tiers, visibility rules, and customer account associations.
SellStack Responsibilities
- Shared between B2B and B2C:
- Customer-facing enriched data (descriptions, images, marketing copy)
- Storefront-level inventory visibility
- Lot Attribute presentation and storefront filtering behaviour
- Initiation of Sales Orders
- B2B-specific SellStack considerations:
- Business account registration and approval workflows
- Role-based account access (purchasing agent, manager, accountant)
- Custom pricing and discounts tied to ERP contracts
- Bulk order templates and reorder facilitation
- B2C-specific SellStack considerations:
- Guest checkout and customer self-registration
- Integration with consumer payment gateways (credit card, Interac) and banking ACH payment gateways such as Aeropay
- Customer-facing promotions, coupons, and loyalty features
- SEO, product recommendations, and marketing integrations
- Shipping and delivery options; SmartRoutes (Standard/Plus) supported for both B2B and B2C
2. Storefront-Side Features Unique to B2C
The following features require explicit planning and configuration for B2C storefronts, whereas they may not exist or differ significantly in B2B implementations:
- Customer Accounts: self-service registration, password recovery, consumer identity verification.
- Checkout Flow: simplified checkout with tax and compliance checks applied automatically, versus purchase order or credit account logic in B2B.
- Payment Integration: consumer-facing payment methods with instant settlement; no reliance on ERP-managed credit terms.
- Shipping and Fulfilment: configuration of consumer shipping carriers, pickup scheduling, and delivery tracking integrations.
- Promotions and Marketing: support for consumer discount codes, loyalty programs, upsell and cross-sell strategies.
- Regulatory Considerations: storefront enforcement of legal sales limits, ID verification processes, and per-transaction restrictions unique to B2C compliance frameworks.
3. Comparison Table
| Aspect | B2B | B2C |
|---|---|---|
| Customer Accounts | Business account registration with approval; role-based access | Self-service registration, guest checkout, identity verification |
| Pricing | Custom contract pricing; ERP-driven account agreements | Standardized retail pricing; promotions and discounts |
| Payments | ERP-managed credit terms, purchase orders | Consumer payment gateways (credit card, Interac, Aeropay ACH) |
| Ordering | Bulk order templates, reorders | Simplified checkout flow with compliance checks |
| Catalogue Visibility | Restricted to approved business accounts | Open catalogue visibility; consumer-facing marketing copy |
| Shipping & Fulfilment | ERP-driven logistics; business delivery terms; optional SmartRoutes (Standard/Plus) for routing and dispatch | Consumer carriers, pickup/delivery scheduling; SmartRoutes (Standard/Plus) supported where applicable |
| Marketing | Not a core requirement; ERP/sales-driven engagement | SEO, loyalty, upsell/cross-sell, coupons, campaigns |
| Compliance | Business licence validation; account-level restrictions | Consumer sales limits, ID verification, per-transaction restrictions |
4. Key Takeaways for Administrators
- B2B and B2C share the same core SellStack ↔ 365 Cannabis integration framework; distinctions arise from account management, pricing structures, and storefront feature sets.
- ERP remains the source of truth for compliance, core product data, pricing baselines, and inventory. SellStack governs enriched data, storefront behaviour, and customer-facing workflows.
- Core product data modelling within 365 Cannabis remains consistent across both models; administrators should focus on storefront configuration and customer account management as the primary areas of differentiation.
- B2C requires significantly more storefront configuration, including payment, fulfilment, marketing, and consumer account flows not relevant in B2B.
- SmartRoutes is equally applicable in B2B and B2C operations; in B2B it supports structured logistics and delivery scheduling, while in B2C it supports consumer-level delivery coordination.
