> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/other-products/xorowms/wms-receive/edit-lpn-attributes.md).

# Edit LPN Attributes

The Edit LPN Attributes section allows users to update the attributes of an existing ILPN, ensuring that inventory records are accurate and reflective of the most current data. By navigating through this section, users can easily modify key attributes such as manufacture date, batch number, lot number, expiry date, and quality.

{% hint style="info" %}
To edit the LPN attributes, go to **Receive > Edit LPN Attributes**
{% endhint %}

### Scanning LPN

Selecting the Edit LPN Attributes directs you to the Scan ILPN module, where you can begin the process of updating LPN attributes.

**Entering the Existing ILPN**:

In the **ILPN#** field of the Scan ILPN module, enter the number of the LPN you wish to edit. Click **"Accept"** to proceed. This redirects you to the LPN Attributes module.

<div align="left"><figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FTSrBaZRop22bzKlvWoRf%2Fimage.png?alt=media&amp;token=3afbd294-a726-4520-922a-3f025c8d7063" alt="" width="252"><figcaption></figcaption></figure></div>

### Editing LPN Attributes

In the LPN Attributes module, you can edit the attributes associated with the LPN.

* **Mfg Date (Manufacturing Date)**: This field allows you to update the date when the product was manufactured to ensure traceability and compliance.
* **Batch#**: This field allows you to modify the batch number to accurately reflect the production lot associated with the items.
* **Lot#**: This field allows you to update the lot number if needed, which is essential for tracking product batches.
* **Exp Date (Expiration Date)**: This field allows you to change the expiration date to ensure that the inventory in the LPN reflects the accurate expiration date and is efficiently handled.&#x20;
* **Quality**: This field allows you to adjust the quality attribute to reflect any changes based on inspections or quality checks.

After making the necessary edits to the attributes, click **"Accept"** to apply the changes.&#x20;

<div align="left"><figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FFeXvRZRRYYFKoUusA2R4%2Fimage.png?alt=media&amp;token=2713647c-ff17-4acf-ba0c-86e8ef89b73c" alt="" width="252"><figcaption></figcaption></figure></div>

This updates the LPN attributes in the system, ensuring that all modifications are recorded and reflected in the inventory records.


---

# 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://docs.xorosoft.com/other-products/xorowms/wms-receive/edit-lpn-attributes.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.
