To map Salesforce products to Acumatica items, match Salesforce Product SKU to the Acumatica Inventory CD. The integration guide says the import looks up Inventory CD using Product SKU. A match retrieves the existing item. If there is no match, the Import Item setting determines whether the integration may create a new item or stops with a missing-item error.
That is the documented identity rule for the Biz-Tech Services Salesforce Acumatica Connector. Item Details also shows Salesforce ID, product code, product name, price, and weight after synchronization, but the guide does not make any of those values an alternate key for the SKU lookup.
Check the Salesforce Store Item Settings
The Biz-Tech Services Acumatica Salesforce Connector places product controls in Salesforce Store under Item Settings. Review the settings before you import an order or synchronize the catalog:
Import Item allows new ERP items to be created from Salesforce products when selected. When cleared, the item must already exist in the ERP.
Add Items in Inventory Sync enables synchronization with Salesforce items.
Use Numbering Sequence for Product ID Generation generates a unique product ID for a new product from a predefined numbering sequence.
The guide does not identify item class, stock status, unit of measure, or a default warehouse as item-creation rules in this section. Set those requirements separately with the implementation team instead of assuming the checkbox supplies them.
Salesforce Product Mapping, Step by Step
The practical sequence is short. Use a small, known set of products to test the decisions before opening the full catalog.
Identify each Salesforce Product SKU and the Acumatica Inventory CD it should resolve to. Correct mismatches in the source records or target item setup before import.
Decide whether Import Item may create missing items. Leave it cleared when every imported product must match an existing Inventory CD.
In Salesforce Store, use Item Details and Load Acumatica items to display existing ERP items for review.
Use Sync all from Salesforce when the approved task is to retrieve and create Salesforce items in Acumatica. Use Sync to Salesforce when approved Acumatica items should be created or updated in Salesforce.
After a test, review Salesforce ID, product code, product name, price, and weight in Item Details. Confirm that the intended item was used or created.
For order retrieval and import steps, see the related lesson, How to Import Salesforce Orders into Acumatica.
What Happens to an Unmatched SKU?
The Biz-Tech Services Salesforce Acumatica Integration guide gives one explicit item-mapping exception. With Import Item cleared, a Salesforce Product SKU that does not find an Inventory CD produces the message ‘The item {0} does not exist in the system.’ The source prints the placeholder {0}; it does not show a completed example with a product value.
With Import Item selected, the guide says new ERP items are created based on configured settings. It does not name every required field or explain whether a duplicate Salesforce product can produce a duplicate item. Test creation with one product and review the resulting record before using the option at scale.
The guide does not describe an unmapped-product queue or a retry workflow. For a failed import, start by comparing Product SKU with Inventory CD and confirming the Import Item choice. Record any additional behavior seen in your own environment before making it an operating rule.
Cross-References, Aliases, and Item Classes
The Biz-Tech Services Acumatica Salesforce Integration has Cross-Reference Options and a Cross-Reference tab, but the guide’s examples are Payment, Country, and Ship Via. It does not identify product aliases or alternate item IDs as Cross-Reference mappings. Product SKU to Inventory CD remains the documented item lookup.
The guide also does not state how the lookup handles letter case, leading zeros, punctuation, or multiple aliases. If two identifiers could be interpreted as the same product, settle the intended SKU and Inventory CD before a live import. That review is an implementation check, not a connector rule described by the manual.
Customer Class appears elsewhere in the Salesforce Store settings for customer creation during order import. It is not an Item Class setting. The source gives no item-class mapping rule.
Price Books Follow the Product Relationship
Price Book Details and Salesforce Price Books handle membership and list price after products are available. The guide says an item must first be included in the standard price book before it is added to another price book. It also says a product already in a Salesforce price book is brought into Acumatica through order import and added to the corresponding price book.
Export Salesforce Price Books processes selected or all price books, while the guide says only changed items are exported. These screens help verify where a product appears and its list price; they do not provide a second documented SKU-matching rule.
Where to Check Your Mapping
The Biz-Tech Services Salesforce Acumatica Integrator provides these checkpoints in the manual:
Salesforce Store > Item Settings: confirm Import Item, Add Items in Inventory Sync, and product ID numbering choices.
Item Details: compare Salesforce ID, product code, product name, price, and weight with the intended item.
Load Acumatica items: display the available ERP items before synchronizing.
Import Salesforce Orders: use Get Orders and then Import or Import All only after testing the SKU match on a small set.
Salesforce Price Books: check standard price book membership and the desired list price where price books are in scope.
The manual supplies no Acumatica screen IDs for Salesforce Store, Item Details, or its price-book screens. Use their displayed names rather than assuming an ID.
Salesforce Product Mapping: Frequently Asked Questions
Which field connects a Salesforce product to an Acumatica item?
Salesforce Product SKU is used to search Acumatica Inventory CD during import.
What if Product SKU does not match an Inventory CD?
With Import Item cleared, the documented error says the item does not exist. With Import Item selected, the integration can create an item according to configured settings.
Does Salesforce ID replace Product SKU as the lookup key?
The guide displays Salesforce ID in Item Details but does not say it replaces the Product SKU lookup.
Can the Cross-Reference tab hold product aliases?
The guide does not document that use. Its Cross-Reference examples are Payment, Country, and Ship Via.
Does Item Class control mapping or item creation?
No item-class rule is specified in the product section. Customer Class is a separate customer-import setting.
Where can I verify a synchronized product?
Open Item Details and review the Salesforce ID, product code, product name, price, and weight. Compare them with the intended ERP item.
Confirm the SKU Rule Before Expanding the Catalog
The safest test is one known match and one intentionally unmatched SKU. Check which item the first resolves to and how the second behaves under the chosen Import Item setting. Keep the result with your implementation record, especially when product IDs or price books are also synchronized.
For help reviewing the Product SKU to Inventory CD rule in your setup, contact the Biz-Tech Services Acumatica Salesforce Integrator team at https://biz-techservices.com.
