Shopify Nursery Plant Import: Care Guide Metafields

A garden centre in regional Victoria migrated 1,200 plant SKUs to Shopify. Titles, prices, and images all transferred correctly. What did not arrive: light requirements, watering schedules, hardiness zones, mature heights, and seasonal availability windows. Every product page went live with a name, a price, and a photograph.

Customers browsing for frost-hardy groundcovers had no way to filter for them. Seasonal species that should have shown as pre-order in June appeared as out of stock with no explanation. Three months after launch, the store's bounce rate was higher than its previous website.

This is a common outcome for nursery and garden plant imports. Plants carry four distinct layers of structured data that standard Shopify product fields cannot hold: care requirements, growth specifications, variant dimensions, and seasonal availability. A shopify nursery garden plant import with care guide metafields in place before the first row is processed produces a different result entirely.

Why Plant Catalogues Break Standard Import Workflows#

Standard Shopify fields handle title, description, price, inventory, images, and vendor. For most retail products, that covers everything a customer needs. For plants, it covers roughly half.

Three data layers have no home in standard product fields. Care guide data (light requirements, watering frequency, soil type, hardiness zone) exists in supplier catalogues but has nowhere to land in a Shopify CSV without a metafield schema defined in advance. Growth specification data (mature height, mature spread, growth rate, lifecycle) is structured in supplier files but gets buried in description text or discarded entirely. Seasonal availability is more nuanced than stock status: a deciduous tree in winter has zero inventory but is available for pre-order delivery in August. Showing it as out of stock loses the sale. Showing it as in stock when bare-root stock has not yet arrived creates a fulfilment problem.

Without a metafield schema built before the import, this data evaporates. The import happens, the products go live, and the store is missing the information that makes plant product pages usable.

Building a Care Guide Metafield Schema for Nursery Plant Import#

The goal is a schema where every plant attribute a customer might filter by, or a feed might require, lands in its own structured field. Before running the import, define these metafields in Shopify or through Importier's column mapping step:

Hardiness zone classification varies by region. Australian and New Zealand merchants typically use Bureau of Meteorology climate zones, which differ from the USDA Plant Hardiness Zone Map used in North America and the RHS classification used in the UK. If your supplier file uses a different zone system than your customers expect, the column mapping step in Importier's import flow is where that conversion happens, before the products are created rather than in a post-import bulk edit.

These metafields handle care guide data specific to nursery products. Category metafields for plant specification data populate Shopify's Standard Product Taxonomy attributes for the same products, covering plant type classification across the platform's structured data layer. The two systems work alongside each other.

Seasonal Availability as a Structured Metafield#

The Seasonal Availability metafield changes how a product page communicates with a customer during the off-season. Instead of a binary in-stock or out-of-stock state, the product page can display the availability window when the theme is configured to surface the metafield value.

The Next Available Date field pairs with this. For a deciduous rose available as bare-root stock from June, the merchant sets Seasonal Availability to Bare Root Season and Next Available Date to 2027-06-01. Stock remains at zero. The product stays published. The page communicates when the plant will be available, and the sale is not lost to an unexplained out-of-stock message.

“

The worst outcome for a plant nursery on Shopify is a customer searching for a deciduous Japanese maple, finding the product, seeing out of stock with no context, and closing the tab. The bare-root stock arrives in June. That customer needed to know that.

For year-round species (most perennials, native groundcovers, potted herbs), the Seasonal Availability value is Year Round and Next Available Date is left empty. The import mapping only needs to populate Next Available Date for seasonal rows.

Supplier files handle seasonal availability in three common formats. The first is a notes column with free text like "Autumn bare root only." The second is a set of quarterly availability columns with Y or N values. The third is no availability data at all. For the absent case, seasonal classification can be assigned at import time by product type: the species lifecycle value and the nursery's typical sourcing patterns give enough signal to produce a first-pass seasonal assignment for batch review before publishing.

Pot Size and Root Form as Variant Options#

Nursery products have two genuine variant dimensions that supplier files handle inconsistently: pot size and root form.

Pot size is a physical container dimension: 75 mm tube stock, 140 mm pot, 200 mm pot, 300 mm advanced. Each size carries its own price and inventory count. In most supplier files, these appear as separate rows with the same species name and a different size code in the SKU column. Without variant configuration at import time, the import treats each row as a separate product, producing 600 products from a 200-species catalogue offered in three sizes.

Root form is a separate dimension: bare root, tube stock, container, advanced, and espaliered. A rose may be available as bare-root stock in winter and as a 200 mm container year-round. These are the same product with different form options, not two separate products. Grouping them correctly consolidates the SEO signal onto a single product page rather than splitting it across two.

1. 01
   Map the SKU column and identify the species grouping key (botanical name or supplier product code) that links rows of the same species across sizes
2. 02
   Configure Pot Size as Option 1 using the size values from the Size or SKU column; configure Root Form as Option 2 from the Form column if both dimensions are present
3. 03
   Map Seasonal Availability and Next Available Date to their metafields from the appropriate supplier columns
4. 04
   Review the grouped product structure in Importier's import preview before sending to Shopify

   confirm 200 products with variants, not 600 individual products
5. 05
   Publish with Seasonal Availability values set; use Draft status for seasonal species not yet in their season

The most common error at this step is importing pot sizes as separate products rather than variants. For species with genuine search volume (roses, lavender, natives), the SEO consolidation from a single product page with three pot size variants is meaningful.

AI Descriptions for Plant Products#

Plant descriptions need to do two things that pull against each other: communicate care requirements clearly enough that a first-time gardener can succeed, and communicate aesthetic and lifestyle benefit compellingly enough that the gardener wants the plant.

Technical care specifications belong in metafields, not in the description body. The description's job is to convey how a plant changes a space and when it performs. Care information lives in structured fields where it can be filtered, exported to product feeds, and displayed in Shopify's taxonomy attribute block.

The Sensory-Rich description style with the Horticultural Advisor persona produces plant descriptions that open with seasonal performance and ambience (how the plant looks in late summer, what it does at the boundary between a path and a fence line) before grounding the care requirements in practical terms. A description that opens with "Coast rosemary fills the gap between the path edge and the fence line where most plants refuse to perform" anchors the plant in a real gardener's problem rather than a catalogue listing.

The critical input for this quality of output is the product title. Importier's AI needs the common name, cultivar, and pot size to produce descriptions specific to the species: "Coast Rosemary 'Blue Gem' 200mm", not "WFR-BLG-200". A SKU code as the title produces generic copy that could apply to any low-water native. Map the Common Name and Cultivar columns into a concatenated title field at import time and the description quality improves proportionally across the entire catalogue.

Managing Catalogue Rotation at Scale#

A nursery catalogue changes by season. Autumn brings deciduous trees and bare-root roses. Spring brings warm-season annuals and vegetable seedlings. A 1,200-SKU catalogue may rotate 200 to 300 products per season.

The workflow for seasonal rotation uses two mechanisms. The Seasonal Availability metafield keeps every species in Shopify across all seasons. Year-round species stay published. Seasonal species are set to Draft at the end of their availability window and republished when their season returns. This preserves each product page's SEO authority across multiple years rather than deleting and recreating products each season, which would discard accumulated backlinks and search history.

Scheduled imports handle new stock arrivals at the start of each season. When a supplier sends an updated price and availability file in late February for the autumn bare-root season, Importier's scheduled import picks it up, updates inventory levels, and republishes the Draft species entering their season. The import flow is configured once; the seasonal rotation runs without a manual reconciliation every six months.

Shopify's metafield documentation covers how to define and display custom metafields across your theme. For deciding when to use custom care guide metafields versus Importier's Industry Pack category metafields, the product metafields versus category metafields guide covers both types and their relationship within the same import.

A plant nursery's Shopify catalogue is not a product list. It is a structured knowledge base about living things that behave differently across seasons, climates, and growing conditions. The metafield schema is the architecture that makes that knowledge surfaceable: for customers filtering by light requirements, for merchants managing seasonal rotation, and for search engines indexing structured plant data.

The import is the moment to put that architecture in place. Building the metafield mapping as a saved import configuration in Importier means every new catalogue file from a supplier lands with the same structure. The setup cost is one session. The benefit is a plant catalogue that works for both the gardener who knows exactly what they want and the one browsing for something that will survive their conditions.

Try Importier free at importier.app