Managing stock levels

Definition

Stock management is a set of rules and procedures that ensure the right quantity of product is available at the right time in warehouses and points of sale, taking into account demand, lead times and the seller’s business goals.

How stock management works

Stock management includes recording current inventory, demand forecasting, calculating reorder points, reserving stock and transmitting data to sales channels (including Kaspi.kz). The process typically looks like this:

• data collection: sales, reservations, returns, deliveries and defects;
• demand forecast per SKU for the planning horizon;
• calculation of reorder point and replenishment quantity;
• placing orders with suppliers taking lead time and minimum order quantities into account;
• receipt of goods and their distribution across warehouses or to a fulfilment centre.

For sales via Kaspi.kz an important element is timely synchronization of stock in the catalogue. If stock is not updated, an item can be ordered when actual stock is zero, which leads to cancellations, fines and a drop in the product’s ranking in search results.

Why this matters for a Kaspi.kz seller

Concrete reasons why stock management affects a seller’s profit and reputation:

• Fewer cancellations and returns: order cancellations due to out-of-stock items worsen the cancellation metric. On Kaspi.kz a high cancellation rate can lead to restricted seller functionality and lower customer trust.
• Ranking and visibility: Kaspi factors product availability into ranking. Products with stable availability receive more impressions and clicks.
• Cost of lost revenue: example: a product with a gross margin of 4,000 KZT selling 30 units/month, if out of stock for 5 days in a month, loses approximately 5,000 KZT revenue per day × 5 = 25,000 KZT. This is direct loss before reputational effects.
• Logistics penalties and extra costs: frequent rush deliveries or small order batches increase unit cost. With planned orders, logistics savings per batch can be 10–20%.

Examples of real situations on Kaspi.kz

Below are three typical seller cases in Kazakhstan and practical takeaways.

1. Case — seasonal demand: home appliances before Nauryz

   An electronics seller records a 40% sales increase in the two weeks before Nauryz. If planning is based on monthly average, stock runs out and cancellations occur. Solution: increase order quantities ahead of the season using a short-term forecast (weekly) and safety stock adjusted for the expected uplift; negotiate earlier shipments with suppliers or stage partial deliveries to avoid gaps.

2. Case — supplier lead time growth

   A seller suddenly faces a two-week increase in lead time due to supplier constraints. Without adjusting reorder points, the seller experiences stockouts. Solution: monitor lead time trends, recalculate reorder points immediately, and, if possible, use alternative suppliers or emergency shipments to bridge the gap.

3. Case — inaccurate integration with the marketplace

   Stock numbers from the warehouse are uploaded only once per day. High-turnover SKUs sell out mid-day, causing overselling and cancellations on Kaspi.kz. Solution: increase synchronization frequency for fast-moving SKUs (via API/webhooks), reserve stock for pending orders and implement alerts for discrepancies.

Practical techniques and calculation algorithms

Basic formulas and rules you can apply immediately:

• Daily average demand = total sales for period / number of days in period. Use 30–90 days depending on volatility.
• Reorder Point (ROP) = average daily demand × lead time + safety stock.
• Safety stock can be estimated as z × σd × sqrt(lead time), where σd is the standard deviation of daily demand and z is the service level factor (for example, z≈1.65 for ~95% service level).
• Replenishment quantity (EOQ / batch) — use business rules: either economic order quantity formulas, or fixed multipliers aligned with supplier MOQ and logistics efficiency.

Practical tips:

• segregate SKUs by velocity (fast / medium / slow) and apply different replenishment policies and sync frequencies;
• for promotional periods plan a separate forecast window and treat promotions as a separate demand driver;
• maintain a small emergency buffer for top-SKU items that heavily affect ranking and revenue;
• run weekly or daily reviews of top 100 SKUs by turnover and margin to catch deviations early.

Technical tools and integrations

Recommended tools and patterns for Kazakhstan sellers:

• ERP / WMS — central source of truth for receipts, shipments and stock movements. Ensure it records reservations and quality quarantine.
• API integration with Kaspi.kz — real-time or near-real-time stock updates via API or webhooks reduce oversells. For heavy SKUs consider a high-frequency sync (5–15 minutes).
• Middleware / iPaaS — use an integration layer to map data between ERP, marketplaces and couriers, handling transformations, error retries and logging.
• Forecasting tools — from simple statistical models (moving average, exponential smoothing) to ML models for complex seasonality or promotion effects.
• Monitoring and alerting — dashboards for Days of Inventory, stockout rate, cancellations and lead time variability; set threshold alerts for each metric.

Integrations to prioritise:

1. ERP → Kaspi API: push available stock and reservations;
2. Kaspi webhooks → ERP: receive order/reservation events and update available stock;
3. Logistics partner → ERP: receive shipment status and expected receipts.

When choosing vendors or contractors in Kazakhstan, check experience with Kaspi.kz flows and local courier integrations.

Seller mistakes and how to avoid them

Common pitfalls:

• Infrequent or manual stock updates: leads to oversells. Automate synchronization and increase frequency for fast movers.
• Ignoring reservations and pre-orders: available stock must exclude reserved quantities. Track pending orders and shipments.
• Wrong lead time assumptions: underestimate variability. Use historical lead time distribution, not a single number.
• No seasonality adjustment: planning by long-term averages misses peaks. Use short-term forecasts for promo windows.

How to avoid them: automate integrations, run regular data audits, implement adaptive replenishment rules and conduct stress tests for peak scenarios.

Implementing a stock management system: roadmap

Example phased approach for a Kaspi.kz seller:

1. Assessment (2–4 weeks): map current processes, systems and top pain points; identify top SKUs by revenue and cancellations.
2. Quick wins (4–8 weeks): increase sync frequency for top SKUs, add simple reorder rules, configure alerts for discrepancies.
3. Automation (2–4 months): implement API/webhook integration, automate reservation handling and basic forecasting.
4. Optimization (3–6 months): refine forecasts, implement safety stock by SKU group, tune reorder quantities and supplier collaboration.
5. Continuous improvement: monthly reviews, A/B tests for replenishment policies, and updates for new sales channels or promos.

Conclusion and a practical tip

Good stock management balances service level, carrying costs and supplier constraints. For Kaspi.kz sellers, accurate and timely synchronization with the marketplace is crucial — it protects ranking, reduces fines and preserves revenue.

Practical tip: start by identifying your top 20% SKUs that generate 80% of revenue — automate and prioritise them first (higher sync frequency, tighter monitoring and dedicated safety stock). This delivers the fastest impact on cancellations and sales.

Часто задаваемые вопросы

How to calculate the reorder point (Reorder Point) for a specific SKU on Kaspi.kz taking into account lead time and demand variability?

The reorder point is usually calculated as average daily demand × lead time plus safety stock. Safety stock is determined by demand volatility and the desired service level (for example, using the standard deviation of demand over the period and a safety factor). For practice, use sales data from the last 3–6 months and the current lead time from your supplier.

How to synchronize stock between ERP/warehouse and the product page on Kaspi.kz to avoid selling with zero stock?

Set up two-way integration via API or regular batch uploads at a frequency that matches sales volume (high-frequency SKUs — every 5–15 minutes, others — hourly or per shift). Account for reservations and in-progress shipments when calculating available stock, and process Kaspi webhooks for instant order status changes. Regularly reconcile reports and trigger automated alerts on discrepancies.

Which metrics should be monitored to timely detect risk of stockouts and avoid fines on Kaspi.kz?

Key metrics are Days of Inventory, stockout rate, order cancellation rate and sell-through rate. Also monitor average lead time and its variability; a sudden rise in lead time or a drop in sell-through requires immediate order adjustments. Set threshold alerts for each metric.

How to properly account for returns and defects in the system so that stocks on the platform remain correct?

Introduce a returns intake procedure: quarantine — quality check — decision to return to sale or write off, and record this status in the accounting system. Only after checks are complete update available stock and synchronize changes with Kaspi; unrecorded returns cause discrepancies and overselling. Include average processing time of returns when calculating safety stock.

What typical mistakes during stock management implementation most often lead to reduced visibility and sales on Kaspi.kz and how to avoid them?

Common mistakes are infrequent or manual stock sync, ignoring reservations and preorders, incorrect lead time accounting and not considering seasonality. Avoid them by automating integrations, running regular data audits and applying adaptive replenishment rules (including seasonal coefficients and promotion effects). Also run peak-sale test scenarios and have an emergency replenishment plan.