A Boutique client card is a QR code that identifies a client at the shop counter without handing the operator the client's full record. Staff issue the card from the client's record. The client keeps it (printed, or saved as a photo or wallet pass), and a paired Boutique device scans it at checkout.
The QR carries only a version marker and a random token, for example coolfocus-boutique:v1:8k3F.... It contains no name, date of birth, phone number, address, client number, notes, or clinical data. CoolFocus stores only a one-way hash of the token, never the token itself, so a scan is the only way to prove who holds a valid card.
Use this when a shop counter needs to confirm a client's identity and points balance quickly, without an operator opening the client's CRM record.
From the client's record, issue their first card. This generates a token, shows the QR code once, and returns a plaintext token you can also read aloud or type in by hand if a scan fails.
Once a card is issued, issuing again does not replace it. CoolFocus blocks a second issuance while one is already active, because silently swapping a client's working card just because a dialog got reopened would strand them holding a card that no longer scans. To replace an active card, rotate it instead.
A client can have at most one active card at a time. A card can optionally be pinned to a single center; if it is, a device at a different center cannot resolve it.
Rotate a card when it is lost, damaged, or needs to be reissued. Rotating immediately retires the current card and issues the next one. There is no grace period: the old QR stops scanning the moment the new one is created, since the usual reason to rotate is that the old card is no longer in the client's hands.
Rotation requires the generation number of the card being replaced. This protects against a retried request accidentally rotating a card that was already replaced by someone else in the meantime; a stale retry fails instead of revoking the newer card.
Revoke a card when it should stop working and the client isn't available to receive a new one on the spot, for example a card reported lost over the phone. Revoking is safe to repeat: if nothing is currently active, it simply reports that there was nothing to revoke.
An operator scans the client's QR on a paired Boutique device. Resolving a scan requires both:
• A paired, active device session for that center.
• A signed-in operator session on that device (see Boutique Operators: PINs and Supervisor Approval). A device sitting unattended on a counter cannot resolve a card by itself.
A successful scan returns only what the counter needs:
• Points balance
• Boutique eligibility
• Verification state
No name, DOB, phone, address, client number, notes, or clinical field comes back. Every successful scan is written to the client's audit history so a card's use can be traced later.
A scan can also fail. The device shows a plain message and, depending on the reason, the operator knows what to do next:
What happened
What the operator sees
The code isn't a recognized card
Card not recognized
The card was rotated, revoked, or the client was merged away
This card is no longer valid; issue a new one from the client's record
The client's record isn't currently active
This client's record is not currently active
The card was issued for a different center
This card was issued for a different center
Scan attempts are rate-limited, since a QR token is a bearer credential and repeated guessing is the only way anyone could try to test one.
A client's record shows every card generation ever issued, newest first: its state (active, revoked, or merged), which center it was pinned to, when and by whom it was issued, and when, by whom, and why it was revoked. The plaintext token and QR are never shown again after the moment they were issued or rotated; if a client cannot produce a working card, the fix is to rotate, not to look up the old one.
If a client with an active or past card is merged into another client record, every one of that client's card generations is marked merged and stops working permanently. A merged client can't be reissued a card under the old record.
• Issuing, rotating, or revoking a card requires Clients (CPC) - Update.
• Viewing a client's card history requires Clients (CPC) - View.
• Points & Inventory must be enabled for your organization.
• Boutique Devices: Pairing Phones for Checkout
• Boutique Operators: PINs and Supervisor Approval
• Points & Inventory Overview
• Claiming Items With Points
