What cost fields are available on PO line items, and how do I include costs when bulk-importing purchase orders?

Cost columns on the Purchase Order Line Items view

When you open the Order Items tab on a purchase order (or visit the cross-PO Line Items page), each line shows a set of cost columns. These columns are visible only when your user account has cost-viewing permission.

Column	What it shows
Unit Cost	The per-unit price agreed with the supplier for that SKU
Line Total	Unit Cost × Ordered quantity, automatically calculated. On the PO detail page this column is labelled Line Total (Received / Ordered) and shows the received value alongside the ordered value (e.g. 0 / $125).

All cost columns show amounts in the currency of the parent purchase order. If your account manages POs in multiple currencies, each row displays its own PO's currency symbol rather than a single symbol for the whole grid.

Down payments are not tracked as a per-line column. They're recorded at the PO level, on the Payments tab (Add Payment / Add Prepayment) — not on individual line items.

Shipment Extra Costs Total appears as a filter on the cross-PO Line Items page (letting you narrow the list to POs with extra shipment costs), but it is not a per-line column — extra costs are recorded on the PO's own Extra Costs tab, not on individual line items.

Bulk-importing purchase orders — available cost fields

When you use the Import Purchase Orders template (CSV), the following fields are supported per row. Each row represents one line item; rows that share the same ALTERNATE_PO_ID are grouped into a single purchase order.

Required fields (every row)

CSV column	What it does
`ALTERNATE_PO_ID`	Identifies which PO this row belongs to. Rows with the same value are grouped together. Used to match an existing PO or create a new one.
`SUPPLIER_NAME`	Name of the supplier. If no match is found, a new supplier record is created automatically.
`ORDER_DATE`	Order date. Accepted formats: `YYYY-MM-DD` or `DD-MMM-YYYY` (e.g. `2024-12-12` or `12-Dec-2024`).
`MASTER_SKU`	The SKU for this line item. Must already exist in Luminous.
`QUANTITY`	Ordered quantity for this line item.
`UNIT_COST`	Unit cost for this line item. The line total is calculated automatically as `QUANTITY × UNIT_COST`.

Optional fields

CSV column	What it does
`REQUEST_SHIP_DATE`	Requested ship date (`YYYY-MM-DD` or `DD-MMM-YYYY`).
`SHIP_DATE`	Ship date. Used as the arrival date fallback if `ARRIVAL_DATE` is not provided.
`ARRIVAL_DATE`	Arrival / due date for the PO.
`WAREHOUSE`	Destination warehouse name (must match an existing warehouse).
`STATUS`	PO milestone status. Accepted tokens: `active`, `production_started`, `production_completed`, `in_transit`, `completed`, `deleted`. Numeric IDs (`1`, `20`, `40`, `50`, `99`, `-1`) and legacy aliases (`ordered`, `delivered`) are also accepted.
`FINANCE_STATUS`	Finance status label (e.g. `Deposit Paid`, `Paid`, `Unpaid`).
`PAYMENT_TERMS`	Payment terms (e.g. `100% Down`, `Net 30`). Falls back to the supplier's default if omitted.
`LOGISTIC_CODE`	Incoterm code (e.g. `exw`, `fob`). Defaults to `exw`.
`LOGISTIC_LABEL`	Incoterm display label (e.g. `EXW`, `FOB`).
`TRACKING_INFO`	Tracking reference for the PO.
`ORDER_TYPE`	`1` = bulk order, `10` = sample order. Defaults to `1`.
`PUBLIC_NOTE`	Public-facing note on the PO.
`PRIVATE_NOTE`	Internal / private note on the PO.
`CUSTOM_<field name>`	Any custom field you have configured on purchase orders. Use the prefix `CUSTOM_` followed by the exact field label (e.g. `CUSTOM_Season`).

What cost fields cannot be set via import

The bulk import only accepts UNIT_COST at the line level. The following line-level cost fields are not supported by the import template and default to zero:

Per-unit shipping cost
Line-level tax
Discount amount or discount percentage
Down-payment percentage

If you need to record these values, open the purchase order after import and edit the line items or use the PO shipping/cost sections in the UI.

Tips

Re-importing a PO: If you re-upload rows for an existing ALTERNATE_PO_ID, the importer updates the matching line items. Received quantities that have already been logged are preserved — the import will not reset them to zero.
If UNIT_COST is zero: The importer will automatically fall back to the unit cost saved in your Supplier Product SKU catalog for that supplier + SKU combination, if one exists.
Supplier auto-creation: If the SUPPLIER_NAME value does not match any existing supplier, a new supplier record is created with that name and a default payment term of 100% Down.