How do I set a different PO number or notes for each style in a buy session?

Last updated: October 6, 2026

Setting per-style PO numbers and notes in the buy sheet

When you build a buy using Bulk Order by Variant, each style becomes its own purchase order. You can give each PO a distinct Alternate ID (your buyer-facing PO number) and separate Public and Private Notes — without leaving the build step.

Where to find the fields

In Bulk order by variant (Inventory → Purchase Orders → Bulk order by variant), add your master SKUs on the Purchase order step. Each master SKU becomes its own purchase order.

Alternate ID appears as a column in the Quantities grid by default.

  • To also edit Public note and Private note in the grid, click Columns and check them.

  • To see every per-style override in one place, click the pencil icon in the PO column. This opens PO details for [SKU], which has - Alternate ID, Public note, Private note, and the other per-style fields.

Field

What it does

Alternate ID

Sets this style's PO number. Leave it blank to keep the Luminous-generated PO number.

Public note

Shown to the supplier on the PO. If left blank, the note from Order details is used.

Private note

Internal only. If left blank, the note from Order details is used.

The same three fields are also available in the PO details dialog that opens when you click the overrides icon on a style — useful when the panel is collapsed or you want to see all per-style overrides in one place.

Setting the fields via CSV upload

If you seed the buy from a CSV, include these columns:

Column header

Notes

Alternate ID

Buyer PO number for that row's style. Blank rows inherit no default — each style's Luminous number is used.

Public note

Per-style public note.

Private note

Per-style private note.

Download the CSV template from the build step to get the correctly labelled columns.

Notes on Alternate ID

  • There is no session-wide default for Alternate ID because one value cannot sensibly apply to multiple POs. It must be set individually per style (or per CSV row).

  • The value is applied at commit time. If a style is retried after a failure, the same Alternate ID is re-sent — creation is still idempotent on the client side (a style already marked Created is never re-submitted).

Related articles