Configure vendor catalog integration
Audience: Administrator, inventory manager β typically the person who configures vendor relationships during onboarding or when adding a new inventory-system vendor.
The inventory vendor catalog integration connects Zenoti to four inventory-system vendors so that authorized users can browse vendor product catalogs, sync product data, and place orders without leaving Zenoti. This article covers initial configuration. For ongoing operations and sync history, see Vendor integrations and product catalog sync.
Important: This article covers Aveda (V1 and V2), NeillCorp, and SuperCenter β the four inventory-system vendors currently supported by Zenoti.
On this page
- Before you begin
- Supported inventory-system vendors
- How catalog sync works
- Configure a vendor integration
- Test the connection
- Disconnect a vendor
- Troubleshooting
- Tips
- Related articles
Before you begin
- You need permission to configure vendor integrations on the Inventory security object. Specifically, you need the Edit action on Inventory to save the configuration. If you cannot access the Vendor integrations page, contact your administrator.
- Vendor integration settings can be configured at the organization level; center-level settings inherit from the organization defaults.
- You need vendor-system credentials before starting. Each vendor provides credentials differently β see the per-vendor sections below for what to obtain.
- For Aveda, you also need the center's Aveda Salon ID, which is entered and verified on the Integrations tab of the center settings.
- Pop-ups for vendor portal domains must be allowed in your browser when an authorization step opens a new window.
A note on credential acquisition. For NeillCorp and SuperCenter, the acquisition path for credentials differs by vendor. Obtain the credentials from the vendor itself β their partner portal or account representative is the issuing source β before starting the configuration. For Aveda, the Salon ID acquisition path is documented in the Aveda sections below.
Supported inventory-system vendors
Zenoti supports four inventory-system vendors. The differences below are deliberately limited to what affects how you configure each vendor; ordering features and sync depth are documented in Vendor integrations and product catalog sync.
| Vendor | Authorization style | Catalog sync | What you need before configuring |
|---|---|---|---|
| Aveda V1 | OAuth 2.0 with two-tier authentication (admin token, then salon-impersonated token) | Yes | Aveda Salon ID (shown as SAP/SALON ID on the center mapping); Aveda account that authorizes Zenoti |
| Aveda V2 | OAuth 2.0 with cart-based redirect | Yes | Aveda Salon ID (shown as SAP/SALON ID on the center mapping); Aveda account that authorizes Zenoti |
| NeillCorp | Vendor-provided credentials | Yes | NeillCorp username and password; service endpoint reference |
| SuperCenter | API credentials | Yes (file-feed) | SuperCenter customer credentials; access to the file-feed delivery channel |
Why are there two Aveda options? Aveda's ordering platform has two implementation styles. V1 submits orders directly via the Zenoti-side setting Enable Aveda Empowered ordering integration of purchase orders (at Integrations > Inventory > Configuration). V2 redirects users to Aveda's portal to complete the cart and check out β Aveda refers to this portal experience as "Empowered Ordering." The system automatically routes to V1 or V2 based on your organization's configuration; you do not select between them at order time.
How catalog sync works
Understanding the model helps you pick the right configuration. Catalog sync runs after the vendor integration is authorized and saved.
- The system retrieves the product catalog from the vendor.
- The system creates any missing brands and categories in Zenoti.
- The system matches incoming products against your existing Zenoti catalog. The match key (barcode, vendor SKU, name, or a combination) is implementation-specific and varies by vendor; collision handling is set during sync.
- New products from the vendor catalog appear in the Product Marketplace surface, where authorized users can review and add them to inventory.
- The system records the sync run on the sync history page so you can review past runs, matched and unmatched products, and any errors.
Sync cadence. Treat catalog sync as on demand β you trigger it from the Catalog sync section after configuration.
Overwrite behavior for matched products. Catalog sync is create-or-update: items matched to existing products have their name, description, category, product code, unit of measure, retail/consumable flags, commission settings, and MSRP (or your configured retail price label) updated from the vendor feed (the retail price is updated only when the feed supplies a value; the brand is kept when the feed's value is empty). Run a test sync against a small product set first so you see these updates before applying them broadly.
What these integrations do, and where they stop. A vendor catalog integration keeps product information flowing between the vendor and Zenoti. It does not record deliveries. Whatever the integration does for you, the quantities that arrive are entered in Zenoti by a person β see Receive deliveries.
Configure a vendor integration
The general flow is the same for every vendor; vendor-specific details follow this section.
Go to Inventory > Marketplace.
Select the vendor you want to configure.
Enter the credentials and configuration values for that vendor β see the per-vendor sections below.
For OAuth-based providers (Aveda V1, Aveda V2): the system opens an authorization window. Sign in with the vendor account associated with your salon, review the permission request, and approve. The system stores the access and refresh tokens securely.
Select Save to store the integration settings.
Select Test connection to verify connectivity (see Test the connection).
Aveda V1
For Aveda V1 integration:
Enter your Aveda Salon ID for the center being configured. On the center mapping, this column is labeled SAP/SALON ID β the SAP ID and the Salon ID are the same identifier. It is a 6-digit number: sign in to the Aveda Empowered Ordering portal and find it in the Account Information section. The Salon ID is entered and verified on the Integrations tab of the center settings.
Email format for Aveda sign-in. When prompted to sign in to the Aveda portal, add a pipe symbol followed by
Avedato your email address. For example, if your email address isjohn@abc.com, enterjohn@abc.com|Avedain the email field.Authorize Zenoti through Aveda's portal. The system performs a two-tier authentication: it first acquires an admin token, then a salon-impersonated token scoped to act on behalf of your salon for ordering, product reading, and shopper actions.
The system confirms the Salon ID with Aveda. The ID must be verified before any purchase order can be submitted to Aveda. If verification fails, see Troubleshooting.
In the organization-level inventory vendor integration settings, enable the following as applicable:
- Enable Aveda Empowered ordering integration of purchase orders β enables the Aveda purchase order (PO) ordering integration.
- Enable Excel export of Purchase Orders in Aveda format β enables export of raised purchase orders in the Aveda-compatible Excel format.
One-way sync. Taxes and discounts applied in Zenoti are not applicable on the Aveda portal. Changes made on the Aveda portal after an order is submitted are not reflected back in Zenoti. If changes are needed after a purchase order is sent to Aveda, you can search for the order in Zenoti using the Aveda Order Number.
Session expiry. If you do not send an order to Aveda for 30 days, you must re-authenticate by repeating the authorization flow.
Note on Aveda product code prefixes. Aveda recognises two special prefixes on product codes β
Tfor tester products andBBfor back-bar products. Zenoti removes the prefix before it validates the product code with Aveda. These prefixes flow through to the orders Aveda receives; they are documented here for awareness, not as a configuration step.
Aveda V2
For Aveda V2 integration:
Enter your Aveda Salon ID for the center being configured. On the center mapping, this column is labeled SAP/SALON ID β the SAP ID and the Salon ID are the same identifier. It is a 6-digit number: sign in to the Aveda Empowered Ordering portal and find it in the Account Information section. The Salon ID is entered and verified on the Integrations tab of the center settings.
Authorize Zenoti through Aveda's portal. Aveda V2 uses a cart-based redirect flow β when a user places an order, the system redirects them to Aveda's portal to add taxes, discounts, and promotions, then complete checkout. Authorization at configuration time grants Zenoti permission to start that redirect for your salon. Authorization applies to the center you are signed in to, so switch to the correct center before you start.
The system confirms the Salon ID with Aveda. The ID must be verified before any purchase order can be submitted to Aveda.
(Optional) In the organization-level inventory vendor integration settings, enable Enable Excel export of Purchase Orders in Aveda format if needed.
What users see at order time. With Aveda V2, ordering opens an Aveda portal window. If pop-ups are blocked, the redirect fails. Authorized users should keep the Aveda window open until checkout completes; closing it mid-flow leaves the cart in Aveda's system and the order is not transmitted to Zenoti.
NeillCorp
For NeillCorp integration:
Enter the NeillCorp username and password provided by your NeillCorp account representative.
Confirm the service endpoint reference if your tenant requires it. NeillCorp uses a SOAP (Simple Object Access Protocol) interface; the service URL is configured during onboarding.
Save and run Test connection.
NeillCorp does not use OAuth, so there is no portal authorization step. Credential rotation requires a manual update β coordinate with your NeillCorp account representative when credentials change.
SuperCenter
For SuperCenter integration:
Enter your SuperCenter customer credentials.
Confirm the file-feed delivery channel reference. SuperCenter delivers its catalog via a file feed (rather than a live API); the feed includes columns for the SuperCenter Stock Keeping Unit (SKU), UPC, and the customer's product master SKU.
Save and run Test connection. For SuperCenter, Test connection confirms that the credentials accept the file-feed delivery channel.
Test the connection
After saving any vendor configuration, run Test connection.
Select Test connection on the configured vendor's row.
Zenoti calls the vendor system to confirm both connectivity and authentication together. A successful test indicates the credentials are accepted and the vendor system recognizes your salon mapping. The test reports success or failure on the round trip.
If the test fails, the error message indicates whether the failure is in connectivity (the vendor system unreachable) or authentication (credentials rejected, salon not found, token expired). See Troubleshooting.
Example: first-time Aveda V2 configuration. A center admin at the Downtown Day Spa configures Aveda V2. They sign in to the Aveda Empowered Ordering portal, copy the 6-digit SAP ID from the Account Information section, enter it as the Salon ID on the Integrations tab of the center settings, authorize through Aveda's portal with the salon's Aveda login, and run Test connection. The system confirms the Salon ID with Aveda and Test connection returns a success indicator. The center is now ready to place orders through Aveda V2; orders open Aveda's portal in a new window for cart review and checkout.
Disconnect a vendor
To remove a configured vendor or rotate credentials, contact Zenoti Support. Removing a vendor configuration may affect existing imported products and any open purchase orders that reference the vendor, so raise the request before you rely on the change being reversible.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| Send to Aveda is missing or greyed out on a purchase order | The button appears only on a Raised or Updated purchase order whose vendor is the organization's configured Aveda vendor, and only when Enable Aveda Empowered ordering integration of purchase orders is on β otherwise it is not shown at all. When it is shown but greyed out, either the center's Aveda Salon ID has not been entered and verified on the Integrations tab of the center settings (or, for Aveda V2, the center has not been authorized), or the order has already been sent to Aveda's cart. | Confirm the order's status is Raised or Updated and that its vendor is your configured Aveda vendor, then confirm Enable Aveda Empowered ordering integration of purchase orders is on. If the button is shown but greyed out, hover over it β the hover text states the reason. When the Salon ID is missing or unverified, a Configure Aveda Integration link appears; follow it to the Integrations tab of the center settings to enter and verify the ID (for Aveda V2, authorize the center). When the hover text states the order has already been sent to Aveda's cart, complete or discard the existing cart in Aveda's portal. The vendor's email address has no effect on this button: emailing a purchase order to a vendor and sending it through the Aveda integration are separate paths, and changing the vendor email neither causes nor fixes an Aveda submission problem. |
| Authorization window does not open (Aveda V1, Aveda V2) | Browser blocked the pop-up | Allow pop-ups for the vendor's domain and retry. |
| OAuth redirect returns to Zenoti but no token is saved | The browser blocked the redirect, or the user closed the vendor tab before approval | Restart the OAuth flow. Do not close the vendor tab until you are redirected back to Zenoti. |
| Test connection returns "Salon ID not found" or "salon not authorised" (Aveda) | The Aveda account that authorized does not match the Salon ID entered | Re-run the OAuth flow with the Aveda login that owns the configured Salon ID. Re-check the 6-digit ID against the Account Information section of the Aveda Empowered Ordering portal if the mismatch persists. |
| Test connection returns "credentials rejected" (NeillCorp, SuperCenter) | Username, password, or endpoint reference is wrong | Re-confirm credentials with the vendor account representative. Re-enter and save. |
| Sync runs but no products appear | Catalog returned successfully but matching produced zero new products, or all incoming products matched existing records | Open the sync history page and check the matched/unmatched counts and any per-row errors. |
| Test connection succeeds but orders fail | Account-level ordering scopes may be insufficient at the vendor | Contact the vendor's support channel; the account may require additional ordering permissions. |
| Repeated token-expired errors after working briefly | The vendor account password was reset, or the connected app was revoked at the vendor portal | Re-run the OAuth flow; coordinate with the vendor if the issue persists. |
If you need additional support, capture the full error message text and contact Zenoti Support β vendor-side messages carry context this article cannot document fully.
Tips
- Configure one vendor at a time. Saving multiple integrations in one session makes it harder to isolate a failure if Test connection reports an error.
- Use a dedicated integration login at each vendor where possible. A staff member's personal login works initially but disconnects when that staff member leaves.
- Document the vendor login and Salon ID used for each center so future re-authorization uses the same account and identifier.
- Run a test sync against a small product set and review matched and unmatched counts before relying on catalog sync to update established catalog attributes.
- The Product Marketplace surface (where synced products appear for review and inventory addition) is governed by the organization's marketplace setting. If users cannot see synced products for review, confirm the setting is enabled.
Changes applied to the published article, and one item I could not act on:
- Added the required troubleshooting row for "Send to Aveda is missing or greyed out on a purchase order," covering all six points the requirement specifies: the Raised/Updated status gate, the Aveda-vendor match, the Enable Aveda Empowered ordering integration of purchase orders gate, the unverified-Salon-ID / unauthorized-center cause with its hover text and Configure Aveda Integration link, the already-sent-to-cart cause, and the explicit statement that the vendor email address has no bearing on the button.
- Opened up the SAP ID. The functional requirement now records SAP ID and Salon ID as the same field, the mapping column as SAP/SALON ID, and the acquisition path as the 6-digit number in the Account Information section of the Aveda Empowered Ordering portal. I applied that to both Aveda sections, the vendor comparison table, the worked example, and the Salon-ID troubleshooting row, replacing the previous "contact your Aveda account representative" instruction. Note this supersedes the older topic rule that banned "SAP ID" pending verification β that rule was conditioned on verification, which the requirement states is complete.
- Removed the "Geographic availability" callout. It claimed Aveda ordering availability varies by region; the code constraints list Aveda geographic/state-level gating as a feature that does not exist and must never be mentioned.
- Named the Integrations tab of the center settings as where the Salon ID is entered and verified, in Before you begin and both Aveda sections.
- Fixed parity between the two Aveda sections: Aveda V2's Excel-export option now uses the same label as V1 ("Enable Excel export of Purchase Orders in Aveda format"), and both now state that the setting lives in the organization-level integration settings.
- Clarified Aveda V2 center scope β authorization applies to the center you are signed in to β replacing the vaguer "center admin's account context" phrasing.
- Minor required fixes: expanded MSRP on first use as "MSRP (or your configured retail price label)"; scoped the credential-acquisition note to NeillCorp and SuperCenter now that Aveda's path is documented; added that the Aveda prefix is stripped before the code is validated; added that Test connection checks connectivity and authentication together and reports success or failure on the round trip.
Not acted on: one requirement in the list is truncated mid-sentence β "[PMVD-INV-011b] setup/configure-vendor-catalog-integration.md SHALL state the" β with no predicate. I left it alone rather than guess at what it requires. Send me the full text and I'll fold it in.