Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

The Rate Moved, and Now Your Prices Differ in Three Places: Price List Management in an ERP

How to run retail, wholesale and dealer prices in an ERP in Uzbekistan: som pricing rules, mass repricing, discount limits, price history and channel sync.

The Rate Moved, and Now Your Prices Differ in Three Places: Price List Management in an ERP

Picture this. The dollar rate climbs, and on Monday a supplier sends a new price list: some items go up by 6–8%. A manager updates the Excel file, but the shop till still shows the old price. A sales rep takes a wholesale order from the outdated list on his phone. By Friday you discover that several hundred units were sold at well below the planned profit, and some at a loss. Has something like this happened in your business?

This guide is for anyone setting up a trading company in Uzbekistan. It explains how to run price lists in an ERP (enterprise resource planning software): several price types, rate-based costing, mass repricing, discount approvals, price history and who may change prices. A checklist at the end helps you prepare before rollout.

Pricing is a process that should become a rule. The approach of writing the rule on paper first and then handing it to software is covered in the guide to business process automation.

Why one price is not enough: price types

A price list is simply a list of products with their selling prices. A distributor rarely has just one. The same shampoo sells at one price to a shop customer, at another to a wholesale buyer and at a third to a dealer.

An ERP handles this with "price types". One product sits in several price columns. Each customer card carries a price type. When a manager opens an order, the system fills in the right price automatically.

  • Landed cost — For whom: Internal, never shown to buyers; How it is calculated (hypothetical example): Supplier price + freight + customs costs
  • Retail — For whom: Shop customers; How it is calculated (hypothetical example): Landed cost + 35% markup
  • Wholesale — For whom: Shops, small wholesalers; How it is calculated (hypothetical example): Retail price − 12%
  • Dealer — For whom: Regional partners, large volumes; How it is calculated (hypothetical example): Landed cost + 15%
  • Marketplace — For whom: Uzum Market and other platforms; How it is calculated (hypothetical example): Retail price + share of commission and logistics

The percentages are illustrative. What matters is that price types are linked by formulas, so when cost changes, every other price recalculates on its own.

Keep two terms apart. Markup is the percentage added on top of cost. Margin is the profit share inside the selling price. A 25% markup gives only a 20% margin. Mix them up and your prices will come out lower than planned.

Dollar costs, som prices: what the law requires

Companies that import goods usually see costs form in US dollars. Many foreign managers therefore want to price in dollars too. Uzbek law draws a clear line here.

Also read Software for a Building Materials Store in Uzbekistan: Units of Measure, Credit, Contractor Bonuses and Delivery Technology · 10 min

Under Article 9 of the Law on Currency Regulation (in the version adopted by Law ZRU-573 of 22 October 2019), prices for goods in Uzbekistan are set exclusively in som. Pegging the prices of goods sold in the country to foreign currencies or conventional units is not allowed. The exception is narrow: certain projects under public-private partnership or investment agreements with the Government, and only by decision of the President.

In practice it works like this. The dollar is only a basis for internal calculation. Your ERP stores landed cost in dollars and converts it to som at a rate you choose. The customer-facing price list, the invoice and the payment are in som only.

Which rate to use is a management decision: some use the Central Bank rate, others add a small buffer. The key point is that the rate should not reprice goods automatically every day. Otherwise till prices jump daily and customers stop trusting them.

A good practice is a threshold. For example, if the rate moves more than 2% since the last repricing, the system alerts the pricing manager. A person still makes the decision. Currency balances and exchange differences are covered separately in multi-currency accounting in an ERP.

An accountant recalculates product cost at the new dollar rate on a calculator

Mass repricing: thousands of items in one day

A supplier sends new prices, or the rate shifts noticeably. In Excel this means days of work and a risk of error in every row. In an ERP it is a single repricing document.

It usually follows six steps:

  1. Selection. Which items change: one supplier, a brand, a category or an import group.
  2. Rule. Apply the new rate to cost, upload the supplier's new file or raise prices by a set percentage.
  3. Rounding. Not 23,417 som but 23,500. The rounding rule is set in advance, to the nearest 100 or 500 som.
  4. Preview. The system shows old and new prices and margins side by side. Rows where margin falls below the minimum are highlighted.
  5. Effective date. The new price starts not immediately but, say, on Monday morning. Shops and reps are warned in the meantime.
  6. Approval. The person responsible for pricing approves the document. Only then do prices change.

The most common confusion is old stock in the warehouse. Do you sell it at the old price or switch at once? That is a policy question: management decides it once and records it in the system, so nobody invents the answer each time.

A hypothetical example: the week the rate went up

The case below is invented, but it reflects a pattern common in distribution.

A household chemicals distributor in Tashkent carries 1,800 items. Half are imported, with costs in dollars. The company has retail, wholesale and dealer prices, 12 sales reps and a store on a marketplace.

Over a month the rate rose noticeably. The system had a 2% threshold, so the pricing manager received an alert. She selected the import group, applied the new rate and opened the preview. For 140 items the dealer margin had fallen below the minimum. The dealer markup for those items was corrected by hand.

The document was approved on Thursday, effective Monday. On Friday reps saw the new prices in their mobile app and warned customers in advance. Tills and marketplace listings updated on Monday morning. Nobody dug for an Excel file in their inbox.

A sales rep tells a neighbourhood shop owner about new prices in advance

Discounts: who, how much and with whose approval

A discount is any step down from the list price. Without rules for discounts, the price list exists only on paper. A manager gives 10% to keep a customer, and later nobody can explain where the margin went.

An ERP controls discounts on three levels:

  • Automatic discounts. For volume (for example, −3% above 50 cartons), for a promotion period or for prepayment. They are written into rules and need no approval.
  • Role limits. The manual discount each role may grant. For example, up to 2% for a sales rep and up to 5% for the head of sales.
  • Approved discounts. Above the limit, the order stops and goes for approval. The approver sees the customer, the amount and the margin after the discount on a phone.

Judge a discount by margin, not by percentage. On a high-margin item a 5% discount may cost nothing. On a low-margin item the same 5% means a loss. How to build the approval route is shown in document workflow and approval chains in an ERP.

Who may change prices, and why price history matters

The right to change a price is one of the most sensitive permissions in a company. If a cashier, a storekeeper and a sales rep can all change prices, there is no control.

The rule is simple. Only the pricing manager or commercial director edits price types and formulas. Sales staff work within their allowed discount. Manual price entry at the till is switched off entirely.

Price history is a log of every change: which item, old and new price, who changed it, when and with which document. It pays off in three situations:

  • a customer says "you gave me a lower price last month", and a dispute begins;
  • margin dropped at month-end, and you need to find out why;
  • you need to check whether an employee cut prices on their own.

Combined with sales data, price history shows which pricing decisions earned profit and which cost volume. BI analytics in an ERP is the natural tool for that analysis.

Shops, reps and marketplaces: one price everywhere

A correct price in the ERP is useless if it never reaches the point of sale. Prices usually need to flow to four channels. An API in the table below is simply the way two programs exchange data automatically.

  • Shop tills — How the price gets there: Integration with the POS software; What to watch: Leave time to change shelf tags
  • Sales reps — How the price gets there: Mobile app; What to watch: New prices must be loaded for offline use too
  • Online store and chatbot — How the price gets there: Via API; What to watch: Promo prices should revert automatically when the promo ends
  • Marketplace — How the price gets there: Platform API or file upload; What to watch: Commission and logistics must be built into the price

Syncing and offline mode in a sales rep app are covered in mobile apps for field staff. Marketplace prices that follow competitors have their own logic, explained in automated repricing on marketplaces.

The core rule is a single source of truth. Prices change only in the ERP, and every other channel pulls them from there. If you edit a price by hand in the marketplace seller account, the next sync will overwrite it, or you will end up with two different prices.

Before rollout: an 8-question checklist

  1. How many price types do you have, and which formulas link them?
  2. In which currency does cost form, and at which rate is it converted to som?
  3. What rate change triggers repricing?
  4. What is the rounding rule?
  5. At what price is old stock sold?
  6. What is the discount limit for each role?
  7. Who changes prices, and who approves them?
  8. Which channels must receive a new price, and how fast?

With these answers on paper, configuring the system goes quickly. Without them, even the best software only spreads the confusion faster.

Key takeaways

A price list is not one file but a set of pricing rules. Price types are linked by formulas. The dollar is only an internal basis; customers in Uzbekistan see prices in som. Repricing runs as one document, with a preview and an effective date. Discounts are controlled through limits and approvals, and price changes through history. A good first step is to work through the checklist above with your commercial team this week.

Frequently asked questions

Can we quote prices in US dollars to local customers in Uzbekistan?

No. Under Article 9 of the Law on Currency Regulation, prices for goods sold in Uzbekistan are set only in som, and pegging prices to a foreign currency or conventional units is not allowed. You can keep dollar costs in internal accounting, for example to track import costs, but the customer sees a som price.

If the exchange rate moves every day, should prices change every day?

Usually not. Daily price jumps confuse customers and sales reps alike. A threshold works better: when the rate drifts beyond a set percentage since the last repricing, the system alerts the pricing manager, who makes the call.

Does a small company need several price types?

If you sell both to retail shoppers and to wholesale buyers, you need at least two. When they are linked by a formula, a cost change recalculates both at once and nobody has to update them by hand.

How do we move a price list from Excel into an ERP?

Clean the product catalogue first: duplicates, different names for the same item, old SKUs. Then agree on price types and the formulas between them. Only then import the price file, and compare the result against Excel for the first week.

Do your prices match across every channel?

In a short call we can review your current price types, repricing routine and discount rules for the Uzbek market and outline a sensible starting point in an ERP. Free, no obligation.

Book a consultation →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.