Receiving messages and what to do about them

Step by step

The terminal refused a put-away — what now?

1. Read both lines of the banner. The top line is the message; the lower line is the server’s reason or a hint. The actual reason is usually on the lower line.
2. Product not recognized or Code matches multiple products — the terminal disarms the scan automatically and returns to Scan location or goods. Set that item aside and report the code to the office. Do not try repeatedly.
3. Location not recognized or Code matches multiple locations — the product stays armed; scan the correct shelf. If the rejected shelf was the one pinned, the Location bar disappears and you need to pin another one.
4. Invalid scan or Receipt rejected — read the sentence underneath and follow it.
5. No confirmation received — do not scan again. Tap Retry: the retry uses the same identifier and will not post the goods a second time.
6. Retry does not match the original put-away — the terminal reloads the receipt automatically. Check the lines list to see what was actually posted, and only then continue scanning.
7. Receipt has been closed — someone approved the document. The terminal returns to the start screen; start a new receipt or return to another one in In progress.
8. No permission for this receipt — your role lacks permission, or someone else started the receipt. Ask a manager; scanning further will not change anything.

I cannot start receiving at all

1. The Could not start receipt banner has a third line with a hint. Read it — at startup, the system tells you the remedy.
2. No active warehouse — set a warehouse for yourself: open the settings drawer on the terminal and select one from Select warehouse. The hint may also direct you to your user profile or an administrator.
3. No PZ document type configured — there is nothing you can do here. An administrator must create a PZ document type for this company.
4. PZ document type is not suitable for receiving — this is also for the administrator: The PZ type requires a contractor or price that receiving cannot provide.
5. You already have an empty receipt open — return to it from In progress or ask the office to delete it.
6. Could not load the receipts list — do not start a new one. Open receipts may exist even though the list did not load them. Try again.

Codes that cannot be used

For the last two cases, the terminal does not ask which one — it simply refuses. A duplicate code is a record that needs fixing, not something to resolve on the warehouse floor.

After an unrecognized product, the terminal disarms the scan so you do not fire off a series of rejected attempts with the same faulty code. Each attempt is still recorded in the document history as a rejected scan — the manager will see it.

Refusals at startup — those with a hint

Hints appear only when starting fails. When a put-away fails, you will see only the message — this is a known inconsistency, not a problem with your device.

Refusals during receiving

• Receipt has already been closed — someone approved the document. Return to the list.
• Retry does not match the original put-away — see “Connection dropped during put-away.”
• Invalid scan — the server rejected the request contents.
• Receipt rejected — a general message; read the server’s sentence below it, because that contains the actual reason.
• Carrier {code} is full — this warehouse has the “one product per pallet” rule enabled, and this put-away would exceed the pallet’s additional-products limit. The terminal gives a short message, but below the Location bar it shows red rows with what is actually on the pallet (code, name, quantity — up to five lines), and below those, how much more will fit: “Additional-products limit: {N} units. You can add {M} more units,” or “Additional-products limit of {N} units reached” if nothing else will fit. The scanned product stays armed while the pallet is disarmed: scan another pallet, for example an empty one. There is no button to deliberately bypass this rule — it is always enforced the same way. Rule details: docs/apps/wms/RECEIVING_SETTINGS.md.
• Wrong carrier — this receipt already has a pallet with only this product, and you are trying to put it away on another. The terminal briefly says “Wrong carrier” and shows “Put away on {code}” — go to the suggested pallet instead of trying this one again. This is the same refusal as “Carrier full” from the server (pallet_has_other_product) — the only difference is that the terminal knows the correct destination.

A location from another warehouse

You can put goods away only at a location in the warehouse assigned to this document. A receipt cannot span warehouses.