Label templates — what the company prints on parcels

A company can configure extra information that the carrier prints on a label, such as an order number or buyer comment.

Screen: Settings → Delivery → Carrier labels.

First you see the list of templates: name (a star marks the company default), who it prints for, note, shipping method, and status. Above the list are search (by name and text) and carrier-account and status filters. Clicking a row opens the template at full width; the page URL identifies the open template, so you can send it to someone as a link. The arrow in the header returns to the list, and save buttons appear only after a change.

One template is one label

A template is a named set of decisions—because that is how people think about it: “this is what our parcels look like.” Fill in only what should be printed and leave the rest empty.

An empty field does not mean “print nothing”; it means “leave it as it was.” The standard note is exactly what carriers have always received.

Blocks instead of syntax

Typing {{ in a text field suggests variables with example values from the latest order; the Variable button above the field does the same. An inserted variable is highlighted; an unknown one is red because it would print nothing.

There are also clickable blocks below the text fields: Noxti order number, marketplace number, store number, customer note, parcel contents, delivery method, customer name, and separator. Clicking inserts a block at the cursor. Nobody needs to learn syntax just to decide that the store number should appear on a parcel.

Underneath, these are expressions in the same syntax as print templates. If you want, you can write your own, such as a condition or a calculation based on weight.

Preview on a real label

On the right of the editor is a preview: the selected carrier's actual label with your text overlaid in the field where that carrier prints it. Character count does not tell you the same thing. DPD wraps the note into three lines under the address, Packeta prints it sideways, and Orlen squeezes it into a corner—the template author needs to see what it will look like, not just how many characters fit.

Below the preview is the “Where carriers truncate text” table for the field under the cursor: carrier, its character limit, and what it will print. Carriers that truncate the text appear first. A red scissors marker below the field shows which carriers it will not fit; if it fits everywhere, nothing appears below the field.

All company carrier accounts are available to select. Accounts without a label background are marked “no label sample”—there is no image for them, but the limits table is still available.

The backgrounds are real labels with test-company data—no one’s personal details or billing numbers are visible.

Template for a carrier account

The Carrier account field says who the template applies to.

• Any carrier account (general template)—the template applies to every carrier.
• Specific account, for example DPD—the template applies only to that account and can override its settings.

This lets one carrier account have several templates. Only a general template can be the company default; services use only a template assigned to an account. For example, one DPD template for clothing and another for tires, each with a different sender and label format. There is no need to open another carrier account.

The editor has tabs: Template (name, account, default, active), What to print on the label (text fields), and How to ship the parcel. The last tab has expandable sections: Sender, Parcel, Carrier services, COD and insurance, Print, and Other. A summary below each section name shows what is set, and a marker tells you how many settings the template overrides.

Carrier codes stored as text (for example, DHL product, who pays, or label format) are selected from the same list as in account settings.

Each setting is visible immediately. An empty field shows the value the parcel would use without a template (from the carrier account or company settings); an ⓘ icon by the name says where it comes from. Entering a value saves it in the template: a dot appears by the name, “was: …” appears below the field, and ↺ in the field restores the account value. Choosing the same value as the account does not save anything.

Variables {{ … }} do not work in account settings—the carrier would receive them literally, so saving rejects them. Variables work in the text fields on the What to print on the label tab.

In Sender, fields follow the order used on an envelope: company name, first name, last name, street, number, unit, postal code, city, country, phone, and email. If the carrier account has its own sender fields (for example, UPS), the sender from company settings is collapsed below them. Choose who appears as sender:

• From company and carrier-account settings—as before.
• From the warehouse we ship from—the address and contact details of the warehouse where the order's products come from. Any field missing at the warehouse is taken from settings.

An override entered farther down always wins. This is how to set a custom sender, such as the store name.

Without a selected account, the sections contain only company shipping settings, such as sender details. Parcel dimensions and carrier services belong to an account, so they appear only after you select one; until then, Carrier services is disabled.

A template never changes passwords, logins, tokens, or carrier connection details. Those fields are not in the list, and the system will not accept them.

Parcel size

On the Parcel tab, Parcel size specifies the size used for a parcel locker when nobody has chosen one. Doorstep deliveries and returns keep their dimensions.

• As set in carrier account—no change.
• S (A), M (B), L (C)—use that size. The packing kiosk will not ask for it.
• Ask employee while packing—the kiosk and label window ask for the size. An automation action that should send a label immediately will not send this shipment: it creates a task on the order, and the size is chosen during packing. An action that only prepares a shipment (a draft) can proceed; the kiosk asks for the size when the draft is confirmed.

The size field appears only for carriers that sell parcel sizes (InPost, Orlen Paczka, Packeta). The general template always shows it because it may be used for one of them.

Extra services, COD, and insurance

The Services tab shows every carrier service as a checkbox, including services not covered by your contract. The carrier will reject a parcel with an out-of-contract service. Selecting or clearing a service makes the template send exactly the selected set. The ↺ button in the header restores the services from the carrier account.

Geis, DB Schenker, and Ambro do not publish a service list. For these carriers, enter the codes from your contract.

On the COD and insurance tab:

• COD amount: order value, value excluding delivery, or amount still due.
• Insurance: carrier default, no insurance, order value, COD amount, or a fixed amount. A fixed amount is in PLN; an order in another currency uses that amount converted at the exchange rate for the day.

DHL, InPost, and Ambro never insure below the COD amount—this is required. DHL insures orders only in PLN. Allegro and Packeta always declare a value, so “No insurance” means the order value for them. Nowe Kolory calculates COD its own way. The screen shows these exceptions. A fully paid order with the “amount still due” rule has no COD. Returns do not get template services or insurance. Template insurance is used by DPD, DHL, InPost, Geis, Ambro, Allegro, and Packeta. Other carriers keep their own rule, as the screen explains.

Manually creating a label

In Create shipment, below the carrier, Label template: … appears when the order uses a template. Below it are the carrier's Extra services. The services selected by the template are checked. A change applies only to this label; ↺ restores the template values. Services are not available for a return or when confirming an InPost draft, because the shipment already exists. If the template says Ask employee while packing, the window asks for the parcel size.

Which store uses which template

Not on this screen. A template is assigned when mapping the carrier, because the mapping is the specific store/carrier pair. The Label template field is in both places where the mapping can be edited: on the integration page (the Shipping step, Carrier mapping section) and under Settings → Integrations → Carrier for delivery method. An empty field means Company default.

In Settings → Integrations → Carrier for delivery method, the Label template column shows how each mapping prints without opening it. A disabled template is marked in orange.

Only a role with read access to the Delivery module can see and change this field. Without it, saving a mapping preserves its template, and the system will not accept a template change either.

A disabled template cannot be assigned: it appears in the list with “inactive” beside it, but cannot be selected. A mapping that already had it keeps it and prints the company's default template until someone enables it or chooses another.

The list for a mapping contains general templates and templates for the account selected in that mapping. If you change the account, a template for another account disappears from the field. The system will not accept that template either, since it could not be printed.

This lets a company with several stores print different information on each store's parcels using the same carrier. A mapping with no selected template uses the company's default template; if there is no default, it uses the standard behavior.

When several mappings match, one specifying a specific carrier account takes precedence over one specifying only the carrier. A company with seven DPD accounts can therefore set a separate label for just one of them.

Weight and number of parcels

Both fields apply only when nobody has supplied a value of their own. An operator who weighs a parcel or counts boxes at the station always takes precedence over the setting.

The template gets weight from one of two options on the Weight line:

• From products (default)—sum of product weights multiplied by quantity. A product without a weight uses the fallback weight from company settings.
• Custom with the field empty—parcel weight from settings: first the template override (the Parcel section), then the carrier account, then the company. This suits a company that ships one carton type and is billed at a fixed weight class.
• Custom with a number or expression entered—one weight for every parcel.

The remaining sources act as fallbacks: if a fixed weight is invalid or products have no weight, the parcel still gets a weight from the products or settings.

Packaging weight is added at the end to every parcel, regardless of source, as a fixed number of kilograms or as a percentage of parcel weight.

A mapping without a template calculates weight as before: from products, then settings, without packaging weight.

At the packing station, nobody weighs parcels—the station calculates the weight of scanned products for each parcel. The template treats this as “from products,” not as weight entered by an operator: a template using “fixed” or “from settings” replaces it, and packaging weight is added just as for other shipments.

In the label-creation panel, the weight field is prefilled with what the selected carrier's template produces and recalculates when you change the carrier. With several parcels, each row gets the weight for one parcel: a fixed weight and a settings weight are the same for each, while product weight is divided evenly. A number entered manually by the operator always takes precedence.

Deleting a template

Deleting a template assigned to carrier mappings requires confirmation—the screen tells you how many mappings are affected. After deletion, they return to the company default template, changing what prints on those stores' parcels.

If a template is broken

A typo in an expression is caught on save and shown beside the field. If something still goes wrong while printing, the label gets the standard text. A template failure costs you a setting, never the shipment.

Permissions

Viewing the screen and preview requires read access to the Delivery module; creating, changing, and deleting requires write permission. The preview is read-only: a role that can only view still sees both the label and the table.