What is How Does Sage 100 Pricing Hierarchy Work?

Definition

The Sage 100 pricing hierarchy determines which configured price or discount applies to an item when a customer quote, sales order, or invoice is entered. Pricing can depend on the item, customer, quantity purchased, price level, effective dates, and discount rules enabled in the company's Sales Order and Inventory Management setup. Understanding the hierarchy helps sales teams quote consistently and helps finance protect margins while maintaining accurate transaction values.

The exact order in which pricing rules take precedence depends on the Sage 100 version, installed modules, and configuration. Businesses should verify their system's pricing options and test representative transactions rather than assume every installation follows an identical sequence.

Pricing Rules and Their Priorities

Sage 100 pricing typically draws on item prices, customer-specific arrangements, price levels, quantity breaks, and applicable discounts. The system uses its configured rules to determine the price presented for a transaction. A customer agreement may provide a special price for one item, while a quantity-based rule may offer a different rate for a larger order. The applicable result depends on which records and options are active and how precedence is configured.

For example, assume an item has a standard price of $100 per unit, while a customer-specific price is $92. If the customer orders 20 units and a quantity-break price is also configured, the user should confirm which rule takes priority in the live Sage 100 transaction. The order's unit price and extended amount should reflect the rule that actually applies, not a manually assumed discount.

Pricing should also be reviewed alongside the company's Approval Hierarchy. If a sales representative requests a discount outside authorized limits, the business can require review before the exception is accepted.

How Customer and Item Pricing Interact

Customer records help define the commercial terms associated with an account, while item records provide product-specific pricing information. Price levels can support different selling arrangements, such as standard, wholesale, or contract pricing, when configured. Quantity breaks may reward larger orders, and effective dates can control when a promotion or special rate applies.

Before finalizing a quote or sales order, confirm the customer account, item code, unit of measure, requested quantity, and relevant pricing dates. A price intended for a case of 12 should not be applied as though it were a single-unit price. Similarly, a special rate that has expired should not be treated as current without verifying the configured terms.

For purchasing context, How Does a Purchase Order Work? 2025 Complete Guide explains how requisitions, approvals, and purchase orders establish authorized buying terms. Although purchase order pricing concerns procurement rather than customer selling prices, consistent controls across both processes improve spend visibility and financial accountability.

Testing and Troubleshooting a Price Result

When a displayed price does not match expectations, trace the transaction from the customer and item records through the applicable price level, quantity break, discount, and effective date. Check whether the transaction uses the expected unit of measure and whether a manual price override has been entered. Compare the result with a known test case and confirm that the order, quote, and invoice carry the intended amount.

  • Unexpected standard price: Check the item's base price and the price level assigned to the transaction.
  • Customer discount not applied: Verify the customer-specific terms, eligible items, and effective dates.
  • Quantity price differs: Confirm the ordered quantity, unit of measure, and configured break thresholds.
  • Quote and order differ: Review the records and settings used when the order was created, including any changed quantities or manual overrides.

An Order Validation Process can help confirm that the customer, item, quantities, and commercial terms are accurate before the order proceeds. An Order Review Process adds a check that the final price aligns with the approved quote or agreement. Documenting these checks makes pricing decisions easier to explain and audit.

ERP Integration and Finance Automation

Pricing hierarchy remains a business rule within Sage 100, but related workflows may connect the ERP to sales approvals, finance operations, and reporting tools. The ERP Integration Layer: How It Powers Finance Automation explains why reliable data exchange matters when extending finance workflows around an ERP. ERP Modernization vs Finance Automation: Key Differences provides additional context on how system improvements differ from automating the work that takes place around those systems. How Many Levels Does a Typical ERP System Include? offers a broader view of how application, data, and AI layers can work together.

The Hyperbots Platform supports company-specific configurations for ERP integration, workflows, roles, and general ledger structures. Process Specific Capabilities describes process-trained AI support for finance workflows, while Ready to Deploy Capabilities covers pre-trained agents and ERP connectors. Self Learning Capabilities explains how human feedback can refine workflow handling, and Human in the Loop describes how people can review exceptions and provide oversight. These capabilities can support surrounding finance processes, but Sage 100's configured pricing rules should remain the source of truth for the transaction price.

For cross-system planning, Sage Intacct Integration is a relevant example of connecting finance systems and exchanging data. A Statement Of Work can document the scope, responsibilities, and acceptance criteria for an integration or pricing-process improvement project.

Best Practices for Pricing Control

Maintain clear ownership of price records and discount approvals. Restrict changes to authorized users, record the business reason for exceptional pricing, and test common customer and quantity scenarios after configuration changes. Review expired promotions and customer agreements regularly so that the active pricing setup reflects current commercial policy.

Finance teams should compare selling prices with approved discount limits and item costs when evaluating gross margin. Sales teams should confirm the final price on the quote or order before communicating a commitment to the customer. Together, these practices improve consistency, protect profitability, and help prevent avoidable corrections during invoicing.

Summary

Sage 100 pricing hierarchy uses configured item, customer, price-level, quantity, date, and discount rules to determine the applicable selling price. The precise precedence depends on the system's setup, so verify the resulting price in a representative transaction. Accurate records, controlled overrides, approval checks, and regular testing help businesses maintain consistent quotes, reliable invoices, and stronger margin visibility.