Glenora Cannabis - Hybrid Fulfillment Architecture
Glenora Cannabis built its brand on a strict “Fastest Same-Day Delivery” promise, but scaling their hybrid fulfillment model, balancing local dispatch with national mail orders, created severe operational bottlenecks.
As the Technical Project Manager, I led the architecture and rollout of a unified digital platform that automated their logistics pipeline, eliminating administrative waste and securing their delivery SLAs at scale.
Why was Glenora Cannabis created?
As a multi-location retailer offering distinct services at each branch (some offer local delivery, others mail order), Glenora needed a way to route customers to the right inventory without friction. Their previous setup struggled to handle the complexity of hybrid fulfillment, where a single customer might qualify for same-day delivery from Store A but only pickup from Store B, leading to operational confusion and lost sales.
Logistics Bottlenecks
Manual order routing protocols were creating severe administrative lag, threatening the brand's core "Same-Day Delivery" SLA.
Fulfillment Fragmentation
The legacy system lacked the intelligence to segment "Mail Order" and "Local Delivery" inventories, resulting in unfulfillable orders and lost revenue.
Omnichannel Loyalty Gap
A critical disconnect between in-store points and online accounts prevented a unified view of customer lifetime value (LTV) and loyalty.
Operational Data Silos
The inability to reward local customers digitally led to churn and missed opportunities for high-margin, targeted regional promotions.
How did we tackle the challenge?
I managed the end-to-end SDLC for this logistics overhaul, acting as the operational bridge between the Glenora ownership team and the technical developers.
Technical Execution: I mapped the dual-pipeline business logic and defined the API integration requirements, allowing developers to successfully connect the WooCommerce frontend with dedicated dispatch software and Canada Post APIs.
Stakeholder Management: I mapped the new operational workflows, created strict SOPs for the fulfillment staff, and utilized Jira to manage the development sprints, ensuring the new system was deployed without disrupting daily revenue.
- Cova POS (Multi-Location Sync)
- Cova Pay (Payment Processing)
- SpringBig (Loyalty Integration)
- Figma (Prototyping)
- Jira, Asana, Google Sheets
Hybrid Fulfillment Architecture
Engineered a dual-pipeline routing logic to segment localized same-day delivery from national mail-order fulfillment.
Workflow Logistics Automation
Reduced manual administrative touchpoints by 45% through a unified dispatch and order-routing technical ecosystem.
Omnichannel Inventory Sync
Architected a real-time data bridge to ensure inventory accuracy across distinct localized and provincial stock pools.
Unified Loyalty Infrastructure
Managed the technical integration of SpringBig and Cova Pay to synchronize in-store points with digital accounts.
The Spotlight Feature: Smart Fulfillment Context Switcher
The Problem
Glenora’s "Fastest Same-Day Delivery" promise was being jeopardized by a manual fulfillment process. Without a technical gatekeeper at the start of the user journey, customers in mail-order-only zones were frequently viewing and purchasing "Same-Day Delivery" stock. This led to high-volume unfulfillable orders, manual refund cycles, and a total collapse of the brand's delivery SLA.
The Tech
A dynamic filtering engine that instantly checks the user's postal code against three distinct delivery zones and inventory databases.
The Win
This logic effectively runs three different businesses (Local Delivery, In-Store Pickup, and Provincial Mail Order) from a single domain. It prevents "unfulfillable orders" by ensuring a customer in a "Mail Order Only" zone never sees "Same Day Delivery" stock, reducing refund rates to near zero.
