Documents

Intro

Documents controls the layouts your team prints — picking lists to pull stock, packing slips for the box, invoices, manifests, item labels, and the pickup slip. Once configured, they print from the Print menus on Orders and Shipments.

Purpose

• One consistent layout per document type for the whole store
• Include exactly the fields your bench and customers need — including custom fields and destination weather

Document types

Every store starts with sensible defaults for each type; edit them or create additional documents.

Configure a document

1. Open Advanced → Documents and create a document or open an existing one.
2. Choose the type, then the page: A4, Letter, Legal, A5, A3, or Custom (inches); Portrait / Landscape; margins.
3. Edit the Header, Body, Footer, and CSS tabs. Use Insert variable to place data — see Template variables. Turn on Tailwind CSS to use utility classes instead of writing CSS.
4. In Printing, set the defaults the print preview starts from — see the table below.
5. Watch the live preview: it renders with sample data until you pick one or more real shipments (or orders) in the preview picker, which is the quickest way to check bins, metafields and custom fields on your own data. Save, then print a test from a shipment.

From the Documents list each row offers Duplicate (copy layout and printing defaults under a new name — the starting point for one template per product group), Activate / Deactivate (inactive documents disappear from Print menus but keep their layout) and Delete; a star marks the Default document of each type, set in the editor.

Printing defaults

Location and condition are defaults, not locks: the print preview preselects them and the operator can change them for one print without touching the document.

Templates use Mustache syntax, for example:

{{# weather }}Destination: {{ low }}–{{ high }}{{ unit }} · {{ condition_text }}{{/ weather }}

Bin location on pick lists

{{ bin_location }} on an item row resolves in this order:

1. A product or variant metafield synced for bin location (e.g. custom.bin_location)
2. A line-item custom field whose name contains bin — e.g. Item Bin Location captured from variant.metafield:custom.bin_location (see Custom Fields)
3. Otherwise -

To print a specific custom field regardless of its name, use its slug: {{ custom_fields.item_bin_location }} (the field name lower-cased with underscores). Custom fields and metafields can also be sort columns (custom_fields.<slug>, metafields.<key>). The Shopify location id is never printed as a bin.

Template variables

Insert variable lists everything available for the document's scope and drops it into the pane you are editing. The main groups:

Helpers wrap a value: {{# barcode }}{{ shipment.label }}{{/ barcode }} renders a Code 128 barcode (what Scan & Ship reads), {{# qr }}…{{/ qr }} a QR code, {{# money }}{{ price }}{{/ money }} a formatted amount.

Prices and discounts. price is the raw unit price, before any line discount. When a line is discounted, discounted_price is the unit price the customer actually pays, line_discount the amount taken off, and line_total the discounted quantity × price — the same figures the shipment page shows. has_discount lets a template strike through the original only when there is one:

{{# money }}{{ discounted_price }}{{/ money }}
{{# has_discount }}<s>{{# money }}{{ price }}{{/ money }}</s>{{/ has_discount }}

A 100% line discount prints 0.00, not the full price. Product thumbnails are cached and embedded when a PDF is generated, so a batch of a few hundred lines does not wait on the Shopify CDN.

Printing

Open Print on a shipment or order (or on a selection in a list) and pick a document. The preview opens with the document on the left and a panel on the right:

The preview is the real rendered document, so Print is immediate; only Download PDF waits for PDF generation. Changes in the panel apply to this print only. The document's saved defaults (sort, location, condition) are preselected each time you open it; "Save a default on the document" means editing it under Advanced → Documents.

Filter rows by condition

Pick any active Condition. Two kinds of rule behave differently:

• Item rules (Product item entity — type, SKU, vendor, tags, collections, location, metafields…) hide the item rows that do not match. A shipment left with no rows is skipped.
• Shipment-level rules (Order, Shipment, Customer, Shipping address, and the any item / no item gates) cannot be answered per row, so the whole condition is evaluated against each selected shipment and non-matching shipments are left out entirely — with all their rows.

A condition can mix both: order label starts with W and item type is Frozen prints only the frozen lines of wholesale orders. If nothing matches you get a single "No items match the selected filters" page instead of an unfiltered print.

Filters change what is printed only — hidden items still ship.

The "Printing" condition group

The dropdown lists every active Condition. To keep it short, create a rule group named Printing (any capitalisation) under Advanced → Conditions and move your print-only conditions into it: as soon as that group has one active condition, the print preview and the document editor list only that group. Stores without a Printing group keep seeing all conditions.

One template per product group

When a pick slip should look different for, say, fish and supplies, make two documents rather than one clever template:

1. Duplicate the pick slip: Pick Slip – Fish and Pick Slip – Supplies.
2. Give each its own layout, and set Default condition to Fish products / Supplies (and a Default location if the stock lives in one place).
3. Both appear in Print and in the preview's Template switcher; choosing one gives the right layout with the right rows. The operator can still override the condition for a one-off print.

One row per fulfillment location

On a picking list, order pick list, batch pick list, Pick + Pack, and item labels, a line that Shopify has open at two or more fulfillment locations prints once per location, using that location's own quantity. A quantity of 3 with 1 at Online | Your Store and 2 at Retail | Your Store is two rows: Online required 1, Retail required 2. The pick-list column keeps the full location name. A line at only one location stays one row with the shipment quantity.

Packing slips, invoices, and the local pickup slip stay one line. Those go to the customer.

Item labels print the short name — the text before the | — under the shipment number ({{ item.location_short }}), including when the line is only at one location. In Split labels, two locations of the same product stay separate rows.

Item labels: split before printing

For Item Label (per-quantity) documents, Print… and Download PDF first open Split labels:

• The list shows only the lines with quantity above 1 that will print under the current Location / Filter rows by condition — quantity-1 lines have nothing to split, print one label each, and are counted in the total. When every line is quantity 1 the popup is skipped and the print goes straight through.
• Choose Print single label per line item or Break out every line item by quantity, or tick individual lines and set an optional pack per bag (20 snails, 5 per bag → 4 labels). The button shows the resulting label count.
• Confirm and the labels print (or download). After that Print acts directly; Split labels… reopens the popup to change the plan, Reset goes back to one label per line.

Carrier labels are not documents: their format (PDF / ZPL / EPL) and Zebra Browser Print setup live under Printing.

Print tracking

Print and Download PDF are recorded per shipment (previews and Open in new tab are not). Each print adds a Document printed entry to the shipment's Activities and immediately re-runs the shipment automation rules on the affected Awaiting shipments, so print-driven rules fire without waiting for the next sync. Order-scoped documents count for every Awaiting shipment holding that order's items.

Two shipment fields in Conditions read this history:

Address, customer, and shipping-method edits are not line-item changes and do not make a print outdated. A document that was never printed is never "outdated".

Troubleshooting

Related

• Conditions — the logic behind "Filter rows by condition" and the Printing group
• Printing — label formats and printers
• Custom Fields — capture values you want printed
• Apps → Weather — forecast variables for slips
• Shipments → Labels & rates