Main focus

Import stock entries from Excel or CSV into an existing inventory. This adds transaction rows, not product records, so the products referenced by the file should already exist.

Applies to

  • Android
  • iOS

Entry import vs product import

  • Entry import: Adds stock entry or transaction rows, such as counts or stock movements, for products that already exist in the inventory.
  • Product import: Creates or updates product records, such as product name, SKU, Barcode, category, unit, and product custom fields.
  • Use entry import when your spreadsheet represents stock activity. Use Import/update products in batch when your spreadsheet represents the product catalog.
  • Entry import does not create missing products. Fix missing products first, then import the entries.

Watch the steps

Pause the walkthrough on the Verify import screen to review the field mapping.

Quick path

Follow these steps

  1. Open the inventory that should receive the entries.
  2. Open Entries.
  3. Tap Import.
  4. Select the Excel or CSV file.
  5. On Verify import, map SKU or Barcode, then map Quantity and Location when needed.
  6. Tap Proceed with the import.

Keep products ready first

The importer matches entry rows to existing products. It is not a product-creation flow.

Before you start

  • Prepare an Excel (.xls, .xlsx) or CSV (.csv) file with one row per entry.
  • Include Quantity and at least one product identifier: SKU or Barcode.
  • Make sure the products in the file already exist in the inventory.
  • Add a Location column when entries should be assigned to specific locations.
  • For Excel files, keep the entry data on the first sheet.
  • Use clear column headers so the Verify import step is easy to check.

Test important imports on a duplicate inventory

Entry imports can change stock history and current quantities. Duplicate the inventory and test the file there first before importing into live data.

Required columns and matching

ColumnRequiredHow Mobile Inventory uses it
SKURequired if Barcode is not mappedMatches the row to an existing product by SKU.
BarcodeRequired if SKU is not mappedMatches the row to an existing product by Barcode.
QuantityRequiredSets the quantity for the imported entry row.
LocationRequired when you track entries by locationAssigns the imported entry to an existing location.
Entry typeRequired when your stock management template separates IN, OUT, or MOVE rowsControls how the entry affects stock. Map it only when the app shows this field in the import flow.
Date, price, notes, or entry custom fieldsOptionalImported only when the field exists in the inventory and is mapped during verification.

How products are matched

  • Mobile Inventory matches each spreadsheet row to an existing product using the mapped SKU or Barcode.
  • If both SKU and Barcode are mapped, make sure they identify the same product.
  • Rows that do not match an existing product should be corrected before you confirm the import.
  • To add or update products, use Import/update products in batch before importing entries.

Key screens

Open Entries before starting the import.
Map the product identifier and quantity columns.
Review Entries after import and check several rows.

Written steps

  1. Open a duplicate inventory for testing, or open the live inventory when you are ready.
  2. Go to Entries.
  3. Tap Import.
  4. Select the Excel or CSV file from the device, cloud storage, or the import code flow if your app version offers it.
  5. On Verify import, map SKU or Barcode so each row can be matched to a product.
  6. Map Quantity and any location, entry type, date, price, note, or entry custom field columns that should be imported.
  7. Review the mapping and any unmatched-row warnings before continuing.
  8. Tap Proceed with the import.
  9. Return to Entries and check several imported rows, including their product, quantity, location, and date.

What this does not do

  • It does not create products that are missing from the inventory.
  • It does not update product catalog details such as product name, category, or product custom fields.
  • It does not remove existing entries that are not present in the file.
  • It does not protect live stock from incorrect quantities, locations, or entry types. Test first when the file is important.

Next step

After importing, review a few products and confirm their current stock reflects the imported entries correctly.