Connection lost while putting an item away — what now

The worst case in the whole module: you sent a put-away and do not know whether it went through. The terminal is prepared for this and has a separate state for it.

Step by step

1. You saw the No confirmation banner — stop. Do not scan this item again.
2. Do not change anything. The Quantity: {n} and Batch and traceability buttons are greyed out in this state for this very reason.
3. Tap Retry — the amber button at the very top of the action bar.
4. Did the green Received banner return? Done. The item was posted exactly once; continue scanning.
5. Did the red Retry does not match the original put-away banner return? The terminal will reload the receipt itself. Review the item list and check what is actually there before scanning anything else.
6. Did Receipt has been closed return? A manager approved the document. Go back to the start list and begin a new receipt.
7. If none of this works, stay on this screen and call a manager. The back button is deliberately locked — pressing it would only turn the banner amber.

“No confirmation”

Red banner:

No confirmation — Press “Retry”. The retry uses the same identifier and will not post the item twice.

The same banner turns amber if you try to leave this screen — this only means the back gesture was intercepted.

It appears when the response does not prove that nothing happened: no response at all, a 5xx error from the proxy, or a timeout (408). All three can happen after a write that succeeded.

Only a clean 4xx error from the application proves that nothing was posted.

What to do

Do not scan again. The terminal keeps the same armed product, quantity, shelf, and request identifier. Press the large amber “Retry” button.

In this state, the quantity keypad and batch dialog are locked, and the back button does not work — this ensures you cannot change anything in the request that must be sent identically.

Why this is safe

Each physical put-away gets its own identifier. The server stores it together with the stock movement. Retrying with the same identifier does not create a second movement — the server finds the first record and returns the same item.

This protection works regardless of which gesture you used to send the put-away.

“Retry does not match the original put-away”

Red banner:

Reloading receipt — check the list to see how much was actually posted.

This means the same identifier came back with a different product, location, quantity, or batch number than on the first attempt. The terminal reloads the entire receipt from the server itself and returns to scanning — because the server is the only one that knows whether the original put-away went through.

Your task: look at the item list and check what is really there before scanning anything else.

“Receipt has been closed”

Someone approved the document while you were still scanning. Return to the list and start a new receipt — you cannot add anything to a closed one.