Event catalog¶
This catalog lists the business events published on the logs topic, module by module. Any module adding one records it here — see Emit a business event.
By platform convention, the WARN level marks deletions and cancellations, and the SECURITY level the uninstallation purge as well as exports.
Stocks¶
Inventories¶
| Type | Level | Subject | Emitted when | Data |
|---|---|---|---|---|
stocks.inventory.created |
INFO |
inventory |
An inventory is created | warehouse, type |
stocks.inventory.updated |
INFO |
inventory |
An inventory is modified, including its status changes and the bulk actions on its lines | lines_deleted, lines_treated, lines_untreated |
stocks.inventory.validated |
INFO |
inventory |
An inventory is validated and its variances are posted to stock | warehouse, lines |
stocks.inventory.finalized |
INFO |
inventory |
An inventory is closed | — |
stocks.inventory.adjusted |
INFO |
inventory |
An inventory is adjusted | — |
stocks.inventory.recalculated |
INFO |
inventory |
The theoretical quantities of an inventory are recalculated | — |
stocks.inventory.cancelled |
WARN |
inventory |
An inventory is cancelled | — |
stocks.inventory.restored |
INFO |
inventory |
A cancelled inventory is restored | — |
stocks.inventory.deleted |
WARN |
inventory |
An inventory is deleted | — |
stocks.inventory.imported |
INFO |
inventory |
The lines of an inventory are imported from a file | — |
Inventory lines are not journaled one by one
Modifying an inventory line emits no event: the journal aggregates those changes into stocks.inventory.updated, which carries the number of lines deleted, treated or put back on hold. An inventory of several thousand lines thus stays readable.
Operations and orders¶
| Type | Level | Subject | Emitted when | Data |
|---|---|---|---|---|
stocks.operation.created |
INFO |
operation |
A stock operation is created | type |
stocks.operation.validated |
INFO |
operation |
An operation is validated | type, lines |
stocks.operation.updated |
INFO |
operation |
An operation is modified | type, contact, date |
stocks.operation.executed |
INFO |
operation |
An operation goes from draft to execution | type, lines |
stocks.operation.deleted |
WARN |
operation |
An operation is deleted | type |
stocks.order.received |
INFO |
order |
A purchase order is received | — |
stocks.order.delivered |
INFO |
order |
A sales order is delivered | — |
stocks.order.reception_cancelled |
WARN |
order |
A reception is cancelled, including when the platform cancels the purchase order | — |
stocks.selling.cancelled |
WARN |
selling |
A sales issue is cancelled by the platform | — |
An executed operation is journaled only once
stocks.operation.executed is emitted once per operation, whatever the entry point: operation screen, order reception or a call from another module.
Reference data¶
| Type | Level | Subject | Emitted when | Data |
|---|---|---|---|---|
stocks.warehouse.created |
INFO |
warehouse |
A warehouse is created | — |
stocks.warehouse.updated |
INFO |
warehouse |
A warehouse is modified | — |
stocks.warehouse.deleted |
WARN |
warehouse |
A warehouse is deleted | — |
stocks.location.created |
INFO |
location |
A location is created | — |
stocks.location.updated |
INFO |
location |
A location is modified | — |
stocks.location.deleted |
WARN |
location |
A location is deleted | — |
stocks.location.activated |
INFO |
location |
A location is activated or deactivated | active |
stocks.family.created |
INFO |
family |
An item family is created | — |
stocks.family.updated |
INFO |
family |
An item family is modified | — |
stocks.family.deleted |
WARN |
family |
An item family is deleted | — |
stocks.subfamily.created |
INFO |
subfamily |
A subfamily is created | — |
stocks.subfamily.updated |
INFO |
subfamily |
A subfamily is modified | — |
stocks.subfamily.deleted |
WARN |
subfamily |
A subfamily is deleted | — |
stocks.operation_type.created |
INFO |
operation_type |
An operation type is created | — |
stocks.operation_type.updated |
INFO |
operation_type |
An operation type is modified | — |
stocks.operation_type.deleted |
WARN |
operation_type |
An operation type is deleted | — |
stocks.contact.created |
INFO |
contact |
A contact is created | kind (person or society) |
stocks.contact.updated |
INFO |
contact |
A contact is modified | kind |
stocks.contact.deleted |
WARN |
contact |
A contact is deleted | kind |
stocks.batch.cost_recorded |
INFO |
batch |
A batch cost is recorded | — |
stocks.article.converted |
INFO |
article |
An item is converted into another unit | — |
stocks.article.planned |
INFO |
article |
An item replenishment is planned | — |
stocks.settings.cost_method_configured |
INFO |
settings |
The stock costing method is configured | — |
Platform writes¶
These events are born outside a user request: they carry the system actor, identifier 00000000-0000-0000-0000-000000000000 and name stocks. The journal shows the fact, not a user.
| Type | Level | Subject | Emitted when | Data |
|---|---|---|---|---|
stocks.article.created |
INFO |
article |
An item is created by the platform | — |
stocks.article.updated |
INFO |
article |
An item is modified | — |
stocks.article.archived |
INFO |
article |
An item is archived | — |
stocks.family.synced |
INFO |
family |
An item family is synchronized from the platform | — |
stocks.family.deleted |
WARN |
family |
An item family is deleted by the platform | — |
stocks.subfamily.synced |
INFO |
subfamily |
A subfamily is synchronized from the platform | — |
stocks.subfamily.deleted |
WARN |
subfamily |
A subfamily is deleted by the platform | — |
stocks.stock.replenished |
INFO |
stock |
A stock is replenished | quantity |
stocks.alerts.synced |
INFO |
alerts |
The stock alerts are synchronized | — |
stocks.module.uninstalled |
SECURITY |
module |
The module is uninstalled and its data purged | — |
Event journal¶
| Type | Level | Subject | Emitted when | Data |
|---|---|---|---|---|
logs.events.exported |
SECURITY |
export |
A CSV export of the journal is produced | filters, limit |
Planned¶
These events are planned but not emitted yet. They are given here so that the modules expecting them know their final name.
| Type | Level | Subject | Emitted when | Status |
|---|---|---|---|---|
sales.cash_receipt.closed |
INFO |
cash_receipt |
A cash receipt is closed | Planned |
minlessika.user.signed_in |
SECURITY |
user |
A user signs in to the platform | Planned |
Changelog¶
- 1.1 (August 26, 2026): full stocks catalog.
- 1.0 (August 23, 2026): document created.