Item list price
Base sales or purchase price and currency for an item or item group.
ERP Guides
Prices and commercial terms
How to Manage Prices
Price management is more than storing one number for an item. When sales or purchase direction, customer/supplier, currency, quantity, validity dates and permissions are defined together, the price applied to an order becomes clear and traceable.
How an order price is resolved
Account-specific terms
A specific price linked to a customer, supplier, channel or agreement.
Transaction conditions
Quantity tier, variant, delivery terms and start/end dates.
Applied order price
The result of conditions captured on the order at transaction time.
When setting up a price list
Define scope and validity for every price
A price row should specify not only the amount but also the transaction conditions under which it applies. If multiple rules exist for one item, define their priority in advance.
Price scope
Sales or purchase; which item, customer/supplier and channel does it cover?
Amount and currency
Specify unit price, currency, unit of measure and tax-display assumptions.
Quantity and variant
Define which quantity tier, colour/size or product option the price applies to.
Validity and approval
Start/end dates, approver, reason and applicable sales channel if limited.
Price precedence
Make the applicable price rule visible on the order
An item list price, customer agreement and quantity tier may suggest different prices for the same item. The system or business procedure should define which source takes precedence and show users where the applied price came from.
Illustrative price condition
Item MX-02 · Customer A
General list price1.000 TRY
Customer agreement price920 TRY
Applied to order920 TRY
Customer price takes precedence; effective 1–31 March. Illustrative values.
Tax, freight and other terms are determined separately under company settings.
Quantity and condition tiers
Manage different order quantities with separate price conditions
If volume pricing is used, define quantity limits, units and how boundary values are handled. Ambiguous or overlapping tiers can select the wrong price during order entry.
Standard terms
Single / lower volume
1–9 units
Defined volume threshold
Mid volume
10–49 units
Agreed tier
Higher volume
50+ units
Quantity ranges are illustrative and are not price recommendations or commercial advice.
Price revisions
Publish new prices with an effective date
Overwriting a previous price can obscure why older orders were entered at that amount. Create a new version, set its effective date and retain the last date the previous price applied.
1 · Prepare a draft
Identify affected items, customers, channels and currencies.
2 · Test sample transactions
Check expected results across multiple item and customer conditions.
3 · Approve and activate
Record the reason, approver and effective date.
4 · Preserve history
Archive the old price; do not alter amounts already applied to past orders.
Permissions and approval
Keep discount exceptions visible and traceable
Define who can enter prices, where approval is required and how exceptions are justified. Showing list price, special price and additional discount separately on the order makes the net amount traceable.
User permissions
Permission to create or change prices.
Discount threshold
Approval step for out-of-policy changes.
Reason record
Reason for the exception and related order.
Transaction history
Who changed what and when?
Price records within an ERP
List prices, account-specific prices, volume tiers, validity versions, applied order prices and user permissions.
Profit targets and consumer discount advertising
A price-list record does not determine profitability or cover all consumer promotion rules. Business specialists should assess margin and cost assumptions; requirements for consumer-facing prices and discounts should be checked separately against current official rules.
Frequently asked questions about price management
How do item list prices and customer-specific prices work together?
Business rules should define whether the item list price or customer/agreement price takes precedence. The applied rule and price source should be visible on the order, with exceptions following approval.
When should price lists be updated?
Prepare new prices before their effective date and review them against sample item and customer conditions. Creating a new validity version instead of deleting old prices preserves transaction history.
Can discounts be changed freely on every order?
This depends on company pricing and approval policy. Limits can be set by user, amount or percentage; changes outside permissions can require a reason and authorised approval.
Does this guide cover promotions and consumer-facing discount prices?
This guide focuses on managing internal ERP price records and transaction conditions. Requirements for consumer-facing labels, tariffs or discount announcements are separate and should be checked against current official sources.