> 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/xoroerp-1/admin/warehouse/carrier-confirmation-codes/fields.md). # Fields ### Fields to fill in Two of the primary fields you will encounter are **Name** and **Carrier Confirmation Code**. Here's a detailed explanation of these fields: **Name:** This field represents the identifier or label for the specific Carrier Confirmation Code. Essentially, it is the name you assign to the code within the XoroERP system. This name is used for easy reference and organization, allowing you to quickly identify and differentiate between various carrier confirmation codes in your logistics and shipping operations. The name should be descriptive and align with the carrier or shipping service it corresponds to, helping ensure clarity and accuracy in managing shipping processes. **Carrier Confirmation Code:** The **Carrier Confirmation Code** field is where you input the actual code provided by the carrier that confirms the successful execution of a shipping operation. This code is crucial for tracking and validating shipments, as it links the shipment within XoroERP to the carrier's tracking and confirmation system. The code ensures that the shipment status is updated accurately and in real-time, reflecting the carrier's confirmation of key events such as pickup, transit, and delivery. By properly configuring the **Name** and **Carrier Confirmation Code** fields, businesses can maintain a well-organized and efficient shipping process within XoroERP, ensuring that each shipment is accurately tracked and confirmed throughout its journey. ### Header Options **Delete** : This allows you to delete the selected code **Save** : This allows you to save the created code. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xorosoft.com/xoroerp-1/admin/warehouse/carrier-confirmation-codes/fields.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.