ZenotiHelp

Configure Aveda loyalty provider

ZTZenoti Docs Team Updated September 5, 2026 7 min readHow-to

The Aveda Plus Rewards integration connects Zenoti to Aveda's external loyalty program. Once configured at a center, staff can look up Aveda members, verify points balances, enroll new members, and accept Aveda loyalty payments at the point of sale. Aveda Plus Rewards is operated by Aveda β€” Zenoti is a participating point-of-sale. This article covers the integration setup only; program rules and point-earning configuration are owned by Aveda and, for the Zenoti side, covered in the Loyalty category.


On this page


Scope and category boundaries

This article covers:

  • Enabling Aveda LP at the organization and center level in Zenoti.
  • Entering the center's Aveda Location ID and verifying the connection.
  • The Zenoti-side payment agents that are auto-created.

This article does not cover:

  • Program rules (points per dollar, tier thresholds, redemption value). These live in the Aveda Plus Rewards program itself, operated by Aveda. For Zenoti-side loyalty program configuration unrelated to Aveda, see the Loyalty category.
  • Member enrollment flows at the POS (Point of Sale) β€” see Loyalty provider integration (Aveda).
  • Aveda inventory/ordering β€” a separate integration covered under inventory supplier articles.

For loyalty program configuration and point rules, see the Loyalty category.


Before you begin

Permission: Organization administrator access is required to enable Aveda LP at the org level. Center administrator access is required to configure the integration at an individual center.

  • Your organization must be an authorised Aveda partner enrolled in the Aveda Plus Rewards program.
  • Your center must have a Location ID assigned by Aveda. This is how Aveda identifies the center within the Plus Rewards program.
  • A Zenoti super administrator has set the loyalty-program integration enablement bit for your organization (handled during initial onboarding by Zenoti). If the LP menu does not appear under Configuration > Integrations, open a Zenoti Support ticket to confirm enablement before proceeding.

External-system prerequisites

These are the responsibility of Aveda and the hotel/salon's Aveda account manager, not Zenoti:

  1. Aveda Plus Rewards program activation for your organization. The organization must be onboarded into Aveda's Plus Rewards program.
  2. Location ID assignment. Your Aveda account representative issues a numeric or alphanumeric Location ID per participating center. Each center has its own Location ID.
  3. Aveda member enrollment is live in your organization's Aveda account β€” that is, your business is authorised to enroll new guests into Aveda Plus Rewards. Ask your Aveda account rep if unsure.
  4. Aveda certificates programs (optional). If you plan to use Aveda-issued certificates (targeted offers, mass offers), these are configured in the Aveda portal by your Aveda account rep.

Global Aveda API credentials (API URL, API key, secret key) are stored Zenoti-side as shared infrastructure β€” you do not need to enter them per tenant. Each center only supplies its own Location ID.


Network requirements

Aveda's API is called from Zenoti to Aveda, not from your network. There is no inbound/outbound requirement on your center's network.

Direction Endpoint Port Purpose
Zenoti β†’ Aveda Plus Rewards API Aveda-hosted URL (managed by Zenoti infrastructure) 443 (HTTPS) Member lookup, enrollment, balance query, redemption, accrual

The Aveda API URL is managed in Zenoti's shared configuration. If Aveda changes their API endpoint, the change is deployed centrally β€” customers do not re-enter it.


Configure Aveda LP at the organization level

The Aveda connection lives on the LP accordion of the Integration settings page (the center page shows it as LP Integration). Its single Configuration panel differs by scope.

  1. Navigate to Configuration > Integrations > Integration settings and expand LP.
  2. In Configuration, enter the API Base URL, the API Auth Key, and the API Pass Code your Aveda account representative issued. All three are required.
  3. Select Test Connection. A success message confirms Zenoti can reach the Aveda service.
  4. Choose the Default Agent: the custom payment type that records Aveda redemptions at the POS. Create it first under Configuration > Payments > Custom payments if it does not exist.
  5. Set Active to Yes.
  6. Select Save.

If the accordion shows Aveda LP is not enabled at Organization level, the organization-level configuration has not been saved yet.


Configure Aveda LP at the center level

  1. Select the center in the center selector, then navigate to Configuration > Integrations > Integration Settings and expand LP Integration.
  2. In Configuration, set Active to Yes for this center.
  3. Enter the center's Location Id (for example 34222), the Aveda Plus Rewards identifier your Aveda account representative issued for this center. Each center has its own value; Zenoti cannot issue it.
  4. Select Verify to check the Location Id against Aveda, then Verify & Save.

If verification fails, do not activate the center. See Failure paths.


Verify the integration

After connecting:

  1. Open a non-production guest profile (or create one).
  2. Use the POS or the guest profile's loyalty section to look up Aveda membership by member ID or registered email.
  3. Confirm the lookup returns a response within a few seconds.
  4. For a fresh enrollment, create a test membership through Zenoti and confirm it appears under the center's Location ID in the Aveda portal (your Aveda account rep can check on their side).

Clean up the test guest and membership before going live.


Payment agents and package code created by Zenoti

When Aveda LP is active at a center, Zenoti creates two custom payment agents and one package for that center:

Name Type Purpose
AvedaLP Custom payment agent Records Aveda Plus Rewards point redemptions as a payment at the POS.
AvedaSSC Custom payment agent Records the redemption of an Aveda service certificate.
Aveda Enrollment Program Package (code AvedaEnrollment) The enrollment package that is added to the invoice when a guest enrols in Aveda Plus Rewards; it is attached to the center when the center is linked to Aveda.

Do not create the agents or the package manually. If they are missing after activation, save the center configuration again; if the Aveda Enrollment Program package is still absent from the center's package list, contact Zenoti Support.


How the two Active switches interact

Organization Active Center Active Result
No No Aveda lookups and payments are unavailable everywhere.
Yes No The connection is configured but this center does not use it.
Yes Yes Aveda is live at this center.
No Yes The center switch has no effect while the organization connection is inactive.

Whether the LP accordion appears at all is a provisioning decision made by Zenoti for your tenant.


Failure paths

Failure mode User-visible symptom Resolution
Location Id wrong or not recognised Verify reports an invalid Location Id. Confirm the Location ID with your Aveda account rep. Each center has its own value.
Aveda API unreachable from Zenoti Test Connection times out or returns network error. Retry after a few minutes. If persistent, open a Zenoti Support ticket β€” this is a Zenoti-side infrastructure issue, not a customer config issue.
Aveda program inactive Test Connection succeeds but Verify fails, or lookups return "inactive member" for every query. Your organization's Aveda Plus Rewards program may be suspended. Contact your Aveda account rep.
LP accordion shows Aveda LP is not enabled at Organization level at center scope The organization-level Configuration has not been saved with Active = Yes. Complete and save the organization configuration first.
Payment agents missing AvedaLP or AvedaSSC do not appear in POS payment lists after activation. Set the center Active switch to No and back to Yes, then save. If still missing, open a Zenoti Support ticket.
Stale credentials (global) All Aveda lookups fail across all customers simultaneously. This is a Zenoti-infrastructure incident β€” the shared Aveda API credentials have expired or rotated. Open a Zenoti Support ticket; no customer-side action available.
Points sync failure mid-transaction Invoice closed but points not credited in Aveda. See Reconciliation. Zenoti's accrual job retries; if persistent, the Aveda account rep can manually credit.

Reconciliation

Reconcile Aveda points on a weekly or monthly cadence (depending on transaction volume).

Item Zenoti side Aveda side Match key
Accruals (points earned) Aveda accrual report or the organization's accrual audit view Aveda Plus Rewards admin portal β€” member transaction history Membership ID + invoice date/amount
Redemptions POS payment report filtered by the AvedaLP payment agent Aveda Plus Rewards admin portal β€” redemption history Membership ID + redemption timestamp
Enrollments Invoice report filtered by the Aveda Enrollment Program package Aveda Plus Rewards admin portal β€” new member list Membership ID + enrollment date
Certificate redemptions Invoice report filtered by the AvedaSSC payment agent Aveda Plus Rewards admin portal β€” certificate redemption list Certificate ID

Recommended cadence: weekly for centers with >100 Aveda transactions/week, monthly otherwise. If the Aveda report name differs in your portal, ask your Aveda account rep for the equivalent view β€” Aveda portal menus vary by deployment.


What to configure next

Required:

Recommended:


Tips

  • Configure one center end-to-end and verify reconciliation before rolling out to additional centers.
  • Never enter a placeholder or dummy Location ID β€” a wrong Location ID causes accruals to credit the wrong center's totals on the Aveda side.
  • Rotate ownership of the Aveda relationship to a current staff member β€” the Aveda account rep is your main point of contact when things break.

Was this article helpful?
Your feedback helps us improve our documentation.