Vendor catalog sync and ordering operations
Audience: Inventory manager, center admin β typically the person who runs catalog syncs, browses the vendor marketplace, and tracks order status from day to day.
After your organization configures an inventory-system vendor (Aveda V1, Aveda V2, NeillCorp, or SuperCenter β see Configure vendor catalog integration), this article covers the day-to-day operations: running catalog syncs, reviewing sync history, browsing the Product Marketplace, managing favorites, placing catalog orders, and tracking their status.
Article scope. This article owns the operational scope: sync, sync history, browse, favorites, submit, status tracking, troubleshooting. The narrow submit-an-order procedure also lives in Place vendor catalog orders for users who only need that step. For initial vendor configuration (OAuth authorization, credential entry, per-vendor setup), see Configure vendor catalog integration.
On this page
- Before you begin
- Sync a vendor catalog
- Review sync history
- Browse and order from the Product Marketplace
- Manage favorites
- Track vendor catalog order status
- Behavior and limitations
- Troubleshooting
- Tips
- Related articles
Before you begin
Your organization must have at least one vendor integration configured before this article applies. Confirm the configuration before troubleshooting sync errors.
The Marketplace row must be available under Inventory for your organization. If it is not visible, contact your administrator.
You need the following permissions:
Permission: View (under Marketplace) β Required to access the Product Marketplace and browse vendor catalogs.
Permission: Add (under Products) β Required to create products from a vendor catalog.
Permission: Add (under Inventory) β Required to place vendor catalog orders.
Confirm with your administrator which vendors are configured at your center. Each center can have a different set of configured vendors.
Sync a vendor catalog
Catalog sync retrieves the vendor's current product list, creates any missing brands and categories in Zenoti, matches incoming products against your existing catalog, and records the run on the sync history page.
How each vendor's sync pipeline matches products differs by integration:
- SuperCenter β de-duplicates incoming feed rows on the vendor Stock Keeping Unit (SKU), then matches or creates Zenoti products on product code (mapped from the vendor SKU). Barcodes are taken from the Universal Product Code (UPC) or the SKU value supplied in the feed.
- Aveda β matches incoming products against existing Zenoti products by barcode, comparing the Aveda Universal Product Code (UPC) against the product barcode list already stored in Zenoti.
Important: The Product Marketplace and the Aveda V2 cart-based ordering flow are distinct features. This sync procedure applies to all configured vendors. The Aveda V2 cart redirect is covered separately in Browse and order from the Product Marketplace.
Go to Inventory > Marketplace.
Find the configured vendor whose catalog you want to sync.
Select Sync catalog for that vendor.
Note: The Marketplace page also surfaces a Configure action for vendor integration settings. If sync schedules have been configured for your organization by Zenoti, the page acknowledges this: "If Sync Schedules have been setup, there is NO need for manual sync to be performed." In that case, skip steps 3β5 and proceed to Review sync history to confirm recent runs.
The system queues the sync and reports progress. Wait for completion before moving on; closing the page does not cancel the sync, but you cannot review the result until the run finishes.
When the sync completes, review the result. The page reports three counts and links to any error log produced during the run. The counts mean:
- Processed β total products considered in the sync run (every product the vendor returned in the catalog feed).
- Matched β products in the vendor feed that were matched against existing Zenoti product records (by barcode, vendor SKU, or name). Matched products may be updated in place β see Behavior and limitations.
- Unmatched β products in the vendor feed with no corresponding Zenoti record. These are typically created as new products in Zenoti, but the exact behavior is vendor- and configuration-dependent. Review unmatched entries in the sync history detail view to confirm what action was taken.
For the cadence, multi-center, and overwrite policies that govern this sync, see Behavior and limitations below.
Review sync history
The sync history page shows past sync runs and their match and unmatch results, so you can audit what changed and investigate errors.
Go to Inventory > Marketplace.
Select the vendor whose sync history you want to review.
Open the sync history page for that vendor. Each entry in the list shows:
- The date and time the sync run ended.
- The processing status of the run (for example, completed or failed).
- The count of products processed during the run.
- The count of products matched to existing Zenoti records.
- The count of products that did not match any existing record.
- Links to source, error, and log files where available.
Select any run to open its detail view. Review the matched and unmatched product lists to confirm the sync produced the expected result.
Note: The sync history page shows the outcome of each run. It does not allow you to re-run or roll back a sync from within the history view. To run a new sync, return to the main Marketplace page and use the Sync catalog action.
Browse and order from the Product Marketplace
After a successful sync, the synced products appear in the Product Marketplace. Authorized users can browse, filter, and order from here.
Note: The Product Marketplace is a distinct feature from the Aveda V2 cart-based ordering flow. Both are accessed from Inventory > Marketplace, but the Aveda V2 flow redirects to Aveda's portal to complete checkout. See the Aveda V2 note at the end of this section.
Go to Inventory > Marketplace.
Use the search and filter controls to find products. You can search by product name or barcode and filter by brand, category, sub-category, or vendor.
Mark frequently ordered products as favorites by selecting the star icon β see Manage favorites.
Add products to your cart:
- Select Add to cart next to each product.
- Specify quantities as needed.
- Review cart contents in the cart sidebar.
Submit your order:
- Select Checkout to review your cart.
- Confirm order details and delivery information.
- Select Submit order to send the order to the vendor.
After submission, the order appears in Inventory > Orders with the vendor catalog indicated as the source. A purchase order (PO) is created and linked to the vendor catalog order.
Note for Aveda V2. Aveda V2 uses a cart-based redirect β submitting an order opens Aveda's portal in a new window where you review the cart, add taxes, discounts, and promotions, and complete checkout. Allow pop-ups for the Aveda domain. Closing the Aveda window before checkout completes leaves the cart in Aveda's system and the order is not transmitted to Zenoti. After Aveda checkout completes successfully, Aveda returns the order to Zenoti and it appears in Inventory > Orders with status Pending (awaiting vendor confirmation, then Confirmed typically within 24 hours).
Worked example. A center manager at a spa browses the Aveda V1 catalog in the Product Marketplace after a Monday morning sync. She searches for "Damage Remedy" and finds three matching products. She marks two as favorites, adds 6 units of the shampoo and 4 units of the conditioner to her cart, then selects Checkout. She confirms the receiving center address and selects Submit order. The order appears in Inventory > Orders within seconds with status Pending. By Tuesday afternoon the status has moved to Confirmed and she can see the expected delivery date.
Manage favorites
Favorites give a center quick access to products it orders frequently. Mark and review favorites while you browse β they live in the same Marketplace view, not in a separate part of the app.
From Inventory > Marketplace, browse the vendor catalog and select the star icon next to any product to mark it as a favorite. The product is added to the center's favorites list immediately.
Open the Favorites tab to see the list. Selecting Add to cart from the favorites list works the same way as from the main catalog.
To remove a favorite, select the filled star icon β either in the favorites list or in the main catalog view.
Favorites scope. Favorites are recorded against the center placing the orders, not against the user. Two front-desk staff at the same center share the same favorites list β they see and can edit the same set. Different centers maintain their own independent favorites β a useful pattern when centers stock different product lines from the same vendor.
Track vendor catalog order status
Vendor catalog orders sync their status back to Zenoti so you can track them without leaving the system. Zenoti polls each order until it reaches a completed status, so the status you see reflects the most recent update the vendor has returned.
Go to Inventory > Orders.
Filter by order type to find catalog-originated orders.
Review the status:
Status What it means Pending Order submitted, awaiting vendor confirmation. Confirmed Vendor has accepted the order. Shipped Order is in transit. Delivered Order has been received. Cancelled Order was cancelled by the vendor or by Zenoti. Open any order to view the full status history and any tracking updates the vendor returned.
For full historical reporting on catalog-originated orders and their costs, see the Inventory orders report and the Cost of goods report.
Modify or cancel a submitted order. Modifications and cancellations are governed by the Edit permission under Inventory plus the order's current status β once an order has moved past Pending, the vendor's acceptance terms apply. For order edits and cancellations end-to-end, see Manage Procurement.
Behavior and limitations
Sync cadence. Catalog sync is run on demand using the steps in Sync a vendor catalog. If recurring sync schedules have been set up by Zenoti for your organization, there is no need to run manual syncs β the scheduled jobs handle catalog refresh automatically. Zenoti can configure recurring sync schedules on your behalf; contact Zenoti Support if you need a recurring schedule established.
Multi-center model. Vendor catalog sync orchestrates at the organization level. The catalog-sync operation joins incoming catalog items to every active center in the organization in a single pass, creating the vendor-product associations for all centers at once. If you need a per-center catalog refresh, run sync at the org level and confirm with the centers that the expected products appear.
Overwrite behavior. Catalog sync is create-or-update, not create-only. When sync matches an incoming product to an existing Zenoti product, the vendor feed data updates the matched product's attributes β including name, description, category, product code, unit of measure, retail and consumable classification, commission settings, and MSRP (or your configured retail price label) where the feed supplies a value. Brand is preserved when the feed value is empty. Run a test sync against a small product set first if you have established product attributes that must not be changed β the test shows exactly which fields your vendor configuration overwrites.
Cart persistence. The cart in the Product Marketplace is per-session: closing the browser tab without submitting clears the cart. There is no save-for-later or cross-device cart persistence in the current release.
Tax and shipping handling. Aveda V2 returns the final tax and shipping totals from Aveda's portal after checkout completes; these flow back to the Zenoti purchase order automatically. For non-Aveda-V2 vendors, taxes and shipping are typically returned in the vendor's order confirmation and reflected on the Zenoti PO when status moves to Confirmed. Specific behavior varies by vendor β reconcile one vendor invoice against its Zenoti purchase order to establish the pattern for that vendor before relying on it.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| Sync starts but never finishes | A long-running operation against the vendor's API, or a vendor-side outage | Wait at least 30 minutes before retrying. Check vendor status pages or contact the vendor's support channel if delays persist across multiple attempts. |
| Sync completes with many unmatched products | Vendor product codes do not match Zenoti's product codes or barcodes | Open sync history and review unmatched products. Decide whether to add the unmatched products as new Zenoti products or reconcile the codes manually. |
| Sync completes but no new products are visible in Product Marketplace | The Product Marketplace organization setting may be disabled, or matching dropped all incoming products as duplicates | Confirm the organization's marketplace setting is enabled. Open sync history to review match counts. |
| Products visible in Marketplace but cannot be added to cart | Permission gap β adding from Marketplace requires both View on Marketplace and Add on Products | Confirm both permissions; users with one but not the other can browse but cannot add. |
| Order submitted but never moves out of Pending | Vendor acknowledgement not received, or vendor portal session not completed (Aveda V2) | For Aveda V2, confirm the user completed checkout in Aveda's portal. For other vendors, contact the vendor to confirm receipt. |
| Order shows Cancelled but the user did not cancel | Vendor cancelled the order (out of stock, account issue, etc.) | Open the order to read the cancellation reason if the vendor returned one. Contact the vendor if no reason is shown. |
| Sync errors reference vendor-specific codes | Vendor-side validation failure on individual products | Open the error file linked from sync history; the vendor's reason text usually indicates the affected products and the validation rule. |
Tips
- Run a small test sync after any vendor configuration change. Catching configuration drift on a 10-product test sync is faster than discovering it on a full catalog refresh.
- Review sync history weekly even when no problems are reported. Trends in unmatched-product counts often reveal a vendor-side product-code change before users complain.
- Keep favorites lists current β periodically review and prune favorites that the center no longer orders.
- For Aveda V2, document the staff member responsible for completing cart-redirect orders. The redirect requires the same logged-in browser session that started the order; transferring an in-flight cart between staff members is not supported.