﻿# Input requests, dispatch and returns

> How a work order requests inputs from the warehouse, how they're dispatched, how actual use is recorded and how leftovers come back.

Source: https://resources.aragro.com/en/input-requests-and-dispatch/
Language: en

Relative links and media resolve against the source URL.

In Aragro, inputs leave the warehouse through **work orders**. That way every liter or kilo is tied to the activity, field and cycle where it was used, and inventory always reflects what really happened in the field.

## The cycle in four steps

1. **Request.** When you add inputs in a work order's **Inputs** section, the order creates a request to the warehouse for those quantities.
2. **Dispatch.** Warehouse staff review the request and dispatch the requested quantity, in full or in part.
3. **Actual use.** When the work order is completed, the supervisor records what was actually used in the field, split by field.
4. **Return.** Whatever wasn't used is recorded as **leftover** and goes back to the warehouse.

Inventory only goes down by what was consumed, not by what was requested.

## Who does each step

| Step | Usually done by | Where |
| --- | --- | --- |
| Request | Field supervisor or whoever creates the work order | **Inputs** section of the [work order](/en/work-order-guide/) |
| Dispatch | Warehouse keeper | Inventory requests |
| Use and leftover | Field supervisor, when completing the work order | **Inputs** section when completing the order |

You can give each person only the permissions they need with [User roles](/en/user-roles/). For example, the warehouse keeper can dispatch without seeing costs or payroll.

## When completing the work order

In the **Inputs** section:

- Use **automatic** distribution if the input was split evenly across fields, or **manual** if you want to record each field's actual use.
- Correct the **Leftover** column with what actually went back to the warehouse.

## Checking inventory

- The **Inventory movements** report shows each product's full cycle: purchase receipts, dispatches, consumption and returns.
- If the physical count doesn't match Aragro, record an [inventory adjustment](/en/inventory-adjustments/) with a comment explaining the difference.
- To move product between warehouses, use [Transfers](/en/transfers-guide/).

## Before you start

- Products must exist in the [inputs](/en/inputs/) catalog, with their unit of measure.
- The warehouse must have stock, loaded with a purchase or an opening balance. See [Receive inventory](/en/receive-inventory/).

## Good to know

- **Approvals apply to purchases**, not to dispatches. If someone needs to authorize a withdrawal, set it in your process (for example, only the warehouse keeper has permission to dispatch).
- **Aragro doesn't send minimum-stock alerts.** Check balances with the inventory reports before planning large applications.
- **If a completed work order had the wrong inputs**, see [Correct a completed work order, purchase or payroll](/en/correct-completed-documents/).

If you have a question this guide does not answer, contact us in the Aragro chat or write to [hola@aragro.com](mailto:hola@aragro.com).
