---
title: "How to prepare stock management in a software system · Lyntev"
description: "Define items, units, movements, reservations and replenishment before configuring software. Includes fictional calculations and a stock-operations worksheet."
url: "https://lyntev.com/en/guides/prepare-stock-management-system"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to prepare stock management in a software system

# How to prepare stock management in a software system

A stock system must explain where items are, their condition and which are already committed. Recording only a total quantity does not resolve reservations, returns or damaged products. This guide helps prepare rules and tests so the figures match operations.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 18 November 2026.
About 5 minutes to read.

[Start reading](<https://lyntev.com/en/guides/prepare-stock-management-system#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/gerir-stock-com-sistema.txt>)

**From data to the next decision**Choose the question, define the calculation and act on the result.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/gerir-stock-com-sistema>); source revision 18 November 2026.

By the end, you can:

- Distinguish quantities and statuses
- Define replenishment with clear assumptions
- Check physical stock against records

In this guide

1. [Define the item and unit before the quantity](<https://lyntev.com/en/guides/prepare-stock-management-system#artigos-e-unidades>)
2. [Separate physical, usable and available stock](<https://lyntev.com/en/guides/prepare-stock-management-system#quantidades-e-estados>)
3. [Record movements with their source and reason](<https://lyntev.com/en/guides/prepare-stock-management-system#movimentos-e-rastreio>)
4. [Prepare replenishment using lead time, demand and commitments](<https://lyntev.com/en/guides/prepare-stock-management-system#reposicao>)
5. [Compare records with physical quantities](<https://lyntev.com/en/guides/prepare-stock-management-system#contagens>)
6. [Test operations most likely to change the balance](<https://lyntev.com/en/guides/prepare-stock-management-system#testes-e-erros>)
7. [Document the rules the team will follow](<https://lyntev.com/en/guides/prepare-stock-management-system#ficha-stock>)
8. [Sources and criteria](<https://lyntev.com/en/guides/prepare-stock-management-system#fontes>)

## Define the item and unit before the quantity

Each item should have a stable reference and a description distinguishing it. Decide when colour, size or packaging represent separate variants. A barcode can help identify an item, but does not replace its definition. Confirm how supplier codes and internal codes are handled.

Choose the stock-control unit and permitted conversions. Buying a box and consuming individual units requires knowing how many units that box contains. In the fictional Oficina Horizonte example, filter F-10 is controlled by the unit and purchased in boxes of ten. Receiving three boxes adds thirty units, not three. The conversion should belong to the item and be tested.

Define the item and unit before the quantity

| Field | Fictional example | Decision needed |
| --- | --- | --- |
| Reference | F-10 | Stable identifier |
| Description | Replacement filter, model A | Distinguish variants |
| Stock-control unit | Unit | Basis for receipts and issues |
| Purchase packaging | Box of 10 units | Conversion and multiple |
| Location | Warehouse A, shelf 2 | Where to count and pick |

## Separate physical, usable and available stock

Define every displayed quantity. Physical stock indicates what is at a location; some may be quarantined or damaged. Usable stock excludes what cannot be delivered. The quantity available for new requests also depends on reservations and the commitment rule used.

In a fictional scenario there are 100 physical units, of which 5 are quarantined and 20 reserved. If reservations apply only to usable units, 95 remain usable and 75 available for new requests. A purchase of 30 units expected next week does not increase today’s physical availability. It should appear separately with its date and status.

The system must make these assumptions visible. If the team subtracts a reservation already deducted in the availability indicator, it counts the same obligation twice. Write each indicator’s formula in the project dictionary.

- [Test the last ring unit between the shop counter and online shop in Porto](<https://lyntev.com/en/website-design/porto#city-focus>)

## Record movements with their source and reason

Receipts, issues, transfers, returns and adjustments have different meanings. Each movement should state item, quantity, unit, location, time and responsible person or source system. Link it to the operational document where one exists so you can explain why the balance changed.

A transfer between locations is neither a purchase nor a sale. A return may need inspection before rejoining usable stock. If the process requires batch or individual-unit tracking, define when that identification is collected and how its journey is followed. Do not enable fields without preparing the team to complete them at the right times.

Fictional return journey

1. **Receive**

  Link the return to the original movement.
2. **Separate**

  Place in an inspection location or status.
3. **Decide**

  Approve reuse, repair or permanent removal.
4. **Record**

  Apply the authorised movement and reason.

## Prepare replenishment using lead time, demand and commitments

Before automating purchases, define how requirements are calculated. A simple approximation for the reorder point adds expected consumption during the supply lead time to a chosen allowance for uncertainty. Assumptions need review for seasonality, delays or limited information. The formula does not guarantee an absence of stockouts.

In a fictional example, consumption of 6 units per day, a lead time of 5 days and an allowance of 10 units produce a reorder point of 40 units. For this test, the position considered is 28 usable + 12 confirmed incoming − 8 committed = 32. Incoming items and commitments belong to the defined horizon and have not already been deducted from the 28.

If the policy proposes replenishing up to 70, another 38 units are needed. With boxes of ten, the proposal would be 40 units and the position would become 72. Odoo documentation shows minimum, maximum and multiple rules; confirm the definition used in your system. Start with suggestions reviewed by a person before authorising automatic orders.

- [Odoo: replenishment rules and purchase multiples](<https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.html>)

## Compare records with physical quantities

Define a counting routine by item, location or risk group. Odoo documentation presents cycle counts by location, an operational alternative to waiting solely for a full count. Frequency should reflect movement, value and your business’s history of discrepancies.

During counting, control movements or record a point in time enabling reconciliation. If someone removes five units while another person counts, the difference may be timing rather than loss. Request review where the discrepancy warrants it. A balance adjustment should retain the previous quantity, new quantity, reason and necessary approval.

### Fictional reconciliation example

The record showed 40 units at 10:00. The count at 10:15 finds 35. Before adjusting, an issue of 5 at 10:10 is confirmed. The movement explains the difference, so no loss adjustment is needed.

- [Odoo: inventory cycle counts](<https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.html>)

## Test operations most likely to change the balance

Use a small set of fictional items and run a complete cycle: receipt, reservation, partial delivery, return and count. Confirm the balance after each step and that its explanation can be consulted. A partial sale should not automatically consume the full quantity unless that is the rule.

Also test concurrency: two people try to reserve the last units. The system must apply the agreed policy without allowing a silently incompatible commitment. Define whether negative stock is accepted, in which circumstances and who can authorise it. A negative balance may be a deliberate operational exception or an error; do not hide it without investigation.

Test operations most likely to change the balance

| Common error | Preventive test |
| --- | --- |
| Confusing boxes with units | Receive two boxes and check the conversion. |
| Adding future purchases to current availability | Compare incoming dates and statuses. |
| Deducting the same reservation twice | Reconstruct the indicator’s formula. |
| Returning directly to usable stock | Test the inspection journey. |
| Adjusting without explaining the difference | Require a reason and check recent movements. |

## Document the rules the team will follow

Choose the first items and locations for a pilot, train the people receiving and issuing material, and monitor discrepancies. Confidence in stock comes from combining rules, timely recording and checks. Software should make that work easier and show exceptions requiring a decision.

### Worksheet for your project

```
Stock management worksheet
Items, variants and identifiers:
Stock-control unit and conversions:
Locations and usage statuses:
Definitions of physical, usable, reserved and available:
Movements and source documents:
Handling partial deliveries and returns:
Batch or individual-unit rules, if needed:
Replenishment lead time, demand and assumed allowance:
Position formula and horizon considered:
Minimums, targets, multiples and purchase approval:
Counts, movement control and adjustments:
Pilot tests, discrepancies and responsible people:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [Odoo 19 — Reordering rules](<https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.html>)
- [Odoo 19 — Cycle counts](<https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.html>)

## Continue to your next decision.

- [Map a business process](<https://lyntev.com/en/guides/map-business-process-before-automation>)
- [Migrate data to a system](<https://lyntev.com/en/guides/migrate-data-new-system>)
- [How to create a management dashboard](<https://lyntev.com/en/guides/create-management-dashboard>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
