Settings

Every setting that affects PO behaviour lives in one of these settings pages. This is the cross-reference — open the matching page in Settings to actually change something. For the runtime toggles that change behaviour day-to-day (auto-sync, label default format, incoming tracking), see Preferences.

Where PO settings live

Most settings live at Settings → Purchase Orders. The page has nine tabs:

General — company info shown on PDFs (name, VAT ID, address including a State / Province field, branding).
Preferences — runtime toggles (see Preferences).
Landed Cost — which components contribute to per-line landed cost, and how they’re allocated across lines (see below).
Export — export templates for line-item CSV / XLSX / PDF and purchase-order-level CSV / XLSX.
Shopify Fields — snapshot and write-back metafields.
Constraints — constraint rule editor (Elevate plan).
Document Tags — categories for uploaded documents (Quote, Invoice, Receipt, etc.).
Product Tags — product-tag-on-transition rules.
Email Templates — supplier email subject/body, per-supplier overrides.

Adjacent settings outside the PO settings page — Tax Rates, Carriers, Locations, Email Sending, Label Printing, Data Import / Export — are listed below.

Tax rates

Where: Settings → Tax Rates.
Types: Sales, Purchase, Shipping. POs use Purchase-type rates.
Assignment: A tax rate is set on the supplier; the PO inherits it; you can override on the PO header.
Per-line override: not supported for product line items. To handle mixed-tax lines, split the PO.
Additional costs & discounts: each entry can carry its own independent purchase tax rate (or none), separate from the header rate above — see Additional costs → Tax.
Behavior on change: tax rate changes apply to future POs only. Existing POs keep the rate set at creation.

Landed cost

Where: Settings → Purchase Orders → Landed Cost tab.
Included components: toggles for which PO-level costs contribute to each line’s per-unit landed cost — shipping cost, purchase tax, additional cost or discount, payment tax, and payment tariff.
Allocation method: how the included charges spread across the PO’s lines:
- By quantity (default) — evenly per received unit.
- By value — proportionally to each line’s goods value (unit cost × received quantity). Lines with no value, such as free samples, then carry none of the charges; if no received line has a positive value, the charges fall back to the per-unit spread.
Purchase tax is the exception: it is not affected by the allocation method — each taxable line carries tax on its own value at the PO tax rate, and tax on shipping is spread evenly across taxable received units.

Snapshot metafields

Where: Settings → Purchase Orders → Shopify Fields tab.
What it does: picks which Shopify variant / product metafields are snapshotted onto the PO line at creation. Those snapshots are then visible as columns on the line-item table and can appear on the PO PDF (subject to the export template).
Adding new metafields: the definitions offered here come from Settings → Variant Settings → Attribute Definitions — link the Shopify metafield there first and it appears in this list.
Why snapshot? The PO carries the value that was true at the time of ordering, even if Shopify-side data later changes.

Write-back metafields

Where: Settings → Purchase Orders → Shopify Fields tab, Shopify Writeback Rules card.
What it does: writes a PO-derived value back into Shopify when the PO hits a trigger status you choose.
Per rule, configure: trigger status, source field (ordered / confirmed / received / pending quantity, or other calculation), owner type (Shopify product or variant), target metafield key.
Boolean metafields: if the target Shopify-linked attribute is a Boolean, configure separate TRUE and FALSE status lists instead of quantity/date aggregation. The shipped default is TRUE for Confirmed / In Progress / Partially Received and FALSE for Draft / Received / Completed / Cancelled.
Multiple active POs: Boolean rules stay TRUE while any other active PO for the same product or variant still matches a TRUE status. This prevents one received PO from turning off a storefront preorder flag while another open PO should keep it on.
Retrospective apply: new rules can be applied to existing matching POs in one batch operation.
Use case: Storefront badges keyed off “is something on order,” 3PL integrations, internal dashboards.

Product tags on transition

Where: Settings → Purchase Orders → Product Tags tab.
What it does: applies (or removes) a Shopify tag on the linked product / variant when a PO transitions between statuses.
Per tag, configure:
- Apply statuses — operator picks which transitions trigger the apply.
- Remove statuses — operator picks which transitions trigger the remove.
- Removal policy — always (always remove) or protected (only remove if no other active PO holds this product).
Not hard-coded. You can wire Sent → apply / Completed → remove if that’s typical, or any other combination that matches your storefront’s needs.

Constraint rules

Where: Settings → Purchase Orders → Constraints tab.
What it does: opens Constraint Studio, where you build purchase-order rules from presets such as MOQ, pack size, Product MOQ, supplier minimums, CBM/weight caps, group rules, and bundle ratios.
Editor behavior: rules can be previewed against sample data or a real PO before saving. The Advanced graph remains available for debugging/power users.
Inputs: rules can bind built-in PO fields, Product & variant attributes, and Data Modeling semantic mappings.
Runtime: saved rules show as PO line-item badges and purchase-order hints. Optimizer-target rules also guide the Constraint optimizer.
Limits: active rule statuses are Draft and Sent. Rebalance/reduce/remove optimizer plans are not available yet; the active optimizer mode is Fill gaps.
Elevate plan only.

Email templates

Where: Settings → Purchase Orders → Email Templates tab.
What it does: subject + body for the supplier email per PO event.
Placeholders: supports things like supplier name, PO number, your shop name.
Per-supplier overrides: you can assign a specific template as the default for a given supplier. When you send to that supplier, the override is used in place of the shop-wide template.
PDF attachment: each email template links to an export template, which drives the PDF layout / column set. Changing the export template changes the PDF the supplier receives.

Export templates (CSV / XLSX / PDF)

Where: Settings → Purchase Orders → Export tab.
Line-item templates: two separate sections, two separate template types. XLSX/CSV templates drive the column set and order of CSV / XLSX outputs; PDF templates drive the layout and styling of the PO PDF (and the supplier-email attachment). A template is one type or the other — never both. Between them they cover bulk line-item export, individual PO export, supplier emails, and PDF attachments.
Purchase-order-level templates: drive the global PO-list CSV / XLSX export that creates one row per PO with supplier, location, status, totals, payment, and paid-status fields. These templates are not used inside an individual PO and are not attached to supplier emails.
Per template: XLSX/CSV templates carry column selection and order. PDF templates carry date-field mapping, optional PDF date labels, and layout config (totals visibility, address formatting, compact layout, which standard line-item columns show). The logo and company details are shop-wide and come from the General tab, not from the template. Blank date-label fields keep the default labels.
Column picker: on CSV / XLSX templates, the available-columns list is searchable and grouped by source, with collapsible groups and a per-group Select all / Clear toggle. The line-item catalog includes live inventory, planning-constant, and ABC / revenue columns read from your Logistified data at export time — none selected by default. PDF templates use their own fixed set of standard line-item columns instead. Details at Exports → Finding a column.
Per-supplier defaults: available for line-item / PDF templates. PO-level templates are global list templates and do not have supplier assignment controls.
Selectable at export time: override the default by picking a template in the export dialog.
Multiple presets: save many; use the right one for each downstream system.

Import templates

Where: Settings → Import Templates (under the Data Import group in the settings sidebar).
What it does: column-mapping presets for bulk uploads — PO line item data, supplier links, variant overrides.
Linked to: the unified import flow that appears wherever you click “Import” (PO list, add-line-items dropdown, etc.).

Label printing

Where: Settings → Label Printing. Four tabs:
- Simple Mode — defaults for the rule-based label PDF (label size, barcode style, fields shown).
- Advanced Designer (Beta) — template-driven layout for custom designs. Build per-template field placements, font sizes, alignment.
- Test Print — generate a sample label PDF from real PO data without committing settings, so you can verify physically before saving.
- Preferences — shop-wide defaults shared by both print modes: PDF page layout, bottom layout (size & price), label print order, and price format (with a preview to sanity-check formatting).
No full live layout preview yet — Test Print is the closest approximation.

Document tags

Where: Settings → Purchase Orders → Document Tags tab.
What it does: defines categories for documents you upload to a PO — Quote, Invoice, Receipt, custom labels.
Why: each tag has its own colour, so the Type badge on the Documents card tells you at a glance what a file is. You can also type a brand-new type straight into the upload dialog — defining it here just gives it a colour and keeps the naming consistent. There is no document-type filter or report yet.

Adjacent settings that affect POs

Setting	Effect on POs
Settings → Email Sending	Email prefix (sender address), reply-to addresses, sender name. Required before any PO email can be sent.
Settings → Carriers	The carrier dropdown in the Shipping card on the PO.
Settings → Locations & overrides	The “from” address on the PO PDF (location overrides apply at PDF render time).
Supplier row (Suppliers detail)	Default payment terms, default currency, default tax rate, default email-template assignment — inherited by new POs from this supplier.

What settings don’t exist yet

Knowing what’s missing helps you triage “is this a setting I haven’t found, or is it genuinely unavailable?”

Per-line tax override on product line items — workaround: split the PO. (Additional cost / discount entries carry their own rate.)
Per-shop default constraint rule set applied at PO creation — rules are evaluated but not auto-applied to ordered quantities at creation.
“Send test email” button — templates can only be tested by triggering a real status change (or by using Test Print for label printing).
Automatic credit application on PO creation — credits are applied manually.
Auto-cancel of applied credits when a PO is cancelled — credit applications must be reversed manually.
Bulk re-send of failed emails — re-send is per-PO from the actions menu.
Full live layout preview in label printing settings — Test Print is the workaround.