A good IT inventory does not start with as many columns as possible. It starts with a few fields the team keeps up consistently: what is the item, how can it be identified unambiguously, what state is it in and who is currently responsible for it?

This template helps you start in a structured way and is built directly for the hardware import in AssetNode:

Download the IT inventory template as an Excel file

The file uses exactly the English column headings the importer expects. That lets AssetNode recognise the fields automatically on upload and propose the matching mapping. Before the actual import you can — and should — check that mapping once more in the preview.

Which columns does the IT inventory template contain?

Column Required Content Example
Serial Number no Manufacturer's serial number PF3ABC12
Model yes Model designation of the asset ThinkPad T14 Gen 5
Category (name) required for hardware Consistent asset category Laptops
Manufacturer (name) required for hardware Manufacturer name Lenovo
Status (name) no An existing status name; empty uses the available default status Available
Purchase Price no Purchase price as a number, without explanatory text 1299.00
Purchase Date no Date of purchase 2026-05-14
Warranty Expiry no End of the warranty 2029-05-14
Notes no A short, factual remark Dock recorded separately

Model has to be mapped for a hardware import. A row without a model cannot be imported. Supply the category and manufacturer as well, so a valid hardware record can be formed from them. For an inventory that is genuinely usable you should also record the serial number wherever the item has one. It is usually the best way to tell two devices of the same model apart.

Why the template is deliberately small

Many inventory projects fail not for want of fields but for want of clear definitions. A sheet with 40 columns looks complete but turns contradictory fast: one row holds the location, the next the department and a third the person's name — all in the same field.

The nine import columns therefore make a solid starting point:

  • the identity of the asset through model and, where possible, serial number,
  • consistent classification through category and manufacturer,
  • the current lifecycle state through the status,
  • purchase and warranty period for planning and replacement,
  • a notes field for exceptions, not as a substitute for structured data.

Assignments to employees are documented afterwards in asset management. That keeps apart what an item is and who is currently using it. The separation stops an old personal assignment from lingering permanently in an imported free-text column.

How to prepare existing inventory data

1. One row per physical asset

Every single device gets its own row. Three identical laptops are three records, not one row with the quantity "3". Only then can serial number, status, warranty and later assignment be traced per device.

Consumables are a different kind of stock. Toner, cable supplies or batteries are managed by quantity and do not belong in this hardware template as pretend individual devices.

2. Standardise your terms

Decide on one spelling before the import. "Laptop", "notebook" and "notebooks" may mean the same thing but create needless variants as categories. The same goes for manufacturers and models.

A short reference list helps:

  • categories in the plural or the singular, but consistently,
  • the official manufacturer name rather than shifting abbreviations,
  • model family and generation following a common pattern,
  • status values taken from the existing AssetNode workspace.

If your source sheet contains several spellings, unify them before the upload. That is easier to check than cleaning up later inside a live inventory.

3. Treat serial numbers as text

Spreadsheet programs alter values that look like numbers or dates. Serial numbers can carry leading zeros or be converted into scientific notation. Format the column as text and avoid formulas.

Also check for placeholders such as "N/A", "unknown" or "123456". Where no serial number exists, an empty field is more honest than a value that later gets mistaken for a unique identifier.

4. Write dates unambiguously

For purchase and warranty dates we recommend the format YYYY-MM-DD, for example 2026-08-11. It is unambiguous and readable regardless of the spreadsheet's language setting.

Do not enter approximate values such as "summer 2024" into a date field. If the exact date is unknown, leave the field empty for now and record the uncertainty in the notes if it matters.

5. Record prices as numbers

Write the purchase price as a number, not as a sentence. Additions such as "net", "approx." or a currency abbreviation do not belong in the value. Record internally which currency and which price basis apply to the whole file. With mixed currencies the conversion should be settled before the import, because the template has no separate currency column.

6. Keep free text to genuine exceptions

The Notes field is useful for peculiarities but quickly becomes a second, unstructured inventory. Write short remarks there that fit in no other column. Personal names, status or manufacturer should not be repeated in the notes on top of that.

Finding duplicates before the import

For devices with a serial number a simple duplicate check is possible. Highlight duplicate values in the Serial Number column in Excel and resolve every hit:

  • Is the same device listed twice by mistake?
  • Is it a generic serial number from the manufacturer?
  • Was a replacement device carried on under the old record?
  • Are characters missing because of automatic formatting?

Missing serial numbers are not automatically an error. For items without a manufacturer identifier the team needs a consistent internal marking instead. That can be carried in the system as an asset tag after the import.

Importing the IT inventory into AssetNode

The import runs in steps you can check as you go:

  1. Open the Import area in AssetNode.
  2. Choose Hardware / Assets as the data type.
  3. Upload the completed .xlsx file.
  4. In the field mapping, check that every column corresponds to the right target field.
  5. Pay particular attention to Model being mapped — without that required field the import stays blocked.
  6. Check the preview against several typical and unusual rows.
  7. Start the import and read the result, including any row-level notes.

The template's headings are mapped automatically because they match the target field names. Automatic mapping is still only a proposal: a manual check before writing protects you from mistakes when headings have been changed or extra columns inserted.

The import processes the first sheet of the file. Leave the hardware table in first position and move explanations or helper sheets behind it. Empty rows inside the data range should be removed before the upload.

Test first, then take over the whole inventory

Before cleaning up, save an unchanged copy of your source file. Then build a test file with a few representative rows:

  • one fully maintained standard device,
  • one device without a serial number,
  • one older device without a purchase price,
  • one model with special characters,
  • one record with a typical category and an existing status.

Import that selection and check the result in the asset list. Only then comes the whole inventory. That way you catch problems of definition or format before they affect many records.

A spot check after the import is worthwhile. Compare a few serial numbers, prices and dates against the source file. Check the total of successful and failed rows as well. A completed upload on its own is not yet proof that every row was classified correctly.

From a spreadsheet stock to a running process

The template creates a clean start. But the inventory only stays reliable if every later change has a fixed path. Define at least:

  • Who creates new assets after goods receipt?
  • When is a handover to an employee documented?
  • Who updates condition and status after a return?
  • How do MDM devices reach the inventory automatically?
  • When are warranty expiries or replacement decisions reviewed?
  • How are retired devices documented without losing their history?

AssetNode brings hardware, assignments and lifecycle data together in one workspace. The managed cloud is free for up to 100 assets. For internal use the fair-code, source-available version can be self-hosted with no limit on the number of assets.

Download the template or create a free workspace.