Skip to content
Gabriel de Freitas logo

CASE STUDY · BUSINESS SYSTEMS

24K Business Systems: A Multi-Location Operations Platform

A five-location retail and hospitality group runs its daily operations on an internal software platform I planned, designed and built: customers, tasks, inventory, purchasing, costing, loyalty, training and accounts, tied together across every store.

Store locations in the group
5Store locations in the group
Point-of-sale systems unified
5Point-of-sale systems unified
Customers on one record
30,000+Customers on one record
Internal tools in daily use
15+Internal tools in daily use

Context

Twenty Four Karats is a five-location retail and hospitality group: a cannabis dispensary, a headshop, a liquor store, a restaurant and the plaza that ties them together.

Each location sells differently, carries different stock and serves customers under different rules, but they operate as one business with shared staff, shared leadership and shared customers.

I planned, designed and built the internal platform the group uses to run day to day, and I remain the person accountable for it.

The operational problem

Five stores meant five points of sale, and customer, inventory and task information spread across disconnected systems and spreadsheets.

A customer who shopped at two locations existed as two unrelated records. Stock counts were reconciled by hand and then re-entered. Daily tasks lived wherever a manager happened to write them down. Purchase orders arrived from suppliers and were typed into the point of sale line by line.

None of this was a failure of effort. It was the predictable result of growing to five locations on tools that were each designed for one.

What was built

A staff portal of purpose-built tools sharing one set of accounts, roles and data: customer database unification, task boards for staff and leadership, inventory counting and reconciliation, purchase-order processing, menu costing, loyalty, in-store display management, training and account control.

The tools were planned as one system rather than assembled one at a time. Requirements came from the people doing the work, the data model was designed once and shared, access was scoped by location and responsibility, and each tool was tested against real operational scenarios before staff relied on it.

  • One shared account and permission model across every tool
  • Role-based access per location and responsibility
  • A single customer record synchronized across five POS systems
  • Point-of-sale and commerce connections where the data lives
  • Tools built for the floor, phone-ready and quick to use
  • Leadership visibility across all five locations

Representative tools

A selection of the tools in daily use across the group.

  • Customers

    Customer Database Unifier

    Keeps 30,000+ customers in sync across all 5 POS stores.

  • Operations

    Staff Task Manager

    Daily tasks viewed and completed across all 5 stores.

  • Operations

    Leadership Task Board

    Projects organized among the leadership team.

  • Operations

    Order Shipments & Receivables

    Track shipments, orders and receivables across locations.

  • Inventory

    Liquor Store Inventory Counter

    Scan, count, review discrepancies and sync updates.

  • Inventory

    HQ Inventory Hub

    Locate items on the floor map and print price tags.

  • Costing

    Restaurant Menu Cost Calculator

    Ingredient costs, margins and pricing for menu items.

  • Purchasing

    Liquor Store PO Onboarding

    Process purchase orders into Shopify POS.

  • Customers

    Loyalty Program

    Assign stamps, check balances, manage redemptions.

  • Displays

    Cannabis Mega-Screen Menu Editor

    Edit the in-store mega-screen menu display.

  • People

    Staff Training Tool

    Training modules with Q&A to onboard and upskill.

  • People

    24K User Accounts

    Central control of accounts, passwords and roles.

How the system supports the business

Staff open one portal and see the work that belongs to their location: the day's tasks, the counts to run, the orders to receive, the customers to look up.

Managers and leadership work from the same data rather than a summary of it—tasks across all five stores on one board, projects organized among the leadership team, shipments and receivables tracked in one place.

Customer information stays consistent because it is unified rather than duplicated. Inventory decisions are made against counts that reconcile back to the point of sale. Menu pricing is set from ingredient cost and margin instead of estimates. New hires are onboarded through the same training modules regardless of which store they join.

What this demonstrates

This is what custom business software looks like when it is planned as one system: not a single flagship application, but a coherent set of tools that share accounts, data and design, each built for a specific job someone does every day.

It also demonstrates the working model. One person gathered the requirements, designed the interfaces, built the software, connected it to the systems the business already ran on, tested it and deployed it—and is still accountable for it.

The same group's public-facing storefronts were designed and built alongside the internal platform, so the customer experience and the operation behind it were planned together.

Back to all selected work, or read how these engagements are scoped under custom business software and automation and integrations.

Could your operation run on tools built for it?

Describe how your locations, staff and systems work today. I review it personally and reply with the clearest next step.