Extension fields on printed documents

Retailer-specific data (like a Target DPCI) often has no system field. Define it once as an extension field — or adopt a platform preset — fill it on the order, and reference it in your packing list or label template.

Extension fields are custom fields that printed documents can use. The flow is always the same four steps: define the field (or adopt a preset), fill it on the order, reference it in the template, and it prints with the order’s value.

Step 1 — Adopt a platform preset (fastest)#

1. Go to WMS → Settings → Custom Fields and open the Outbound Order tab (document level) or the Outbound Order Line tab (line level).
2. In the purple “Platform presets” box, find the field you need — DPCI (line), Item # (line) or Return Method (document) — and click Adopt. The field is copied into your organization and appears in the list below.
3. Nothing matches? Create your own field with “+ New field” on the same page — the steps below work exactly the same.

Step 2 — Fill it on the order#

Open the outbound order form. Document-level fields appear on the order form itself; line-level fields appear in the line editor, one value per line. Values are checked against the field definition when you save (a required field cannot be left empty; a dropdown value must be one of the options).

Step 3 — Reference it in the template#

• In the template editor, the variable list is split into two groups: System variables (blue) and Extension fields (purple). Extension fields are further split into document level and line level.
• Document-level extension fields insert as [[CF:field_key]] — click the field in the editor list and it is inserted for you.
• Line-level extension fields are columns of the items table: add the column token CF:field_key to the [[LINES:...]] column list of your packing list (the editor’s line-level group inserts the declaration for you).

Document level:  Return via [[CF:return_method]]
Line level:      [[LINES:sku,CF:dpci,qty]]