Item Aliases

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 vendors, customers, or legacy systems use different part numbers to identify the same product.

Common Use Cases:

• Vendor Part Numbers: Map supplier catalog numbers to your internal SKUs for purchasing and catalog management
• Customer Part Numbers: Link customer-specific item codes for sales orders and quotes
• Manufacturer Model Numbers: Cross-reference OEM part numbers for warranty and service operations
• Legacy System Migration: Bridge old and new item numbering during system transitions
• SKU Consolidation: Support multiple naming conventions when merging catalogs from acquisitions

Access: Inventory → Items → Item Alias List

Understanding Item Aliases

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 transactions, the system automatically resolves it to the correct internal item ID.

Key Characteristics:

• Unique: Each alias can only map to one item-no duplicates across your entire inventory
• Automatic Resolution: Transactions accept aliases anywhere item IDs are entered (receiving, issuing, orders, cycle counts)
• Transparent: Users don’t need to know whether they’re entering an alias or native item ID
• Bidirectional Search: Search by item to find all its aliases, or search by alias to find the associated item

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.

Managing Item Aliases

Adding Aliases

Create individual aliases for cross-referencing vendor catalogs, customer specifications, or alternative naming conventions.

Workflow:

1. Navigate to Inventory → Items → Item Alias List
2. Click Add Item Alias
3. Fill in required fields:
   • Item ID: Select the inventory item this alias represents (search by ID or description)
   • Alias ID: Enter the alternate part number (50 characters max)
   • Warehouse (Optional): Restrict alias to specific warehouse if the same alias means different items in different locations
4. Click Save

Validation:

• Alias ID must be unique (system prevents duplicates)
• Item must exist in your inventory master
• Alias cannot match an existing primary Item ID (prevents ambiguity)

Tips:

• Use a consistent naming pattern (e.g., “VENDOR-PARTNO” or “CUST-ABC-12345”)
• Document the source in a separate tracking system if managing many vendor catalogs
• For manufacturer model numbers, consider adding them as the item’s “Manufacturer Model” field instead if they’re globally recognized

Editing Aliases

Modify existing aliases to correct data entry errors or update vendor catalog changes.

Workflow:

1. Navigate to Inventory → Items → Item Alias List
2. Search for the alias or item
3. Click the alias record to open the edit screen
4. Make changes to Alias ID, Item ID, or Warehouse
5. Click Save

Important: Changing an alias doesn’t affect historical transactions. Past receipts and issues remain linked to the original item regardless of alias updates.

Deleting Aliases

Remove obsolete aliases when vendors discontinue part numbers or after completing system migrations.

Workflow:

1. Navigate to Inventory → Items → Item Alias List
2. Search for and select the alias record
3. Click Delete
4. Confirm deletion

Safe to Delete When:

• Vendor has discontinued the part number
• Customer no longer uses the alternate ID
• Legacy system migration is complete
• Duplicate or erroneous entries exist

Warning: Deletion is permanent and cannot be undone. Historical transactions remain intact, but future attempts to use the deleted alias will fail.

Using Aliases in Transactions

Aliases work transparently in all transaction screens-receiving, issuing, moving, cycle counting, and order entry. Simply enter the alias ID in the Item field, and the system automatically resolves it to the correct inventory item.

Barcode Scanning with Aliases

The system’s barcode lookup function (fn_GetItemIDFromScan) checks aliases automatically when scanning:

Scan Priority Order:

1. Primary Item ID (ShortID)
2. UPC/Barcode (Manufacturer Model field)
3. Vendor Part Number (from Vendor Catalog)
4. Item Alias

Example: If you scan barcode “VENDOR-ABC-123” and it doesn’t match the primary ID, UPC, or vendor catalog, the system checks aliases before rejecting the scan.

Mobile Device Scanning: Inventory Pro Mobile supports the same alias resolution, enabling warehouse staff to scan vendor labels, customer barcodes, or legacy tags without manual cross-referencing.

Purchase Order Receiving

When receiving against purchase orders, enter the vendor’s part number (if configured as an alias) instead of your internal item ID.

Workflow:

1. Navigate to Orders → Purchasing → Purchase Orders → Receive
2. In the Item ID field, enter the vendor’s part number
3. System resolves to your internal item and displays the description
4. Complete quantity, location, and serial number fields
5. Receive to update inventory

Benefit: Reduces errors when warehouse staff only see vendor packing slips with manufacturer or vendor part numbers.

Customer-Specific Part Numbers

Sales and shipping teams can use customer-assigned part numbers when processing shipping orders.

Workflow:

1. Navigate to Orders → Shipping Orders → [Select Order] → Pick/Pack
2. Enter customer’s part number in the Item ID field
3. System translates to your internal SKU
4. Complete pick/pack workflow

Use Case: Customers with proprietary part numbering systems (common in automotive, aerospace, or large retail accounts) can provide orders using their own IDs, while your warehouse operates with your standard SKUs.

Inventory Adjustments and Cycle Counts

Aliases work seamlessly in inventory adjustments and cycle count workflows.

Workflow:

1. Navigate to Inventory → Stock → Receive/Issue/Move Stock or Cycle Counts
2. Enter alias ID in the Item field
3. System resolves to internal item
4. Complete transaction as normal

Example: During physical inventory, counters can scan manufacturer barcodes or vendor labels without needing to know your internal item numbering scheme.

Bulk Import and Management

For large-scale alias creation (hundreds or thousands of mappings), use the import utility instead of manual entry.

Import Workflow

Prerequisites:

• CSV or Excel file with columns: Item ID, Alias ID, Warehouse (optional)
• Item IDs must already exist in your inventory master
• Alias IDs must be unique

Workflow:

1. Prepare your import file:

   ItemID,AliasID,Warehouse
   ITEM-001,VENDOR-ABC-123,
   ITEM-001,CUST-XYZ-789,
   ITEM-002,MFG-MODEL-456,Main

2. Navigate to Utilities → Import and Export → Import Item Aliases (if available)
3. Select your file
4. Map columns to system fields
5. Validate for duplicates and errors
6. Execute import
7. Review import log for success/failure counts

Common Import Issues:

• Duplicate Alias IDs: System rejects if alias already exists for a different item
• Invalid Item IDs: Item must exist before creating aliases
• Format Errors: Remove special characters or line breaks from Alias IDs

Tips:

• Start with a small test batch (10-20 records) to validate your format
• Export existing aliases first to understand the required structure
• Use consistent warehouse codes (or leave blank for global aliases)
• Document your import source and date for future reference

Export for Reporting

Export your alias mapping to Excel for documentation, sharing with trading partners, or integration with other systems.

Workflow:

1. Navigate to Inventory → Items → Item Alias List
2. Apply filters if needed (specific items, warehouses, or date ranges)
3. Click Export to download CSV/Excel
4. Share with vendors, customers, or internal teams

Use Cases:

• Provide customers with your alias mappings for their ordering systems
• Share vendor part number cross-references with purchasing teams
• Document manufacturer model numbers for service departments
• Archive alias history before system migrations

Key Reports

Report Tips:

• Use Item Alias List with filters to generate vendor-specific part number cross-references
• Export to Excel for vendor catalog updates or customer order guides
• Review periodically to identify and remove obsolete aliases

Best Practices

Alias Naming Conventions

Consistent naming patterns improve findability and reduce errors:

Recommendation: Choose one pattern per alias type and document it for your team.

When to Use Aliases vs. Other Fields

Why This Matters: Overusing aliases can create maintenance overhead. Use aliases for identifiers that appear on external documents (POs, packing slips, customer orders) where automatic resolution saves time.

Maintenance and Cleanup

Regular Reviews:

• Quarterly: Export alias list and review with purchasing/sales teams for obsolete entries
• After Vendor Changes: Update or remove aliases when suppliers change part numbers
• Post-Migration: Delete temporary legacy system aliases once transition is complete

Identifying Candidates for Removal:

• Aliases not used in transactions for 12+ months
• Vendor part numbers for discontinued suppliers
• Customer-specific IDs for inactive accounts
• Duplicate mappings from data import errors

Multi-Warehouse Considerations

Global Aliases (Warehouse = blank): Alias resolves to the same item across all warehouses-ideal for manufacturer model numbers or corporate-wide vendor catalogs.

Warehouse-Specific Aliases (Warehouse = specified): Alias resolves to different items depending on warehouse-useful when the same external part number represents different products in different locations.

Example:

• Warehouse A: Alias “VENDOR-123” → Your Item “WIDGET-RED”
• Warehouse B: Alias “VENDOR-123” → Your Item “WIDGET-BLUE”

Recommendation: Use global aliases unless you have a specific business need for warehouse-specific mappings (rare in practice).

Related Topics

• Items and Inventory Master - Understanding item records, fields, and master data management
• Receiving Stock - Using aliases in receiving workflows and barcode scanning
• Purchase Orders - Vendor part number cross-referencing during PO processing
• Shipping Orders - Customer part number mapping for order fulfillment
• Mobile Operations - Barcode scanning with aliases on mobile devices
• Import and Export - Bulk alias creation and maintenance