Zupright Documentation

Product documentation

Practical product guidance for Zupright modules. These public docs share content with in-app contextual help.

Browse documentation
Inventory/ Item masterReady

Inventory Items & SKUs

Understand item masters, SKUs, stock behavior, tracking policies, pricing defaults, and location availability.

Items define the business object your teams buy, sell, store, produce, or service. SKUs are the sellable or stockable variants of that item, such as size, color, packaging, or UOM-specific versions.

In Zupright, the Item Details workspace brings together item identity, SKU behavior, tracking policy, barcode identities, UOM setup, and current availability by SKU and location.

Key terms

Item
The master record for a product, material, service, asset, or non-stock business object.
SKU
A specific stock keeping unit or variant under an item. Use SKUs for variants that need separate stock, barcode, price, or tracking behavior.
Item Code
The business code for the item master. Keep it stable and readable for operations and reporting.
SKU Code
The code for a specific SKU or variant. It should be unique and suitable for warehouse and sales workflows.
Item Type
The root behavior of the item, such as stock-backed, service, digital, or asset-oriented.
Category
The commercial or operational classification used for browsing, reporting, tax assignment, and policy defaults.
UOM
Unit of measure. Base, purchase, and sales UOMs should reflect how quantities are stored and transacted.
Track Inventory
Controls whether the item participates in warehouse stock balances and movement history.
Stockable
Indicates that quantities are held in inventory locations and can be reserved, received, moved, or issued.
Batch / Lot Tracking
Groups stock by batch or lot for traceability, expiry, recalls, or regulated handling.
Serial Tracking
Tracks individual units by serial number. Use it for assets or unique high-value items, not bulk goods.
Barcode
A scannable identity for an item, SKU, or vendor-specific packaging code.
Reorder Level
The replenishment threshold that helps buyers and planners identify when stock needs attention.
Minimum Stock
The lowest intended stock position for a SKU/location policy.
Maximum Stock
The upper planning limit used for replenishment and overstock control.
Default Warehouse
The default warehouse used when transactions do not specify a more precise warehouse.
Default Location
The default storage or staging location used for item movement suggestions.
Purchase Price
The default buying price used as a starting point for procurement documents.
Sales Price
The default selling price used as a starting point for sales documents.
Valuation Method
The inventory valuation policy. Treat changes after transactions as controlled policy changes.
Active / Inactive
Controls whether the item or SKU is available for new transactions.
Supplier / Vendor
A preferred or known source for purchasing the item.
Tax Classification
A placeholder for statutory category assignment such as HSN, SAC, HS, HTS, TARIC, or service category.
Attachments / Notes
Supporting documents or operational notes used for item governance where available.

Using Item Details

Use the item details panel to validate identity, behavior, policy, UOM, pricing, tax classification, barcode, and location availability before using the item in purchasing, sales, production, or inventory movement.

Availability by SKU and Location

Availability is summarized by SKU and location so the same location is not repeated unnecessarily. On hand, reserved, and available quantities should be read as current operational balances, not as planning forecasts.

Governance Guidance

Treat tracking mode, valuation, and tax classification as controlled fields once transactions exist. Changes can affect downstream procurement, inventory, sales, and financial reporting.

Best practices

  • Keep item names business-friendly and understandable to non-technical users.
  • Use SKU records for variants instead of encoding every variant into the item name.
  • Enable lot or serial tracking only when operations actually need that traceability.
  • Avoid changing tracking mode after transactions exist unless a clear migration policy is approved.
  • Use reorder levels and minimum/maximum stock policies for replenishment control.
  • Keep barcode values unique and aligned with scanner workflows.
  • Separate item master defaults from transaction snapshots; documents should preserve the values used at transaction time.

Common mistakes

  • Using the item name as the SKU code and losing variant-level clarity.
  • Enabling serial tracking for bulk goods where batch tracking or no tracking would be simpler.
  • Forgetting the default UOM and creating inconsistent purchase or sales quantities.
  • Creating duplicate SKUs for the same physical variant.
  • Editing tax or valuation fields after transactions without a policy decision.

Related documents

Inventory LocationsStorage and movement points used by stock balances.WarehousesWarehouse setup and operational scope.Procurement Purchase OrdersPurchase documents that consume item and SKU defaults.Financials Purchase InvoiceInvoice capture that references PO and item context where available.