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.
Before you startCheck file format, product matching, optional fields, and test safety
- 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.
- Add a Transaction type column only when the file must explicitly identify IN, OUT, or MOVE rows.
- For Excel files, keep the entry data on the first sheet.
- Use clear column headers so the Match fields step is easy to check.
Watch the steps
Quick path
Follow these steps
- Open the inventory that should receive the entries.
- Open the inventory menu and tap Import.
- Choose Continue with the Import if the safe-simulation warning appears.
- Tap Import transactions.
- Select the Excel or CSV file.
- On Match fields, make sure SKU or Barcode and Quantity are mapped.
- Tap Proceed with the import.
Keep products ready first
The importer matches entry rows to existing products. It is not a product-creation flow.
Entry import vs product importUse entry import for stock activity; use product import for catalog changes
- Entry import adds stock transaction rows for products that already exist.
- Product import creates or updates product records, such as product name, SKU, Barcode, category, unit, and product custom fields.
- Use this article 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. Add or fix missing products before importing entries.
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
| Column | Required | How Mobile Inventory uses it |
|---|---|---|
| SKU | Required if Barcode is not mapped | Matches the row to an existing product by SKU. |
| Barcode | Required if SKU is not mapped | Matches the row to an existing product by Barcode. |
| Quantity | Required unless Total is mapped | Sets the quantity for the imported transaction row. |
| Total | Optional | Sets the final transaction quantity when the file already contains the total. |
| Location | Optional | Assigns the imported entry to a location. If the location is missing, the importer can create it. |
| Transaction type | Required only when the file must explicitly separate IN, OUT, or MOVE rows | Controls how the row affects stock. Map it when the app shows this field in the import flow. |
| User | Optional | Stores the user name from the file. If it is not mapped, the current user is used. |
| Conversion factor (Batch) | Optional | Applies the batch conversion factor when Total is not supplied directly. |
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 import transaction custom field values in the current Android transaction import flow. That includes custom notes, dates, prices, and other transaction-level 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 transaction 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.