iyibir WMS
FeaturesAI ModeIntegrationPricingResourcesGet started
All articles

Internal requests: from a verbal ask to an approved, fulfilled record

If "we need two cases of this on the line" never becomes a record, nobody knows who asked, who approved or how much was sent. Request, approval and fulfilment are links in one chain.

A production line, a branch or another warehouse asks the store for material. The ask often comes by phone or in the corridor. Goods are sent, but which request they were sent for, how much of it was met and what happens to the rest is not on record. At month end the transfers are visible; the requests are not.

Three links of the request chain

  • Request: who asked, for which warehouse, how much?
  • Approval: who accepted the ask, which lines were cancelled?
  • Fulfilment: with which transfer, how much was sent, how much is left?

If the three links are not tied together, the request list never closes or closes wrongly. Good practice ties fulfilment to the request line, so a partial delivery also shows as partial on record.

Requests in iyibir WMS

  • A request is opened on mobile with Create request; the fulfilling warehouse is recorded on it and a request document is created in Logo.
  • A request opened on the floor stays in Logo as an unapproved proposal and does not reach the fulfilment list.
  • The manager approves it on the request's page in the web panel, or cancels lines not yet fulfilled at all. This runs the same path as writing on mobile: the lines read from Logo are shown first, it is written once on approval, and the result is read back from Logo.
  • An approved request reaches the Request fulfilment list on mobile; fulfilment is a warehouse transfer linked to the request.
  • A partly fulfilled request stays on the list with its remaining quantity; once fully met it drops off.

Following it in the web panel

The request fulfilment screen shows requests with their states: awaiting approval, approved, being fulfilled, fulfilled, cancelled. The request detail also shows each line's own state. Approval and cancellation stay as separate transactions on the Movements screen; who, when and which Logo document can always be answered.

Step by step: Approving and fulfilling a request opened on the floor

  1. The requester enters the item, quantity and fulfilling warehouse with Create request on mobile and sends it to Logo.
  2. The manager opens the request's page in the web panel and taps Approve, or cancels unfulfilled lines.
  3. After checking the Logo lines in the dialog, they choose Approve and write to Logo; the result is read back.
  4. The warehouse operator picks the request from the Request fulfilment list on mobile, scans the goods and sends the transfer.
  5. If anything remains, the request stays on the list with that quantity; once fully met it drops off.

Frequently asked questions

Can a request opened on a phone be fulfilled right away?
No. A request opened on the floor stays in Logo as an unapproved proposal; it reaches the fulfilment list once the manager approves it.
Can a request line that has started being fulfilled be cancelled?
No. Only lines not fulfilled at all can be cancelled; if every line is cancelled, Logo cancels the request too.
What happens if only part of a request is sent?
Because fulfilment is tied to the request line, the request stays on the list with its remaining quantity and the rest is fulfilled later.

Try it in your own warehouse