> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/features/purchasing/receiving-inspection.md).

# Receiving/Inspection

Get your parts from dock to stock with ION Receipts and Inspection runs

## What are Receipts?

Receipts are used to track the event of bringing parts into the factory from outside suppliers. They allow population of key inventory fields such as serial number, lot, and location.

Additionally, receipts can be tied to runs to enable procedural inspections of incoming parts.

### Processing receipts

A receipt is automatically created when moving a PO's state to "Ordered". You can click on "Receive" to go directly to the receipt and process it.

![](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-88910414ff1cf1c03ee1e0c1bd0434c13bb63c0f%2Fimage.png?alt=media)

Here's a short video showing how to do a receipt

{% embed url="<https://www.loom.com/share/445b5471314f4457a8abf9da6012f57f>" %}

If the part being received requires serial tracking (as specified on the part), a serial number will need to be populated before it can be received. The same also applies for lot tracked parts.

Only purchase orders in an **ordered** status can be received. When all parts on a purchase order are received, the purchase order status will be changed to **received** as shown below for the purchase order linked to the above receipt:

![](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-3c1815c383feac7bb3c3cf3f312880ece98677e0%2Fimage.png?alt=media)

### Adding parts to receipts

Additional parts can be added to receipts with the **Receive more parts** button.

![Receive additional parts](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-beafff09a96dee8c9848b6000cea3098aea3cc8d%2F2021-04-19%2023.25.46.gif?alt=media)

### Inspection runs

Procedures now have a type to designate build vs inspection.

![Inspection procedures](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-86eb24ba3ecfdb3cce90789d9192fba2954c5b65%2F2021-04-19%2023.28.44.gif?alt=media)

On the part/procedure link, the inspection run can be set as required:

![](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-81207d341812e616bb0990c628760b3981c38e6f%2F2021-04-19%2023.37.47.gif?alt=media)

Setting this as required and approving the part-procedure relationship will automatically create an inspection run upon receipt for that part number:

![Inspection run automatically created](https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-167a4c65af5565dd05addbb2d2057465823cb3ee%2F2021-04-19%2023.45.34.gif?alt=media)

#### Receiving non-part purchases (i.e. services)

You can also use receiving to receive purchase items that do not have a part number.

There is little difference to receiving non-parts. The only major difference is that properties that are normally accessible on the inventory such as location, serial number, and lot number are not there because these are not inventory items.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-caf4b076caab73c3004b51dbb9e6e25a1d520e64%2F2022-12-21%2013.54.14.gif?alt=media" alt=""><figcaption></figcaption></figure>

#### Accessing your fully received receipt

Receipts for a PO can be seen by typing the PO number in the search box on the Receipts page:

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-d68df0fe01504a952f12f421eace942e3e994b53%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://manual.firstresonance.io/features/purchasing/receiving-inspection.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.