Create a storage

Creating a storage batch links a storage code (drum, pot) to the honey it contains, to ensure traceability after extraction. On the website, creation is done from Documents → Storage code. On the mobile app, scan a storage code then choose the method, or use the + button in the storages list.

Three methods are available depending on how you track your harvest. Choose yours:

Manual

The manual method creates a storage batch by directly entering its gross weight and information, without going through the weighings flow. It links a storage code to an apiary, a harvest date and a honey type, to trace the honey after extraction.

Form fields

• Gross weight: weight of the full container, in kg.
• Apiary (required): origin of the batch's honey.
• Harvest date (required): defaults to today's date.
• Honey type: selected from the configured honey types.
• Comment: optional free-text note.

The batch is saved locally then queued for synchronization.

Extraction period

The extraction period method links a storage code to all weighings done between two dates, rather than to a single apiary. The honey extracted during this period is thus traced down to the container, including the originating apiaries.

Form fields

• Start date (required): start of the extraction period. Defaults to the start of the scan day, or the end of the previous period to ensure continuity.
• End date: end of the period. Left empty, the period stays open ("in progress") and will be closed by the next period.
• Emptied Chain Start: when the extraction chain was emptied before the period's start, this option also captures the weighings done just before the start date (the duration kept depends on the storage type).
• Gross weight: weight of the full container, in kg.
• Comment: optional free-text note.

Apiaries within the range

Below the form, a real-time preview lists the apiaries with weighings falling within the chosen period. It updates with every date change, so you can check the honey's origin at a glance before saving.

The batch is saved locally then queued for synchronization.

Fill-up

The fill-up method traces a transfer: when the honey from one or several containers (the sources) is poured into another container (the destination), the application records the source → destination link to preserve traceability. Each container remains identified by its storage code.

Two fill-up directions

At the start, choose the direction that matches your action:

• Fill into: first scan the destination you are filling, then add the source containers it comes from.
• Fill from: first designate the source container(s), then scan the destination receiving them. Handy for emptying several sources into the same container.

Both directions produce the same result: the destination keeps the list of its original containers.

Form fields

• Source codes (at least one): the original containers, typed or scanned. A source cannot be the same as the destination, nor repeated.
• Gross weight: weight of the destination once filled, in kg.
• Comment: optional free-text note.

The fill-up is saved locally then queued for synchronization.