Bulk import and export inventory
To bulk import and export inventory, start with inventory access, the intended branch, and verified item, unit, cost, or quantity information. In Admin, download template, export inventory, upload CSV, and review row validation. Verify the item, unit of measure, branch, quantity, and cost before saving any stock change.
Before you start
- Inventory access, the intended branch, and verified item, unit, cost, or quantity information
- Search before creating records and preserve the item unit of measure
Steps
- Open /inventory/bulk-import and download the current CSV template before preparing rows.
- Keep the template headers unchanged, populate only supported fields, and preserve each item’s unit and branch context.
- Upload the CSV once and review row-level validation before confirming an import.
- Correct rejected rows in the source file and upload a revised file; export inventory separately when a read-only snapshot is needed.
Expected result
Upload validation identifies accepted and rejected rows before import. Confirmation imports only the validated file state, while rejected rows remain traceable for correction; export produces a separate read-only inventory snapshot.
Permissions
- Bulk Import accepts inventory.admin, inventory-v1.admin, or inventory.write; backend plan and operation-specific checks still apply to import and export.
Troubleshooting
The CSV is rejected before row review.
Download the current template, preserve its headers and file type, and remove unsupported columns or formatting. Upload the corrected file once; never confirm an import that has not reached row validation.
Some rows fail validation or import status is uncertain.
Use the row numbers and messages to correct only rejected source rows. Check import history before resubmitting the full file, and provide Support the import reference and redacted errors rather than the customer file.
Related articles
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback