paying, cash, transaction, payment, green, wallet, russia, moscow, italian food, food, pay, woman, female, girl, customer, retail, consumerism, consumer, sale, buy, young, buyer, shopper, purchasing, friends, woman shopping, food cart, russian rubles, russian roubles, paying, paying, cash, payment, wallet, wallet, pay, pay, pay, customer, customer, customer, customer, customer, retail, consumer, consumer, consumer, buy, buy, buyer, shopper
Photo by 1139623 on Pixabay

System Selection

POS customer records

Manage POS customer records through clear collection purposes, accurate profiles, staff access controls and an export plan.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Systems.

Decide why each detail is needed. Find an existing profile before creating another. Keep marketing permission separate from service contact. Control who can view or export records.

First check whether the Privacy Act 1988 covers the business: it covers organisations with an annual turnover of more than $3 million and some other organisations, including some smaller ones. Covered businesses must follow the Australian Privacy Principles (APPs), which the Office of the Australian Information Commissioner (OAIC) oversees.

Key steps for managing POS customer records responsibly

  • Verify if the Privacy Act 1988 applies to your businessCheck annual turnover ($3M+ threshold) or other coverage criteria
  • Collect only personal information that is reasonably necessaryAlign with APP 3 – ensure data collection supports a clear purpose
  • Separate marketing consent from service contact detailsDo not assume email collection = marketing permission
  • Control access to customer records across systemsReview admin, app, and till access permissions regularly
  • Plan for data export and migration when changing providersInspect sample exports for identifiers, notes, loyalty balances and marketing status

Collect for a clear purpose

A delivery may need an address and contact number. A routine counter sale may need no named customer. Choose fields for the task rather than asking every shopper for the same details. Keep payment card numbers, health information and casual judgements out of customer notes.

Where the Australian Privacy Principles apply, APP 3 governs collection: ordinary personal information must be reasonably necessary for the organisation's functions or activities.

An email address collected for a digital receipt does not, by itself, establish permission for promotional messages. Keep evidence of the customer's choice separate from service contact details. Email and SMS marketing falls under the Spam Act 2003, and where it applies, APP 7 on direct marketing does not.

Every marketing message should offer a simple way to opt out, such as an 'unsubscribe' reply or a prominent link to a subscription control centre in an email, or a 'STOP' reply to a text message. Record each opt-out against the customer profile straight away.

In Square, manually entering an email address into a profile can automatically opt the customer into email marketing. Check the permission record against the customer's choice before sending a campaign.

Sensitive information has a stricter collection test for APP entities: collection must be reasonably necessary for the entity's functions or activities, and the individual must consent unless an exception applies.

Personal information must be collected by lawful and fair means and generally from the individual concerned, unless that is unreasonable or impracticable.

Square's directory can hold visit history, preferences, frequently purchased items, loyalty points and personalised notes alongside contact information.

Changes to a profile, including updates and deletions, appear in both Square Dashboard and the point of sale app, so staff can work from the same current record.

Keep checkout moving

Give staff a short reason for asking, such as attaching a purchase to an existing profile for a warranty enquiry. Search first, confirm the match without disclosing another person's details, and collect only what the current task needs. If the request is optional and the customer declines, complete the sale through an available checkout path.

Square allows staff to add a customer during or after a sale. Check whether customer details are optional or required before making a routine profile request part of every sale.

Choose checkout fields deliberately

Shopify POS can be configured to request a first name, last name, phone number, email address, or combinations of contact details.

Its settings distinguish between details that are not required, recommended but skippable, and required. A required setting prevents checkout if a customer does not provide the information.

Required vs recommended vs optional checkout fields in Shopify POS

Required
Mandatory field – checkout blocked if missing (e.g., email for digital receipt)
Recommended but skippable
Displayed as optional – staff may prompt but can proceed without
Not required
No input needed – no impact on checkout flow

Maintain accurate profiles

Duplicate records can divide purchase history and leave conflicting contact or marketing details. APP 10 requires reasonable steps to keep personal information accurate, up to date and complete.

A shared name, phone number or email address is a reason to review two profiles, not proof that they belong to one person.

Square flags possible duplicates sharing an email address or phone number. Square warns that a completed profile merge cannot be reversed. Confirm identity and current preferences before an authorised person merges records.

Some Square records are created without a staff member entering a profile during checkout: customers are automatically added when they book through Square Appointments, enrol in Square Loyalty or are charged through Square Invoices. Account for these entry points when reviewing why a profile exists and whether its details remain current.

For Square customer email imports, the status column can be set to Subscribed, Unsubscribed or Unknown. Square describes Subscribed addresses as available for Square Marketing communications; an Unknown status is distinct from a recorded subscription and should not be treated as evidence of consent.

Key compliance requirements under the Australian Privacy Principles

  • APP 3: Collection of personal informationMust be reasonably necessary for functions or activities
  • APP 10: Accuracy of personal informationReasonable steps must be taken to keep records accurate and up to date
  • APP 11: Security of personal informationProtect against misuse, interference, loss, and unauthorised access

How to merge duplicate customer profiles in Square safely

  1. Identify potential duplicatesUse Square’s alerts for shared email addresses or phone numbers
  2. Confirm identityAsk for proof of identity (e.g., name, last purchase date, payment method)
  3. Review preferences and historyCheck visit history, loyalty points, and notes before merging
  4. Merge with cautionNote: Merged records cannot be reversed – use only after confirmation
  5. Update marketing statusRecord opt-out choices immediately after merge

Pros and cons of auto-adding customers via Square integrations

  • ProsReduces manual entry errors; captures leads from bookings, invoices and loyalty sign-ups
  • ConsCan create incomplete or outdated profiles if not reviewed; increases risk of duplication

Control access and plan an exit

Check separately who may attach a customer to a sale, open details, edit a profile, merge records and download a list. Review admin and connected-app access as well as the till. APP 11 requires reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure.

A customer CSV is another copy of personal information. Restrict its storage and decide when working copies can be removed; under APP 11 an entity also has obligations to destroy or de-identify personal information in certain circumstances.

Before changing providers, inspect a sample export for identifiers, contact details, notes, custom fields and marketing status. Ask separately how loyalty balances and stored payment arrangements would move. For transaction history, see the supporting article on transaction-history migration.

Keep a short operating record of collection purposes, identity checks, marketing choices, merge authority, access and export ownership. Revisit it when checkout settings, staff roles or providers change.

Explain access and correction

For an organisation covered by the Australian Privacy Principles, its privacy policy under APP 1 must explain how a person can access personal information held about them (APP 12) and seek its correction (APP 13).

It must also describe the kinds of information collected, how it is collected and held, and the purposes for which it is used or disclosed.

The policy must also explain how a person can complain about an APP breach and how the organisation will handle the complaint. A complaint should first go to the business in writing, with a reasonable time, usually 30 days, to respond; it may then go to a recognised external dispute resolution scheme.

When a customer asks for their record, an organisation must respond within a reasonable period, and the OAIC considers 30 days reasonable. Search the POS, the admin dashboard and any connected marketing app, because each may hold part of the profile.

If the organisation is likely to disclose personal information to overseas recipients, the policy must say so and, where practicable, identify the countries involved.

Further reading: Collect customer information (squareup.com).

In this guide

  1. Collecting customer details without slowing a saleA short checkout process for asking for needed customer details, finding existing profiles and recording marketing choices separately.
  2. Finding duplicate customer profiles in a POSFind likely duplicate POS customers, verify identity and marketing preferences, and check irreversible merge limits before acting.
  3. Reviewing customer-data access at the tillCheck which till roles can view, edit, delete or export customer records against the actual plan, location and access routes.
  4. Exporting customer records when changing POS providersPrepare a POS customer export, map fields and consent status, check a small import and handle order history separately.

More from System Selection