Why spa counts drift
Picture a day spa at closing time. The retail shelf by the front desk looks a little thin, but the point-of-sale report says six bottles of a body lotion should be there. Two went home with guests after a massage and were added to the service ticket as a note instead of a product line. One was opened as a tester. Another went back to a treatment room when the professional-size container ran out mid-afternoon. Nobody did anything wrong, but the count is now fiction.
That scene is an illustration, not a TwoQM client. Spas sit between salon operations, like those on TwoQM's pages for hair salons and nail salons, and retail: the same product can be sold at the counter, sold on a service ticket, or used in a treatment room. TwoQM builds connected systems that tie those movements to the tickets and counts the spa already keeps.
This article is about operations: product records, stock movements, and who reorders. It gives no advice about products, treatments, or results. It is also not about keeping online and in-store counts in sync, which covers a store selling the same item through two channels. Here the problem is one location where retail and service use share the same shelves.
Here is an original example, not a measured result. A spa with four treatment rooms and a small retail wall in the Rio Grande Valley runs its booking software for appointments and a separate point-of-sale screen for the counter. Products sold at checkout after a service are sometimes rung up on the ticket, sometimes at the counter, and sometimes written in the ticket notes. Professional-size containers for treatment rooms come out of the same back-room stock as retail bottles. Testers are opened from retail stock and never recorded.
Products move in three places, and only one subtracts from inventory.
One product list, two kinds of stock
Start with a single product list that knows the difference between:
Retail units: sealed items a guest can buy and take home.
Professional stock: containers used in treatment rooms, tracked by container, not by drop or pump.
The same product can have both kinds, each with its own count and its own reorder point that the owner or manager sets. Software stores those reorder points; it does not decide them.
Every movement gets a reason
Counts stay honest when every change has a reason from a short, fixed menu:
Sold on a service ticket. A retail line on the guest's ticket, entered by the provider or front desk at checkout.
Sold at the counter. A retail-only sale with no service attached.
Moved to a treatment room. A retail or back-room unit opened as professional stock.
Tester opened. Recorded once, so it stops looking like missing stock.
Damaged or past date. Removed from sale, with who removed it.
Returned or exchanged, following the spa's own return rules.
Received from vendor. Checked in against the order, with who checked it in.
The rule that matters most: a product mentioned in ticket notes is not a sale. If a guest takes something home, it goes on the ticket as a product line, or the ticket cannot be closed. That one rule is what ties retail inventory to service tickets. It also gives the spa clean data for retail commission rules, if it uses them; how commission works is the spa's decision.
Counts, alerts, and reorders
With movements recorded, a weekly shelf count becomes a check, not a rescue. The manager counts a short list of items, the system shows the expected count beside the actual one, and any difference above the spa's chosen tolerance becomes a line to explain, owned by a named person.
When a retail or professional count reaches its reorder point, the named buyer gets an alert with the last few weeks of movements. The buyer decides what to order and places the order. The system never orders on its own.
Where AI helps, and where it stops
Subtracting stock and sending low-stock alerts is ordinary business automation and does not need AI. AI can help a person think: drafting a reorder list from recent movements for the buyer to edit, summarizing which products show the most unexplained differences, or preparing a first Spanish draft of a shelf-count checklist that a bilingual team member reviews. It never places orders, never changes counts, never closes a ticket, and never writes product descriptions that make claims about results.
Connect it to the systems you already run
Your booking software stays the source of truth for appointments and your point-of-sale system for payments. An inventory layer can read product lines from closed tickets and counter sales, if those systems allow it, and keep the movement log and reorder alerts in one place. Whether your current tools support those connections is confirmed during scoping. Sometimes your point-of-sale system's built-in inventory, plus the "no notes, product lines only" rule, is enough, and scoping should say so.
Where to start this week
Pick the five retail products that sell most and run out most often. Count them today, then compare that count with what your point-of-sale report says. For each difference, ask which movement was never recorded: a ticket note, a treatment-room transfer, or a tester. That list is your first draft of movement reasons.
If you want spa retail inventory tied to the tickets and counts you already keep, TwoQM can scope the product list, movements, and connections around your booking and point-of-sale tools. Pricing explains how business apps, systems, and custom software are scoped. Nothing here is product, health, or tax advice.
Describe Your Spa Inventory Flow · Explore connected systems