Most discounts are evaluated against the cart — the products in it, their quantity, the time of day. A smaller set is evaluated against the customer: whether this is their first visit, their second, and so on. Historically those rules could only ever see one store's record, so a customer who claimed a first-time discount at one location could claim it again at every other location in the organization.

With central customer enabled, Treez evaluates these discounts against the organization's view of the customer rather than a single store's. A customer is a first-time customer once.

This first iteration covers Nth visit discounts only, and it operates in two places: automatically, when the cart is priced, and advisory, through a banner that appears wherever a discount is applied manually. Other customer-event discount types are a natural extension of the same foundation and may be centralized in future releases.

The same principle extends to who a customer is, not just how often they've visited. Customer group designations — veteran, senior, compassion, and the like — are shared organization-wide, so the discounts tied to them follow the customer from store to store.

Nth visit discount rules — first visit, second visit, third visit, and so on — are applied automatically during cart pricing. When central customer is enabled, the visit number Treez evaluates is the customer's visit number across the entire organization rather than at the current store.

Visit history is combined across all stores. A customer's visit number reflects every completed purchase at every location, so a first-visit discount is only ever available on their genuine first purchase within the organization.

Nothing changes about how discounts are configured. Discounts are created and maintained exactly as they are today. Only the visit count they're measured against changes.

Example. A customer makes their first purchase at Store A and receives the first-visit discount. When they later shop at Store B, Treez recognizes them as being on their second organization-wide visit, so the first-visit discount doesn't apply — but a second-visit discount, if configured, would.

This behavior is absolute while central customer is enabled. Nth visit discounts are evaluated organization-wide at every location, and there is currently no option to configure a location to grant first-time discounts based on its own visit history alone.

If organization-wide visit data is temporarily unavailable, pricing falls back to the store's own visit count so the cart is never blocked. Once the customer's central profile loads, the cart re-prices automatically so the correct discount is applied before checkout.

Only Nth visit discounts are centralized today. Other customer-based discount triggers continue to evaluate against store-level data. The framework is built to accommodate additional customer event types over time.

Automatic pricing handles Nth visit rules on its own, but discounts applied by hand are still a user's decision. To prevent a new-customer discount from being manually granted to someone who has already shopped elsewhere in the organization, Treez surfaces an advisory banner at the point of application — in both the manual discount modal and the loyalty wallet.

The banner appears only for returning customers. If the customer is genuinely on their first organization-wide visit, nothing is shown.

It states the customer's history plainly, including how many prior visits they have and how many of those occurred at other stores.

It is advisory, not a restriction. The banner informs the decision; it never blocks a discount. Users retain full control over manual discounts and any override their store's policy permits.

It reflects the same data as automatic pricing, so what a user sees in the banner matches the visit count Treez used when evaluating automatic discounts on the cart.

Customer groups — veteran, senior, compassion, employee, and any other designation a store maintains — are shared organization-wide. A designation applied at one store travels with the customer's central profile, so it's recognized at every location they visit rather than having to be re-applied each time.

Group membership syncs automatically. When a store assigns a customer to a group, that membership flows up to the central profile along with the rest of their data, and becomes part of the organization's view of that customer.

Memberships combine across stores. Central maintains the full set of groups a customer belongs to anywhere in the organization, rather than one store's version of the list.

Associated discounts apply automatically in the POS. When a customer is recognized as a member of a group, any discount that store has configured for that group is applied during cart pricing, exactly as it would be for a locally assigned group. Users don't need to re-apply the designation or add the discount by hand.

Each store's discount configuration still governs the value. Groups are shared; the discount attached to a group is configured by each store. A customer designated as a veteran at one store receives whichever veteran discount the store they're currently visiting has set up — and if that store doesn't offer one, no discount is applied.

Designations are durable. Because membership is contributed by the stores that assigned it, a customer keeps a designation as long as any store still asserts it.