How to Map Inventory IDs for Acumatica Imports with Biz-Tech AI Analyst
Biz-Tech AI Analyst can design an Acumatica Import Scenario from an attached Excel or CSV file, including the mapping from spreadsheet columns to the selected entry screen. For an inventory import, the important review is whether the file's item identifier points to the intended Acumatica Inventory ID. The product page says AI Analyst checks key and required fields, then shows its proposed mapping for approval. Your team still prepares and imports the data.
That approval step is where a supplier SKU, legacy product code, or blank identifier should be resolved. AI Analyst's published description does not promise automatic SKU matching or item creation from an unmatched code. Treat the proposal as a design to inspect, using a small sample file before it is used with a full catalog.
What AI Analyst Builds for an Inventory Import
A user attaches an Excel or CSV file and describes the intended import in the AI Analyst screen. The assistant selects an Acumatica entry screen, maps file columns, checks required fields and keys, and presents a plain-language proposal. The preview identifies the import mapping and any limitations or Heads up notes. The user can request changes; the Data Provider and Import Scenario are created only after approval.
Acumatica uses the Data Provider to define the external file's columns and the Import Scenario to map those columns to fields on a data-entry form. The scenario is specific to the selected form and the file schema. A design for new stock items therefore needs a different review from a design that updates existing items or imports transaction lines.
Inventory ID Mapping at a Glance
Use this sequence while reviewing an AI Analyst proposal:
Identify the source column that holds the item's code. Record whether it contains Acumatica Inventory IDs, supplier SKUs, customer part numbers, or mixed values.
Confirm the selected Acumatica entry screen and the target field for that source column. The proposed destination must match the job: item maintenance, a document line, or another entry form.
Ask which source columns satisfy the key and required target fields. A description or display name should not silently stand in for the item identifier.
Separate unmatched, duplicate, or ambiguous codes in the sample file for a human decision. Do not approve an assumed match when two Acumatica items could fit.
Approve the mapping only after the sample rows show the intended target. The team then uses Acumatica's Prepare and Import actions and reviews the results.
Define What the Source Item Code Means
Start with the actual header and values in the spreadsheet. A column named SKU may be your company's Inventory ID, a vendor's number, or a code left over from another system. Those meanings lead to different mappings. Keep a few representative rows that include a known item, a code that does not exist in Acumatica, a blank value, and a duplicate. This is an editorial test set for reviewing the proposal, not a claim that AI Analyst classifies those cases automatically.
Acumatica identifies stock and non-stock items by Inventory ID. Its Stock Items (IN202500) and Non-Stock Items (IN202000) forms can also hold alternate IDs on the Cross-Reference tab. If the source file uses an alternate ID, confirm how the chosen import form and scenario will interpret it. An alternate ID that works in one Acumatica entry field does not by itself prove that this import design will resolve it correctly.
Check the Target Screen, Keys, and Required Fields
The target screen determines what a row will do. An import to Stock Items (IN202500) can maintain stock-item records; a transaction-line import has a different destination and document context. Ask AI Analyst to show the target screen and each source-to-target field pair in its proposal. Confirm whether the job is creating items, changing existing items, or referencing items on another record before approving the design.
The product page says AI Analyst checks key and required fields, but it does not publish a universal field list for inventory imports. Your tenant's configuration, custom fields, and chosen screen can change the requirements. Review the proposal against the actual Acumatica form. If the key is missing or points to the wrong spreadsheet column, revise the design before a Data Provider and Import Scenario are built.
AI Analyst works from a catalog of fields and relationships in the customer's Acumatica environment, including fields added by published customizations. This gives the proposal a tenant-specific basis. It does not replace the team's decision about which external code identifies the right product.
Handle Unmatched and Duplicate Items Before Approval
For each source code that lacks a clear match, decide whether it represents a new item, a missing cross-reference, or an error in the file. Record that decision outside the import proposal if needed. The AI Analyst product description does not specify an unmatched-item queue, a duplicate-SKU rule, or an automatic alias resolution process, so those behaviors should not be assumed.
Review a small file first. Check leading zeros and punctuation in codes, repeated identifiers, and any rows that combine stock and non-stock products. These are practical file checks, not AI Analyst features promised by the product page. If a sample row could update the wrong item, correct the source file or mapping proposal and test again.
Prepare, Import, and Inspect the Result
Approval creates the Data Provider and Import Scenario. It does not run the import. On Import Scenarios (SM206025), the team can inspect the selected provider, target screen, and mapping. On Import by Scenario (SM206036), Prepare loads rows for review without importing them. The Prepared Data area shows errors on affected rows. Import is a separate action that processes the prepared rows.
Run the sample through Prepare first, inspect the selected target values and errors, and correct the file or scenario before importing. After Import, check the target Acumatica records against the sample. A successful processing status is useful, but the business check is whether the intended Inventory ID was created, updated, or referenced. Keep the approved proposal and the sample results for the next file revision.
Where to Check Your Work
AI Analyst proposal: review the entry screen, column mapping, limitations, and approval record; confirm the key and required-field decisions before approval.
Data Providers (SM206015): confirm the attached file schema and source columns.
Import Scenarios (SM206025): inspect the scenario's target form and Mapping tab.
Import by Scenario (SM206036): use Prepare to review rows and the Error column before Import.
Stock Items (IN202500) or Non-Stock Items (IN202000): compare the resulting item with the source sample when those forms are the intended target.
Inventory ID Import Mapping: Frequently Asked Questions
Does AI Analyst import the inventory records for me?
No. Biz-Tech's product page says AI Analyst creates the Data Provider and Import Scenario after approval. Your team controls Prepare and Import.
Can a supplier SKU be used as the Acumatica Inventory ID?
That is a mapping decision, not a published automatic rule. Confirm whether the source code is the intended Inventory ID or an alternate ID, then test the proposed mapping on the selected entry screen.
What if a source item has no match?
The product description does not define an automatic unmatched-item workflow. Hold that row for a human decision about creating an item, correcting the file, or maintaining an appropriate cross-reference.
Will AI Analyst catch duplicate SKUs?
No duplicate-SKU behavior is documented. Put repeated and ambiguous codes in the sample review and verify the resulting mapping before a full import.
Where do I see import errors before records change?
Acumatica's Import by Scenario (SM206036) form lets the team run Prepare and review prepared rows and errors before choosing Import.
Can I change the mapping before it is built?
Yes. AI Analyst presents the proposal in plain language, accepts refinements in the conversation, and builds only after the user approves it.
Review the Mapping with Your Team
The safest starting point is one representative file and a precise definition of each item identifier. Let AI Analyst propose the scenario, then review the key, destination fields, and exceptions with the people who own the item catalog. They retain the final control over Prepare and Import.
Bring a sample inventory file to a Biz-Tech AI Analyst demonstration. Visit https://biz-techservices.com to discuss the mapping and approval steps with Biz-Tech Services.
Sources: Biz-Tech Services, Biz-Tech AI Analyst, https://biz-techservices.com/biz-tech-ai-analyst; Acumatica, Import Scenarios (SM206025), https://beacon.acumatica.com/r/Form-Reference-Guide/Integration-Forms/Import-Scenarios; Acumatica, Import by Scenario (SM206036), https://beacon.acumatica.com/r/Form-Reference-Guide/Integration-Forms/Import-by-Scenario; Acumatica, Stock Items: Identifiers of Items, https://beacon.acumatica.com/r/Inventory-Management-Guide/Creating-Stock-Items/Stock-Items-Identifiers-of-Items.
How to Map PayPal Invoice Lines to Acumatica Items
The PayPal integration guide does not document a way to map PayPal invoice lines to Acumatica Inventory IDs, stock items, or non-stock items. Its documented workflow creates a PayPal invoice from an Acumatica sales order, accounts receivable invoice, or payment amount and then tracks the resulting payment at the document and application level.
The Biz-Tech Services PayPal Acumatica Connector sends payment requests and stores PayPal invoice identifiers, URLs, statuses, transaction IDs, refund IDs, and paid amounts. The source does not name a SKU, Inventory ID, item class, item alias, or product cross-reference field. Item mapping therefore remains outside the documented PayPal customization workflow.
What the PayPal Connector Sends from Acumatica
The Biz-Tech Services Acumatica PayPal Connector creates a PayPal payment request from one of three Acumatica entry points. A user can start from Sales Orders, from an Invoice, or from Payments and Applications. All three paths create or use an AR Payment, send a PayPal invoice to the customer's email, and place the payment on Hold with a Sent status.
From Sales Orders, Create Payment reads the order total, currency, and customer details. After Cash Account and Payment Reference are supplied, Request PayPal Payment creates an AR Payment linked to the order and stores PayPal Invoice ID, Invoice URL, and Invoice Number on the payment.
From the documented Invoice workflow, Request PayPal Payment creates a payment pre-applied to the invoice. The PayPal invoice amount matches the outstanding balance. The guide does not state that Acumatica invoice lines are copied, matched, or recreated as PayPal invoice lines.
PayPal Invoice Line Mapping at a Glance
The source supports the following conclusions about the boundary between item records and PayPal payment requests.
1. Sales Orders can supply order total, currency, and customer details to the payment request
2. An accounts receivable invoice can supply its outstanding balance to the PayPal invoice amount
3. A standalone payment can supply a customer, PayPal payment method, email, amount, and optional description
4. Orders to Apply and Documents to Apply can associate a payment with a Sales Order or Invoice
5. PayPal fields are stored on the AR Payment and related ARAdjust and SOAdjust application records
6. No documented field maps a PayPal line description or product code to an Acumatica item
Sales Orders Supply Totals Rather Than Documented Item Mappings
The Sales Order path starts on Sales Orders. Create Payment reads the order total, currency, and customer details, and the resulting AR Payment remains accessible from the order's Payments tab. The source describes the payment link to the order, not a line-by-line link to inventory records.
No PayPal line-item table, Inventory ID field, quantity field, unit price field, or product identifier is listed in this workflow. The documentation also does not say whether the customer sees one summarized PayPal invoice line or several lines. Any such behavior would need confirmation outside the supplied guide.
The payment application preserves a document relationship, but a document relationship is not an item cross-reference. The source does not provide evidence that changing an Acumatica sales order line changes an already sent PayPal invoice or that PayPal can update an inventory item.
AR Invoices Supply the Outstanding Balance
The Invoice path is designed for billing that has already been posted. Request PayPal Payment creates a payment pre-applied to the invoice, sends the PayPal invoice, and puts the payment on Hold. The source states that the PayPal amount matches the outstanding balance on the AR invoice.
Outstanding balance is the only invoice-content rule documented for this path. The guide does not mention invoice-line descriptions, Inventory IDs, quantities, item classes, tax categories by line, discounts by line, or line-level references in the PayPal request.
The Payment Method ID becomes locked once an invoice has been sent. That rule protects the PayPal payment method assignment; it is not an item-mapping lock or a line validation rule.
Standalone Payments Have No Required Item Context
Payments and Applications supports a standalone payment, such as a deposit that is not tied to a specific document. The user selects the customer and PayPal payment method, reviews PayPal Customer Email, enters the payment amount and an optional description, and sends the request.
A payment can optionally be applied to a Sales Order or Invoice through Orders to Apply or Documents to Apply. The source does not require an Inventory ID or item line for a standalone request. This confirms that the documented PayPal process operates at the payment and document level.
The optional description is not defined as a SKU, alias, inventory description, or matching key. The guide provides no rule for using it to identify an Acumatica item.
Cross References Aliases and Unmapped Items Are Not Documented
The Biz-Tech Services PayPal Acumatica Integration documentation contains no item cross-reference screen, alias table, SKU lookup, Inventory ID field, product-code mapping, item-class default, or unmapped-product queue. It does not describe any record that pairs a PayPal value with an Acumatica item.
No behavior is defined for an unknown PayPal product, duplicate product code, blank item value, different letter case, leading zeros, stock versus non-stock items, or multiple external aliases for one local item. The source also does not describe creating inventory records from PayPal data.
The only related line records named by the guide are ARAdjust and SOAdjust. The PayPal custom fields are available on those applied-to lines so payment status information remains consistent across related records. The guide does not identify either record as an invoice-item mapping table.
PayPal Fields Track Payment Status Not Inventory Items
The custom fields added to the AR Payment screen are PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Status, PayPal Invoice Number, Transaction ID, PayPal Invoice URL, Refund Number, and PayPal Paid Amount. Each field supports payment delivery, status checks, or refund tracking.
The processing screen also displays Payment Ref, Customer, Customer Email, Currency and Amount, Sales Order, Invoice Number, PayPal Invoice Number, PayPal Status, and Transaction ID. None of the documented columns identifies an item, SKU, quantity, warehouse, item class, or product alias.
PayPal Invoice Status can be Sent, Partially Paid, Paid, Cancelled, Refunded, or Partially Refunded. These statuses govern the AR Payment lifecycle and do not validate invoice-line-to-item matching.
Validation Rules Apply to Payments and Requests
The guide documents validation and troubleshooting for PayPal credentials, customer email, invoice status, release eligibility, and refunds. Test Connection validates the API credentials on Payment Methods. A Customer Payment Method supplies the customer's PayPal email address.
A payment must not have been sent previously before Send PayPal Request is used. A payment still in Sent status cannot be released because PayPal has not confirmed payment. Refunds require a Paid PayPal state and a fully released local payment. These are payment-level rules.
The source gives no item-mapping validator, line-error field, item exception log, or rule that blocks a PayPal request when an Acumatica invoice contains a particular item. It does not provide an item reconciliation screen after the request is sent.
Where to Check the Documented PayPal Data
The Biz-Tech Services PayPal Acumatica Integrator exposes payment and document evidence in the following documented screens and fields. None is identified as an item-mapping review.
1. On Sales Orders (SO301000), review the Payments tab and linked AR Payment
2. On Payments and Applications (AR302000), review PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Number, PayPal Invoice URL, and PayPal Invoice Status
3. Review Orders to Apply and Documents to Apply for document-level applications
4. On the Check PayPal Payment Status processing screen, review Sales Order and Invoice Nbr links
5. Review Currency and Amount, PayPal Status, Transaction ID, and PayPal Paid Amount for payment reconciliation
6. Treat the absence of Inventory ID, SKU, quantity, item class, and alias fields as a documented scope boundary
PayPal Invoice Line Mapping Frequently Asked Questions
Does the PayPal integration map invoice lines to Inventory IDs?
The Biz-Tech Services Acumatica PayPal Integration guide does not document that capability. It describes totals, outstanding balances, payment applications, and PayPal status fields, but it names no Inventory ID or item-mapping field.
Does PayPal receive the sales order line items?
The source says the Sales Order workflow reads the order total, currency, and customer details. It does not say that individual order lines are sent.
What amount is used when the request starts from an AR invoice?
The PayPal invoice amount matches the outstanding balance on the AR invoice. No line allocation rule is supplied.
Can an item SKU be stored in the payment description?
The standalone payment accepts an optional description, but the guide does not define it as a SKU, item alias, or product-matching field.
Are ARAdjust and SOAdjust item mapping records?
The source says PayPal fields are available on ARAdjust and SOAdjust applied-to lines to keep status information consistent. It does not describe them as item cross-reference records.
Does the connector create missing Acumatica items from PayPal?
No item-creation workflow is documented. The customization creates and updates AR Payments and PayPal invoices, not inventory records.
Can item classes or aliases control PayPal invoice content?
The guide does not mention item classes, item aliases, alternate product IDs, or rules that use them to build a PayPal invoice.
Where should item mapping be validated?
The supplied PayPal documentation gives no item-mapping validation screen. Item accuracy must be established in the source Acumatica document or another documented product process before a PayPal request is created.
Work With Biz Tech Services on PayPal Payment Requests
The documented PayPal customization sends document-level payment requests and tracks their status through AR Payment fields and application records. It does not define product, SKU, item-class, alias, or line-level Inventory ID mapping.
If your team needs help confirming the boundary between Acumatica document data and PayPal payment requests, the Biz-Tech Services Acumatica PayPal Integrator can support your implementation. Visit https://biz-techservices.com to contact Biz-Tech Services or schedule a personalized demonstration.
Check the video lesson here: https://www.youtube.com/watch?v=wkjPKdLzv2M
How to Map Magento Products to Acumatica Inventory Items
Mapping Magento products to Acumatica inventory items starts with the Magento Product SKU and the Acumatica Inventory CD. During item or order import, the connector searches Inventory CD using the Magento Product SKU, retrieves the matching item when it exists, and follows the configured Import Item or Replace Missing Products rule when it does not.
The Biz-Tech Services Magento Acumatica Connector also stores Magento Product SKU, Acumatica Inventory ID, and Magento Product ID values for later synchronization. This guide focuses on that product relationship, item defaults, attribute mapping, missing-product handling, and validation. Earlier connector articles cover connection, general configuration, data flow, order import, and inventory synchronization in their own workflows.
Magento Product Mapping Prerequisites
The Biz-Tech Services Acumatica Magento Connector is installed through Customization Projects (SM204505). After publication, Magento Credentials establishes the Store Code and connection settings, while Magento Store controls item import and creation, cross-references, warehouse settings, and other connector behavior.
The product-mapping controls are distributed across Item Information, Inventory Details, Inventory Mappings, Attribute Details, and Category Details. Item Information defines the SKU lookup and defaults for new items. Inventory Details loads products from both systems and stores product identifiers. Inventory Mappings connects Acumatica Attributes and User Defined Fields to Magento attributes.
Before mapping products, confirm which process will run. Sync from Magento and Import Magento Items bring store data into the ERP. Sync to Magento and Export Magento Items send ERP item data to the store. Each direction uses the stored product identity, but the source gives its most explicit matching rule for import.
Magento Product Mapping Step by Step
Use this sequence to establish and verify the product relationship.
1 Open Magento Store for the intended Store Code and review Item Information.
2 Decide whether Import Item should be selected. When selected, the connector can create a new Acumatica item when the Magento Product SKU does not match an existing Inventory CD.
3 If new items may be created, set Import Item Type, Item Class, UOM, and the other documented item defaults required by the business.
4 If Import Item is disabled, decide whether Replace Missing Products should substitute the selected item for an unmatched product during order import.
5 On Inventory Details, use Load Acumatica items and Load Magento Items to retrieve the product records available in each system.
6 Confirm that Magento Product SKU and Acumatica Inventory ID identify the intended pair before selecting the record for synchronization.
7 For attribute mapping, configure Inventory Mappings with the relevant Acumatica Attribute or User Defined Field and the corresponding Magento attribute.
8 On Attribute Details, use Load Active Attribute Options only after the required attribute properties are present in Inventory Mappings.
9 Run Sync from Magento or use Import Magento Items, then confirm that the existing item was retrieved or that a new item was created according to Item Information.
10 After export to Magento, confirm Magento Item and Magento Product ID on the item record and verify the identifier on the Magento Inventory tab.
SKU and Inventory CD Matching
The source defines one direct identity rule for import. The connector searches Inventory CD using Magento Product SKU. If it finds a match, it retrieves that item. This is the documented product-level match used when store data enters the ERP.
If no Inventory CD matches and Import Item is selected, a new item is created using the configured Import Item Type, Item Class, and UOM. Import Items on Inventory Details Tab can place items on Inventory Details while orders are imported. Date Last Received Item records the last date used to retrieve products.
Inventory Details also provides Get Item, which retrieves a specified item by SKU or Name. The source does not explain whether Name is a secondary identity rule during normal import, so the documented SKU-to-Inventory-CD search should remain the primary mapping assumption.
For quantity export, the source says Magento Product SKU and Acumatica Inventory ID must be set on Inventory Details before an item appears on Export Magento Inventory Quantities. These two stored values provide a direct review point for the mapped pair.
Unmatched Products and Replace Missing Products
When Import Item is not selected, the connector prohibits import and creation unless the corresponding item already exists in Acumatica. If the Magento Product SKU does not resolve to an Inventory CD, the documented error is “The item {0} does not exist in the system”. The placeholder represents the item value used by the process.
Replace Missing Products provides a separate order-import fallback. When Import Item is disabled, it replaces source items that do not exist in the ERP with the selected item. The documentation does not name an unmapped-record queue or describe how the original product is retained on the resulting line, so users should validate the order line before processing it further.
The source does not explain what happens when two records share a candidate SKU, when the source system contains duplicate SKU values, or when Magento Product SKU conflicts with a stored Magento Product ID. It also does not document retry counts, an Unmapped status, or a dedicated product-mapping error inquiry.
Item Class and Default Item Values
The Biz-Tech Services Magento Acumatica Integration uses Item Class as a default for items created during import. The documentation says Item Class groups stock or non-stock items with similar properties and provides default settings for new items.
Import Item Type determines the type of item created, while UOM defines its unit of measure. Warehouse ID is the default warehouse on imported orders. These settings support item creation and order processing, but they do not change the documented SKU-to-Inventory-CD identity rule.
The source does not describe a mapping between product categories and Acumatica Item Class. Category Details can import or export product categories, but Item Class is configured separately under Item Information. Do not treat a store category as an automatic Item Class selector without additional approved documentation or testing.
Inventory Mappings for Attributes and User Defined Fields
Inventory Mappings allows Acumatica Attributes and User Defined Fields to synchronize with store attributes. The user adds the properties of a particular attribute selected on the Attributes tab of the Item Class screen. The documentation does not list the exact grid columns for this mapping, so only the named screens and actions should be treated as confirmed.
Attribute Details loads the active options for a particular attribute after its properties have been added to Inventory Mappings. Use Load Active Attribute Options to retrieve them. The Magento Property attribute must already exist in the store, or synchronization cannot proceed.
The source also requires the Acumatica attribute Control Type to match the Magento Attribute Control Type before active options can be retrieved. This is an explicit attribute validation rule. It validates field compatibility, not the SKU or product identifier.
Cross References Categories and Product Aliases
Cross-Reference Options selects the entities that should be matched between the two systems. The Cross-reference section then shows enabled entities in the Field list. Magento Value and Ship Via are described as the matching source and ERP values.
The documentation does not identify product SKU, Inventory CD, Inventory ID, or product alias as a cross-reference entity. It does not describe alternate IDs, manufacturer numbers, customer part numbers, alias priorities, or an alias lookup sequence. Therefore, the Cross-reference process should not be presented as documented product-alias support.
Category Details has a different purpose. Get Magento Categories retrieves product categories, and Sync Magento categories creates or updates categories in the store. Product categories can also be exported and imported as an Excel document. Category synchronization does not replace the SKU mapping or the separate Item Class default.
Inventory Details and Magento Product IDs
Inventory Details is the central review screen for the relationship after products are loaded. Load Acumatica items retrieves stock and non-stock items. Load Magento Items retrieves store products. Sync to Magento exports selected ERP items, while Sync from Magento imports selected store items.
After an ERP item is created in the store, the platform generates a unique ID. The source says that ID appears in Magento Store and on the Stock Items Magento Inventory tab. The Magento Item checkbox is selected and Magento Product ID is added after item synchronization.
Export Magento Items requires Magento Product SKU on the Magento Inventory tab before an item appears on the processing screen. After synchronization, Price, Description, Weight, Length, Height, Width, and Category are updated in the store. If the connector does not find the item there during synchronization, the source says it creates the item automatically.
The source does not define a precedence rule among Magento Product SKU, Magento Product ID, and Name after these values have been stored. For audits, confirm that all available identifiers point to the same product rather than relying on one field in isolation.
Where to Check Your Work
The Biz-Tech Services Magento Acumatica Integrator provides these documented review points for product mapping.
1 On Item Information, verify Import Item, Import Item Type, Item Class, UOM, Replace Missing Products, and Import Items on Inventory Details Tab.
2 Confirm that Magento Product SKU matches the intended Inventory CD.
3 On Inventory Details, compare Magento Product SKU and Acumatica Inventory ID before saving or synchronizing a record.
4 Use Load Acumatica items and Load Magento Items to confirm that both sides of the intended relationship are available.
5 After Sync from Magento or Import Magento Items, confirm that the correct item was retrieved or created.
6 After Sync to Magento or Export Magento Items, verify Magento Item and Magento Product ID on the Magento Inventory tab.
7 On Inventory Mappings, confirm that each Acumatica Attribute or User Defined Field points to the intended Magento attribute.
8 On Attribute Details, confirm that active options load and that the Acumatica and Magento Control Type values match.
9 When a product cannot map, review the missing-item error and determine whether Import Item or Replace Missing Products should apply.
10 For quantity export, confirm that the item was selected and saved on Inventory Details and that Magento Product SKU and Acumatica Inventory ID are both set.
Magento Product Mapping Frequently Asked Questions
What field matches a Magento product to an Acumatica item?
The documented rule uses Magento Product SKU to search Acumatica Inventory CD. A matching Inventory CD retrieves the existing item.
What happens when Magento Product SKU does not match an item?
If Import Item is selected, a new item can be created using the configured item defaults. If it is disabled, the process displays The item {0} does not exist in the system unless Replace Missing Products supplies the selected fallback item during order import.
Can Magento products use an Acumatica Item Class?
Yes. Item Class is a documented default for imported items created in Acumatica. The source does not document automatic mapping from a Magento category to Item Class.
Does Cross Reference support product aliases?
The Biz-Tech Services Acumatica Magento Integration documents cross-references for enabled entities and describes Magento Value matched to Acumatica Ship Via. It does not identify product aliases, alternate IDs, SKU, or Inventory CD as cross-reference entities.
How are Magento attributes mapped to Acumatica?
Use Inventory Mappings to connect Acumatica Attributes or User Defined Fields with Magento attributes. Add the attribute properties from the Item Class Attributes tab, then load active options through Attribute Details.
Why will active attribute options not load?
Confirm that the Magento Property attribute exists in Magento and that its Attribute Control Type matches the Acumatica attribute Control Type. The source says active options cannot be retrieved when the control types do not match.
Where is Magento Product ID stored after synchronization?
The generated ID appears in Magento Store and on the Stock Items Magento Inventory tab. The Magento Item checkbox is also selected after synchronization.
Where can I review unmapped Magento products?
The source does not identify an unmapped-product queue or product-specific mapping inquiry. Review Item Information, Inventory Details, Magento Product SKU, Acumatica Inventory ID, and the documented missing-item error.
Work With Biz Tech Services Magento Mapping
A reliable Magento product mapping starts with a consistent Magento Product SKU and Inventory CD, then uses Item Information for item-creation defaults and Inventory Mappings for attributes. Inventory Details and the stored Magento Product ID provide the practical checkpoints after synchronization.
For help configuring and validating the Biz-Tech Services Acumatica Magento Integrator, visit https://biz-techservices.com to learn more about Biz-Tech Services and schedule a personalized consultation.
How to Map CommerceHub Items to Acumatica Inventory IDs
Mapping CommerceHub items to Acumatica Inventory IDs is performed on the Cross-reference tab of the CommerceHub Mappings screen. The documented purpose of that tab is to associate an Acumatica item with the Item ID contained in the inbound file during order import.
The Biz-Tech Services CommerceHub Acumatica Connector uses a file-based Secure File Transfer Protocol, or SFTP, flow rather than direct application programming interface requests.
What CommerceHub Item Mapping Does
The Biz-Tech Services Acumatica CommerceHub Connector uses the Cross-reference tab to map Acumatica items to the Item IDs contained in CommerceHub files during order import. The source identifies the two sides of the relationship at a high level: the Acumatica item and the external file Item ID.
The Mappings screen controls connector behavior for import, export, and synchronization. Store Codes provide distinct configurations for specific processes, with parameters such as Transaction Type, Description, Default Customer, and Document type. Item mapping should therefore be reviewed in the store and process context used for the inbound order file.
The source does not name the individual Cross-reference grid fields, a match button, or a save sequence. It also does not say whether the Acumatica side displays Inventory ID, Inventory CD, a description, or another item field. Use only the controls visible in the installed Mappings screen.
CommerceHub Item Mapping at a Glance
Use this sequence to configure and test the documented file Item ID relationship.
1. Open the CommerceHub workspace that appears after the connector customization is published.
2. Open Mappings and select the Store Code used for the relevant order-import process.
3 Confirm the store parameters, including Transaction Type, Description, Default Customer, and Document type, before changing item cross-references.
4. Open Cross-reference and associate each inbound file Item ID with the intended Acumatica inventory item.
5. Retrieve a purchase order with Import Purchase Orders for the same Store Code.
6. Process one selected order and confirm the resulting item lines on Sales Orders before using Process All.
7. Review Error Log, CommerceHub Errors, and Import Failed Purchase Orders when an item or order does not process as expected.
8. Keep Inventory Template selection separate from inbound Cross-reference mapping because it controls which items appear for inventory quantity export.
Select the Store and Process Context
CommerceHub data moves through text files over SFTP. The manual describes a path through FileZilla between CommerceHub and Acumatica in both directions. Because the transfer is file-based, the Item ID in the file is the documented external side of the item cross-reference.
Store Codes allow individual configuration for different import and export operations. The source names Inventory, Item, and Shipment as examples of processes that can have distinct parameters. Before reviewing an item mapping, confirm that the selected Store Code belongs to the inbound order process under test.
The documentation does not explain whether a Cross-reference row is shared among Store Codes or isolated by Store Code, Transaction Type, or process. It does not define what happens when the same file Item ID exists in more than one configuration. Treat each configured process as separate until its behavior is confirmed in the installed connector.
Map the File Item ID to an Inventory Item
The Cross-reference tab maps Acumatica items to their respective Item IDs contained within the file during order import. This is the only documented product-to-item identity rule in the manual.
The source does not provide a sample value or screen-level field list. It does not say whether the external Item ID is an SKU, universal product code, vendor part number, retailer item number, or CommerceHub internal identifier. It also does not define the file name, record type, or column in which the Item ID appears.
The Biz-Tech Services CommerceHub Acumatica Integration should therefore be configured from the actual inbound file and the fields exposed by Cross-reference. Do not relabel the external value as an SKU or alias unless that meaning is confirmed by the CommerceHub file specification used by the implementation.
No bulk mapping import, spreadsheet loader, wildcard, automatic item creation, or default replacement item is documented. The manual also does not explain whether one file Item ID may map to multiple inventory items or whether duplicate rows are rejected.
Validate the Result on an Imported Sales Order
Import Purchase Orders retrieves CommerceHub purchase orders for a selected Store Code. Process imports selected records, while Process All imports every order shown. The imported document appears on Sales Orders.
A controlled validation should use one order first. Compare each source file Item ID with the corresponding item on the created sales order line. The manual does not name a dedicated mapping status, resolved-item field, or line-level diagnostic, so the resulting sales order is the documented business record available for comparison.
Customer handling is independent of item matching. Customers are not imported from CommerceHub; the connector assigns the Default Customer and overrides the address on the Sales Order Addresses tab with the actual address received from the order. A correct customer or address does not prove that item IDs were mapped correctly.
The source gives no formal item-mapping validation rule and no exact message for an unknown Item ID. It does not state whether one unmapped item blocks the full order, creates a partial order, or sends the record directly to Import Failed Purchase Orders.
Separate Inbound Mapping from Inventory Template
Cross-reference supports inbound order item resolution. Inventory Template supports outbound inventory quantity selection. When Inventory IDs are selected and saved on Inventory Template, the associated items appear on Export CommerceHub Inventory.
Warehouse Details also belongs to quantity export rather than inbound item identity. It selects warehouses and sets the Quantity basis to On Hand Quantity, Available Quantity, or Available for Shipment Quantity. These settings decide which quantity is exported; they do not map a file Item ID to an order-line item.
The source does not explain whether the Inventory IDs saved in Inventory Template must already have Cross-reference rows, whether an outbound inventory file uses the same CommerceHub Item ID, or how that external identifier is written to the export file. Do not assume that selecting an item for quantity export creates its inbound cross-reference.
Use Error Screens Without Inventing Failure Behavior
The Mappings screen includes Error Log. The documentation says errors encountered during order import and export are displayed there for review and resolution. Purge Logs deletes all error messages from the tab.
CommerceHub Errors is another screen that displays errors received from CommerceHub for various processes. Import Failed Purchase Orders allows orders that failed on Import Purchase Orders to be imported again after selecting a Store Code.
The manual does not connect a specific item-mapping error to one of those locations. It provides no error codes, message examples, failed-line fields, or correction workflow. Review all three places when a mapped item does not produce the expected sales order line, but do not claim that a particular screen always owns the error.
Purge Logs removes messages, so preserve the information needed for diagnosis before using it. The source does not state whether purging errors changes the failed order itself, its source file, or eligibility for Import Failed Purchase Orders.
Document Alias Item Class and Matching Gaps
No item alias mechanism is documented. The manual does not mention alternate IDs, customer part numbers, vendor part numbers, SKUs, barcodes, global trade item numbers, case normalization, wildcard values, or identifier precedence. It names only the Item ID contained within the file.
Item classes are also absent. There is no item-class default, class-based filter, inheritance rule, or instruction to restrict a CommerceHub Item ID to a class of inventory items.
Unmapped-record behavior is not defined. The source does not identify an automatic item-creation option, replacement item, queue, partial-import rule, or mapping suggestion. It also does not explain how a corrected cross-reference is applied to an order that already failed.
No CommerceHub screen ID is provided anywhere in the manual. The Mappings, Import Purchase Orders, Import Failed Purchase Orders, CommerceHub Errors, Export CommerceHub Inventory, and Sales Orders screens are named, but their IDs must not be inferred.
Where to Check Your Work
The Biz-Tech Services CommerceHub Acumatica Integrator exposes the documented mapping and result across these screens and tabs.
1 Mappings: confirm the Store Code and process parameters before reviewing item cross-references.
2 Cross-reference: compare the inbound file Item ID with the selected Acumatica item.
3 Import Purchase Orders: retrieve the order for the same Store Code and process one selected record.
4 Sales Orders: compare each imported line with the source Item ID and the intended Acumatica inventory item.
5 Error Log: review import or export messages before using Purge Logs.
6 Import Failed Purchase Orders: find and retry an order that failed during the initial import.
7 CommerceHub Errors: review errors received from CommerceHub for the affected process.
8 Inventory Template: confirm only the Inventory IDs intended for quantity export are selected and saved.
9 Export CommerceHub Inventory: verify that saved Inventory IDs appear, without treating that appearance as proof of the inbound Item ID cross-reference.
CommerceHub Item and Inventory ID Mapping Frequently Asked Questions
Where are CommerceHub Item IDs mapped to Acumatica items?
Use the Cross-reference tab on the CommerceHub Mappings screen. The manual says this tab maps Acumatica items to the respective Item IDs contained in the inbound file during order import.
Does the manual say that CommerceHub Item ID is an SKU?
No. It uses the term Item ID and does not define that value as an SKU, barcode, universal product code, vendor part number, or another identifier.
Can CommerceHub create a missing Acumatica inventory item?
The documentation does not describe automatic item creation or a replacement item. Create and approve the required inventory item and cross-reference before relying on order import.
Can item class control CommerceHub mapping?
No item-class behavior is documented. The source does not name item class as a filter, default, validation rule, or matching key.
Where should I look when an item does not map?
The Biz-Tech Services Acumatica CommerceHub Integration provides Error Log, CommerceHub Errors, and Import Failed Purchase Orders. The source does not state which one always contains an item-mapping failure, so review all relevant records for the selected Store Code.
Does Inventory Template create an inbound item cross-reference?
The manual does not say that it does. Inventory Template selects and saves Inventory IDs for Export CommerceHub Inventory, while Cross-reference handles Item IDs in inbound order files.
Can the same Item ID use aliases or several inventory records?
Aliases, duplicate handling, one-to-many mapping, and identifier precedence are not documented. Confirm any such requirement with Biz-Tech Services before configuring a production process.
How should I test a new CommerceHub item mapping?
Use the intended Store Code, create the Cross-reference row, retrieve one purchase order, process only that order, and compare its Sales Order lines with the source file before using Process All.
Work With the Biz-Tech Services CommerceHub Connector
A dependable CommerceHub item mapping starts with the exact Item ID in the inbound file, the correct Store Code, and a verified Cross-reference row. Keep inbound item resolution separate from Inventory Template and Warehouse Details, which control outbound quantity export.
If you need help validating CommerceHub file Item IDs, correcting failed order mappings, or documenting a controlled cross-reference process, visit https://biz-techservices.com to work with the Biz-Tech Services Acumatica CommerceHub Integrator.
How to Map EZCom Item Numbers to Acumatica Inventory IDs
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.
How to Map DSCO SKUs to Acumatica Inventory IDs
Mapping DSCO SKUs to Acumatica Inventory IDs uses the cross-reference controls on the Inventory Items tab of DSCO Store. The documented example selects SKU as the search method, finds the corresponding DSCO item, and associates that product with its Acumatica Inventory ID for order import.
The Biz-Tech Services DSCO Acumatica Connector uses this item relationship separately from warehouse and shipping cross-references. This guide focuses on SKU lookup, line-level item matching, unmapped-product errors, and the limits of the source. Earlier DSCO articles cover setup, order-to-cash flow, order import, and inventory quantity synchronization.
DSCO SKU Mapping Definition and Prerequisites
The Biz-Tech Services Acumatica DSCO Connector is installed through Customization Projects (SM204505). After the connection is established, DSCO Store contains General Settings, Order Settings, Cross-Reference, Inventory Items, Inventory Availability, and other connector controls.
Cross-Reference Options determines which entities appear in the Cross-Reference Field list. The Inventory Items tab contains its own cross-reference section with dropdown fields that determine how the connector searches for an item and maps it to Acumatica Inventory ID. The source gives SKU as its only item-search example.
Before importing orders, confirm that the correct Partner Code is selected and that the required entity is enabled under Cross-Reference Options. The documentation does not provide all possible Inventory Items search values, exact mapping-grid column names, or a separate item-master setup screen.
DSCO SKU Mapping Step by Step
Use this sequence to set up and check the documented item relationship.
1 Open DSCO Store for the intended Partner Code.
2 Review Cross-Reference Options and enable the entity required for item matching so it becomes available in the relevant Field list.
3 Open the Inventory Items tab and locate its cross-reference section.
4 Select the item search method from the dropdown. Use SKU when applying the example documented in the source.
5 Associate the corresponding DSCO SKU with the intended Acumatica Inventory ID.
6 Save the DSCO Store record before importing an order or selecting products for quantity synchronization.
7 Retrieve the order on Import DSCO Orders and run the import process.
8 If the order line fails, review the line error, hover over the red cross for more information, and use Tools and Trace when additional detail is needed.
How SKU Search Maps to Inventory ID
The Inventory Items documentation describes dropdown fields that choose how to search for an item within the connector. In its example, SKU is selected. The system searches for the item with the corresponding SKU number and associates it with an Acumatica Inventory ID.
This establishes the documented line-level relationship for DSCO orders. A source product identifier is resolved through the selected search method, and the resulting Inventory ID identifies the item used in Acumatica. The source does not describe a separate item-creation option when that Inventory ID is missing.
The documentation also does not state whether SKU matching is case-sensitive, whether leading zeros are preserved, or how spaces and punctuation are normalized. It gives no rule for duplicate SKU values or for multiple source records pointing to one Inventory ID. Those cases require controlled validation in the configured environment.
Cross References Warehouses and Product Aliases
The Biz-Tech Services DSCO Acumatica Integration uses Cross-Reference Options for more than one entity, but the source separates item matching from warehouse mapping. If Use Cross Ref for Warehouse is selected, the source warehouse value must be mapped to an Acumatica warehouse through Cross-Reference.
The documented warehouse validation is explicit. If a warehouse value is not mapped, order import displays Warehouse does not have value. This error concerns the warehouse relationship, not the SKU-to-Inventory-ID relationship.
The source does not document an Alias field, alternate item ID, vendor part number, customer part number, or precedence among multiple identifiers. Although the Inventory Items dropdown allows a search method to be chosen, only SKU is named. Do not claim that additional aliases are supported without separate approved documentation.
Unmapped Items and Import Validation
The manual warns that an error appears during order import when item values are not mapped. It does not provide the actual item error text, error code, or the exact field displayed in the grid. Therefore, troubleshooting should begin with the SKU selection and Inventory ID association rather than an invented message string.
Import DSCO Orders displays an error on the line corresponding to the order when processing fails. Users can hover over the red cross to view additional information and open Tools and Trace for more detail. These are order-import diagnostics; the source does not define a dedicated unmapped-item inquiry.
No unmapped-record queue, Unmapped status, retry counter, automatic substitute item, or batch remediation action is documented. The source also does not state whether correcting a mapping allows the same retrieved order to be reprocessed or requires retrieving it again.
Item Classes and Other Mapping Limits
The DSCO manual does not document Item Class selection, item-type defaults, unit-of-measure mapping, new-item creation, or product-category mapping. It only describes searching for a source item and associating it with Acumatica Inventory ID.
The manual also does not name product attribute mappings, metadata fields, product variants, or parent-child item relationships. These omissions matter because the selected SKU may identify a product, but the source does not explain how additional product properties are transferred to an inventory record.
Inventory Availability is downstream of the saved item setup. Users choose the required items from Inventory Items on DSCO Store and save them before they appear for quantity synchronization. This requirement confirms that selected item records feed the quantity process, but it does not add another documented identifier or alias rule.
How Inventory Quantity Records Confirm the Item Relationship
Export DSCO Inventory Quantities synchronizes quantities for items selected and saved on Inventory Items. Quantity is a read-only field representing the inventory quantity in Acumatica. DSCO Quantity is editable and can be sent as the source-system inventory quantity.
This screen can confirm that a saved item is available to the downstream process. It does not prove that every SKU on every incoming order is mapped correctly, and it does not expose an alias chain. Use the order-import result to validate the actual line relationship.
Inventory Availability also determines which warehouses contribute to synchronized quantity and whether the value represents On hand, Available, or Available for Shipment. Those warehouse and quantity choices are covered in the inventory synchronization workflow and should not be confused with product identity mapping.
Where to Check Your Work
The Biz-Tech Services DSCO Acumatica Integrator provides these documented checkpoints for SKU mapping.
1 On DSCO Store, confirm the intended Partner Code.
2 Under Cross-Reference Options, confirm that the entity needed for item matching is enabled.
3 On Inventory Items, confirm the selected search method and use SKU when following the documented example.
4 Confirm that the source SKU is associated with the intended Acumatica Inventory ID.
5 Save the DSCO Store record before order import or quantity synchronization.
6 On Import DSCO Orders, review the corresponding order line after processing.
7 If a red cross appears, hover over it for additional information and open Tools and Trace when necessary.
8 If Warehouse does not have value appears, correct the warehouse cross-reference rather than changing the product mapping.
9 On Export DSCO Inventory Quantities, confirm that the selected item appears and that Quantity reflects the intended inventory record.
DSCO SKU Mapping Frequently Asked Questions
What DSCO value maps to Acumatica Inventory ID?
The source example uses SKU. The Inventory Items dropdown selects the search method, and the corresponding SKU is associated with Acumatica Inventory ID.
Does the connector support product aliases?
No product-alias behavior is documented. The manual does not name alternate IDs, vendor numbers, customer numbers, or identifier precedence.
What happens when a DSCO item is not mapped?
The manual says order import displays an error, but it does not give the item-specific error text. Review the line error, the red-cross detail, and Tools and Trace.
Can the connector create a missing Acumatica item?
The Biz-Tech Services Acumatica DSCO Integration documentation does not describe automatic item creation. It describes mapping a searched source item to an existing Inventory ID.
Does Item Class control DSCO product mapping?
No Item Class field or class-based rule is documented for DSCO item mapping. The source also omits item-type and unit-of-measure defaults.
Is the warehouse cross reference part of SKU mapping?
It is a separate relationship. Use Cross Ref for Warehouse maps source warehouse values to Acumatica warehouses. Missing warehouse mapping produces Warehouse does not have value.
Where can I review unmapped products?
The source identifies no unmapped-product queue or mapping inquiry. Review Inventory Items on DSCO Store and the error shown on Import DSCO Orders.
Does the quantity screen validate each incoming SKU?
No. Export DSCO Inventory Quantities confirms that selected and saved items participate in quantity synchronization. Incoming line validation occurs during order import.
Work With Biz Tech Services DSCO Mapping
A reliable DSCO item relationship starts with the intended search method, a consistent SKU, and the correct Inventory ID. Cross-reference setup, order-line errors, and saved Inventory Items provide the documented points for validating that relationship.
For help configuring and validating the Biz-Tech Services Acumatica DSCO Integrator, visit https://biz-techservices.com to learn more about Biz-Tech Services and schedule a personalized consultation.
How to Map ShipStation Items to Acumatica Inventory Items
ShipStation items are connected with Acumatica inventory through the Inventory Details tab on the ShipStation Store screen. The documented controls load local Stock and Non-Stock items, load products from ShipStation, retrieve one ShipStation product by its Stock Keeping Unit, or SKU, and generate missing items locally.
The Biz-Tech Services ShipStation Acumatica Connector also defines what happens when an imported order contains a product that is not present locally. Import Item can create the new record with configured defaults, while other settings can generate a SKU through the ERP numbering sequence. The source does not show a dedicated item cross-reference table or an alias field.
What ShipStation Item Mapping Does in Acumatica
The Biz-Tech Services Acumatica ShipStation Connector uses Inventory Details as the documented item workspace. It can display local Stock and Non-Stock items, display products retrieved from ShipStation, export local items to ShipStation, and generate local items from ShipStation products that do not already exist.
The guide describes item synchronization and creation rather than a manual row that pairs one ShipStation SKU with one Acumatica Inventory ID. Load ShipStation Item by SKU can retrieve the exact external product, but the source does not name the internal key used to determine whether that product matches an existing item.
For order imports, Import Item checks whether the item exists. If it does not, the system can create a new item record. Defaults for Imported Item Type, Item Class, unit of measure, or UOM, and Warehouse ID appear when Import Item is selected. These settings define new-item creation; the guide does not say that they remap an existing product.
Before Mapping ShipStation Items
The ShipStation Store's Integration Option controls which tabs and item functions are available. For ShipStation-to-Acumatica processing, the visible tabs include General Info, Import Info, Ship Via Cross Reference, Warehouse Cross Reference, and Inventory Details. Inventory Details is not listed for the opposite integration direction in the source.
The Store Code identifies the corresponding ShipStation store. General Info can retrieve connected stores with Get Stores, and Selected identifies the store used to import orders and shipments. Confirm the store and integration direction before reviewing items so that the Inventory Details data belongs to the intended store.
Test Credentials checks the API connection configured through Consumer Key, Consumer Secret, and Base URL Shipstation Credentials. This is a connection test, not an item-mapping validation. The guide does not describe a separate test for SKU matching.
Map ShipStation Items to Acumatica Inventory Items Step by Step
The documentation provides item actions and import settings rather than one formal mapping wizard. The following sequence stays within those documented controls.
1 Open the ShipStation Store and confirm that Integration Option is set to ShipStation to Acumatica
2 Confirm Store Code and the selected ShipStation store in General Info
3 Open Inventory Details and use Load Acumatica Items to display Stock and Non-Stock items
4 Use Load ShipStation Items to retrieve and display products from ShipStation
5 When a specific external item must be reviewed, use Load ShipStation Item by SKU and enter its SKU
6 Use Generate Items in Acumatica from ShipStation when a ShipStation item does not exist locally and should be created
7 If order import should create missing items automatically, select Import Item and set Imported Item Type, Item Class, UOM, and Warehouse ID
8 Decide whether Use Numbering Sequence for SKU Generation should create a new SKU when no existing SKU number is found
9 Import a controlled order and review the resulting line before processing a larger set of orders
How Import Item Handles Missing Products
Import Item defines the documented missing-product behavior during order import. When selected, the system checks whether an item exists in Acumatica and creates a new item record when it does not. The default fields that appear with this option supply the type, class, UOM, and warehouse for the created item.
When Import Item is not selected and a new product is encountered, the guide says the system automatically assigns default values such as Replace Missing Products for the item name and uses the Warehouse ID from setup. It does not explain whether Replace Missing Products is an Inventory ID, description, placeholder record, or another value.
No unmapped-record queue, pending-review status, or exception inquiry is documented. The source also does not say whether several unknown products share the same placeholder, whether an order remains importable, or how a placeholder is replaced with the final inventory item later.
Item Type Item Class UOM and Warehouse Defaults
Imported Item Type, Item Class, UOM, and Warehouse ID appear only when Import Item is selected. They are documented as defaults for creating new items in Acumatica. This is the guide's only item-class behavior: one configured Item Class can be applied during creation.
The manual does not describe class-specific mapping rules, multiple classes chosen by SKU pattern, or an item-class cross-reference. It also does not define how Imported Item Type affects Stock versus Non-Stock creation or whether the UOM must already exist in Acumatica.
Warehouse ID is a creation and import default in this section. Warehouse Cross Reference is documented separately and maps warehouses between the systems. The source does not state that warehouse cross-references participate in identifying the inventory item itself.
How SKU Generation Works for a Missing Number
Use Numbering Sequence for SKU Generation applies when the system does not find an existing SKU number during item creation. When enabled, it generates a new SKU from the numbering sequence configured in Acumatica. The guide says this produces consistent and unique SKUs for created items.
The source does not identify the numbering sequence screen, field, format, prefix, or next-number behavior. It also does not say what happens to the original ShipStation SKU after a different local SKU is generated or which value is used on later imports.
No rule is provided for blank SKUs, duplicate SKUs, case differences, spaces, leading zeros, or SKU length. Those cases should not be assigned undocumented matching behavior.
Inventory Details Actions for ShipStation Products
The Biz-Tech Services ShipStation Acumatica Integration provides five documented item actions in Inventory Details. Together they load data from either system, export local product data, retrieve one product by SKU, or create missing local items.
Load Acumatica Items retrieves all Stock and Non-Stock items and displays them in a table. Update ShipStation Items from Acumatica exports the listed items to ShipStation so external product data reflects current local information. Load ShipStation Items retrieves external products and displays them locally.
Generate Items in Acumatica from ShipStation creates a local record when an item exists in ShipStation but not locally. Load ShipStation Item by SKU retrieves one specific external product. The guide does not name the table columns, selection checkboxes, generated Inventory ID field, or result status for any action.
Cross References and Alias Coverage
The source documents Cross-Reference Options for warehouses and Ship Via methods. Use Cross Ref for Warehouse reveals the warehouse-mapping tab, and Use Cross Ref for Ship Via reveals the shipping-method-mapping tab. It does not document Use Cross Ref for Item or an item cross-reference tab.
Load ShipStation Item by SKU supplies direct SKU lookup, but the guide does not call that value an alias or describe alternate identifiers. There are no documented customer part numbers, vendor item numbers, universal product codes, external product IDs, or many-to-one alias rules for items.
Because an item cross-reference structure is not shown, the article cannot assign field names or precedence rules to one. Inventory Details and the Import Item creation settings are the documented controls for this topic.
Validation Rules and Item Mapping Gaps
The ShipStation guide does not document an item-validation button, mapped or unmapped status, line-level item error field, duplicate warning, or validation report. Import ShipStation Orders can display an error when a store uses the wrong Integration Option, but that check validates store direction rather than item mapping.
The source also does not state how the system decides that an item exists, what field is compared with the ShipStation SKU, or whether a generated item is Stock or Non-Stock under each Imported Item Type. No behavior is documented for conflicting matches or for an item that exists but is inactive.
A controlled import is therefore the available documented confirmation path. The manual says Get Orders retrieves ShipStation orders and Import sends selected orders to Sales Orders in Acumatica, but it does not list the item fields to inspect on the resulting line.
Where to Check Your ShipStation Item Setup
The Biz-Tech Services ShipStation Acumatica Integrator exposes the following documented places to review store direction, item creation defaults, and inventory actions.
1 On ShipStation Store, confirm Store Code and Integration Option
2 In General Info, use Get Stores and verify that the intended ShipStation store is Selected
3 In Item Information, review Import Item, Imported Item Type, Item Class, UOM, and Warehouse ID
4 Review Use Numbering Sequence for SKU Generation when the product has no existing SKU number
5 In Inventory Details, use Load Acumatica Items to display local Stock and Non-Stock records
6 Use Load ShipStation Items or Load ShipStation Item by SKU to display the external product
7 Use Generate Items in Acumatica from ShipStation only when the missing external product should create a local item
8 On Import ShipStation Orders, retrieve a controlled order and inspect the Sales Order created by Import
ShipStation Item Mapping Frequently Asked Questions
Where can I load ShipStation items for review in Acumatica?
Use Inventory Details on the ShipStation Store configured for ShipStation to Acumatica. Load ShipStation Items retrieves external products and displays them locally.
Can I retrieve one ShipStation product by SKU?
Yes. Load ShipStation Item by SKU retrieves a specific product by its SKU and displays it in Acumatica.
What creates a missing Acumatica inventory item?
The Biz-Tech Services Acumatica ShipStation Integration can create a missing item through Import Item during order import or through Generate Items in Acumatica from ShipStation in Inventory Details. The guide does not explain precedence when both are used.
Which defaults are used when Import Item creates a record?
Imported Item Type, Item Class, UOM, and Warehouse ID appear as defaults when Import Item is selected.
What happens when Import Item is not selected?
For a new product, the guide says default values such as Replace Missing Products are assigned for the item name and the setup Warehouse ID is used. It does not explain the resulting record structure.
Can ShipStation items be mapped through an item cross reference?
The documentation only defines cross-references for warehouses and Ship Via. It does not show an item cross-reference option or tab.
Can different SKUs be treated as aliases for one inventory item?
No alias behavior is documented. Load ShipStation Item by SKU performs a direct lookup, but the guide does not describe many-to-one aliases or alternate item identifiers.
How can I validate an item mapping before importing orders?
The source does not provide an item-mapping validation action. Review the store, creation defaults, and Inventory Details, then use a controlled order import to confirm the resulting line.
Work With Biz Tech Services on ShipStation Item Setup
ShipStation item setup depends on the correct store direction, the Inventory Details actions, and the missing-item defaults used during creation. The source supports direct SKU retrieval and product generation but does not document an item alias table or formal mapping validator.
If your team needs help reviewing item creation and SKU behavior, the Biz-Tech Services Acumatica ShipStation Integrator can support your connector setup. Visit https://biz-techservices.com to contact Biz-Tech Services or schedule a personalized demonstration.
How to Map ShipHero SKUs to Acumatica Inventory Items
Mapping ShipHero SKUs to Acumatica inventory items requires a careful reading of what the connector documentation actually defines. The manual documents bidirectional item synchronization, missing-item creation or replacement, item-class defaults, and warehouse cross-references, but it does not name a ShipHero SKU field or state the exact comparison rule that links an SKU to an existing Inventory ID.
The Biz-Tech Services ShipHero Acumatica Connector provides the controls needed to load and synchronize items and to decide what happens when a record is missing. This guide focuses on those documented item-level controls and marks the unsupported areas clearly.
What ShipHero Item Mapping in Acumatica Establishes
The Biz-Tech Services Acumatica ShipHero Connector uses the Inventory Details tab to load and display items from both systems. Load Acumatica Items displays the ERP items, Load Ship Hero Items displays the warehouse management system items, Sync Acumatica Items exports items to ShipHero, and Sync Ship Hero Items imports items into Acumatica.
When an imported ShipHero item does not exist in Acumatica, Import Item controls whether a new inventory record may be created. When that checkbox is selected, imported item type, item class, UOM, and warehouse ID become available as defaults. When it is not selected, the source says the connector does not create a new item and uses the configured Replace Missing Products default instead.
Warehouse Cross-Reference is part of the item synchronization path, but it maps warehouse values rather than item identifiers. The source says the connector creates or assigns the warehouse for an imported item according to this setup. It does not say that Warehouse Cross-Reference maps an SKU, Inventory ID, alias, or product code.
ShipHero Item Mapping at a Glance
Use this sequence to configure the documented item behavior without assuming an undocumented SKU rule.
1 Select the integration direction on Ship Hero Store because the available tabs and processing behavior change between Ship Hero to Acumatica and Acumatica to Ship Hero.
2 Configure Warehouse Cross-Reference for the warehouse values used during item synchronization and order import.
3 On Sync Info, decide whether Import Item should create a missing Acumatica item or whether the connector should use Replace Missing Products.
4 If Import Item is selected, set imported item type, item class, UOM, and warehouse ID as the defaults for a newly created item.
5 Open Inventory Details and use Load Ship Hero Items or Load Acumatica Items to review the records available for processing.
6 Run Sync Ship Hero Items to import selected ShipHero items or Sync Acumatica Items to export ERP items.
7 Open the Ship Hero Item inquiry to review item availability, connected vendors, bin transfers, and the result of Sync Ship Hero Item.
8 Treat the SKU, alias, duplicate, and precedence rules as unresolved until Biz-Tech Services supplies product-specific guidance because the manual does not define them.
Choose the Item Synchronization Direction
Ship Hero Store includes an Integration Option that determines the workflow direction. Ship Hero to Acumatica brings data from the warehouse management system into the ERP and exposes General Info, Import Info, Ship Via Cross Reference, Warehouse Cross Reference, Inventory Details, Sync Info, and Locations.
The Inventory Details actions show the documented item flow. Load Acumatica Items retrieves the ERP item list, and Load Ship Hero Items retrieves the ShipHero item list. Sync Acumatica Items sends ERP items to ShipHero. Sync Ship Hero Items brings ShipHero items into Acumatica. Purge deletes the items displayed on the Inventory Details table, while Sellect All, as written in the source, selects all displayed items.
The manual does not list Inventory Details grid columns or identify an SKU, product ID, inventory code, or line-level key on that tab. It also does not explain whether synchronization updates an existing record or creates a new one based on an SKU comparison. Confirm the visible fields in the installed customization before documenting a local matching procedure.
Configure Missing Item Creation and Item Class Defaults
Import Item is the documented switch for missing inventory records. Select it when the connector should allow a new item to be created during synchronization or order import. The following default fields then appear: imported item type, item class, UOM, and warehouse ID.
Item class is used as a default for new item creation. The source does not describe item class as a cross-reference, a match condition, or a way to resolve multiple records with the same external identifier. It also does not state whether any attributes or settings inherited from the class are required by the connector.
When Import Item is not selected, the manual says that the connector does not create a new item and sets a default item for each missing product. Replace Missing Products supplies that default item, and Warehouse ID supplies the warehouse value. The source also contains an awkward sentence saying it sets Replace Missing Products as the item name; it does not clarify whether this means the selected replacement item, the displayed line description, or another value.
These controls define how an unmapped or missing product can be handled during import, but they do not define the condition that makes a product missing. No rule is given for blank SKUs, unknown SKUs, duplicate SKUs, inactive items, stock versus non-stock items, or a ShipHero record whose code differs from the Acumatica Inventory ID.
Separate Warehouse Cross-References from Item Identity
Warehouse Cross-Reference is explicitly used by item synchronization and order import. Based on that setup, an imported order receives the mapped warehouse on the sales order, and an imported item receives or creates the warehouse associated with that mapping.
The Biz-Tech Services ShipHero Acumatica Integration also uses the mapped warehouses when locations are loaded. The Locations note states that locations are loaded for warehouses configured on Warehouse Cross-Reference. When Use Location Mapping is selected, a grid appears to map locations; otherwise, Sellable Location and Non-Sellable Location provide the documented defaults.
Ship Via Cross-Reference serves a different purpose. The Import Info settings expose Use Cross Ref for Ship Via and Use Cross Ref for Warehouse. Selecting these options shows the corresponding tabs so ShipHero values can be matched with Acumatica values. The manual does not provide an item cross-reference option or an SKU cross-reference tab.
Box Mapping and Reason Code Mapping are also named mapping features, but neither identifies an inventory item. Box Mapping pairs Acumatica Box ID with ShipHero Box name. Reason Code Mapping supports return orders. Keep these mappings separate from the unresolved item-identity question.
Validate Imported Items Vendor Data and Locations
When Sync Ship Hero Items imports an item, vendor information is also synchronized if the stock item has a vendor or vendors that have already been synchronized to ShipHero. The source does not state which vendor field is used for the connection or what happens when the vendor has not been synchronized.
The Ship Hero Item inquiry provides three review areas. Warehouse Details displays item availability. Vendors displays the vendor connected with the item in ShipHero. Bin Transfers displays transfers for the item. Update Item displays changes made to the ShipHero item, Sync Ship Hero Item synchronizes the item into Acumatica, and Update Warehouse In Ship Hero updates item quantity in ShipHero.
Location setup should be reviewed with the item. Load Acumatica Locations displays ERP locations, and Sync Acumatica Locations exports them to ShipHero. Load Ship Hero Locations displays warehouse-system locations. The documentation says only locations for warehouses configured on Warehouse Cross-Reference are loaded.
The manual supplies no screen IDs for Ship Hero Store, Inventory Details, Warehouse Cross-Reference, Locations, or Ship Hero Item. The only screen ID stated in the document is Customization Projects (SM204505), which is used for package installation and is not an item-mapping screen.
Apply the Documented Mapping Validation Rules
The source provides configuration dependencies rather than a formal SKU validation table.
1 Select a Ship Hero Store integration direction before expecting the related item and mapping tabs to appear.
2 Select Use Cross Ref for Warehouse before expecting Warehouse Cross-Reference to appear.
3 Configure the mapped warehouse because the setup is used for both item synchronization and order import.
4 Select Import Item before expecting imported item type, item class, UOM, and warehouse ID defaults to appear.
5 If Import Item is not selected, confirm Replace Missing Products and Warehouse ID before importing a product that may not exist.
6 Confirm that a vendor is already synchronized before expecting the vendor information of an imported stock item to synchronize with the item.
7 Configure Warehouse Cross-Reference before loading locations because the source limits loaded locations to configured warehouses.
The documentation does not provide error-message text, validation codes, duplicate handling, or a rejected-record inquiry for item synchronization. It does not say how a failed item appears on Inventory Details or whether Purge removes only the displayed staging records or affects data outside the table.
Document the SKU and Alias Rules the Manual Does Not Define
Despite the business need to map ShipHero SKUs, the source never names an SKU field. It does not say that ShipHero SKU equals Acumatica Inventory ID, Inventory CD, Alternate ID, or another field. It also does not show item-level mapping columns on Inventory Details or provide a sample product-to-item mapping.
No alias mechanism is documented. The manual does not identify customer part numbers, vendor part numbers, global trade item numbers, universal product codes, barcodes, alternate IDs, wildcard matching, or case-insensitive matching as valid connector keys. It does not define which identifier wins if multiple candidates exist.
Unmapped-record behavior is documented only through Import Item and Replace Missing Products. The source does not identify a holding queue, error log, notification, or correction screen for a product that cannot be matched or created. It also does not state whether a later successful match replaces an earlier replacement-product line.
A safe implementation record should therefore distinguish documented configuration from tested local behavior. Record the installed screen fields, the exact ShipHero value, the resulting Inventory ID, the Import Item state, the selected defaults, and the warehouse mapping observed in a controlled test. Do not present the observed key as a product guarantee unless it is confirmed by Biz-Tech Services.
Where to Check Your Work
The Biz-Tech Services ShipHero Acumatica Integrator exposes the documented item result in these locations.
1 Ship Hero Store: confirm Store Code, Integration Option, and the tabs displayed for the selected direction.
2 Import Info: confirm Use Cross Ref for Warehouse and Use Cross Ref for Ship Via when those mappings are required.
3 Warehouse Cross-Reference: compare the ShipHero warehouse value with the Acumatica warehouse value used during item synchronization and order import.
4 Sync Info: check Import Item, imported item type, item class, UOM, warehouse ID, Replace Missing Products, Export Price Type, and Export price Quantity.
5 Inventory Details: load both item lists, review the displayed records, and run only the synchronization direction intended for the test.
6 Ship Hero Item: review Warehouse Details, Vendors, and Bin Transfers, then use Update Item or Sync Ship Hero Item as documented.
7 Locations: confirm that the expected warehouses were mapped before loading locations, and review Use Location Mapping, Sellable Location, and Non-Sellable Location.
8 The resulting Acumatica inventory item and sales order line: compare the item, warehouse, UOM, and replacement-product outcome with the configured defaults. The manual does not provide a specific screen ID for this review.
ShipHero SKU and Inventory Item Mapping Frequently Asked Questions
Does the connector documentation say which Acumatica field matches a ShipHero SKU?
No. The manual documents item synchronization and missing-item settings but does not name a ShipHero SKU field or state that it matches Inventory ID, Inventory CD, Alternate ID, or another Acumatica field.
Can the connector create an inventory item that does not exist in Acumatica?
Yes, when Import Item is selected. The connector can create a new item using imported item type, item class, UOM, and warehouse ID as the documented defaults.
What happens when Import Item is not selected?
The source says the connector does not create the new item. It uses the default configured in Replace Missing Products and takes the warehouse from Warehouse ID.
Is item class used to match ShipHero products?
The manual only identifies item class as a default for new item creation. It does not define item class as an SKU match, alias, or cross-reference rule.
Does Warehouse Cross-Reference map ShipHero SKUs?
No SKU behavior is documented for that tab. It maps warehouse values used during item synchronization and order import, including the warehouse associated with an imported item.
Where can I review a synchronized ShipHero item?
Use Inventory Details to load and process item records, then use the Ship Hero Item inquiry to review Warehouse Details, Vendors, and Bin Transfers. The source provides no screen IDs for those locations.
Does the connector support aliases or alternate item identifiers?
The Biz-Tech Services Acumatica ShipHero Integration documentation does not define item aliases, alternate IDs, barcodes, customer part numbers, vendor part numbers, or wildcard matching. Obtain product-specific confirmation before building a mapping process around any of those identifiers.
How can I validate an SKU mapping when the manual does not define the key?
Run a controlled item synchronization and record the exact source value, resulting inventory item, Import Item setting, item defaults, replacement-product outcome, and warehouse mapping. Treat the result as environment-specific until the key is confirmed by Biz-Tech Services.
Work With the Biz-Tech Services ShipHero Connector
A reliable mapping design starts with the controls the manual actually documents: synchronization direction, missing-item handling, creation defaults, and warehouse mapping. The SKU key, aliases, matching precedence, and rejected-record workflow require product-specific confirmation.
If you need help confirming ShipHero item identifiers, testing missing-item behavior, or documenting a controlled SKU-mapping process, visit https://biz-techservices.com to work with the Biz-Tech Services Acumatica ShipHero Integrator.
How to Map Amazon SKUs to Acumatica Inventory IDs
Amazon SKUs map to Acumatica Inventory IDs through the Amazon Store's Inventory Details and Cross-Reference settings. The documentation supports direct Amazon Value to Acumatica Value matching, SKU-based Inventory ID creation when Import Item is enabled, and SKU maintenance for existing items in Inventory Details.
The Biz-Tech Services Amazon Acumatica Connector gives administrators a choice between mapping an Amazon item to an existing inventory record and allowing a new record to be created during import. This article focuses on those documented item and SKU controls, the behavior of unmapped items, the product lookup actions, and the limited error information available during order import.
What Amazon SKU Mapping Does in Acumatica
The Biz-Tech Services Acumatica Amazon Connector uses item mapping to associate an Amazon product identifier with an inventory record. The Amazon guide names two related work areas on the Amazon Store screen: Cross-Reference, which matches external and internal values for selected entities, and Inventory Details, where a new Amazon SKU is mapped and existing SKU assignments can be changed.
The guide also describes Import Item. When this checkbox is selected and an order contains a product that does not yet exist in the ERP, the connector imports the new product information and generates an Inventory ID based on the SKU. When Import Item is not selected, the documentation says an integration error occurs for a product that does not exist.
These controls establish the documented mapping boundary. The manual does not define a general alias engine, item-class default, or external-ID hierarchy. It describes Amazon Value, Acumatica Value, SKU, ASIN, SELLERSKU, and Inventory ID, but it does not specify matching precedence among them.
Map Amazon SKUs to Acumatica Inventory IDs Step by Step
Use the following documented controls to prepare item matching. The source does not supply one end-to-end numbered workflow, so each step below stays within the functions it explicitly assigns to the Amazon Store settings.
1 Open the Amazon Store record for the store whose Amazon products need to be matched
2 In Cross-Reference Options, select Items so the item entity is available in the Cross-Reference Field list
3 In Cross-Reference, select the item entity in Field and enter the Amazon Value and corresponding Acumatica Value
4 In Inventory Details, create the mapping required for a new Amazon SKU or review the SKU assigned to an existing Acumatica item
5 Decide whether Import Item should create product information for Amazon items that do not yet exist in Acumatica
6 If order imports should populate Inventory Details, select Insert Item in Inventory Details Tab
7 Use Get Product by ASIN or Get Product by SELLERSKU to retrieve and display the Amazon item in Inventory Details
8 For Fulfillment by Amazon products, use Load FBA Products to display store products and Sync From Amazon on a loaded item when an Acumatica item must be created from its SKU
9 Import a controlled Amazon order and review the order line or import error before applying the setup to a larger group of orders
How Import Item Handles an Unmapped Amazon Product
Import Item determines what the connector does when Amazon supplies product information that does not exist in the ERP. With the checkbox selected, the connector imports the new product information. The Inventory Details note adds that order import generates an Acumatica Inventory ID based on the SKU.
With Import Item cleared, the guide says an integration error occurs. It does not provide the exact error text, identify a separate queue for unmapped items, or state whether the order is partly imported. It also does not say whether the error can be resolved directly from the order grid or requires a new mapping on the Amazon Store screen.
Send Email Notifications for Errors can send notifications about Order IDs that have errors. On the Amazon Orders screen, an error message can be displayed for an order, and the import grid can show a red cross with more information on hover. The guide also points users to Tools and Trace for additional error details, but it does not tie a named message specifically to an unmapped SKU.
How Amazon and Acumatica Values Are Cross Referenced
The Biz-Tech Services Amazon Acumatica Integration includes cross-reference functionality for Items, Payments, and Ship Via. Cross-Reference Options selects which external and internal entities should be matched. Only selected entities appear in the Field drop-down on Cross-Reference.
For each selected entity, Field identifies what is being matched. Amazon Value specifies the external value, and Acumatica Value specifies the corresponding internal value. These are the exact field labels documented for general cross-references. The source does not show a completed item example or explicitly state whether the value displayed for Items is the Inventory ID.
The Cross-Reference settings and Inventory Details both participate in product setup, but the guide does not explain their precedence or whether they store the same relationship. Do not assume that an item entered in one area automatically appears in the other without confirming the result in the installed connector.
How Inventory Details Maintains Amazon SKUs
The Amazon Store Inventory Details tab is the documented location for creating a mapping for a new Amazon SKU. The guide also says that an existing item's SKU can be changed in Inventory Details and imported without creating a new Acumatica item. This gives the setup a documented maintenance path as well as an initial creation path.
Insert Item in Inventory Details Tab controls whether items retrieved during order import are placed in the Amazon Store's Inventory Details tab. The guide does not say whether this action creates a complete mapping, creates a pending record, or only displays the Amazon product for review.
When an item already exists on the Stock Item screen, Import Item does not update its description. Instead, the Sales Order line description is set to the Amazon item title. During order import, the connector also uses the Amazon item price rather than the mapped Acumatica item price. Description and price therefore do not establish or change the SKU-to-Inventory-ID relationship described here.
Amazon Product Lookup and FBA Item Creation
Inventory Details includes two documented lookup actions. Get Product by ASIN retrieves and displays an Amazon item by Amazon Standard Identification Number, or ASIN. Get Product by SELLERSKU retrieves and displays the product by its seller SKU. The guide does not state which identifier wins if the values identify different products.
For Fulfillment by Amazon, Load FBA Products loads and displays all Amazon products in the store. After a loaded FBA item is selected, Sync From Amazon creates the local item through the product SKU. The source also says FBA products are loaded through API requests and mapped with local inventory, but it does not provide the mapping fields used by that API process.
The manual does not state whether the FBA action applies the same Inventory Details mapping used for Fulfillment by Merchant orders. It also does not define duplicate detection when an Inventory ID already exists for a similar SKU.
Validation and Mapping Exceptions for Amazon Items
The documented validation evidence appears during order processing rather than as a dedicated item-mapping validation screen. Users can view an Amazon order before import. If an error appears, the Amazon Orders screen displays an error message intended to indicate what must be corrected and in which system.
During import, a line-level error appears on the corresponding order row. Hovering over the red cross shows additional information, and Tools and Trace provides another diagnostic location. These controls are documented for order errors in general. The guide does not identify an Inventory ID validation button, a mapping status field, or an item-specific error catalog.
Import Item provides the only explicit rule for a missing product: create the product information when selected, or encounter an integration error when it is not selected. No rule is supplied for blank SKUs, duplicate SKUs, different letter case, leading zeros, inactive Inventory IDs, or stock versus non-stock items.
Mapping Features Not Defined in the Amazon Guide
The guide does not describe item classes, item-class defaults, alternate SKU aliases, wildcard matching, SKU normalization, units of measure for SKU matching, or an unmapped-item inquiry. It does not show whether the generated Inventory ID is identical to the Amazon SKU or transformed to meet local numbering rules.
The source also does not explain how Inventory Details interacts with the general Cross-Reference table, what value uniquely identifies an existing item during an SKU change, or how conflicts are handled when Amazon Value, ASIN, and SELLERSKU point to different records. Those are implementation questions, not documented connector behaviors.
Where to Check Your Amazon SKU Mapping
The Biz-Tech Services Amazon Acumatica Integrator exposes the following documented places to review item setup and import results.
1 On Amazon Store, confirm the Store Code for the store whose products are being mapped
2 In Cross-Reference Options, confirm that Items is selected as an entity to be matched
3 In Cross-Reference, review Field, Amazon Value, and Acumatica Value
4 In Inventory Details, review the Amazon SKU and its existing Acumatica item assignment
5 In the Import Settings area, confirm the intended status of Import Item and Insert Item in Inventory Details Tab
6 Use Get Product by ASIN or Get Product by SELLERSKU to verify that the intended Amazon product is displayed
7 On Amazon Orders, view the order and inspect any displayed error message before import
8 In the import grid, hover over a red cross for additional error information and use Tools and Trace when more detail is needed
9 On the resulting Sales Order, confirm the Inventory ID, Amazon item title in the line description, and Amazon item price
Amazon SKU and Inventory ID Mapping Frequently Asked Questions
Where do I map a new Amazon SKU in Acumatica?
Create the mapping in the Inventory Details tab of the Amazon Store. The guide identifies this tab as the location required to upload a new Amazon item SKU.
What happens when an Amazon item does not exist in Acumatica?
When Import Item is selected, the connector imports the new product information and can generate an Inventory ID based on the SKU. If it is not selected, the guide says an integration error occurs.
Can an existing Amazon SKU be changed without creating a new item?
Yes. The documentation says the SKU can be changed for an existing item in Amazon Store Inventory Details and imported without creating a new Acumatica item.
How does the Amazon item cross reference work?
The Biz-Tech Services Acumatica Amazon Integration uses Cross-Reference Options to select entities and uses Field, Amazon Value, and Acumatica Value to define the match. The guide does not show a completed item record or explain its relationship to Inventory Details.
Can I find an Amazon item by ASIN or seller SKU?
Yes. Inventory Details provides Get Product by ASIN and Get Product by SELLERSKU. Both actions retrieve and display the Amazon product using the selected identifier.
Does item mapping use the Acumatica price or Amazon price?
The guide states that order import uses the Amazon item's price rather than the mapped Acumatica item's price.
Can Amazon SKUs be mapped by Acumatica item class?
The source does not document item-class mapping, item-class defaults, or alias rules. It documents Inventory Details and value-based cross-references.
Where can I see an Amazon item mapping error?
Review the Amazon Orders screen and the import grid. An error can appear for the order, a red cross can expose more information on hover, and Tools and Trace can provide additional details. No item-specific error list is included in the guide.
Work With Biz Tech Services on Amazon Item Mapping
Amazon item setup in Acumatica depends on a documented choice: match the Amazon value and SKU to an existing item, or enable Import Item so a missing product can be created from the SKU. Inventory Details, Cross-Reference, and the order-import error displays provide the available control points.
If your team needs help reviewing Amazon SKU mappings and Inventory ID behavior, the Biz-Tech Services Acumatica Amazon Integrator can support your connector implementation. Visit https://biz-techservices.com to contact Biz-Tech Services or schedule a personalized demonstration.
How to Map Shopify Products and Variants to Acumatica Inventory Items
Mapping Shopify products and variants to Acumatica inventory items depends on the direction of the synchronization. On import, the connector can use a Shopify SKU to create an Acumatica Inventory ID, create a new item when allowed, or use the configured missing-product default. On export, the documentation states that item mapping is not supported and the Acumatica Inventory CD becomes the Shopify SKU.
The Biz-Tech Services Shopify Acumatica Connector also separates identity mapping from field mapping. The Shopify Inventory tab handles product and item synchronization, Inventory Mapping connects ERP properties to Shopify fields and metafields, and the template and matrix item workflow represents Shopify products and variants. This article stays focused on those product, variant, SKU, cross-reference, item-class, and validation decisions rather than repeating connection setup, order import, or quantity synchronization.
What Shopify Product and Variant Mapping Does
The Biz-Tech Services Acumatica Shopify Connector provides documented paths for resolving item identity and synchronizing product data. When Sync from Shopify runs on the Shopify Inventory tab, the connector takes the Shopify item SKU and creates an Acumatica Inventory ID. When an order import encounters an item that does not exist, the Import Item setting determines whether a new inventory item may be created.
Field mapping is configured separately on the Inventory Mapping tab. That tab connects Acumatica attributes, item currency settings, and user-defined fields with Shopify fields. It also supports Shopify metafields at the product or variant level. A product or variant can therefore have both an item identity, normally tied to SKU, and a set of mapped descriptive or custom properties.
The connector documents a third layer for catalog structure. An Acumatica Template Item represents the base product, while Matrix Items represent the sellable Shopify variants. Each Matrix Item is a unique attribute combination, such as a specific size and color, and is stocked, priced, and sold separately.
Shopify Product and Variant Mapping at a Glance
Use this sequence to separate item identity, missing-item behavior, field mapping, and variant structure.
1 Review Import Item on the Shopify store Import Settings before importing products or order lines that may not exist in the ERP.
2 If new items may be created, set the imported item type, item class, UOM, and warehouseID defaults that appear when Import Item is selected.
3 If Shopify may send an item without an SKU, decide whether Use Numbering Sequence for SKU Generation should generate a new value from the configured numbering sequence.
4 Load Shopify items on the Shopify Inventory tab, then use Sync from Shopify for the documented SKU-to-Inventory ID import path.
5 Use Inventory Mapping to pair ERP properties with Shopify properties and to configure product-level or variant-level metafield mappings.
6 For products with options, sync the Acumatica Template Item as the Shopify product and select the Matrix Items that should become Shopify variants.
7 Select the required import or export checkbox for each field mapping before processing mapped values.
8 Validate the resulting SKU, Inventory ID or Inventory CD, Shopify product identity, template identity, matrix-item selection, and required field checkboxes on the documented screens and tabs.
Resolve Shopify SKUs to Acumatica Inventory Items
The Shopify Inventory tab can load both Acumatica and Shopify items. Load Acumatica Items retrieves stock and non-stock records. Load Shopify Items retrieves Shopify items. Sync to Shopify exports ERP items, while Sync from Shopify imports Shopify items into the ERP. Get Item by ID retrieves a Shopify item by its ID, and Purge removes the items displayed in the table.
For Sync from Shopify, the manual gives a direct identity rule: the connector takes the Shopify item SKU and creates an Acumatica Inventory ID. That statement establishes SKU as the documented import identifier. The manual does not say whether the comparison is case-sensitive, whether spaces or punctuation are normalized, or how duplicate Shopify SKUs are resolved.
The export direction uses a different rule. The connector does not support item mapping when an ERP inventory item is exported to Shopify. Instead, it sets the item Inventory CD as the Shopify SKU. Before choosing an item-code design, account for that restriction because the manual does not document an export alias that substitutes a different Shopify SKU.
The manual alternates between Inventory ID for the imported item and Inventory CD for the value sent as the Shopify SKU. It does not explain whether those terms refer to the same visible item identifier in this connector context. Preserve the documented terms when testing each direction and verify the actual values displayed in the Shopify Inventory table and the inventory record.
Configure Missing Product Creation and Item Defaults
Import Item controls the connector behavior when a Shopify item is not found in the ERP during synchronization or order import. When the checkbox is selected, the system allows a new item to be created. The imported item type, item class, UOM, and warehouseID options then appear and supply the documented default values for that new item.
Item class is therefore documented as a new-item default, not as an alternate matching key. The source does not state that an item class decides which existing inventory record matches a Shopify SKU, nor does it document class-based product aliases or variant resolution. Use the item class to classify newly created items only to the extent shown by the setting.
When Import Item is not selected, the source says the new item import case uses Replace Missing Products as the item name and takes the warehouse from Warehouse ID. The wording is imprecise, but it clearly identifies Replace Missing Products as the documented fallback setting for a missing imported item rather than describing automatic creation of a normal inventory record.
Use Numbering Sequence for SKU Generation applies during item creation when the system does not find an SKU number. In that case, the connector generates a new value from the numbering sequence setup. The documentation also warns that an absent corresponding numbering sequence produces an error message, although it does not provide the exact message text.
Populate Items in Inventory Details adds the imported item to Inventory Details. Save Item Properties in Line Notes allows item properties from the order to be synchronized to line and header notes. These settings affect the created record or imported order context; the manual does not present them as matching or alias rules.
Use Cross-References Without Assuming an Item Alias Model
Cross-Reference options on Import Settings determine which entities may be set up and matched between Shopify and Acumatica. The Cross-Reference tab visibly supports values such as Ship Via. For customer imports that use tags and the Code type, the source specifically describes Shopify Value and Acumatica Value fields and explains how a Shopify tag can select a customer record.
The manual then states that the same logic works for items, but it does not provide the corresponding item example, item field names, or a complete matching sequence. It does not say whether the Shopify value is an SKU, tag, product ID, variant ID, title, or another property. It also does not explain the relationship between an item cross-reference and the SKU-based behavior on Shopify Inventory.
The Biz-Tech Services Shopify Acumatica Integration should therefore be configured only from the item choices actually exposed in Cross-Reference options. Do not infer a customer part-number, vendor part-number, alternate ID, wildcard, or alias table from the brief statement that item logic is similar. The documentation does not define those mechanisms.
For an unmapped record, the documented outcomes depend on the workflow and settings. Shopify Inventory import can create an Acumatica Inventory ID from the Shopify SKU. Order import can create a new item when Import Item is selected, or use Replace Missing Products when it is not. The manual does not state which behavior takes precedence if an item cross-reference exists but conflicts with the SKU, or if an item cross-reference is enabled but no row matches.
Map Product Variant and Metafield Properties
Inventory Mapping handles field-level data after the product or variant identity is established. The tab supports Acumatica attributes, item currency settings, user-defined fields, and Shopify fields. It also supports exporting and updating Shopify metafields at the product or variant level.
Use Get Metafields to retrieve existing Shopify metafields before organizing the mapping. Each mapping has checkboxes that specify whether it applies to import or export. Select the appropriate direction before processing; the source explicitly tells users to confirm that the corresponding checkbox is selected before importing or exporting mapped values.
The documentation defines Acumatica property as the Acumatica item category and Shopify property as the Shopify item category. It does not list the complete set of allowed categories, provide sample product-level and variant-level rows, or describe type conversion between the platforms. It also does not define what happens when a metafield type or mapped value is invalid.
Export Item Mappings is a related but separate tab. It determines which product-related fields are synchronized to Shopify, and its checkboxes can exclude fields that should not be updated. The source warns that if required fields are not selected for creation or update, corresponding data such as price, description, or weight will not be updated on Shopify processing screens.
Connect Template Items Matrix Items and Shopify Variants
An Acumatica Template Item is the base product used to create multiple Matrix Items and is not itself a sellable product. A Matrix Item is a child product generated from the template. Each Matrix Item represents one attribute combination and is stocked, priced, and sold separately. In Shopify terms, the template supplies the product structure and the matrix items supply the variants.
After the Template Item is synchronized, the Shopify-generated Template ID is displayed on the Shopify Product tab. Syncing can then include selected matrix items or all matrix items.
1 Select Sync Matrix Items.
2 Open the Matrix Items tab.
3 Select the desired items.
4 Select Include Item in Sync.
5 Confirm that the selected items appear on the Shopify Details tab, which the manual uses as confirmation that they are in the Shopify store and ready to synchronize.
Sync All Matrix Items sends all matrix items with the template product. After the template item exists in Shopify, Shopify Product Data becomes available on the Shopify Product tab. Selecting it exposes additional fields such as Custom URL, Meta Description, and Page Title. Export to Shopify is automatically selected when the product exists in Shopify.
The same selected-checkbox logic applies to stock items. When the template and matrix synchronization checkboxes are selected, the items synchronize as one template with its matrix items. When they are not selected, the manual says items export as ordinary individual products.
Understand Export Direction and Validation Limits
The export path must be reviewed separately from import. Because export item mapping is not supported, the Acumatica Inventory CD becomes the Shopify SKU. If the connector cannot find some items in the Shopify store during synchronization, the documentation says it creates them automatically. On sales order export, Create Product determines whether a missing Shopify product is created; when it is not selected, the default product under Replace Missing Products is used.
Track Quantity has a documented validation rule. If Track Quantity is not selected in either Shopify or Acumatica, an error message should appear during synchronization. If it is not selected in Shopify but is selected in the ERP, synchronization should update the quantity and automatically select the option in Shopify. The source does not provide the error text or describe the opposite mismatch.
Product-field synchronization also depends on selected checkboxes in Export Item Mappings. Price, description, weight, and other fields are not updated when their required creation or update fields are not selected. Image synchronization depends on Product Image, but the source separately warns that punctuation marks can duplicate an image without defining which punctuation, filename field, or comparison rule is involved.
The source does not provide screen IDs for Shopify Stores, Shopify Inventory, Inventory Mapping, Export Item Mappings, Export Shopify Inventory Items, Stock Items, or the template and matrix workflow. No screen ID should be inferred from a standard installation or from another connector.
Where to Check Your Work
The Biz-Tech Services Shopify Acumatica Integrator exposes the documented mapping result across these screens and tabs.
1 Shopify Stores Import Settings: check Import Item, imported item type, item class, UOM, warehouseID, Use Numbering Sequence for SKU Generation, Replace Missing Products, Warehouse ID, Populate Items in Inventory Details, and Save Item Properties in Line Notes.
2 Cross-Reference options and Cross-Reference tab: confirm that the item entity is selected before expecting its values to appear, then review the Shopify Value and Acumatica Value fields that the screen exposes.
3 Shopify Inventory: use Load Shopify Items or Get Item by ID, review the Shopify SKU, and confirm the result of Sync from Shopify in the Acumatica inventory record.
4 Inventory Mapping: confirm the Acumatica property, Shopify property, product-level or variant-level metafield selection, and the import or export checkbox for each mapping.
5 Export Item Mappings: confirm that every product field intended for synchronization is selected before running a related processing screen.
6 Shopify Product tab: after template synchronization, confirm the generated Template ID, Shopify Product Data, and Export to Shopify state.
7 Matrix Items and Shopify Details tabs: confirm which matrix items were selected with Include Item in Sync and which variants are ready to synchronize.
8 Export Shopify Inventory Items: confirm that the intended price, description, and weight checkboxes were enabled in Export Item Mappings before processing.
9 Import Shopify Orders or another importing workflow: when a line does not resolve to the expected item, compare the SKU, Import Item state, item creation defaults, Cross-Reference setup, Replace Missing Products, and Warehouse ID.
Shopify Product and Variant Mapping Frequently Asked Questions
Does the connector map a Shopify SKU to an Acumatica inventory item?
Yes, in the documented Shopify-to-Acumatica path. Sync from Shopify takes the Shopify item SKU and creates an Acumatica Inventory ID. The source does not describe normalization or duplicate-SKU handling.
Can I map a different Acumatica item code when exporting to Shopify?
The documentation says the connector does not support mapping during Acumatica item export. It sends the Acumatica Inventory CD as the Shopify SKU.
What happens when a Shopify item does not exist in Acumatica?
With Import Item selected, the connector can create a new item using the configured imported item type, item class, UOM, and warehouseID defaults. Without Import Item, the documented fallback uses Replace Missing Products and Warehouse ID, although the manual does not explain the fallback record in detail.
Can the connector generate an SKU when Shopify does not provide one?
Use Numbering Sequence for SKU Generation allows a value to be generated during item creation when the system does not find an SKU. The corresponding numbering sequence must be configured or an error message is displayed.
How are Shopify variants represented in Acumatica?
The documented model uses a Template Item as the base product and Matrix Items as the individual variants. Each matrix item represents one attribute combination and is stocked, priced, and sold separately.
Can product and variant metafields use different mappings?
Inventory Mapping supports Shopify metafields at the product or variant level. Retrieve existing fields with Get Metafields and select import or export for each mapping. The source does not provide examples of the allowed data types or conversion rules.
Does the connector support item aliases and alternate identifiers?
The Biz-Tech Services Acumatica Shopify Integration documents SKU-based identity, selected Cross-Reference entities, and property mapping. It does not define an alias table, alternate item ID, wildcard match, customer part number, or vendor part number for product and variant resolution.
Why did a product field fail to update in Shopify?
Check Export Item Mappings and the relevant Inventory Mapping direction. The manual warns that price, description, weight, or other data is not updated when the required creation or update checkbox is not selected.
Work With the Biz-Tech Services Shopify Connector
Reliable Shopify product mapping starts by treating item identity, field properties, and variant structure as separate controls. Validate the SKU and missing-item behavior first, then configure Inventory Mapping, and finally confirm how Template Items and Matrix Items appear as products and variants.
If you need help validating Shopify SKU resolution, item-creation defaults, metafield mappings, or template and matrix item synchronization, visit https://biz-techservices.com to work with the Biz-Tech Services Acumatica Shopify Integrator.
