Contents
Item aliases provide alternate part numbers for the same inventory item, enabling cross-referencing between your internal item IDs and external numbering systems. This simplifies transactions when suppliers, customers, or legacy systems use different part numbers to identify the same product.
Common Use Cases:
Access: Inventory → Items → Item Alias List
| Action | Path |
|---|---|
| View all aliases | Inventory → Items → Item Alias List |
| Add new alias | Inventory → Items → Item Alias List → Add Item Alias |
| Search or filter | Inventory → Items → Item Alias List (use report column filters) |
| Export alias list | Inventory → Items → Item Alias List → Print / CSV / XLSX |
Permissions:
An item alias creates a one-to-many relationship where a single inventory item can have multiple alternate identifiers. When you enter an alias during a supported transaction, the system automatically resolves it to the correct internal item ID.
Key Characteristics:
Alias vs. Primary Item ID: Your primary item ID (ShortID) is the master identifier used throughout Inventory Pro for reporting, stock levels, and internal operations. Aliases are convenience mappings that point to the primary ID but don’t replace it.
The Item Alias List is a report-style page with built-in search, filtering, and export-not a simple maintenance grid.
Create individual aliases for cross-referencing supplier catalogs, customer specifications, or alternative naming conventions.
Workflow:

Validation:
Tips:
VENDOR-PARTNO or CUST-ABC-12345)There is currently no dedicated bulk import tool for item aliases in the standard Import and Export interface. Plan to add and maintain aliases through the Item Alias List.
Modify existing aliases to correct data entry errors or update supplier catalog changes.
Workflow:
Important: Changing an alias doesn’t affect historical transactions. Past receipts and issues remain linked to the original item regardless of alias updates.
Remove obsolete aliases when suppliers discontinue part numbers or after completing system migrations.
Open the alias record from Item Alias List and use the delete action on that record to remove the alias. Confirm the deletion prompt before continuing.
Safe to Delete When:
Warning: Deletion is permanent and cannot be undone. Historical transactions remain intact, but future attempts to use the deleted alias will fail.
Aliases resolve automatically in supported stock and order workflows. Purchase order receiving is the primary confirmed example from this pass. Other stock screens (issuing, moving, cycle counts) use the same backend lookup infrastructure, but each screen has not been individually confirmed through live testing.
The backend barcode lookup checks aliases as part of a defined resolution order:
Scan Resolution Order:
If you scan “VENDOR-ABC-123” and it doesn’t match the primary ID, UPC, or supplier catalog, the system checks aliases before rejecting the scan.
Mobile scanning: Mobile devices use the same backend resolver. Validate mobile-specific behavior in your own environment before depending on alias-only scanning workflows.
When receiving against purchase orders, enter the supplier’s part number (if configured as an alias) instead of your internal item ID.
Workflow:
Note: Purchase order line views include an alias cross-reference field (AliasShortID), making it easier to match supplier part numbers on PO lines to your internal items.
Issuing, moving, and cycle count screens share the same item resolution infrastructure as receiving. Enter the alias ID in the Item field and the shared lookup layer resolves it to the internal item before the transaction continues.
Global Aliases (Warehouse = blank): Alias resolves to the same item across all warehouses-ideal for manufacturer model numbers or corporate-wide supplier catalogs.
Warehouse-Specific Aliases (Warehouse = specified): When resolving an alias, the system first looks for a warehouse-specific match for the current warehouse. If none is found, it falls back to a global alias row. This allows the same external part number to map to different items in different locations.
Example:
Recommendation: Use global aliases unless you have a specific business need for warehouse-specific mappings.
Consistent naming patterns improve findability and reduce errors:
| Pattern | Example | Use For |
|---|---|---|
VENDOR-PARTNO | ACE-ABC-123 | Supplier-specific part numbers |
CUST-NAME-SKU | CUST-FORD-X789 | Customer-assigned IDs |
MFG-MODEL | MFG-DELL-LAT5520 | Manufacturer model numbers |
LEGACY-ID | LEGACY-OLD-SYSTEM-456 | Temporary migration IDs |
Recommendation: Choose one pattern per alias type and document it for your team.
| Scenario | Recommended Solution |
|---|---|
| Supplier’s unique part number | Alias or Supplier Catalog |
| Globally recognized manufacturer model | Manufacturer Model field (system checks during barcode scans) |
| Customer-specific SKU | Alias (if used in transactions) |
| Barcode/UPC | Manufacturer Model field |
| Internal alternate naming | Alias only if it appears on external documents |
Why This Matters: Overusing aliases creates maintenance overhead. Use aliases for identifiers that appear on external documents (POs, packing slips, customer orders) where automatic resolution saves time.
Regular Reviews:
Identifying Candidates for Removal:
On this page