Skip to main content

All About Central Customer

Central Customer gives your organization one shared customer profile across every store, so returning customers are recognized, bans and notes follow them, and metrics and discounts reflect their full history.

What Central Customer Does

Without Central Customer, each of your stores keeps its own separate record for the same person. A customer who shops at three of your locations looks like three different people. They show up as "new" at every store, first-time discounts can be claimed more than once, notes and warnings stay at the store that wrote them, and a ban at one location doesn't stop them at another.

Central Customer adds an organization profile (also called the org profile) that sits above each store's own customer record. Every store's record for the same person links to that one org profile. The org profile is what your stores share: identity, bans, warnings, cross-store notes, documents, customer groups, and purchase history.

Each store still keeps its own customer record, and point-of-sale logic still runs on it. The org profile connects those store records. It does not replace them.

Why It Matters

  • Accurate new vs. returning customers. A customer is recognized as returning even on their first visit to a particular location.

  • Org-wide bans and warnings. A ban or warning set at one store is enforced at every store right away.

  • Cross-store notes. Notes written at one store are visible to staff at every location.

  • Shared documents. IDs, medical cards, and agreements uploaded at one store can be viewed at the others without asking the customer again.

  • Org-wide discounts. Nth visit discounts, such as first-time customer discounts, are checked against the customer's visits across the whole organization.

  • Org-wide metrics in the POS. Lifetime value, average order value, order count, last visit, and visit frequency cover every store, and the new Insights tab shows purchase preferences and shopping patterns.

How It Works at a Glance

  1. Backfill. When Central Customer is turned on, a one-time process consolidates existing store records that clearly belong to the same person into one org profile.

  2. Linking. When staff scan an ID or open a customer in Customer Management, Treez looks for a matching org profile. Exact matches link automatically. Possible matches are shown to staff to confirm.

  3. Syncing. Customer changes made at any store flow up to the org profile automatically. Changes never flow down to a store's record without a person confirming them.

  4. Shared records. Bans, warnings, notes, documents, and groups are contributed by individual stores and shared across the organization.

  5. Org-wide view. The POS customer drawer, discount logic, and Event History use the org profile to show and act on the customer's full history.

Getting Started

Central Customer must be enabled for your organization by Treez. There is no Config Page toggle. To have it enabled, contact Treez Support or your CSM.

When it is turned on:

  • Backfill runs automatically. Your team doesn't need to do anything.

  • Customer Management shows an Org ID: LINKED or Org ID: UNLINKED status on each customer profile.

  • Customers who were consolidated during backfill link to their org profile the first time their profile is opened or they check in.

Important Notes

  • Treez never overwrites your store's records on its own. Each store's record changes only when someone at that store edits it or confirms a sync.

  • Your store keeps working if the org profile can't be reached. If the Central Customer service is temporarily unavailable, check-in and sales continue using your store's own data. Org-wide information appears again once the service is back.

  • Typed searches look only at your store. Searching by name, phone, email, or ID number in the search bar finds only your store's customers. Matching against other stores happens when an ID is scanned in Customer Management, or when a customer's profile is opened or saved.

  • Loyalty is unchanged. Treez Loyalty and Alpine IQ balances were already shared across the organization and continue to work as before.

Related Articles

  • Central Customer | Identity Resolution and Backfill: How Treez decides two records are the same person.

  • Central Customer | Linking and Unlinking Customers: Scanning, reviewing potential matches, and the Org ID status.

  • Central Customer | Syncing Store and Org Profiles: The out-of-sync banner and what stays at the store level.

  • Central Customer | Org-Wide Bans and Warnings: Setting, viewing, and lifting bans and warnings.

  • Central Customer | Cross-Store Notes: Adding and managing notes every store can see.

  • Central Customer | Shared Customer Documents: How uploads, viewing, and deletes work across stores.

  • Central Customer | POS Customer Metrics: What the customer drawer shows, including the New badge.

  • Central Customer | Customer Insights in the POS: The Insights tab.

  • Central Customer | Discounts and Customer Groups: Org-wide Nth visit discounts and the returning-customer banner.

  • Central Customer | Org-Wide Event History: The cross-store audit log.

Did this answer your question?