Inventory Count

Conduct physical inventory sessions directly from the app: scan products on the shelf, record counted quantities, manage lots and expiration dates, count by weight with automatic calculation, and sync adjustments to Odoo with a single touch.

Overview

Inventory Count is SiltaFlow's feature dedicated to warehouse physical inventory sessions. It lets you start a count by selecting a warehouse zone, scanning the products present, and recording the quantities observed. At the end, adjustments are sent to Odoo with a single touch, which automatically updates stock levels.

You can scan barcodes in three ways: with your device camera, with a connected hardware scanner (like Zebra terminals), or by typing the code manually. The app automatically recognizes the barcode format — you don't need to worry about what type of code you're reading.

Each session is automatically saved on the device as you proceed. If you need to stop the count, you can close the app without losing anything and resume exactly where you left off. No paper forms, no double data entry.

Internet connection is required to create a new session and to send adjustments to Odoo. The actual counting — scanning and recording lines — works even without network.

Managing Sessions

Each inventory is organized into sessions. A session represents a physical count: it is associated with a warehouse zone and contains all the lines you recorded during the count.

Creating a new session

From the Inventory Count screen, tap New Session. The app asks you to choose the warehouse zone to inventory. After selection, the session is automatically created with a name that includes date and time (for example INV-2026-04-05 14:30) and is in Draft state: it's ready but not yet active.

Session states

A session goes through these states during its lifecycle:

State	When it is in this state	What you can do
Draft	Session just created, no products yet recorded	Start scanning, cancel the session
In Progress	At least one product recorded	Continue scanning, modify lines, validate or cancel
Completed	Adjustments sent to Odoo successfully	Read-only, delete from list
Cancelled	Manual cancellation by the operator	Delete from list (no changes sent to Odoo)

Resuming an interrupted session

On the main Inventory Count screen you will find a list of all open sessions (in Draft or In Progress state). Each session shows the name, zone, number of lines already recorded, and creation time. Tap a session to reopen it and continue counting from where you left off.

Every confirmed line is saved immediately on the device. Even if the app closes unexpectedly or the battery dies, you lose nothing of what you have already recorded.

Scanning Products

Within an open session, you can add products to the count in three ways:

Camera — Tap the camera icon and frame the product barcode. The app recognizes it automatically.
Hardware scanner — If you use a terminal with built-in scanner (like Zebra), aim and press the physical trigger. Reading happens without touching the screen.
Manual entry — Tap the text field and type the product code.

The app reads all common barcode formats: EAN-13, Code 128, QR Code, DataMatrix, and GS1 codes that contain more information in a single barcode (see the dedicated section below).

The confirmation window

After each scan, a confirmation window opens with the product information found. From here you can verify the data and record the counted quantity before saving the line.

The window shows:

The product name and its code
The quantity that Odoo expects to find in that zone (theoretical stock)
The lot selector, if the product is tracked by lot
The field where you enter the quantity you actually counted

After verifying the data, tap Confirm to save the line. The session automatically becomes In Progress on the first confirmed line. If you want to cancel the scan without recording anything, tap Cancel.

If you scan the same product and lot multiple times, the quantity is summed on the existing line rather than creating a duplicate line. Tap the line in the list to correct it if you scanned by mistake.

Lots and Expiration Dates

For products tracked by lot, the confirmation window shows a selector to choose the correct lot. The behavior changes depending on the information available:

GS1 barcode with embedded lot — The lot is selected automatically. You have nothing to do.
Product with a single lot in the zone — The lot is selected automatically.
Product with multiple lots available — A dropdown menu appears: select the correct lot before confirming.

If the barcode also contains the expiration date (as in GS1 codes on food or pharmaceutical packages), it is shown in the window as a reference.

Weight Count

For products sold in bulk or in bags (flour, granules, spices, etc.), SiltaFlow lets you count by weight instead of by piece. Instead of counting units one by one, weigh all the goods on a scale and enter the total weight: the app automatically calculates how many units correspond.

Weight counting must be enabled in the app Settings (Warehouse section). If you don't see it in the confirmation window, check that the option is active.

How it works

Scan the product: the confirmation window opens.
Enable the Weight toggle in the window.
Enter the total weight detected on the scale (in kg or grams, as set).
The app displays the calculation in real time: for example 342.5 kg ÷ 25 kg/pc = 13.7 → 14 pc.
If the result seems correct to you, tap Confirm. You can also modify the calculated number of pieces before confirming.

To use this feature, the product must have the weight per unit configured in Odoo. If the field is empty, the toggle remains disabled.

Some barcodes (the so-called "weighted codes") already include the product weight within them. If you scan one of these codes, the weight field is automatically populated: you have nothing to type.

The Differences Between Counted and Expected

For each inventory line, the app shows the difference between the quantity you counted and what Odoo expected to find (the theoretical stock).

Surplus (you counted more than expected) — The difference is shown in blue. For example, if Odoo expected 20 pc and you counted 23, the line shows +3.
Deficit (you counted less than expected) — The difference is shown in red. For example, if Odoo expected 20 pc and you counted 18, the line shows -2.
No difference — The counted quantity matches the theoretical stock: everything is fine.

At the bottom of the line list there is a summary with the total products counted, the number of lines with differences, and the session state. It updates in real time as you proceed.

If you notice an error on an already recorded line, tap it to reopen the edit window: you can correct the quantity, lot, or weight without having to delete and re-enter the data.

Validating the Inventory

When you have finished counting, tap the Validate Inventory button. The app sends the quantities to Odoo, which automatically updates stock levels by creating adjustment moves for lines where there is a difference. Lines without a difference do not generate any changes.

After validation, the session moves to Completed state and is no longer editable. You can keep it in the list as a reference or delete it to keep the screen clean.

Avoid validating the inventory while there are picks or transfers in progress on the same zone. Run inventory sessions at low traffic times (for example before opening or after closing) to avoid discrepancies caused by parallel movements.

Usage Examples

Cyclic inventory by zone

The manager plans a weekly inventory divided by zones (Zone A on Monday, Zone B on Wednesday). The operator creates a session for the zone of the day, scans all the products on the shelf, and taps Validate at the end. Odoo updates stock levels automatically. No Excel spreadsheets, no double entry.

Products with lots and expiration dates (pharmaceutical or food)

The operator scans the GS1 barcode on the packages: the app automatically extracts product code, lot number, and expiration date and pre-fills the confirmation window. The operator verifies the quantity and confirms. No manual typing, zero transcription errors.

Bulk products by weight

A food company counts sacks of flour. The operator weighs each pallet on an industrial scale, enters the total weight, and the app calculates the number of equivalent sacks using the weight configured in Odoo. Three times faster than piece-by-piece counting.

Interrupted and resumed inventory

The operator is halfway through counting when called for an urgent matter. Closes the app: everything already recorded is safe on the device. The next day reopens SiltaFlow, finds the session in the list with the lines already recorded, and resumes exactly where they left off.

Step-by-Step Procedure

Complete example: cyclic inventory of a zone with lot-tracked products.

Open SiltaFlow and tap Inventory Count in the Warehouse menu.
Tap New Session and select the zone to inventory. The session is created in Draft state.
Physically go to the zone with the smartphone in hand. Tap the camera icon and scan the barcode of the first product.
The confirmation window opens: verify product name, expected quantity, and lot (pre-selected automatically if the barcode contains it). Enter the quantity you actually counted physically.
Tap Confirm. The line is saved and the session moves to In Progress state. Continue with the next product.
As you proceed, lines with differences are highlighted in red (deficit) or blue (surplus). Tap a line to correct it if necessary.
When finished, review the summary at the bottom of the list. If everything is correct, tap Validate Inventory.
The app syncs quantities with Odoo. The session moves to Completed state. Adjustments are visible directly in Odoo.

Tips

Plan sessions by zone, not by product. Creating a session for each physical area lets you distribute the work among multiple operators, each on their own zone, and validate progressively as zones are completed.

Use a hardware scanner for maximum speed. With a well-configured Zebra terminal, you can scan and confirm hundreds of references per hour without ever touching the virtual keyboard.

Before validating, scroll through the list of lines and check those with large differences. A very large difference often indicates a product scanned without completing the physical count, or a repeated accidental scan.

If you use weight counting, verify before the inventory that the weight per unit field is correctly filled in Odoo for all affected products. An incorrect value produces systematically wrong counts on all lines.

For large warehouses where inventory takes multiple days, leave the session In Progress between shifts. No need to validate every evening: resume the session on the next shift and validate only when the count is truly complete.

Requirements

To use SiltaFlow's Inventory Count:

Internet connection to create the session and send adjustments to Odoo (line counting works offline too)
An Odoo account with write permissions on warehouse stock levels and the Warehouse Manager role for validation
Odoo version 16 or later
Android device version 10 or later
For weight counting: unit weight configured in Odoo for affected products and option enabled in app Settings