ZenotiHelp

Bulk operations

ZTZenoti Docs Team Updated September 23, 2026 2 min readGuide

Zenoti supports bulk creation and update of products, barcodes, center associations, and vendor associations through the bulk operations feature. This is designed for system integrations and large-scale catalog management.

Audience: System integrators and administrators managing large product catalogs.

Before you begin

Permission: Add (under Products) — Required for bulk product creation.

Permission: Edit (under Products) — Required for bulk product updates.

  • Products, centers, and vendors referenced in bulk operations must exist in Zenoti, unless using force-create mode for products.
  • Products in pending purchase orders cannot have their vendor associations modified through bulk operations.

Supported bulk operations

Zenoti supports five types of bulk operations for products:

Operation What it does
Bulk product create/update Creates new products or updates existing ones in batch.
Bulk barcode management Adds or updates barcodes for multiple products at once.
Bulk center associations Creates or updates center associations for multiple products at once.
Bulk vendor associations Creates or updates vendor-product associations for multiple products at once.
Brands Creates or updates product brands in bulk. Brands must exist before a product import can reference them, so run this first when you are setting up a new catalog.

How bulk operations work

Bulk product create/update

Bulk product operations process a batch of product records with comprehensive validation. The system validates each record before processing.

Key options:

  • Force create — When enabled, products that don't exist in Zenoti are automatically created. When disabled, non-existent products return an error.
  • Partial update — When enabled, only the fields you provide are updated. Fields not included in the request retain their current values. When disabled, a full update is performed.

The system returns per-record results showing which records succeeded and which failed, along with the reason for any failures.

Bulk barcode management

Submit a batch of barcode records containing product identifiers and barcode values. The system validates barcode uniqueness and product existence, then processes valid records.

Bulk center associations

Submit a batch of center association records containing product codes, center codes, sale prices, and tax groups. The system validates center codes, tax groups, and zone permissions before processing.

Bulk vendor associations

Submit a batch of vendor association records. The system validates vendor codes, tax groups, and pending purchase order constraints before processing.

Note: Products in pending purchase orders will be rejected in bulk vendor association updates. Fulfill or cancel pending purchase orders for those products before submitting bulk vendor changes.

Validation

Bulk operations include extensive pre-processing validation. Common validation checks include:

  • Product code uniqueness and existence
  • Category, subcategory, brand, and business unit validity
  • Color and size assignments (when variants are enabled)
  • Tag validity against organization tags
  • Center code existence and zone permissions
  • Tax group validity
  • Vendor code existence and permissions
  • Duplicate detection within the batch

When a record fails validation, it is skipped and the error details are returned in the response. Valid records in the same batch continue to be processed.

Tips

  • Use partial update mode when you only want to change specific fields on existing products — this prevents accidental data loss on fields you don't intend to modify.
  • Test with a small batch first to verify your data format and validate that the expected records process successfully.
  • Review the per-record results after each bulk operation to identify and correct any failed records.
Was this article helpful?
Your feedback helps us improve our documentation.