> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/warehouse/receiving.md).

# Goods receipt

Goods receipt in Equipme Pro: book in delivered stock orders, record partial deliveries, assign storage locations, and understand which devices are reserved and which are stored.

**Path:** **"Warehouse" → "Goods receipt"**

In goods receipt you book incoming deliveries of your [stock orders](/pro/procurement/purchase-orders.md) into the warehouse. Only then do the goods count as stock, and customer orders waiting for them can be picked.

{% hint style="info" %}
Only **stock orders** with the status "Ordered" or "Partially delivered" appear here. Dropshipping orders go directly to the customer and do not pass through goods receipt.
{% endhint %}

## Page layout

**Left: "Pending goods receipts".** All open stock orders, sorted by "expected delivery date" (orders without a delivery date last). For each order you see the order number, the supplier's "Order / purchase order number", the expected delivery date, the supplier and the progress *received/ordered*. Use the search to find an order by its order number or the supplier's "Order / purchase order number". If there is nothing to book, it says "There are no open orders".

**Right: the selected order.** Header data ("Order / purchase order number", "Order confirmation", "Order date", "expected delivery date", "Supplier", "Ordered by", "Delivery note number", "Comment"), the **"Date received"** and the table of open items.

## Book in a delivery

1. Select the order on the left.
2. Check the **"Date received"** (pre-filled with today, cannot be in the future).
3. For each item in the table:
   * **"Pending"** shows how many units are still missing.
   * Under **"Quantity"**, set the delivered quantity (at most the pending quantity).
   * Enter the **"Storage location"**. You can choose an existing one or type a new name; new storage locations are created automatically.
4. Click the check mark icon at the end of the row. You see "The received batch has been successfully recorded."

Each confirmation creates a **batch**. Repeat the step for each item and, for partial deliveries, for each further delivery.

Once all items are booked in, "Goods receipt for order *number* completed. Well done!" appears and the order disappears from the list.

{% hint style="warning" %}
If you switch orders or leave the page before confirming entered quantities with the check mark, they are lost. equipme warns you beforehand: "Warning: You have unsaved changes. …"
{% endhint %}

## What happens when you book in

| Device is …                                                         | becomes …      | Consequence                                                                                                                      |
| ------------------------------------------------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| assigned to a customer order (via demand fulfillment when ordering) | **"Reserved"** | The customer position switches to "Ready for picking" and appears in [picking](/pro/fulfillment/picking-production-shipping.md). |
| not assigned to any order (minimum stock)                           | **"Stored"**   | Unassigned stock in the [stock warehouse](/pro/warehouse/stock-warehouse.md), reserved automatically for new orders.             |

The stock order item switches to "Partially delivered" or "Delivered", and the order accordingly.

## Serial numbers and attributes

In goods receipt you book quantities, not individual serial numbers. You record serial numbers and other product attributes (e.g. IMEI, license keys) when a device leaves the warehouse: during [picking](/pro/fulfillment/picking-production-shipping.md) of a customer order or during a manual [stock withdrawal](/pro/warehouse/stock-withdrawals.md). Which attributes are requested is something you set on the product in the [product master data](/pro/portfolio/products.md).

## Goods already received

Under **"Goods received"** you see the order's items that have already been (partially) booked in. Expanded, they show the **"Goods receipt postings"** with quantity, storage location, "Recorded by" and "Recorded on". You find the same overview in the order details on the "Goods receipt" tab.

## Permissions

"Warehouse Manager" and "Administrator" can book in. Without a warehouse, the page first shows **"Create warehouse"**.

## Frequently asked questions

**The order doesn't appear in goods receipt.**

Check whether it is a stock order (not dropshipping) and whether it has been cancelled or already fully delivered.

**The supplier delivered less than ordered.**

Book in only the delivered quantity. The rest remains "Pending", and the order is "Partially delivered". If the remaining quantity is definitely not coming, cancel the item in the [order](/pro/procurement/purchase-orders.md#cancelling-an-item). However, this is only possible as long as nothing of that item has been booked in yet.

**I booked to the wrong storage location.**

Change the batch's storage location in the [stock warehouse](/pro/warehouse/stock-warehouse.md).

**Who gets the delivered devices?**

First, the customer orders you selected in demand fulfillment when ordering. The rest becomes unassigned stock.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/pro/warehouse/receiving.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.