Plant passport labels for online plant sellers

A single plant passport label can look simple on screen: botanical name, issuer registration, traceability reference, and country of origin. The messy part starts when orders arrive from different channels, plant names are written in different ways, and labels need to be printed in time for packing.

A Monday batch might include Shopify order #1042 for Monstera deliciosa, an Etsy order for Philodendron gloriosum, and a CSV row for Ficus elastica collected from a plant fair preorder. Each row needs the right plant information before the label is worth printing. If that data lives in three places, someone has to reconcile it by hand.

Manual label work also creates small quality risks. Sellers copy from old labels, paste into a template, duplicate a PDF, then rename a file later. That can be manageable at five orders. At thirty orders, the question becomes: which label came from which order, which code was used, and where is the saved record?

If your orders come from marketplace and store channels, the Shopify workflow guide and Etsy workflow guide show how the same label process starts from each order source.

The exact information a seller needs depends on their own situation and the rules that apply to them, so this guide stays practical rather than legal. In day-to-day workflow terms, sellers usually need a clean way to keep order data, plant data and traceability data together before labels are printed.

A useful working set might include the sales channel, order number, customer shipment, product title, botanical name, quantity, batch reference, traceability code, supplier or origin note, print date and the person who generated the labels. Even if every field is not printed on every label, keeping the working data together makes later review much calmer.

One-off label tools are useful when the job is to produce a small number of labels from typed information. They become fragile when the same information needs to be reused, checked and stored across many online orders. The label output may be fine, but the surrounding record workflow is still missing.

At order volume, sellers need repeatability. They need to know which products still need botanical names, which orders are ready to print, which batch was exported, and whether the generated labels can be found again without opening a folder of final-final PDFs.

The work also becomes more collaborative. A shop owner may set up plant data, a packer may print labels, and another person may answer a customer or review a past shipment. If the only source of truth is a spreadsheet plus a folder of PDFs, everyone has to remember the same naming system perfectly.

A cleaner workflow starts with the order, not with a blank label. Import the orders that need labels, match each product to a botanical name and traceability reference, flag missing data before printing, then generate the label batch only after the working data has been reviewed.

For example, Shopify order #1042 can be matched to Monstera deliciosa and PP-2026-0418-034, while an Etsy order for Hoya carnosa can be held in a “needs data” state until the right traceability code is added. That keeps unfinished work visible instead of hiding it in a half-edited label file.

Once labels are generated, the batch should be saved as a record. The exported data, label file, order references and batch ID belong together. That way, “What did we print for BATCH-0418-03?” has an answer beyond checking someone’s downloads folder.

When labels are generated, it helps to follow the plant passport records guide and UK online seller workflow guide so batches stay searchable after dispatch.

Plant Passport Ops is built around the repeatable workflow: import order data, organise plant and traceability details, generate printable labels, and save the batch record. It is intentionally lightweight for small online plant sellers who do not want enterprise software just to keep labels and records under control.

It is not a generic plant passport label generator. The product focuses on the work around the label: which order it came from, which plant data was used, whether anything was missing, and how the generated batch can be found later. Sellers remain responsible for the information they enter and for understanding their own obligations.