Purchase Order Import
This document provides detailed instructions for filling out the Purchase Order CSV import templates based on the actual system implementation and V3 API specifications.
Overview​
The PO Import system supports CSV file uploads that get processed into JSON format for the V3 Purchase Orders API. Each CSV row represents one line item with its packaging details, and multiple rows can belong to the same Purchase Order (grouped by Po_Number).
Template Types Available​
- Finished Good PO Template: For finished goods and products
- Material PO: For raw materials and components
Finished Good PO Template - Field Guide​
Purchase Order Information​
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Po_Number | Required | Your original PO number from your system | PO-250901 |
OPO_Number | Required | OPO_Number is another field used to apply unique identifiers for Purchase Orders. Normally it is different from PO_Number. If not empty, make sure it is unique for each PO number. It can be both numbers and/or text. | opo_123 |
Total_Quantity | Optional | The value to display PO total quantity | 100 |
Total_Quantity_Uom_Code | Optional | The value to display PO total quantity UOM Code | m |
Po_Type | Optional | Purchase order type from pre-configured list | po_type_1 |
Po_Source | Optional | Source of materials (domestic/international) | domestic |
Po_Status | Optional | Status (only "canceled" is supported) | canceled |
PO_ClientCreatedDate | Optional | Creation date from your system (YYYY-MM-DD) | 2023-02-10 |
Delivery_Date | Optional | Delivery/shipment start date (YYYY-MM-DD) | 2021-05-23 |
Ship_End_Date | Optional | Shipment end date (YYYY-MM-DDTHH:MM:SSZ) | 2021-05-30T00:00:00 |
In_Store_Date | Optional | In store date (YYYY-MM-DDTHH:MM:SSZ) | 2021-06-01T00:00:00 |
PO_EventName | Optional | Corresponding event name from your system | Event 1 |
Data_Provider | Optional | Local Custom ID of Data Provider organization. Let it empty will be using the current import org. | Provider-01 |
Client_Id | Optional | Local Custom ID of Brand/Retailer organization. | client_1 |
Factory_Custom_Id | Optional | Local Custom ID of Factory organization. | factory_1 |
Vendor_Custom_Id | Optional | Local Custom ID of Supplier organization (min 1 char). | vendor_1 |
Commit_Id | Optional | Commit ID of the purchase order | commit_id_1 |
Commit_Po_Sequence | Optional | Commit PO sequence | commit_po_sequence_1 |
Total_Cost | Optional | Total PO cost (decimal with max 10 digits, 2 decimal places) | 2500.00 |
Share_To_Ids | Optional | Comma-seperated shared organization IDs | sub_org_1,sub_org_2 |
Tips for Items Template:
- If your item already exists in the system, you may only need custom_id and entity_type
- For new items, include color and size for better identification
- Each PO must have at least one line and one packing detail
- Use "solid" packing for individual items, "assortment" for mixed packs
Line Items Information (Manual Items)​
Add one row for each item in your Purchase Order. Each line represents one item with its details.
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Line_Item_Custom_Id | Required | Custom identifier for the product/item | item_123 |
Line_Item_Entity_Type | Required | Must be item for items template | item |
Line_Style_Id | Optional | Style identifier | style_123 |
Line_Style_Name | Optional | Style name/description | Classic T-Shirt |
Line_Product_Category_Id | Optional | Custom ID of product category | cat_123 |
Line_Product_Line_Id | Optional | Custom ID of product line | line_123 |
Line_Department_Id | Optional | Custom ID of department | dept_123 |
Line_Class_Id | Optional | Custom ID of class category | class_123 |
Line_Brand_Id | Optional | Custom ID of brand category | brand_123 |
Line_Color | Conditional* | Item color (required for new items) | Blue |
Line_Size | Conditional* | Item size (required for new items) | M |
Line_Unit_Cost | Optional | Cost per unit (decimal) | 12.50 |
Line_Shipment_Term | Optional | Shipping terms | DDP |
Line Items Information (Linked Items)​
Create with linked items. Which in the Item Management page.
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Line_Item_Custom_Id | Required | Custom identifier for the product/item | item_123 |
Line_Item_Entity_Type | Required | Must be item for items template | item |
Items Packing Details​
Each Purchase Order must have at least one packing detail. Choose between solid or assortment packing.
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Packaging_Type | Required | solid for single items or assortment for mixed packs | solid |
Packaging_Carton_Quantity | Conditional* | Number of cartons/boxes (min 1). ((***required for assortment) | 20 |
Packaging_Assortment_Id | Conditional* | Assortment ID (**required for assortment type) | assort_123 |
Packaging_Item_Custom_Id | Required | Item custom ID | item_123 |
Packaging_Item_Entity_Type | Required | Must be item | item |
Packaging_Case_Pack_Qty | Conditional* | Units per carton (***required for assortment type) | 5 |
Packaging_Quantity | Conditional* | The packing quantity (min 1). (***required for solid type) | 100 |
Packaging_Quantity_Uom_Code | Optional | The packing quantity UOM Code | kg |
Tips for Items Template:
- If your item already exists in the system, you may only need Line_Item_Custom_Id and Line_Item_Entity_Type
- For new items, include Line_Color and Line_Size for better identification
- Each PO must have at least one line and one packing detail
- Use "solid" packing for individual items, "assortment" for mixed packs
Material PO Template - Field Guide​
Purchase Order Information​
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Po_Number | Required | Your original PO number from your system | PO-250901 |
OPO_Number | Required | OPO_Number is another field used to apply unique identifiers for Purchase Orders. Normally it is different from PO_Number. If not empty, make sure it is unique for each PO number. It can be both numbers and/or text. | opo_123 |
Total_Quantity | Optional | The value to display PO total quantity | 100 |
Total_Quantity_Uom_Code | Optional | The value to display PO total quantity UOM Code | m |
Po_Type | Optional | Purchase order type from pre-configured list | po_type_1 |
Po_Source | Optional | Source of materials (domestic/international) | domestic |
Po_Status | Optional | Status (only "canceled" is supported) | canceled |
PO_ClientCreatedDate | Optional | Creation date from your system (YYYY-MM-DD) | 2023-02-10 |
Delivery_Date | Optional | Delivery/shipment start date (YYYY-MM-DD) | 2021-05-23 |
Ship_End_Date | Optional | Shipment end date (YYYY-MM-DDTHH:MM:SSZ) | 2021-05-30T00:00:00 |
In_Store_Date | Optional | In store date (YYYY-MM-DDTHH:MM:SSZ) | 2021-06-01T00:00:00 |
PO_EventName | Optional | Corresponding event name from your system | Event 1 |
Data_Provider | Optional | Local Custom ID of Data Provider organization. Let it empty will be using the current import org. | Provider-01 |
Client_Id | Optional | Local Custom ID of Brand/Retailer organization. | client_1 |
Factory_Custom_Id | Optional | Local Custom ID of Factory organization. | factory_1 |
Vendor_Custom_Id | Optional | Local Custom ID of Supplier organization (min 1 char). | vendor_1 |
Material_Supplier_Custom_Id | Optional | Local Custom ID of Material Supplier organization. | material_supplier_1 |
Commit_Id | Optional | Commit ID of the purchase order | commit_id_1 |
Commit_Po_Sequence | Optional | Commit PO sequence | commit_po_sequence_1 |
Total_Cost | Optional | Total PO cost (decimal with max 10 digits, 2 decimal places) | 2500.00 |
Share_To_Ids | Optional | Comma-seperated shared organization IDs | sub_org_1,sub_org_2 |
Material Line Details​
Add one row for each material in your Purchase Order.
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Line_Item_Custom_Id | Required | Material ID in Material management page | cotton_001 |
Line_Item_Entity_Type | Required | Must be material for materials template | material |
Line_Unit_Cost | Optional | Cost per unit (decimal) | 12.50 |
Line_Shipment_Term | Optional | Shipping terms | EXW |
Material Packing Details​
| Field Name | Required? | What to Enter | Example |
|---|---|---|---|
Packaging_Type | Required | only solid packing is supported | solid |
Packaging_Item_Custom_Id | Required | Material custom ID | cotton_001 |
Packaging_Item_Entity_Type | Required | Must be material | material |
Packaging_Quantity | Required | The packing quantity (min 1) | 100 |
Packaging_Quantity_Uom_Code | Required | The packing quantity UOM Code | kg |
Additional Attributes (Optional)​
The last other fields when using the download template, they are custom attributes for Purchase Order, which defined
by the Data Provider, these columns will be auto-generate based on current active PO custom attributes.
You can input the value (can be string, number, or list(Comma-seperated)) based on the definition of these fields.