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.
When To Use Variants
- Use variants: the same product family has option choices and each choice needs its own SKU, stock, price, weight, or component recipe.
- Use a physical product: there is only one sellable item and no option matrix is needed.
- Use a kit: the customer buys one bundle and Arcus consumes component products.
- Use a variant kit: each variant choice has its own component recipe.
- Use a service: the item is labor, fees, or non-stock work with no inventory or shipping behavior.
Review The Variants Tab
Open the variant parent product and select Variants. The tab shows active variant count, image, option label, SKU, price, cost, on-hand quantity, status, and the actions to open or edit each variant. Matrix view is available when the option shape fits a matrix; list view is better for direct row review.

- Open: use the full variant editor for detailed setup.
- Edit: make quick SKU, price, or cost changes from the row when available.
- Status: inactive variants are hidden from new order entry but kept for history.
- Kit badge: the variant has its own component recipe.
- Selection: select rows when you need bulk price, cost, or active-state changes.
Generate Variants From Options
- Open the variant parent product.
- Go to Variants.
- Click Generate from Options or Add Variants.
- Enter each option name, such as Size, Color, Lid, or Model.
- Add values for each option.
- Review the generated count.
- Click Generate Variants.

Use The Variant Editor
Click Open on a variant row to use the full editor. The editor is where variant-level setup lives when the child choice needs behavior that differs from the parent or from another variant.

- General: variant title, SKU, barcode, active state, and option values.
- Media: variant-specific image behavior when the child needs its own image.
- Variants: switch between sibling variants without returning to the parent first.
- Pricing: variant-level pricing and policies when the child should price differently.
- Purchasing: vendor or buying setup when the child is purchased as its own SKU.
- Inventory: variant-specific stock and movement context.
- Shipping: dimensions, weight, and package behavior for the exact child variant.
- Components: visible when the variant is configured as a kit.
Variant Settings
Use Variant settings for high-impact toggles. The current settings drawer includes active state and kit configuration. If a variant is a kit, selling that variant consumes the components defined on the variant Components tab.

How Variants Affect Other Workflows
- Order entry: operators select the exact variant, not just the parent, before adding the line.
- Inventory: on-hand, allocated, available, transfers, counts, and receiving are tied to the child SKU.
- Pricing: variant policies can beat product-level policies when a child needs different pricing.
- Fulfillment: stock, serials, bins, package data, and component requirements come from the selected variant.
- Purchasing: vendor setup and reorder behavior can differ by variant when each child is bought separately.
- Marketplace listings: external listings should map to the exact product or variant being sold on the channel.
Common Blocks
- Variant does not appear in order entry: confirm the variant and parent are active, and that the order search is using the right SKU or title.
- Generated count looks wrong: review option names and values before generating. The count is the combination of valid values.
- SKU will not save: active variants must keep unique SKUs inside the entity.
- Matrix view is unavailable or too large: use List view when the option set is too large or does not fit a clean matrix.
- Variant kit will not fulfill: review variant components, component stock, serial requirements, and order holds.
- Wrong listing receives updates: review marketplace mapping and make sure the external listing is tied to the exact child item.

