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.
Start With Pricing Levels
Pricing levels are the named customer groups used by product pricing policies. Common examples are Retail, Wholesale, Distributor, Installer, Online, or Marketplace. An account or sales channel can use a pricing level, and product policies can then define the price for that level.

- Keep names clear: operators should understand who belongs in each level.
- Do not delete casually: active product policies and accounts may rely on a level.
- Use settings docs for setup: pricing levels, category defaults, units of measure, and adjustments live under Products and Pricing Settings.
Review The Product Pricing Tab
Open a product and go to the Pricing tab. The Regular Price card shows list price, cost, margin amount, margin percent, and last purchase price. The Pricing Policies table shows account and level rules that can override the product list price during order entry.

- List Price: the fallback selling price when no active policy applies.
- Cost: the product cost used for margin math on this tab.
- Margin Amount: list price minus cost.
- Margin %: margin amount divided by list price.
- Last Purchase Price: a receipt-derived reference value that helps explain recent cost movement.
Add A Regular Pricing Policy
Regular policies set a specific sell price for a pricing level, an attached account, or both. Use them for most customer pricing because the resulting unit price is explicit and easy to audit.

- Click Add Pricing Policy.
- Select the Pricing Level.
- Optionally attach a specific account when only that account should receive the price.
- Choose Regular.
- Enter the quantity break.
- Enter the sell price.
- Review calculated adjustment and margin.
- Leave Active on when the policy should be used.
- Turn Default on only when this should be the fallback product policy.
- Click Save Policy.
Use Quantity Breaks
Quantity breaks apply when the order quantity meets or exceeds the policy quantity. Within the same scope, Arcus uses the highest qualifying quantity break.
- Qty 1: applies when the customer buys 1 or more.
- Qty 10: applies when the customer buys 10 or more.
- Qty 25: applies when the customer buys 25 or more.
- Highest match wins: if the order quantity is 30 and policies exist at 1, 10, and 25, the 25 break applies.
Use Multiplier Policies Carefully
Multiplier policies are calculation-driven. The modal previews the multiplier, derived sell price, adjustment percent, and margin percent while you configure the policy. Use this when your pricing process is based on a multiplier instead of a fixed sell price.

How Arcus Chooses A Price
When a product is added to an order without a manual sell-rate override, Arcus looks for the most specific active policy that qualifies for the order context and quantity.
- Variant and account policy: the exact variant and the exact account.
- Variant and pricing level policy: the exact variant and the order or account pricing level.
- Variant default policy: the exact variant default.
- Product and account policy: the product and exact account.
- Product and pricing level policy: the product and pricing level.
- Product default policy: the product default policy.
- List price: used when no active policy qualifies.
Manual Price Changes On Orders
Order entry can still allow an operator to override a calculated sell rate when permissions and order state allow it. Manual changes should be treated as exceptions because they can bypass the product pricing policy that would otherwise apply.
- Use pricing policies: for repeatable customer or tier pricing.
- Use manual price edits: for one-off corrections, manager-approved exceptions, or temporary overrides.
- Review locked states: some order states restrict line edits after payment, fulfillment, invoice posting, or cancellation history exists.
Common Blocks
- Price did not change on the order: confirm the policy is active, the quantity meets the break, and the order uses the expected account, variant, and pricing level.
- Wrong quantity break applied: check for a higher qualifying break in the same scope.
- Account-specific price is missing: confirm the policy is attached to the correct account, not just the account pricing level.
- Policy will not save: check for an existing active policy with the same level, account, and quantity break.
- Margin looks wrong: review product cost, product list price, sell price, and whether the item is a kit with component cost changes.
- Multiplier result looks wrong: test the product on a draft order and use a Regular policy when the team needs a fixed, explicit sell price.

