How ESAAB works

One single journey, not loose modules

ESAAB does not chain independent screens: it models supply as a continuous cycle. What is consumed feeds what is replenished; what arrives is validated and located; every movement is traced; and all of it becomes actionable visibility. The high-level functional diagram looks like this:

1. Consumption at the source → records usage at the point of use.
2. ↓ feeds
3. Automated replenishment → turns consumption into prioritized requirements and hands them to the purchasing process / ERP.
4. ↓ turns into an order and dispatch
5. Assisted receiving → validates by batch and expiry, reconciles against the order and locates the incoming stock.
6. ↓ updates stock on hand
7. Inventory and traceability → maintains location, balances, counts and kardex by batch and expiry.
8. ↓ emits signals
9. Visibility and alerts → dashboards, KPIs and notices that anticipate consumption again and close the cycle.

The cycle is closed: the visibility of the last stage feeds the replenishment of the first, so the system stops lagging behind the operation and starts anticipating it.

Each box in the diagram corresponds to a real operational step, not a technical layer. ESAAB sits as an operational layer on top of the ERP and the logistics operator (3PL): it does not replace them, it keeps them aligned with what happens in the laboratory.

Recording usage where it actually happens

The stage that breaks the cycle of late records: consumption is captured at the point of use, not hours or days later in a spreadsheet.

• Capture at the point of use Supply usage is recorded at the bay, the workstation or the laboratory self-service point, at the moment it happens. No deferred data entry, and no stock left out of date between usage and record.
• Point-of-use station (LabPoint) ESAAB LabPoint —touchscreen and barcode reader— lets users check stock and location and record consumption with traceability right where supplies are used, without returning to a central computer.
• Consumption attribution Each issue is linked to its source and to its product, batch and expiry, so consumption is not an aggregate number but a traceable data point that can feed replenishment.

Turning consumption into replenishment, with no spreadsheets or emails

Recorded consumption does not stay as history: it becomes the input for replenishment. ESAAB turns issues and minimums into requirements, instead of relying on someone checking a spreadsheet in time.

• Minimum rules and operational signals Minimum levels and replenishment rules are defined per product and warehouse. When the balance crosses the threshold, ESAAB detects it and flags it, instead of waiting for the stockout to make it obvious.
• From consumption to requirement Consumption and minimums become prioritized replenishment requirements: orders and requisitions that reflect what is actually missing, not a manual estimate.
• Pass-through to purchasing and the ERP The requirement is handed to the purchasing process and the corporate ERP so the order flows without re-keying. ESAAB does not replace purchasing or accounting close: it feeds them with reliable operational data.

Receiving what arrives by validating it, not counting it twice

When the order arrives, ESAAB assists receiving so it is fast and verified: scanning instead of typing, validation instead of trust, reconciliation against the order instead of a double count.

• Scan and batch/expiry validation Stock is received by barcode reading, capturing product, quantity, batch and expiry date. Validation warns of expired or near-expiry products and of inconsistencies before they enter the warehouse.
• Reconciliation against the order What is received is reconciled against the order or purchase order: shortages, surpluses and differences are identified, and receiving is approved with an explicit operational close, not an unsupported "received as agreed."
• Handheld operation for the floor Receiving can run on handheld devices with a scanner, designed for the operator on the warehouse floor: the same validation, without being tied to a desktop computer.

Knowing what you have, where it is, and which batch it belongs to

Between receiving and consumption, ESAAB keeps inventory alive: locations, counts and movements that match physical reality and leave a trail by batch and expiry.

• Location control Every stock item has a known location within the warehouse. Location changes and transfers between warehouses are recorded as movements, so the system always reflects where each product physically is.
• Physical counting and adjustments ESAAB supports physical counting —full or partial— and the controlled adjustment of differences, so system inventory and real inventory converge instead of drifting apart over time.
• Kardex and stock by warehouse Each movement feeds the product kardex and the balances by warehouse: the full history of entries, issues and adjustments, and the stock available at each location, consultable at any time.
• Batch traceability and barcode labels Product, batch and expiry travel with every movement end to end. ESAAB generates barcode labels to identify products and locations, which makes scanning at consumption, receiving and counting consistent.

Turning the operation into information before anything runs out

The cycle closes when everything recorded becomes actionable visibility. ESAAB does not wait for the stockout: it anticipates it.

• Dashboards and KPIs Operational boards and reports show consumption, balances, receipts and pending replenishment, so the state of supply is consultable at any time and not rebuilt by hand every time someone asks.
• Notifications and alerts that anticipate stockouts ESAAB issues notices for stock below the minimum and for near-expiry products, so you can act before stockouts or expiry affect the operation. The signal arrives while there is still room to replenish.