ZenotiHelp

Import and export inventory data

ZTZenoti Docs Team Updated November 3, 2026 13 min readGuide

Audience: Inventory administrators who need to bulk-load or extract inventory data β€” typically used for initial setup, periodic reconciliation against external systems, or annual stock counts via spreadsheet.

Zenoti supports bulk import and export of inventory data β€” products, vendors, purchase orders (PO, after first use), audit counts, and inventory reports. This article covers each entity's import and export procedures, the navigation per entity, file format requirements, and validation behavior.


On this page


Before you begin

  • You need the appropriate import or export permission for each data type β€” see Permissions reference below.
  • Prepare your import files using the Zenoti template that ships with each entity. Templates ensure correct column mapping and validation.
  • File format requirements differ by entity type β€” the current Import/Export surface accepts .csv and .xlsx files for products and vendors. Purchase order (PO) imports accept .xls and .xlsx only (not CSV). Audit imports accept .xls, .xlsx, and CSV.
  • The four import categories live in different parts of the admin UI; there is no single import hub. Note the navigation in each section below.

Permissions reference

Permission Security object Allows
ImportProduct (rendered with its seeded name) Import/Export Bulk import products
ExportProduct (rendered with its seeded name) Import/Export Bulk export products
ImportVendor (rendered with its seeded name) Import/Export Bulk import vendors
ExportVendor (rendered with its seeded name) Import/Export Bulk export vendors
Add Inventory Bulk import purchase orders and audit data (governed by the same Inventory create permissions as the corresponding interactive workflows)
Approve Reconcile Inventory Submit audits after import and approve reconciliation
Export Export_Inventory (rendered with its raw name) Generic inventory exports surfaced via report grids

Imports

Import products

Bulk-create or update products from an Excel or CSV file.

  1. At the center level, go to Configuration > Business details > Business setup > Import bulk data and choose the products import type.
  2. Download the import template.
  3. Fill in product data: name, code, category, subcategory, MSRP (or your configured retail price label), sale price, purchase price, UoM (Unit of Measure), barcode, and product type.
  4. Upload the completed file.
  5. Zenoti validates the file and displays a preview with a summary of Total, Valid, and Failed row counts, plus two outcome categories:
    • Errors β€” prevent the row from being imported (for example, duplicate product code, invalid category). Error rows are excluded from the import.
    • Warnings β€” the row is imported, but a flag is recorded in the import log for review (for example, missing optional barcode).
  6. Review the preview and, if needed, fix the source file and re-upload.
  7. Select Import to process the valid rows. To validate without committing, use the Validate action β€” this runs all checks and reports errors without creating or updating any records.

After a successful import, the results screen displays three counts:

  • Imported rows β€” total rows processed without error.
  • Updated rows β€” existing product records modified by the import.
  • Inserted rows β€” new product records created by the import.

Note: If a product code in the file matches an existing product, the row is treated as an update; otherwise it is treated as a create. To avoid accidental updates, ensure your import file's product codes are unique to your new products.

Worked example β€” product import

You are onboarding 50 new retail shampoo products from a new brand. You download the template, paste your product list, set the Product type column to Retail for all rows, and enter the sale price and MSRP (or your configured retail price label) for each. After upload, the preview shows 48 rows as valid and 2 rows with errors (duplicate product codes from a previous import). You correct the two codes in the source file, re-upload, and select Import. Zenoti creates 50 new product records.

Import vendors

  1. At the center level, go to Configuration > Business details > Business setup > Import bulk data and choose the vendors import type.
  2. Download the import template.
  3. Fill in vendor details: name, code, contact information, and center associations. List center associations as a comma-separated list of center codes (for example, CTR001,CTR002,CTR003) in the designated column. Each row creates one vendor; the center-associations field links that vendor to multiple centers.
  4. Upload the file and review the validation preview.
  5. Select Import to create the vendor records.

Import purchase orders

Important: Purchase orders (PO) are raised to external vendors. No transfer order (TO) import path exists β€” transfer orders must be created individually through the interactive workflow. No CSV path exists for PO imports; you must use an Excel file (.xls or .xlsx) with the data on the sheet named Sheet1.

  1. At the center level, go to Inventory > Orders.
  2. Select Import order from the actions menu.
  3. Download the import template.
  4. Fill in order details: vendor code, product codes, retail quantities, and consumable quantities.
  5. Upload the file.
  6. Zenoti validates each row. Errors flag invalid entries (unrecognized product code, missing vendor, inactive center) and display as an on-screen error list.
  7. Review the results and select Import to create the orders.

Imported purchase orders are created in Created status. You must raise them separately through the normal workflow β€” see Manage Procurement.

Note: Despite the import page being labeled Inventory Order import, only purchase orders can be created through this path. There is no transfer order import path in the current surface.

Purchase order import file format

The purchase order import file uses four required columns. Each row represents one product on the order.

Column Description
VendorCode Vendor code defined on the Configuration > Products > Vendors screen. The entire file must reference exactly one VendorCode β€” one file equals one purchase order.
ProductCode Product code defined on the product master record. Must be associated with the selected vendor and active at the importing center.
RetailQty Quantity to procure for retail. Leave blank for consumable-only products.
ConsumableQty Quantity to procure for consumable use. Leave blank for retail-only products.

Import guidelines

Follow these rules to avoid validation errors:

  • One vendor per file. Each import file represents one purchase order. If you need to import purchase orders for multiple vendors, prepare and upload one file per vendor.
  • Don't enter 0 in RetailQty or ConsumableQty for product types that are not applicable. For a consumable-only product, leave RetailQty blank; for a retail-only product, leave ConsumableQty blank. A 0 is treated as an explicit zero-quantity row and fails validation.
  • No spaces or special characters in VendorCode and ProductCode columns.
  • Format codes as Text in Excel to avoid scientific notation. A ProductCode like 111100000072 becomes 1.111E+11 if Excel treats it as a number, which Zenoti rejects as invalid. Set the column type to Text before pasting codes.
  • Use a supported file format. Excel (.xls, .xlsx) only β€” CSV is not accepted for PO imports. Maximum file size is 3 MB.

Tip: Verify the vendor-product associations and product activation status at the center before uploading. The import surfaces a single error per row; if a row fails for one reason and would also fail for another (for example, both an inactive product and a missing vendor association), you may need to re-upload after each fix.

Worked example β€” purchase order import

Your center needs to restock 10 retail products from vendor VEND-042. You download the PO import template, enter VEND-042 in the VendorCode column for all 10 rows, paste the product codes in the ProductCode column, and enter the retail quantities. You leave ConsumableQty blank for all rows because all 10 products are retail-only. After upload, Zenoti validates the file and shows all 10 rows as valid. You select Import. One purchase order in Created status is created for vendor VEND-042 with all 10 products. You then open the order in Inventory > Orders and raise it to send it to the vendor.

Import audit data

Merge audit count data into an in-progress audit from an Excel or CSV file. This is a fast way to capture counts collected on paper or in a separate spreadsheet during a stock count. Audit imports are capped at 6,000 rows per file.

Important: This procedure requires an audit to be in progress for the center β€” the import appends counts to an existing pending audit. It does NOT start a new audit. If no audit is open for the center, first start one via Inventory audit and physical count, then return here to import counts into it. Conversely, you cannot start a new audit while one is already pending β€” the audit-creation prerequisite (no pending audit exists) and the audit-import prerequisite (an audit must be in progress) are two distinct rules for two distinct operations; both are correct in their own context. If you are unsure which path you need, see Methods to enter audit data and pick the method that fits your workflow.

  1. Confirm an audit is in progress for the center (per the prerequisite above).
  2. Navigate to Inventory > Audit > Import.
  3. Download the Export template to get the current column structure for the audit import file.
  4. Enter the physical count data: product code, then either Floor quantity + Storage quantity (if your org has Unify Store and Floor disabled) OR On Hand Quantity (if Unify Store and Floor is enabled β€” see Field labels).
  5. Upload the file.
  6. Zenoti validates the data against the open audit and displays a preview showing Total, Valid, and Failed row counts, plus Errors and Warnings details. Negative values are not allowed; if you accidentally include a minus sign, Zenoti ignores it and imports the value as positive.
  7. Select Continue to merge the valid counts into the current audit session. To validate the file without committing any counts, select Validate β€” this runs all checks and displays the full error and warning list without modifying the audit.

Imported counts merge with any counts already entered manually. After import, review the audit and submit it via the normal flow β€” see Submit the audit. Reconciliation begins after submission β€” see Reconciliation and approval.

Note: The Enable partial audit of products organization setting controls whether you can submit counts for a subset of products. When this setting is enabled, you can import counts for selected products and submit without counting every product in the center. When disabled, all products must be counted before submission.

Worked example β€” audit import

Your team counted 200 products on paper during a weekend stock count. You open the audit import template, paste the product codes and physical counts into the appropriate columns, and save the file as CSV. You navigate to Inventory > Audit > Import, upload the file, and review the preview. Three rows show errors because the product codes were entered with leading spaces. You correct the codes in the source file, re-upload, and select Continue. The 197 valid rows merge into the open audit session. You then review the merged counts in the audit screen and submit for reconciliation.

Exports

The Export option is available across multiple inventory surfaces. Each location exports the data on its current screen with the filters you have applied. PDF is not an export format for inventory reports β€” printing uses your browser's print function (A4 format). Export formats are Excel and CSV only.

Where What exports Format options
Configuration > Business details > Business setup > Import bulk data Products, vendors Excel, CSV
Inventory > Orders Purchase orders Excel, CSV
Reports > Inventory > Audit History Audit history Excel, CSV
Reports > any V2 report The report's grid data with applied filters CSV (flat file), Excel
Reports > Inventory > any legacy report The report's data Excel

To export from a report or grid:

  1. Navigate to the screen containing the data.
  2. Apply filters to narrow the data set if needed.
  3. Select the Export option in the grid toolbar (or Export button in some legacy reports).
  4. Choose the format β€” Excel Export or CSV Export depending on your needs. The file downloads to your device.

Permission: Export under Export_Inventory (the row renders with its raw name in the Inventory Manager section) is required for generic inventory exports surfaced via report grids. Per-report permissions also apply β€” for example, the Current Stock Report permission under View Inventory Reports in the Inventory Manager section is required to view and export that report.

Export purchase orders to CSV

An individual purchase order can also be downloaded as a CSV file when the EnableCSVExportforPO organization setting is enabled. When this setting is active, a Download CSV button appears on the purchase order detail page.

To export purchase order data for use in external systems from the orders listing:

  1. Go to Inventory > Orders.
  2. Apply any filters (order type, status, date range, vendor) to scope the data.
  3. Select Export data from the actions menu.
  4. Choose CSV or Excel as the format.
  5. The file downloads with the columns currently visible in the grid.

Tip: Use the column selector (Select columns to display) in the grid toolbar to add or remove columns before exporting. Only visible columns are included in the export file.

Impacts and considerations

  • Import operations validate data before processing. Rows with errors are skipped, and the system reports which rows failed and why.
  • Product imports enforce uniqueness for product names, codes, and barcodes. Duplicate entries are flagged as errors.
  • Purchase order imports create orders in Created status. You must raise them separately through the normal workflow.
  • There is no import path for transfer orders β€” transfer orders must be created individually through Inventory > Orders.
  • Audit imports merge into the current audit session. If no audit is in progress, the import fails β€” start one first via Inventory audit and physical count.
  • Audit imports are capped at 6,000 rows. Split larger data sets across multiple files and import them sequentially into the same open audit session.
  • Large import files may take several minutes to process. Do not close the browser during the import.
  • Stock adjustments cannot be imported in bulk. Each adjustment must be applied per product. See Adjust stock.

Tips

  • Download a fresh template before each import. Template columns can change between Zenoti releases. Using an outdated template is a common cause of bulk-import failures. Use the Export button on the import screen to get the current version.
  • Test with a small batch first. Before importing hundreds of rows, upload 5–10 rows to confirm your column mapping and data format are correct. Fix any issues before scaling up.
  • Use the Validate action before committing. Both the product import surface and the audit import surface offer a validation-only action (Validate for products; Validate for audits). Run this first to see all errors without creating or modifying any records.
  • Use CSV for large product or audit files. For files with more than 1,000 rows, CSV typically processes faster and is less prone to Excel-specific formatting issues (such as date auto-conversion or scientific notation on long numeric codes). Note that CSV is not supported for purchase order imports.
  • Keep a copy of your import file. If an import partially succeeds and you need to re-import failed rows, having the original file makes it straightforward to isolate and correct the problem rows.
  • Apply filters before exporting. Exports reflect the current grid state. Narrow your data with filters (date range, vendor, status) before selecting Export to avoid downloading more data than you need.

Troubleshooting

Symptom Likely cause What to try
Template download fails Browser pop-up blocker, or session expired Allow pop-ups for the Zenoti domain and refresh the page.
Import preview shows all rows as errors File format mismatch β€” uploaded a previous template version, or the file uses a different delimiter Re-download the current template using Export, copy your data into it, and re-upload. For CSV, ensure the delimiter is a comma (not a semicolon).
PO import rejects CSV file CSV is not a supported format for purchase order imports Save the file as .xlsx or .xls and re-upload.
Audit import rejected with "no audit in progress" No open audit exists for the center Start a new audit via Inventory audit and physical count, then re-attempt the import.
Audit import rejected with row count exceeding limit File has more than 6,000 rows Split the file into multiple files of 6,000 rows or fewer and import them sequentially into the same open audit session.
Audit import rejected with "negative values" The file contains negative count entries Negative values are not allowed in audit data. Ensure all counts are zero or positive in the source file, then re-import.
Vendor import fails on center associations Center code in the file does not match any existing center, or codes are space-separated instead of comma-separated Verify each center code exists. Use comma-separation with no spaces for multiple centers.
Import partially succeeded; some rows missing Validation errors caused those rows to be skipped during import Re-run with the failed rows in a separate file to see the specific errors, correct them, and re-import.
Export file is empty Filters applied to the source view eliminated all rows Clear filters and retry.
Product codes appear as scientific notation in Excel export Excel auto-formatted long numeric codes as numbers Open the CSV in a text editor, or format the column as Text in Excel before pasting codes into an import template.
Was this article helpful?
Your feedback helps us improve our documentation.