Manage production transfers between sites
How to send products made in a central kitchen to other sites while keeping full batch traceability.
Many organisations prepare bases, desserts or semi-finished products centrally and distribute them to other sites. A transfer in Klyra links the outgoing movement at one site and the incoming one at the other, keeping batch, expiry and quantity consistent along the whole path.
Why a tracked transfer matters
Without a formal transfer, the origin site stock stays inflated while the destination stock does not reflect what is actually there. The transfer draws down the origin site and automatically creates a pending receipt at the destination.
Creating a transfer
You can generate a transfer directly from a production order that was just run, or create an independent one by selecting batches already in stock. Either way, the document lists the batches involved, the quantities and the destination site.
A transfer can include several products together, useful when one van carries different semi-finished products to the same site on the same run.
Receiving the transfer on site
The destination site sees the incoming transfer among pending receipts and confirms it by checking quantity and condition, exactly like a delivery from an external supplier.
- Transfer shown as a pending receipt
- Check quantity and condition on arrival
- Confirm to bring goods into stock
End-to-end traceability
Every transferred batch keeps its full history, from the original production to consumption at the final site: essential in case of a product recall or an inspection, since it lets you know exactly where each batch ended up.
Cosa trovi in questa guida
- transfers between sites
- central kitchen
- internal shipments
- transfer receiving
- multi-site traceability
- transfer document
Passaggi
- Open the production order or the origin site stock.
- Select "Create transfer".
- Choose the batches and quantities to send.
- Indicate the destination site.
- Confirm to draw down the origin site.
- At the destination, open pending receipts.
- Check the quantity and condition of the goods received.
- Confirm the receipt to bring batches into stock.
Problemi frequenti
- The destination site does not see the transfer → the transfer was not confirmed at origin → check the document status before contacting support.
- The received batch quantity differs from what was sent → breakage or loss during transport not declared → record the difference at receiving with a note.
- Same batch drawn down twice → transfer confirmed twice by mistake → check the batch movement history before repeating the action.
- Expiry inconsistent between the two sites → production date manually edited at receiving → never alter the original batch date, use notes instead.
Domande frequenti
Can a transfer contain products from different runs?
Yes, you can group several batches and different products into one transfer document to the same site.
Can the destination site partially reject a transfer?
Yes, at receiving you can confirm only the quantities actually arrived and flag the difference.
Does a transfer change the product expiry date?
No, the expiry stays the one calculated at original production: the transfer only moves availability between sites.
Can I see all transfers in progress between sites?
Yes, the production section shows a view of all transfers in transit with their updated status.
Guide collegate
Questa guida ti è stata utile?
Hai ancora bisogno di aiuto?
Descrivi il problema: alleghiamo in automatico pagina, sede, organizzazione e ruolo.
Contatta l’assistenza