SOPHIA XT
Point of sale · Inventory · Retail

Three stores, one system, and every count stays its own.

A multi-store retailer needs one catalogue, one back office and one website, without a customer being shown stock that sits forty minutes away. We build point of sale and inventory where each store's stock is kept apart in the data itself.

See it running
(586) 300-4975
Search stock
travel mug
Travel mug, North: 6 on hand
Travel mug, South: 2 on hand
Travel mug, East: 0 on hand
Selling from
North
South
North
South
East
Scan
Tender
Receipt
Today
Week
Month
South store, sales this week
$6.2k
$0.8k
$1.2k
Sold from South. North and East unchanged.
An illustration of a sale at one store, not a customer's figures.
What it does

One catalogue, every store kept separate.

Smoker's Alley runs all three of its stores on this today, from the public storefront down to the staff time clock.

  1. Per-store stock

    Each location's inventory is isolated in the data layer, so a sale at one store never moves another store's count.

  2. One storefront for every location

    The public site covers all stores and shows each one's stock as that store's stock.

  3. In-store displays

    Screens in the shop are driven from the same catalogue as the website, so a price changes once.

  4. Staff time tracking

    Clock-ins are kept against the store's own records, not a separate app.

  5. Your existing host

    Deployed as a managed application on the hosting the business already pays for.

  6. Built for your shop

    The products you carry and the way your staff ring a sale are written into the system, not configured around it.

In production

Running for a customer today. Open it.

The public Smoker's Alley storefront

Smoker's Alley

Retail operations for a three-store smoke shop on one system, with each store's stock kept its own.

  • A storefront covering all three locations, with per-store isolation enforced in the data layer.
  • Staff time tracking against the store's own records.
  • In-store display surfaces driven from the same catalogue as the public site.
How a build runs

Four steps, and you can watch every one.

Step 1

Map how the work moves

We start from how your people do the job today, and write down the rules the software has to enforce.

Step 2

Build the records first

Customers, stock, jobs and the books come before screens, with the rules in the data layer where they cannot be skipped.

Step 3

Bring your data across

Existing spreadsheets and exports come in through a staged import you review before anything is committed.

Step 4

Deploy where you want it

Your own hardware, a host you already pay for, or a server you control. You keep the keys.

Questions

What people ask first.

Yes. Store isolation is enforced in the data layer rather than filtered in the interface, so one store's stock cannot leak into another's counts or onto the website under the wrong location.

Tell us what you run on now.

A call is enough to know whether a custom system is worth it for you, or whether what you have should stay.

Also builtERP softwareAn ERP that refuses an unbalanced journal.Read it Also builtDispatch softwareFrom the call to the closed job, entered once.Read it