Customer records and loyalty bring visits, purchases and rewards into the conversation. They should help your team—not ask the customer to explain everything again.
Historical FrabPOS material—not a One product screenshot.
CUSTOMERS & LOYALTY / PRACTICAL FUNCTIONS
What it does. Why you’ll use it.
Useful customer details at the right moment. Choose a function, see the example, and check the detail with your business.
01 / CUSTOMER RECORDS
Phone lookupContact recordVisit history
Find a returning customer
Look up the customer rather than create another record for every visit.
WHY IT HELPSA familiar welcome without duplicate information.
See an example +
Try this: Find the same customer at the counter and online.
Check in your setup: Identity matching, permissions and verification must be demonstrated.
02 / CUSTOMER RECORDS
Past purchasesOriginal saleCustomer details
Purchase history
See the recorded purchases when a customer has a question.
WHY IT HELPSLess guessing about what happened on their last visit.
See an example +
Try this: Find a customer’s previous sale and the related receipt.
Check in your setup: History availability depends on the connected source and any agreed data import.
03 / REWARDS
Earn pointsRepeat visitsRedeem reward
Points or visit rewards
Set the earning rules around the behaviour you want to reward.
WHY IT HELPSA reward your team can explain simply.
See an example +
Try this: Run a qualifying purchase followed by a reward redemption.
Check in your setup: Confirm the supported program type, exclusions and rounding rules.
04 / REWARDS
Loyalty onlyMembership onlyBoth if allowed
Membership and loyalty policy
Choose how member benefits and loyalty interact.
WHY IT HELPSNo surprise double discount at the counter.
See an example +
Try this: Test a member using a reward during a special offer.
Check in your setup: The allowed combination is a configured rule, not an automatic promise.
05 / REWARDS
Original saleRefundReward balance
Refunds & reward adjustments
Check what happens to rewards when the original purchase is reversed.
WHY IT HELPSBalances are easier to explain after a return.
See an example +
Try this: Refund an earning purchase and check the resulting balance.
Check in your setup: Demonstrate adjustment behaviour before publishing the reward terms.
06 / CUSTOMER RECORDS
Order contactPermissionMessage preference
Contact preferences
Keep contact information and marketing permission separate.
WHY IT HELPSUseful customer service without unwanted messages.
See an example +
Try this: A customer allows order updates but declines marketing.
Check in your setup: Email/SMS delivery, credits and consent requirements are separate checks.
01 / 06
Swipe, or use the arrows
About these functions and your One setup
These cards describe the supplied One project and the published FrabPOS service range. They are not screenshots or certification of every function in a live One release. Your demonstration and quote confirm the exact menu rules, hardware, connections and service scope before you commit.
One has benefit settings. Demonstrate whether your policy allows loyalty, membership or both before advertising it.
Are SMS messages free?
No. Message usage and credits are separate from the software offer.
About these examples & product scope
These are illustrative business situations, not attributed customer complaints. The explanations use the agreed One project scope and FrabPOS’s published service range. Older FrabPOS or Order Eats material does not certify every function in One. Your demonstration and quote confirm the released setup.