Import Inventory Data from AcMP
Use AcMP Import when you need to import existing inventory data from an AcMP Excel export into FlightLogger Maintenance.
This import option is designed specifically for AcMP inventory exports. It helps you bring existing parts, stock quantities, locations, serial numbers, certificates, and related AcMP reference data into FlightLogger Maintenance during the initial setup phase.
AcMP Import is different from the general Initial Data Import. Use AcMP Import when your source file comes directly from AcMP. Use Initial Data Import when you are working with FlightLogger Maintenance CSV templates or another generic data format.
When to use AcMP Import
Use AcMP Import if you have an AcMP Excel export containing inventory data such as:
- parts catalogue data
- stock quantities
- main storage locations
- minimum and maximum stock levels
- serialized inventory
- batch numbers
- supplier or purchase references
- certificate requirements
- alternate part numbers
The import supports two main AcMP export types:
- Store / parts catalogue exports
- Serialized catalogue exports
FlightLogger Maintenance detects the type of AcMP file from the headers in the first row of the first worksheet.
Before you start
Before importing AcMP data, make sure the account is ready for setup import.
AcMP Import is intended for the initial implementation phase. Because the import can create inventory items, locations, stock records, aliases, and serialized items, it should be completed before the account is used for normal daily inventory operations.
Before running the import, confirm that:
- account setup mode is enabled
- your user has permission to create inventory imports
- your user has an active membership in the account
- the AcMP Excel file is available and has not been manually reformatted in a way that changes the expected headers
- the account is ready to receive new inventory items
- the account can accept new locations created from AcMP
Main Locationvalues
If setup mode is not enabled, the import cannot be completed.
What the AcMP import creates or updates
Depending on the content of the AcMP file, the import can create or update several inventory-related records in FlightLogger Maintenance.
For parts catalogue files, the import can create or update inventory items, stock quantities, locations, stock levels, part number aliases, and required certifications.
For serialized catalogue files, the import can create or update serialized inventory items, serial numbers, batch numbers, received dates, costs, locations, aliases, and certification requirements.
The import also preserves selected AcMP reference information for traceability. This can include AcMP IDs, supplier information, delivery notes, purchase references, barcodes, and other source-file details.
How locations are handled
AcMP locations are imported from the Main Location column.
If a location already exists in FlightLogger Maintenance with the same active location code, the import reuses that existing location.
If the location does not already exist, FlightLogger Maintenance creates it during the import.
Some AcMP location values are interpreted as structured storage locations. For example, certain shelf, aisle, and bin codes can be expanded into a location hierarchy. Other non-empty location values are imported as flat bin locations.
If an inventory item has a Main Location, the imported item is linked to that location as a compatible location. If the Main Location is blank, the item is imported without compatible-location restrictions.
Rows with positive stock quantity but no valid location are reported as stock-count errors instead of being silently imported without a storage location.
How part numbers are handled
The AcMP part number becomes the FlightLogger Maintenance inventory item part number.
-
For parts catalogue exports, the import uses the
Pncolumn. -
For serialized catalogue exports, the import uses
Part Catalog Pn, with fallback toBatch Pnwhere applicable. -
Alternate part numbers are imported as part number aliases. This helps preserve AcMP references without placing all alternate numbers directly into the item description.
If an alternate part number conflicts with another item’s primary part number or an existing active alias, the import does not attach it automatically. Instead, the conflict is shown in the import result so it can be reviewed.
How stock quantities are handled
For standard parts, stock quantities from AcMP are imported as approved stock counts at the relevant location.
If the same part and location appear more than once, quantities are summed where the import service allows it.
Invalid quantities are reported as errors. They are not converted to zero.
For serial-tracked items, bulk stock quantities are not imported as normal stock lines. This is because serial-tracked items require individual serial numbers. Those rows are listed separately so the serialized stock can be handled through the correct serialized inventory flow.
How serialized items are handled
Serialized catalogue exports create or update inventory items that require serial tracking.
Each valid serial number is imported as a serialized inventory unit.
The import uses the Sn column as the manufacturer serial number. Blank serial numbers, placeholder values, or invalid serial values are skipped.
Manufacturer serial numbers must be unique within the account. If the same serial number appears more than once, FlightLogger Maintenance imports the first valid row and reports later rows as duplicate serial numbers.
If a serialized catalogue is imported after a parts catalogue import, and the same part already exists with bulk quantity stock, FlightLogger Maintenance may clear the bulk quantity before promoting the item to a serialized part. If active reservations exist, the item cannot be promoted automatically and must be reviewed manually.
How certifications are handled
AcMP certificate information is mapped to required certifications on the inventory item.
Common AcMP certificate values can be mapped to requirements such as:
- Form 1
- 8130
- Certificate of Conformity
- Other certification requirements
When importing again, FlightLogger Maintenance can add missing certification requirements. It does not remove certifications that were manually configured after the first import.
Re-importing AcMP data
AcMP Import is designed to support re-importing where possible.
If the same identifiers are imported again, FlightLogger Maintenance updates existing records where the underlying import rules allow it. Existing AcMP aliases for the same item can be reactivated instead of duplicated.
However, re-importing should still be done carefully. If inventory has already been used operationally, imported changes may affect stock, serialized items, and item setup. Review the import results after each upload.
Import results and validation
After the file is uploaded, FlightLogger Maintenance processes the import and shows the results when processing is complete.
The result page helps you understand what happened during the import, including:
- records created
- records updated
- skipped rows
- validation errors
- stock-count errors
- duplicate serial numbers
- alternate part number conflicts
- rows that require manual review
Where possible, errors refer back to the original AcMP spreadsheet row and part number. This makes it easier to correct the source data or decide how to handle the issue manually.
Common issues
Missing required columns
If the Excel file does not contain the expected AcMP headers, the import is rejected.
Check that the file is an original AcMP export and that the first worksheet contains the expected header row.
Stock quantity without location
If a row contains stock quantity but no valid Main Location, FlightLogger Maintenance reports a stock-count error.
Add or correct the location in the source data before importing again, or handle the stock manually after import.
Duplicate serial numbers
If the same serial number appears more than once, only the first valid row can be imported.
Review the duplicate rows and confirm whether the source data should be corrected.
Alternate part number conflicts
If an alternate part number already belongs to another item, FlightLogger Maintenance does not attach it automatically.
Review the conflict before deciding whether to merge, rename, or manually adjust the item data.
Archived records
AcMP Import does not reuse archived inventory items or archived locations.
If an archived record already uses a part number or location code from the AcMP file, the import reports an error. Review whether the archived record should be unarchived, renamed, or handled manually.
Best practice
Before importing AcMP data into a production-ready account, review the AcMP export carefully.
Pay special attention to:
- part numbers
- duplicate serial numbers
- blank locations
- unusual stock quantities
- certificate requirements
- alternate part numbers
- archived or duplicate records
- serialized parts that may already have stock quantities
After the import, always review the result page before continuing with inventory setup.
The import result is the best place to identify rows that need correction before the inventory becomes part of daily operations.