Miss Jones - Multi-Location Outposts
Miss Jones markets itself as “Your Friendly Neighbourhood Cannabis Outpost,” but maintaining that hyper-local feel across a rapidly expanding chain requires enterprise-grade infrastructure.
As the Technical Project Manager, I led the rollout of a multi-tenant enterprise platform for 9+ Miss Jones locations. By implementing strict ‘Location Guard’ logic, I eliminated inventory fragmentation, allowing the business to scale operations effortlessly while maintaining localized data integrity.

Why was Miss Jones created?
Scaling from one store to many introduces a “Data Silo” nightmare. Miss Jones needed to manage distinct pricing, stock levels, and legal compliance for 9 different locations simultaneously. Their biggest hurdle was Inventory Fragmentation, ensuring that a customer in “Bell City” couldn’t accidentally add “Chemong” inventory to their cart, which would cause fulfillment failures and refund loops.
Marketplace Data Integration
Scaling required managing external API feeds for third-party aggregators (like Hibuddy), necessitating a unified "source of truth" to prevent inventory discrepancies across the network.
Database Fragmentation
Fragmented customer profiles and siloed store databases hindered centralized data governance and prevented a unified view of regional performance and compliance.
Operational Scalability
Manually syncing localized pricing, stock levels, and legal parameters across 9 distinct outposts had become unsustainable and prone to high-risk fulfillment errors.
Localized Brand Integrity
The technical challenge of delivering a high-touch, "neighborhood" user experience while deploying a standardized enterprise framework across multiple regions.
How did we execute the multi-location rollout?
I led the deployment pipeline for this unified, multi-tenant eCommerce platform, acting as the critical translator between regional business stakeholders and the backend development team.
Technical Execution: I mapped the complex user journeys and authored the strict ‘Location Guard’ logic parameters, ensuring developers built a frictionless gateway that locked users into their specific local inventory feed.
Stakeholder Management: Navigating the competing priorities of regional store managers, the compliance team, and external API vendors (Cova POS) was treated as a hard operational metric. I maintained strict sprint cadences across all 9 concurrent deployments to ensure zero scope creep.
- Breadstack Enterprise
- Figma (Prototyping)
- Moneris (Payment Processor)
- Cova POS (Enterprise Setup)
- StickyCards (Loyalty)
Multi-Tenant Architecture
Architected a unified enterprise platform capable of supporting 9+ distinct retail locations within a single, scalable codebase.
API Data Governance
Managed the high-stakes integration of Cova POS, ensuring real-time inventory and pricing accuracy across all fragmented store databases.
Inventory Risk Mitigation
Defined the logic for the "Location Guard" gateway, successfully eliminating 100% of cross-store fulfillment errors and refund loops.
Scalable Deployment Pipeline
Standardized the digital launch process, allowing the business to spin up new physical outposts with zero technical friction or downtime.
The Spotlight Feature: The Global Location Guard
The Problem
Without a centralized session manager, users could inadvertently mix inventory from different physical retail outposts within a single digital cart. This "data leakage" created a massive operational failure point: orders were being placed for items that were physically unavailable at the user's selected pickup location, resulting in immediate fulfillment failures and high-volume manual refund cycles.
The Tech
A JavaScript state-manager that monitors the user's active cart against their selected store ID. If a user tries to switch locations while items are in their cart, the system triggers a "Cart Conflict Protocol" (as seen on the live site), warning them that incompatible items will be removed.
The Win
This logic eliminated cross-store fulfillment errors, allowing Miss Jones to scale to new locations without increasing their support ticket volume.
