The Loribase Difference

Costs and stock your operation can trust

Event-driven inventory isn’t a technical slogan. It’s why Loribase can show where stock went, why cost changed, and what really happened before your team makes the next decision.

app.loribase.com/my-company/events

Recent Events

Operational timeline for the morning shift

184 today

Receipt

09:14

Extra Virgin Coconut Oil

INV-4421 · L-2026-018·Aline

Reservation

09:07

Lavender Soap 200g

Order WEB-1938 · 24 units·Caio

Transfer

08:52

Kraft Packaging 200g

SP -> RJ · TR-208·Marina

Adjustment

08:26

Caustic Soda

Cycle count · -2 kg·Pedro
Every event preserves user, time, batch, and source document.Immutable history

The Loribase Difference

The real problem isn’t the movement. It’s losing trust in the number

Most operations don’t suffer because stock moves. They suffer because the number everyone depends on can’t explain itself. When quantity changes, the team still doesn’t know what happened, who changed it, and if the cost impact has been reflected.

This is what turns routine into investigation. Planning sees one balance, the warehouse sees another, finance questions the margin, and every discrepancy becomes manual reconstruction between spreadsheets, messages, and memory.

When trust in the balance is weak, all following decisions become weak too: purchasing, pricing, production planning, recall response, and margin analysis. The problem isn’t just traceability. It’s operational confidence.

Model

What event-driven inventory means

In the event-driven model, nothing is ever overwritten. Every action that affects inventory (a purchase arriving, a production consuming raw materials, a reservation for a work order, a transfer between warehouses) is recorded as a discrete, permanent event. The current stock quantity is always derived from the sum of all events, never stored as a mutable value.

Purchase received

A new batch enters inventory. The event records the supplier, quantity, unit cost, and lot number. Stock increases.

Production consumption

Raw materials are consumed by a production run. The event records which batch was used (FIFO), the quantity, and the resulting product.

Reservation

Stock is committed to a work order or shipment. It remains physically present but is marked unavailable for other operations.

Transfer between locations

Stock moves between warehouses. Both the source and destination events are recorded simultaneously, maintaining a complete trail.

Manual adjustment

Physical counts sometimes reveal discrepancies. The adjustment event records the reason, the quantity changed, and who authorized it.

States

Four inventory states, always accurate

Because every event is recorded, Loribase can calculate four accurate states simultaneously, without any approximation or polling:

Physical stock

The precise quantity that physically exists in your warehouse right now. Increases with every purchase or production receipt. Decreases with confirmed consumption or outbound transfer.

Reserved stock

The quantity committed to an in-progress work order, production run, or confirmed shipment. Still physically present, but not available for other uses.

Available stock

Physical stock minus reserved. The only number you should use when planning new production or accepting customer orders.

Incoming stock

Confirmed but not yet received purchase orders. Know what is coming before it arrives so you can plan production without waiting for physical delivery.

Benefits

What you gain with event-driven inventory

Complete audit trail

Every stock movement has a timestamp, a user, a reason, and a link to the originating document (purchase order, production run, or adjustment). Nothing is ever unknown.

Accurate FIFO costing

Because purchase events carry the unit cost and date, Loribase knows exactly which batches were consumed by each production run, calculating real FIFO costs automatically, not estimates.

Lot traceability

You can trace any product batch forward (which productions used it) or backward (which purchase lot it came from). Essential for quality recalls, compliance, and expiry management.

No silent overwrites

Data cannot be silently changed. Any correction requires a new event with a reason. Your historic data is always intact and legally defensible.

Real-time without polling

Because state is derived from events, inventory visibility is always current, with no scheduled sync, no batch update, and no two-hour delay before numbers reflect reality.

Comparison

Event-driven vs. quantity-update: a practical comparison

Stock drops unexpectedly

No way to find out why; the number was just updatedTraditional
Find the exact event: consumption, transfer, or adjustment, with user and timestampLoribase

Production cost calculation

Manual lookup of what was purchased and when, often estimatedTraditional
Automatic FIFO: system knows exactly which batch was used and at what priceLoribase

Quality issue traced to a batch

Impossible if the original lot was not manually recordedTraditional
Every production event links to the input batches; trace in secondsLoribase

Stock discrepancy found in count

Accept the new number and move on; history is lostTraditional
Adjustment event created with reason; history preserved alongside correctionLoribase

Compliance or external audit

Reconstruct from spreadsheets and memory, often incompleteTraditional
Export the full event log: every movement, every user, every timestampLoribase

Ready to professionalize your operation?

Start your 14-day trial today. No commitment. Cancel anytime.

Want to compare plans first? See the pricing page.