Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt

Use this file to discover all available pages before exploring further.

Product type is a workflow setting, not just a label. It controls which tabs appear, whether inventory is tracked on the record, how kits and variants behave, and how downstream inventory value can flow into accounting.

​
Where Product Type Is Managed

Open the product detail page, then use the More actions menu in the header. Physical products, kit products, and variant parents can show Convert Type when your role can edit products. Box and service products do not use this conversion flow.

Product detail page with the More actions menu open, showing Duplicate, Convert Type, Archive, and Delete actions
Avoid converting records with real history If the product has already been sold, purchased, stocked, fulfilled, or used as a kit component, conversion may be blocked. When the old behavior must remain traceable, archive the product and create a replacement record with the correct type.

​
What Each Product Type Means

  • Physical: a stocked item that can be bought, received, counted, allocated, packed, shipped, and valued.
  • Kit: a sellable bundle. The kit line is sold to the customer, but component products drive buildability, cost, inventory availability, and fulfillment.
  • Variant Parent: the family record for child variants. The parent organizes options such as size or color, while child variants carry the real stock and fulfillment behavior.
  • Box: a package or container record used by shipping and packing rules, not a normal sales SKU.
  • Service: labor, fees, subscriptions, installation, or other non-stock lines. Services do not need inventory or FIFO cost layers.
Pick the physical reality first If a warehouse can count, receive, pick, or ship the exact item, it is usually Physical. If the customer buys one bundle made from other SKUs, it is usually Kit. If the customer chooses from a product family such as size or color, use a Variant Parent with child variants.

​
Product Type Conversion Rules

The Convert product type modal shows the current type, allowed target type, and the operational effect before anything changes. Select the target type first so the What changes panel matches the action you are about to take.

Convert product type modal showing current type, new type, conversion effects, and Convert button
  • Physical to Variant Parent: enables variant setup so option sets and child variants can be added. Arcus blocks this if the original product already has live order history.
  • Physical to Kit: changes the record into a kit and clears reorder point and safety stock because kits derive availability from components. Arcus blocks this if the product has on-hand inventory.
  • Variant Parent to Physical: removes variant option sets and child variants when eligible. Arcus blocks this when the parent has more than one variant or live orders.
  • Kit to Physical: changes the kit back to a physical SKU when it has no remaining components. Arcus blocks this when kit components remain or live order history references the kit.
Conversion blockers protect history A blocker is not a random error. It usually means Arcus found orders, inventory, variants, kit components, or other records that would make the conversion unsafe. Resolve the blocker only when the history truly should change; otherwise create a new product.

​
How Product Type Affects Tabs

Arcus only shows tabs that make sense for the product. Physical products can show Purchasing, Inventory, Bin Locations, Shipping, Manufacturing, Listings, and Analytics. Kits show Components. Variant parents show Variants, and the child variants carry their own focused editor for pricing, purchasing, inventory, shipping, and component behavior.

  • Inventory tab: appears for stocked products, not for pure service records or variant parents that delegate stock to child variants.
  • Components tab: appears for kits so the team can maintain what the kit is made from and review kit cost behavior.
  • Variants tab: appears for variant parents so operators can generate and maintain child SKUs.
  • Shipping tab: matters for physical items, kit shipping setup, boxes, package presets, and freight rules.

​
Inventory Value On A Product

Use the product Inventory tab when you need product-specific stock and value context. The tab has its own location filter, so you can review all locations or one location without depending on the global header location.

Product Inventory tab with all-locations scope, stock cards, run rates, Inventory by Location table, value column, and Recost action
  • Available: stock that can still be promised after allocations.
  • On hand: physical quantity in the selected scope.
  • Allocated: quantity reserved for open demand.
  • OPO: quantity on open purchase orders that has not been received yet.
  • Avg unit value: average value shown for the balance row, based on the current inventory value and quantity.
  • Value: inventory value for that location or rollup.
The product tab is an operating view Operators use it to understand stock and cost health for one SKU. Accounting reports still remain the source of truth for financial statements and period-level review.

​
FIFO Layers

Receiving stocked inventory creates FIFO cost layers. Outbound inventory movement consumes eligible layers in FIFO order so cost of goods sold and inventory value have a traceable basis. The product tab can show active layers that still have remaining quantity.

Active FIFO Layers table with location, received quantity, remaining quantity, unit cost, total cost, and received date
  • Received: original quantity added to the layer.
  • Remaining: quantity still available on that layer.
  • Unit cost: cost captured when the layer was created.
  • Total cost: remaining layer quantity multiplied by unit cost.
  • Received at: when the layer entered inventory.
Use transaction detail for consumed layers The product tab shows active layers. For a shipped, adjusted, or consumed movement, open Inventory Transactions and use FIFO Layer Detail to see which layers were consumed by that outbound transaction.

​
When To Use Recost

Recost appears on a location row only when Arcus detects a negative inventory value and the user has inventory adjustment permission. It recomputes the balance row from the live FIFO ledger, refreshing the product value and average unit value.

Recost is a repair action, not a costing shortcut Use Recost when the balance row is poisoned by bad historical value data, such as old zero-cost layers that left the row negative. Do not use it to change a legitimate cost. If a receipt, vendor bill, adjustment, or purchase order cost is wrong, correct that source workflow first.

​
Accounting Impact

Product costing connects to accounting through inventory value, cost of goods sold, receiving, vendor bills, adjustments, and period review. A product can look operationally fine and still need accounting review if the cost basis is wrong.

  • Receiving: creates stock and cost basis. PO receiving should stay tied to the purchase order workflow.
  • Adjustments: can change quantity and value when used for real corrections with a reason.
  • Fulfillment: consumes stock and uses FIFO cost behavior for COGS context.
  • Kits: inherit component availability and cost behavior instead of behaving like a standalone stocked SKU.
  • Variant parents: organize child SKUs, but child variants carry the stock and cost activity.

​
Common Blocks

  • Convert Type is missing: the product may be a service or box, or your role may not allow product edits.
  • Physical to kit is blocked: remove or clear on-hand inventory before converting, or create a new kit product.
  • Variant parent to physical is blocked: review child variants and order history before attempting conversion.
  • Kit to physical is blocked: remove kit components first, unless history means a replacement product is safer.
  • Value is negative: review receiving, adjustments, and FIFO layers. Use Recost only when the row needs repair from the ledger.
  • Average unit value looks wrong: check whether the selected location, active FIFO layers, or source receiving costs explain the value.

Product Setup

Create physical products, services, and product records.

Product Variants

Generate variants, manage child SKUs, use the variant editor, and set variant kit behavior.

Kits and Assemblies

Create kits, add components, understand kit cost, and sell bundles safely.

Inventory Management

Track stock, locations, reorder points, and inventory movement history.

Inventory Transactions

Audit stock movement history, movement types, supply and demand rows, and FIFO layer detail.

Receive Inventory

Receive standalone stock, choose the right PO receiving path, and protect FIFO cost basis.