NexCommand AINexCom Knowledge Base
Tutorial

Create a stock item

Choose Supply Chain, then Items & Categories and Item.

Supply ChainUpdated 13 October 2026Configuration-aware guidance

Before you start

Use your authorized ERP account and the correct company. These screenshots use fictional staging records. Replace the example quantities, dates, warehouses and values with your approved business information. Submission affects the relevant workflow or stock ledger; review the draft first.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Addresses used in this tutorial

ERP_URL is your organization’s ERP address. ACADEMY_URL is the Academy base address: staging uses https://erpstaging.nexcommand.ai/academy; production uses https://academy.nexcommand.ai. Saved record IDs and temporary draft IDs differ between installations. Course IDs and element IDs in the example are not portable to another installation.

Step-by-step instructions

Step 1 of 5

Open Items & Categories

Choose Supply Chain, then Items & Categories and Item.

Example / selection
Supply Chain → Items & Categories
Expected result
The Item list is available.
Expected URL expression{ERP_URL}/desk/nexcom-workflow/Supply%20Chain/Items%20%26%20Categories
Open Items & Categories — redacted NexCom tutorial image
Actual staging capture. Personal identity masked; the captured application viewport is retained. Scroll position follows the action shown.
Step 2 of 5

Start the item

Check whether the item already exists, then select Add Item.

Example / selection
NC-DOCS-STOCK-02
Expected result
The new-item form opens.
Expected URL expression{ERP_URL}/desk/item
Start the item — redacted NexCom tutorial image
Actual staging capture. Personal identity masked; the captured application viewport is retained. Scroll position follows the action shown.
Step 3 of 5

Enter the item identity

Enter a unique Item Code and descriptive Item Name. Choose a stock UOM and open the full form to review stock settings.

Example / selection
DEMO — Documentation pressure sensor; Nos
Expected result
The item identity and unit are explicit.
Expected URL expression{ERP_URL}/desk/item
Enter the item identity — redacted NexCom tutorial image
Actual staging capture. Personal identity masked; the captured application viewport is retained. Scroll position follows the action shown.
Step 4 of 5

Review stock settings and group

Enable Maintain Stock for a physical inventory item. Select the appropriate Item Group using the category control. Review purchasing and sales applicability. A service item requires different stock settings.

Example / selection
DEMO Components; Maintain Stock enabled
Expected result
The item is ready for stock transactions.
Expected URL expression{ERP_URL}/desk/item/new-item-{TEMP_ID}
Review stock settings and group — redacted NexCom tutorial image
Actual staging capture. Personal identity masked; the captured application viewport is retained. Scroll position follows the action shown.
Step 5 of 5

Save and verify

Save and confirm that the record URL contains the permanent item code. Reopen it before adding transaction data.

Example / selection
NC-DOCS-STOCK-02
Expected result
The item is saved and enabled.
Expected URL expression{ERP_URL}/desk/item/{RECORD_ID}
Save and verify — redacted NexCom tutorial image
Actual staging capture. Personal identity masked; the captured application viewport is retained. Scroll position follows the action shown.

Verified result

The pressure-sensor item was created and saved in staging with stock tracking, DEMO Components and Nos. The receipt, transfer and physical-count tutorials use this pressure sensor; the procurement and scanner examples use the earlier NC-DOCS-STOCK-01 sensor. This master creation does not post inventory; variants and services are separate activities.

Troubleshooting

Wait for Link search results and choose the exact record. Leave each edited field to commit its value. Check required dates in every item row. A saved draft and a submitted record are different states. If validation fails, correct the highlighted field and verify the saved result before continuing.

Was this useful?