Why did my inventory import skip rows or leave my stock levels unchanged?

An inventory import skips rows whose SKU does not match a product, and it changes nothing at all when any row has an error.

• “no matching product”: the completion message says “N row(s) skipped — no matching product” and lists the SKUs. The SKU does not match any product in your company, archived ones included. SKUs must match exactly. Create the product or correct the SKU, then import those rows again.
• Creating records: create products, buildings, and locations in Endless before you import stock for them. When a product exists but has no inventory yet and the row’s Stock Level is above zero, Endless creates the inventory and sets the stock.
• Archived products: rows for an archived product’s SKU update its stock like any other row.
• Zero for a SKU that has never had inventory: Endless does not create inventory for the row, and a zero for a location where the SKU has never had stock does not create a record there. The completion message does not list these rows as skipped.
• The same SKU and location twice: Endless applies both rows, and the order in the file does not decide which value stays. Keep one row per SKU and location.

If an import did not change your stock levels, check these causes:

• A row had an error, so Endless rejected the whole file. Look for “Import failed” in your Inbox.
• The file’s quantity already matched the stock level.
• The row points at an inactive location. Endless does not update inactive locations.
• The building’s inventory is managed by a connected system, and its next pull replaced the Default Available and Default Unavailable quantities.
• The row updated a different location from the one you are checking. With Location ID and Location Handle blank, Endless updates Default Available.

The item’s Activity tab shows each import that changed it as “Inventory item adjusted to N units with reason: Manual Adjustment.”