Price monitoring is the regular collection and analysis of competitors’ and your own product price offers with the goal of promptly adjusting prices to protect margin, turnover or share in the search results.
How price monitoring works
Price monitoring consists of three levels: data collection, analysis and action. Data collection can be manual, via the marketplace’s API or by scraping public product pages. Analysis turns raw data into signals—competitor price drops, promotions, availability changes. Action is a repricing rule or a notification to a manager.
- Data sources: Kaspi.kz product pages, promotions feeds, competitors’ exported price lists, internal ERP data on cost and stock levels.
- Update frequency: depends on the category: electronics and mobile devices — once an hour or more; FMCG and accessories — every 30–60 minutes under high competition; furniture and slow-moving appliances — once a day.
- Tools: manual checks, scraping scripts, API integration, specialized repricing services. AWW can integrate with price lists and exchange data via API to automate rules.
Why price monitoring is necessary for a seller on Kaspi.kz
Kaspi.kz is the largest platform in Kazakhstan by traffic and sales, where buyers often compare several offers inside a single product card. Incorrect pricing policy quickly affects sales and margins.
- Sales drop when lagging on price: in electronics categories, a competitor’s 5–10% price reduction can reduce a seller’s sales by 20–40% within 48–72 hours if the seller does not react.
- Margin and calculating the minimum price: with high competition on the Market, sellers often see margin disappear into negative territory with aggressive repricing. Practical rule: minimum allowed price = cost + mandatory expenses (Kaspi commission + delivery) + target margin, minimum 10–15%.
- Managing ads and promotions: Kaspi promotions and internal advertising campaigns change click-through rates. If the price in an ad is above the average in the product card, CPA increases and profitability falls.
Which metrics and events to track
Don’t limit yourself to price only. To make a correct monitoring decision, combine several indicators.
- Competitor price — the current price set by other sellers in the product card.
- Competitor availability — if a new leader has zero stock, their price signal is not critical.
- Your margin and cost — automatically calculate margin after all fees and logistics so repricing never pushes you below the safe level.
- Buy Box/offer position — who is winning the Buy Box and how position changes affect conversion rates.
- Promotion flags — whether an offer is part of a Kaspi promotion, coupon or flash sale; such prices are often temporary.
- Conversion and traffic — monitor changes in sessions and conversion when price or position changes.
- Price and sales history — trends help distinguish short-term drops from persistent undercutting.
Examples of situations on Kaspi.kz and what to do
Below are common scenarios and suggested responses.
- Competitor lowers price by a small amount (1–3%): if your margin is thin, ignore small moves or respond with a non-price action (improve delivery offer, add a coupon). For high-margin SKUs, a small repricing step may be acceptable with frequency limits.
- Competitor drops price by 5–10%: assess whether the change is promotional. If competitor stock is limited or flagged as a promotion, maintain price. If persistent and opponent has stock, apply staged repricing within your minimum price and limit change frequency.
- Sudden price war (multiple sellers undercutting): pause aggressive repricing, raise minimum thresholds, switch focus to profitable SKUs, and use marketing instruments (coupons, sponsored placements) for targeted visibility.
- Competitor price decreases but conversion doesn’t improve: this may indicate poor seller ratings or delivery terms from the competitor; do not automatically match the price.
- Buy Box loss without price change: check delivery times, seller rating, and fulfilment options. Sometimes improving delivery/service or enabling Kaspi fulfillment restores Buy Box without a price cut.
Practical tips for implementing and automating monitoring
- Define goals: decide whether you optimise for margin, volume or share. Rules differ for each goal.
- Set minimum allowed price: calculate it as cost + Kaspi commission + delivery + target margin. Enforce it in all automated rules.
- Use multi-level rules: aggressive repricing only for strategic SKUs, soft adjustments for the rest.
- Threshold triggers: react only to meaningful changes (for example, >3–5%) to avoid constant churn.
- Rate-limit updates: set cooldowns per SKU to avoid excessive API calls and price oscillations.
- Test on a subset: roll out repricing rules on a limited group before full deployment and monitor results.
- Integrate with ERP: ensure reliable SKU mapping, timely stock and cost updates and include returns/refunds in cost calculations.
- Monitor business metrics: track margin, turnover and Buy Box share after rule changes to verify their effect.
- Log and audit: keep histories of price changes, triggers and authors (automated or manual) for post-mortem analysis.
Common mistakes and how to avoid them
- Ignoring total cost: forgetting commissions, delivery and returns leads to selling at a loss. Always include all fees in minimum price calculation.
- Poor SKU mapping: mismatched SKUs result in wrong comparisons. Standardize identifiers and validate mappings regularly.
- Overreacting to short-term changes: reacting to temporary promotions causes margin erosion. Use promotion flags and historical checks to filter ephemeral signals.
- No cooldowns: frequent toggling harms margins and confuses buyers. Apply change frequency limits per SKU.
- Lack of testing: deploying rules platform-wide without tests risks large losses. Start small and iterate.
Conclusion
Price monitoring on Kaspi.kz is a strategic tool: with properly configured data feeds, sensible rules and integration with internal costs, sellers can defend margin and position without unnecessary price wars. Combine automated repricing with business logic, testing and human oversight to achieve stable results. AWW can help integrate data feeds and implement API-driven automation for reliable repricing workflows.
Часто задаваемые вопросы
- What update frequency should I set for price monitoring across different product categories on Kaspi.kz?
- Frequency depends on category volatility: electronics and mobile devices — from once an hour down to every 10–15 minutes under high competition; FMCG and consumables — every 30–60 minutes; furniture and large appliances — once a day. Use dynamic frequency: increase polling when competitors change prices sharply (e.g. >2–3% per session) and decrease it for stable items. Also consider API/scraping limits and system load.
- What additional data besides base price must be collected and why?
- Collect stock availability, promotion/coupon status, seller rating, delivery cost, historical price and sales dynamics, and internal data such as cost and inventory. These parameters help distinguish temporary promotions from long-term changes and correctly calculate minimum allowable price. Ignoring logistics and commissions risks misjudging margin.
- How to configure repricing rules to react to competitors but not destroy margin?
- Set a minimum price = cost + Kaspi fees + target margin and never allow automatic pricing below it. Use trigger thresholds (e.g. react only to competitor drops >3–5%) and limit change frequency per SKU. Implement multi-level rules: aggressive cuts only for priority SKUs and gentle adjustments for others.
- What signs indicate the start of a price war on the platform and what immediate actions should be taken?
- Signs: simultaneous sequential price drops by multiple sellers across a SKU group, sharp conversion decline despite maintained visibility, and accelerated frequency of price changes. In response, pause aggressive repricing, raise minimum thresholds, shift to marketing tools (coupons, promotions) and focus on margin-positive items. Analyze participants: it may be better to lose share on low-margin items than enter a race to the bottom.
- What common mistakes occur when integrating price monitoring with ERP and how to avoid them?
- Typical mistakes include incorrect SKU mapping, delays in syncing stock and cost, and ignoring all fees and returns in price calculations. Avoid them by standardizing mapping, exchanging data frequently (real-time or frequent batches) and accounting for all commissions and logistics when calculating the minimum price. Test rules on a limited set before full rollout and keep change logs.
