Reference for Receive order creation CSV Data

To help you identify which information from a Receive order corresponds to the different data fields in the CSV template for creating Receive orders, we present below the list of the different data fields in the template along with a brief description and the type of information allowed.

This article covers the following topics:

• Mandatory data.
• Additional data.

Mandatory data

This is the data necessary for the system to distinguish and separate the different Receive orders that will be created with the template. The mandatory data for Receive orders are as follows:

Column Name	Usage	Valid Values
Header_warehouse	Code of the warehouse where the inventory will be received.	Codes of warehouses previously enabled in the system.
Header_account_short_name	Abbreviation of the inventory's client.	Abbreviation of accounts previously enabled in the system.
Partnumber	Part number that is expected to be received.	Part numbers previously enabled in the account and in the warehouse where the inventory will be received.

Consider that if there are mandatory custom fields, their data will also be required to import the CSV correctly.

Additional data

Data that is not necessary for the creation of Receive orders but provides more information to each of the orders when they are created. These are the additional data fields:

Column Name	Usage	Valid Values
Header_expected_date	Date when the inventory is expected to be received.	Future date. Use the following format: YYYY-mm-dd For example: 2024-03-20.
Header_notification_date	Date when you were confirmed the inventory will arrive.	Past date. Use the following format: YYYY-mm-dd For example: 2024-02-20.
Reference 1	Usage depends on your internal operational agreement.	Text less than 255 characters.
Reference 2	Usage depends on your internal operational agreement.	Text less than 255 characters.
Reference 3	Usage depends on your internal operational agreement.	Text less than 255 characters.
Reference 4	Usage depends on your internal operational agreement.	Text less than 255 characters.
Quantity	Quantity of the part number that will be received.	Numeric data.
Expected_quantity	Quantity of the part number that is expected to be received.	Numeric data.
Package_quantity	Number of packages in which the part number will be received.	Numeric data.
Package_type	Type of package in which the part number will be received.	Names of packages previously configured in the system.
Lot_serial	Lot number or serials of the part number.	Alphanumeric data. If managing serial numbers, each serial number is required to be unique throughout the inventory and must be separated by commas. For example: LOT-01, LOT-02, LOT-03
PO	Purchase order.	Text less than 255 characters.
Location	Location where the inventory will be placed.	Name of the location previously enabled in the indicated warehouse.
Custom_1	Usage depends on your internal operational agreement.	Text less than 255 characters.
Custom_2	Usage depends on your internal operational agreement.	Text less than 255 characters.
Expiration_date	Product expiration date	By default, only future dates are allowed. If the Allow receipt of expired product option at the account level is active, it also allows past dates. Use the following format: YYYY-mm-dd For example: 2024-03-20.
Notes	Additional notes.	Text less than 65,000 characters.
Packing_list	Packing list.	Text less than 255 characters.
Invoice_supplier	Supplier invoice.	Text less than 255 characters.
LPN	Label of the LPN containing the product	Text less than 255 characters.
Label	Label that the inventory will have.	Custom client labels.
Weight_value	Total weight of the product	Numeric data
Weight_type	Specific weight measurement	g hg kg oz lb
Price	Total sale price of the product	Numeric data

In addition to the data mentioned above, the template may have extra data depending on the custom fields that are configured and enabled at the time of downloading the template.