← All examples

Worked example · fictional data

Buying stock ahead of a busy sales period.

A webshop or wholesaler is preparing a promotion. The buyer asks the system to compare expected sales, available stock and delivery commitments and investigate which products need replenishment.

This example illustrates a possible implementation. It does not describe a delivered client project or measured result.

Stock scenarioFictional example
Promotion in three weeksWill we have enough stock?
Scenario: 20% additional sales
Product A · opening stock 180 units. Week 2 receipt: 120 units.
Product AW1W2W3
Expected demand80120160
Closing stock100100−60

Opening: 180 units · week 2 receipt: 120

Proposal for the buyerReorder 100 units

Minimum order: 100. Delivery before week 3 still needs confirmation.

The workflow in detail

Systems involved
Webshop · Inventory · Purchase orders · Promotions
How the work happens today
The buyer exports sales, checks inventory and looks for supplier confirmations. A planned promotion lives in a separate calendar. Its effect on stock is estimated in a spreadsheet.
What the system does
The system combines sales history, stock, reservations and confirmed receipts. Calculation rules or an appropriate forecasting model project inventory. Agents investigate exceptions, request missing delivery information and prepare purchase proposals using minimum order quantities and lead times.
What the buyer does
The buyer asks: ‘Assume twenty percent more sales for this promotion. Where will we run short?’ They can add a delayed delivery or request alternatives. The system recalculates. The same check can run every Monday without the buyer writing queries or integrations.
Assumptions and decisions
A forecast remains an estimate. Promotional effects and uncertain deliveries are identified separately. The buyer reviews orders and budget exceptions. This example places no order before approval and checks current inventory again before processing it.
What Silvant builds
Silvant connects sales and inventory data, defines product mappings and calculations and builds purchasing and approval steps. Testing against historical periods assesses forecast usefulness. Employees can create scenarios and checks within the available data and permissions.
  1. 01

    Promotion and assumptions

    The buyer selects products, dates and expected additional sales.

  2. 02

    Project stock

    Expected demand is compared with available inventory and receipts.

  3. 03

    Compare alternatives

    Reordering, transferring stock or adjusting the promotion are explored.

  4. 04

    Review the order

    The buyer chooses; approved proposals can be recorded in the purchasing system.

Does this work look familiar?

Tell us how your team handles it today and which systems are involved.

Tell us what you need
More about this application →