The most expensive error between warehouse software and the ERP is the invisible one: the terminal says "sent", the connection drops at that moment, the operator is not sure and enters the transaction again, and the same waybill appears twice in Logo. Or the opposite: a document thought to be written never was. Both surface only at month-end reconciliation.
Good practice: every write is a record, every record has a state
Systems that separate the execution layer from the ERP share one principle: every request to the ERP carries an identity, a second request with the same identity opens no new document, a request with an uncertain answer is never blindly repeated, and the written document is read back from its source and compared. This is not a technical detail; it is the precondition for trusting the stock record.
The steps of a write in iyibir WMS
A transaction in WMS is not written to Logo by itself. Every write takes the same path and each step is recorded in the write ledger:
- Draft: the basket fills on mobile; scanned items, quantities, lot, serial and shelf. The basket is stored on the device and survives the app closing.
- Preview: the server prepares how the document will be written to Logo and shows it. A line that breaks a rule is rejected here; nothing goes to Logo.
- Approval: nothing is written without approval; approval is never given by voice, by AI or automatically.
- Write: the document is written to Logo and the document number Logo returns is recorded.
- Read-back: WMS reads the written document from Logo and compares it with what it sent.
When the connection drops
A record whose answer never arrived becomes "Uncertain". WMS does not send it again; it searches Logo with its own tracking number and settles the state itself. If the same draft is sent a second time, the first result comes back and no second document is written. Without a network nothing is sent; the app says so and keeps the draft.
Records needing attention and Close record
An uncertain, partly written or read-back-mismatched record stays at the top of the Movements screen and the exception centre in the web panel. After checking Logo and doing what is needed, the manager closes it with a reason. Closing only changes the record in WMS; nothing is sent to Logo, and an uncertain record is never sent again.
The web panel plans; execution happens on the floor. What the panel writes to Logo is the manager's request approval and cancellation, and those go through the same preview, approval and read-back path.
Step by step: Safely closing a write that stayed uncertain
- If mobile shows "Uncertain, being checked", do not enter the same transaction again.
- In the web panel open Movements with the Needs attention filter and open the record's detail.
- Search the document in Logo with the record's WMS tracking number and see whether it was actually written.
- Do what is needed in Logo by hand, or confirm that nothing is needed.
- Use Close record, enter a reason and confirm; the record becomes Closed manually and nothing goes to Logo.
Frequently asked questions
- Can the same waybill appear twice in Logo when the connection drops?
- If the same draft is sent a second time WMS returns the first result and no second document is written. A record with an uncertain answer is never re-sent; WMS searches Logo for it with its own tracking number.
- Does the web panel write to Logo?
- The panel plans; transactions that write to Logo are approved on the floor. The exception is the manager's request approval and cancellation, which also go through preview, approval and read-back.
- Are cases and pallets written to Logo?
- No. Cases and pallets are WMS's own records; no packing document is created in Logo.