> ## 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. # Pricing Rules > Configure product list price, cost, customer pricing levels, account-specific prices, quantity breaks, and multiplier policies so order entry can choose the right sell rate. Pricing rules affect revenue. After changing important pricing, add a test line to a draft order and confirm the displayed sell rate before quoting or confirming customer work. ## 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. Entity Settings Pricing Levels page with a list of pricing levels and Add Level button * **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. Product Pricing tab with Regular Price summary and Pricing Policies table showing pricing level, attached account, quantity break, sell price, list price, adjustment, margin, active, and default * **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. * **Policy rows**: active customer, account, level, quantity-break, and default rules that can replace the fallback list price. * **Default**: marks the fallback policy for the product when no more specific active policy qualifies. **Edit list price and cost from the product header** On the product detail page, click **Edit**. The Pricing tab can then show editable list price and cost fields, and the page saves them when you click **Save Changes** at the top. ## 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. Add Pricing Policy modal in Regular mode with pricing level, attached account, product cost, product list price, quantity break, sell price, adjustment percent, margin percent, Active, and Default 1. Click **Add Pricing Policy**. 2. Select the **Pricing Level**. 3. Optionally attach a specific account when only that account should receive the price. 4. Choose **Regular**. 5. Enter the quantity break. 6. Enter the sell price. 7. Review calculated adjustment and margin. 8. Leave **Active** on when the policy should be used. 9. Turn **Default** on only when this should be the fallback product policy. 10. Click **Save Policy**. **Duplicate scopes are blocked** Arcus prevents active duplicate policies for the same product, pricing level, attached account, and quantity break. Edit the existing policy instead of creating a second active rule for the same scope. The modal warns when a matching active policy already exists and can route you back to edit that row. ## 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. Add Pricing Policy modal in Multiplier mode with cost, list price, quantity break, multiplier, derived sell price, calculated adjustment percent, and margin percent * **Multiplier**: enter the multiplier. The modal derives sell price from product cost times the multiplier. * **Derived sell price**: review the calculated price before saving. Switch back to Regular when the team needs one explicit fixed price. * **Adjustment and margin**: review these calculated fields before saving because they reveal the effect against list price and cost. * **Active**: only active policies can be used by order entry. Keep drafts inactive until the price is approved. **Always test multiplier pricing on an order** Multiplier policies are more sensitive than regular fixed-price policies because the final rate depends on calculation inputs. Add a draft order line after saving and confirm the previewed sell rate is the rate your team expects. ## Price Variants Carefully The variant editor can set a child variant's baseline list price and cost. When those fields are blank, the child falls back to the parent product values. Use this for option-specific cost or list price differences, such as a larger size or a premium finish. Customer-specific, account-specific, pricing-level, default, and quantity-break policy rows are maintained from the parent product Pricing tab in the current UI. After changing parent policies, test the exact variant on a draft order so the team can confirm the selected child SKU prices as expected. **Separate baseline price from customer policy** A variant baseline price answers "what is this option worth by default?" A pricing policy answers "what does this customer or pricing level pay?" ## 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-specific policies can qualify when they already exist, while the standard operator workflow manages customer and level policies from the parent product Pricing tab. 1. **Exact variant and account policy**: the exact variant and the exact account, when present. 2. **Exact variant and pricing level policy**: the exact variant and the order or account pricing level, when present. 3. **Exact variant default policy**: the exact variant default, when present. 4. **Product and account policy**: the product and exact account. 5. **Product and pricing level policy**: the product and pricing level. 6. **Product default policy**: the product default policy. 7. **List price**: used when no active policy qualifies, with variant baseline list price used for the exact child when it has one. **Specific beats general** Account-specific policies beat pricing-level policies. Variant policies beat product-level policies. Quantity breaks are evaluated inside the winning scope. ## 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. * **Default toggle did not change the order price**: confirm there is not a more specific active account, pricing-level, variant, or quantity-break policy that wins first. * **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. ## Related Articles Create physical products, services, and product records. Create kits, add components, understand kit cost, and sell bundles safely. Generate variants, manage child SKUs, use the variant editor, and set variant kit behavior. Manage pricing levels, product categories, units of measure, discounts, fees, and coupons. Create customer and vendor accounts with terms, addresses, and preferences. Use pricing rules, quantities, adjustments, and tax-aware line editing.