Sales, packages, and balances
Package selection, usage, and balance management are being refined. A sale is not assumed to create an appointment.
TANCOMMAND POS
Tanning Salon POS System: What TanCommand Is Building
IN DEVELOPMENT
TanCommand is developing a tanning salon POS workflow around sales, packages, balances, and customer context. It is not represented as broadly available. Payment flows, Stripe integration, and cash-discount support remain in development and will be described only after verification.
STATUS FIRST
Sales and package context are being refined for beta use.
Customer and appointment context
Customer history and booking workflows are in development. Their exact behavior will be published only when the relevant workflow is ready.
Payments and processor flows
Payment support, including Stripe, recurring schedules, charges, refunds, and cash discount, is not presented as broadly available until verification is complete.
Guided onboarding
Future migration depends on a source system, available exports, package and membership rules, payment constraints, and readiness validation.
WHAT TO EXPECT FROM A TANNING POS WORKFLOW
The purchase should fit the salon context—not flatten it.
A tanning salon POS system is more than a generic payment screen. Owners should be able to evaluate whether a product can make package rules understandable, keep customer context visible, support staff permissions, and make receipts, inventory, reporting, and payment rules clear to the people using them.
- Customer, package, and membership context before a transaction is finalized.
- Clear treatment of balances, expirations, sharing rules, and exceptions where a business uses them.
- Staff permissions, corrections, and owner review paths that are visible rather than hidden.
- A verified payment and receipt workflow—not an assumed processor connection.
- Reporting that can distinguish what happened from what someone thinks should happen next.
PAYMENTS REQUIRE PROOF
Payment claims need a tested flow, the right disclosures, and human review.
Cash discount support and Stripe integration are in development. TanCommand will not describe a payment flow publicly until the processor, legal and disclosure requirements, safeguards, and operating workflow are verified. That applies to recurring schedules, charges, refunds, and membership-payment changes as well.
BEFORE A POS CHANGE
Ask the cutover questions before you commit to a software change.
Source data
Which customer records, packages, memberships, and balances can be exported from the current system?
Rules
How will package logic, membership rules, permission levels, and locations be mapped and verified?
Payments
What must happen with card credentials and recurring payment authorizations, which may require separate arrangements?
Readiness
What needs to be tested before a cutover, and which workflows remain outside a supported path?
TanCommand’s onboarding design is in development. A future supported path depends on source exports, payment rules, product readiness, and validation.
QUESTIONS AND ANSWERS
Tanning salon POS FAQs
Is TanCommand’s tanning salon POS system available now?
No broad POS availability is claimed. TanCommand’s sales, packages, and balance workflows are in active development and are being refined for beta use.
Does TanCommand POS support Stripe or cash discount?
Stripe integration and cash-discount support are in development. TanCommand will describe a payment flow publicly only after processor, legal, disclosure, safeguard, and workflow verification.
Does a sale automatically create an appointment?
TanCommand does not make that claim. Appointment and customer-history workflows are in active development, and a sale should not be assumed to create an appointment.
Can a salon move memberships and package balances into TanCommand?
The onboarding path is being designed around those records. Any future supported migration depends on the source system, available exports, payment rules, and readiness validation.