Mapping EZCom item numbers to Acumatica Inventory IDs is a partner-specific cross-reference task on the Trading Partners screen. The Inventory Items tab lets an administrator choose how the connector should search for an item within the selected Partner Code and associate the matching value with an Acumatica Inventory ID. UPC Code is the only search value demonstrated in the manual.
The Biz-Tech Services EZCom EDI Acumatica Connector uses that item mapping during EZCom order import and requires every imported item to be mapped. This guide concentrates on the Inventory Items cross-reference, the documented validation and warehouse precedence rules, and the separate mappings used for warehouse orders and inventory availability. It does not repeat setup, full data flow, purchase-order import, or quantity synchronization covered in points 13, 30, 47, 64, and 81.
What EZCom Item Number Mapping Does
The Biz-Tech Services Acumatica EZCom EDI Connector resolves each imported EZCom order item through the Inventory Items tab of the Trading Partners screen. The cross-reference area contains dropdown fields that choose how to search for the item within the current Partner Code and then map the result to an Acumatica Inventory ID.
The source illustrates the dropdown with UPC Code. With that value selected, the connector searches for the corresponding UPC Code number and associates the result with the Inventory ID. The documentation does not list the other available search fields, so it does not establish that an SKU, vendor part number, customer part number, or another identifier is available.
This mapping is required for order import. The manual warns that an error message appears when items are not mapped. It does not provide the exact error text, a rejected-line queue, or an automatic replacement-item rule for an unmapped EZCom order line.
EZCom Item Number Mapping at a Glance
Use this sequence to configure and validate the documented partner-specific mapping.
1 Open Trading Partners and select the Partner Code whose EZCom item values need to be mapped.
2 Review Cross-Reference Option and select the entities that should be matched between EZCom and Acumatica.
3 Open the Inventory Items tab and use its cross-reference dropdown to choose the item-search field available for that partner.
4 Enter or select the EZCom item value and associate it with the correct Acumatica Inventory ID. The manual demonstrates this with UPC Code.
5 Confirm that the item-search entity was checked in Cross-Reference Options because only checked entities appear in the dropdown.
6 Review Default Warehouse and warehouse cross-reference behavior separately from the item-number mapping.
7 Retrieve an order for the partner and validate the mapped Acumatica Inventory ID before importing the full order set.
8 If the order reports an unmapped item, return to the Inventory Items tab; do not infer an alias or fallback that the source does not document.
Set the Partner and Cross-Reference Scope
Trading Partners begins with Partner Code, a lookup that identifies the partner whose options are being configured. Item-number mappings are therefore organized in the context of that partner. The source does not state that one mapping automatically applies to another Partner Code.
Cross-Reference Option controls which entities can be matched during the transition. In the cross-reference area, Field identifies the entity whose EZCom and Acumatica values need to be paired. Only checked Cross-Reference Options appear in the Inventory Items dropdown, so an expected item-search field may be unavailable until the corresponding entity is enabled.
The manual separately documents Use Cross Ref for Country, Use Cross Ref for ShipVia, and Use Cross Ref for warehouse. When one is selected and configured, order import uses the matching cross-reference value. Those settings translate country, shipping, or warehouse values; they are not substitutes for the required item mapping on Inventory Items.
The source does not explain whether item-number cross-references are one-to-one, whether duplicate partner values are blocked, whether case or punctuation matters, or whether a mapping can have effective dates. It also does not document bulk loading, spreadsheet import, or an approval process for mapping changes.
Map a Partner Item Value to Inventory ID
On Inventory Items, select the item-search choice exposed by the cross-reference dropdown. The manual describes the purpose of that choice as determining how to search for the item within Partner Code and map it to the Acumatica Inventory ID.
UPC Code is the documented example. If UPC Code is selected, the system searches for an item with the corresponding UPC Code number and associates it with the Acumatica Inventory ID. The source does not identify the exact name of the partner-value column, the Inventory ID column, or a save or process button on the tab.
The Biz-Tech Services EZCom EDI Acumatica Integration should therefore be configured from the fields visible in the installed Inventory Items tab. Do not assume that Inventory ID itself, Inventory CD, Alternate ID, SKU, barcode, or a global trade item number can be selected unless it actually appears among the enabled options.
The mapping is line-relevant because each corresponding item on an EZCom order must be mapped for the order to import. The documentation does not explain whether one unmapped line blocks the entire order, whether other lines are imported, or whether the error identifies the partner value that failed.
Keep Warehouse Mapping Separate from Item Mapping
Partner Settings includes Default Warehouse through Warehouse ID. A warehouse cross-reference can also translate an EZCom warehouse value to an Acumatica warehouse during order import. The source states a precedence condition: Default warehouse must not have a value if the system is expected to take the warehouse cross-reference value.
This condition affects the warehouse on the order, not the item-number-to-Inventory-ID association. A successful UPC Code mapping does not replace the need for the correct warehouse configuration, and a warehouse cross-reference does not resolve an unmapped item.
Inventory Availability has a separate mapping. The manual names Acumatica Warehouse, quantity option, and EZCom Warehouse Code, followed by the parenthetical Item UPC Code. This setup controls the quantity sent from Send Inventory Availability. The wording does not clearly distinguish an EZCom warehouse code from an item UPC code, so verify the actual field labels before documenting a production procedure.
Send Warehouse Order also transmits Warehouse Code, UPC Code, and quantity for each item during shipment processing. That confirms UPC Code in the outbound warehouse message, but the source does not say whether the value comes from the same Inventory Items cross-reference row or from another item field.
Validate Mapped and Unmapped Order Lines
Import Purchase Orders retrieves partner orders and presents IMPORT and IMPORT ALL actions. Before importing an entire grid, test a selected order and confirm that each partner item resolves to the intended Inventory ID.
The clearest documented validation rule is the warning on the Inventory Items section: if items are not mapped, an error message appears during order import. The manual does not quote that message or state where it is logged after the processing screen is closed.
The following checks stay within the documented behavior.
1 Confirm that the correct Partner Code is selected.
2 Confirm that the intended item-search entity is enabled in Cross-Reference Options.
3 Confirm that the corresponding partner item value is associated with the expected Acumatica Inventory ID on Inventory Items.
4 Confirm that Default Warehouse is blank when a warehouse cross-reference must provide the imported warehouse.
5 Retrieve one order and review its items before using IMPORT ALL.
6 If an unmapped-item error appears, correct the mapping and test again. The manual does not document a skip-line, placeholder-item, or auto-create option.
Use the Mapping in Warehouse and Availability Messages
After a mapped order progresses, other EZCom transactions carry item and quantity information. Import Warehouse Shipment brings the item quantity and tracking number from EZCom and updates the shipment. Send Warehouse Order sends Warehouse Code, UPC Code, and quantity for each item.
Send Inventory Availability displays items already loaded and checked on the Inventory Items tab for the partner. It also requires the corresponding Inventory Availability mapping. Selecting Send or Send All synchronizes item quantity according to that mapping.
These outbound and inventory processes depend on the item setup but do not define a broader item alias rule. The source does not say whether changing an Inventory Items mapping updates previously imported orders, warehouse requests, or availability history. It also does not explain whether an item can have more than one UPC Code per partner.
No screen ID is given for General Settings, Trading Partners, Import Purchase Orders, Inventory Items, Inventory Availability, Send Warehouse Order, or Send Inventory Availability. The only screen ID in the manual is Customization Projects (SM204505), used to install the package.
Document Item Class Alias and Precedence Gaps
Item classes are not mentioned in the EZCom Connector manual. The source provides no item-class default, class-based search, class restriction, or inheritance rule for item mapping. Do not use an item class as a documented resolution key without separate product guidance.
No independent alias model is described. Inventory Items supplies a partner-specific cross-reference and demonstrates UPC Code, but the source does not define aliases, alternate IDs, substitute items, customer part numbers, vendor part numbers, multiple barcodes, wildcard matches, or priority among identifiers.
The manual also does not define a fallback for an unmapped item. It promises an error during order import but provides no replacement item, auto-create behavior, correction queue, or reprocessing instructions. An administrator should not borrow missing-item behavior from another connector.
The one documented precedence rule concerns warehouses: leave Default Warehouse empty when warehouse cross-reference should supply the value. No equivalent precedence is supplied for an item value that could match more than one Inventory ID or for multiple item-search entities selected at the same time.
Where to Check Your Work
The Biz-Tech Services EZCom EDI Acumatica Integrator exposes the documented item mapping and downstream result in these locations.
1 Trading Partners: confirm Partner Code before reviewing any partner-specific mapping.
2 Cross-Reference Option: confirm that the required item-search entity is selected so it can appear in the dropdown.
3 Inventory Items: compare the partner item value, selected search field such as UPC Code, and mapped Acumatica Inventory ID.
4 Partner Settings: review Default Warehouse and Warehouse ID separately from the item cross-reference.
5 Cross-Reference: review Country, ShipVia, and warehouse mappings without treating them as item aliases.
6 Import Purchase Orders: retrieve a selected order and confirm that no unmapped-item error appears during import.
7 Inbound Purchase Orders: review the source order information for the corresponding partner when diagnosing a line.
8 Inventory Availability: confirm Acumatica Warehouse, quantity option, and the EZCom warehouse or UPC-related value shown by the installed screen.
9 Send Inventory Availability and Send Warehouse Order: confirm that the intended mapped item appears and that the expected UPC Code and quantity are sent.
EZCom Item Number and Inventory ID Mapping Frequently Asked Questions
Where are EZCom item numbers mapped to Acumatica Inventory IDs?
Use the Inventory Items tab on Trading Partners for the selected Partner Code. Its cross-reference dropdown chooses how to search for the partner item and associate it with an Inventory ID.
Which EZCom item identifier does the connector use?
UPC Code is the only documented example. The manual does not list every selectable search value or state that an SKU, alternate ID, or another field is supported.
Why is an expected item-search field missing from the dropdown?
Only checked entities from Cross-Reference Options appear in the dropdown. Review the options configured for the current Partner Code.
What happens when an EZCom order item is not mapped?
The source says an error message appears during order import. It does not provide the message text or document automatic item creation, line skipping, or a replacement-item fallback.
Can item class control EZCom item matching?
No item-class behavior is documented. The manual does not name item class as a search key, default, restriction, or cross-reference field.
Does Default Warehouse override warehouse cross-reference?
The manual states that Default warehouse should have no value when the system needs to take the warehouse cross-reference value. This warehouse rule is separate from item-number matching.
Does the connector support aliases or several UPC codes for one item?
The Biz-Tech Services Acumatica EZCom EDI Integration documentation does not define aliases, multiple identifiers, duplicate handling, or matching precedence. Confirm any such design with Biz-Tech Services before relying on it.
How can I test a new item mapping safely?
Enable the required cross-reference entity, create the Inventory Items mapping for one Partner Code, retrieve one purchase order, and validate the resolved Inventory ID before using IMPORT ALL or sending downstream availability data.
Work With the Biz-Tech Services EZCom EDI Connector
A dependable EZCom item mapping keeps partner item resolution, warehouse translation, and inventory availability setup separate. Configure the Inventory Items cross-reference first, verify one order, and document every identifier that the installed screen actually exposes.
If you need help validating UPC Code or other partner item mappings, resolving unmapped order lines, or documenting warehouse and availability precedence, visit https://biz-techservices.com to work with the Biz-Tech Services Acumatica EZCom EDI Integrator.
