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.
