Understanding Sarracenia Names: Species, Subspecies, Varieties, Forms and Cultivars

Part 2 of the Nano Nursery Sarracenia Encyclopedia

A Sarracenia label can read like a sentence in another language. One pot says Sarracenia flava var. cuprea. Another carries Sarracenia purpurea subsp. purpurea f. heterophylla. A third has a name in quotation marks, a multiplication sign or a grower’s code.

Those details are useful once you know what each one is doing. Some describe how a plant is classified. Others describe its parentage, a cultivated selection or its history in a collection. Learning to separate them helps you compare plants, keep accurate labels and avoid giving a seedling or an unknown hybrid a name it has not earned.

A quick guide to the label

  • Species: Sarracenia flava — a two-part botanical name.
  • Subspecies: Sarracenia purpurea subsp. venosa — a subdivision below species.
  • Variety: Sarracenia flava var. cuprea — a botanical variety in treatments recognising that rank.
  • Form: Sarracenia purpurea subsp. purpurea f. heterophylla — a named botanical form.
  • Hybrid formula: Sarracenia flava × Sarracenia leucophylla — a statement of parent taxa.
  • Cultivar: Sarracenia ‘Victoria Morley’ — a named cultivated selection.
  • Accession or clone code: a collection reference whose meaning depends on the grower’s records.

The examples below explain these categories. Their inclusion does not mean that every reference recognises every botanical subdivision, or that Nano Nursery currently stocks each plant.

Start with genus and species

In Sarracenia flava, Sarracenia is the genus and flava is the specific epithet. Together they make the species name. Capitalise the genus, keep the epithet lower case, and italicise both. After writing the full name, you can shorten it to S. flava when the genus is clear.

A species name identifies a taxonomic group, not a single genetically identical plant. Two plants carrying the same species name can differ without either needing a new name. A useful collection record therefore keeps the species identification separate from the identity of the particular plant.

If an author abbreviation follows a botanical name, it identifies the person or people associated with publishing that name. It is not part of a cultivar name, a size grade or a supplier’s stock code. The RHS nomenclature search explains the role of these author abbreviations.

Subspecies, variety and form: ranks within a species

The ranks commonly encountered on Sarracenia labels descend from species to subspecies, variety and form. These sit within the wider hierarchy set out in Article 4 of the botanical nomenclatural Code. A plant’s label does not need to display every intermediate rank.

A subspecies is a taxonomic subdivision of a species. A variety is another rank below species, and a form is a lower rank again. The rank tells you how an author has classified the variation; it is not a numerical measure of how genetically different, rare or valuable the plant is.

Avoid treating “subspecies means location, variety means colour” as a universal rule. Classification requires an author’s judgement about the evidence, and different treatments may place the same plants at different ranks. In this encyclopedia, we will identify the treatment being followed when that distinction matters.

Write the connecting abbreviations subsp., var. and f. in ordinary type. The botanical names on either side remain italicised. The RHS Plant Finder glossary is a useful guide to reading botanical and cultivated-plant names.

Why a botanical variety is not a cultivar

For Sarracenia growers, S. flava var. cuprea is a familiar example of a botanical variety. In Barry Rice’s specialist account of S. flava, it describes plants with a coppery or reddish lid contrasting with a green tube. That name is used for a category of variation, rather than identifying one particular selected individual.

“Variety” also appears informally in gardening conversation to mean almost any kind of plant. That casual usage can blur the difference between a botanical variety and a cultivar. On a careful label, var. cuprea is not interchangeable with ‘Cuprea’ in cultivar quotation marks.

A cultivar can be selected from within a species, or from hybrid material. It is not the next botanical rank below form. The botanical classification and the cultivated selection describe different aspects of identity.

Reading a longer name

Take Sarracenia purpurea subsp. purpurea f. heterophylla. Read it in pieces: the species is S. purpurea; the subspecies is purpurea; the form is heterophylla.

The RHS profile for this form describes plants without the anthocyanin pigmentation responsible for the usual red colouring, with lime-green pitchers and yellow flowers. Here the form name refers to a described botanical variation. It should not be assigned to an unfamiliar plant solely because one photographed leaf looks green.

A repeated word is not necessarily a typing error. Names such as S. purpurea subsp. purpurea are called autonyms: the repeated epithet identifies the subdivision that contains the nomenclatural type of the species name. Article 26 of the Code sets out this rule. It does not mean “the largest”, “the commonest” or “the original clone sold by a nursery”.

Reading hybrid formulas

A multiplication sign between botanical names indicates a hybrid formula. For example, Sarracenia flava × Sarracenia leucophylla names the parent taxa involved. Article H.2 distinguishes this formula from the name of a hybrid taxon.

Do not assume that the first name in every published formula is automatically the seed parent. Botanical formulas may be arranged alphabetically. Breeders often record the seed parent first, but the convention needs to be explicit. For your own crosses, recording “seed parent” and “pollen parent” removes the ambiguity.

Brackets preserve the structure of a more complex breeding record. In a hypothetical cross written (S. flava × S. leucophylla) × S. purpurea, the bracketed hybrid is one parent in the next cross. Keep the brackets and the original record rather than flattening the label into an unordered list of species.

A botanical hybrid name also need not describe just one first-generation seedling. The Code’s Article H.4 allows a hybrid taxon to encompass later generations and backcrosses derived from the stated parent taxa. A hybrid name is therefore not a clone identifier and does not promise that every plant carrying it will look identical.

Cultivars: names attached to defined cultivated selections

Write a cultivar name in single quotation marks, without italicising the cultivar epithet: Sarracenia ‘Victoria Morley’. The genus stays italicised. The RHS glossary distinguishes this presentation from botanical names.

There is a useful real example behind that name. In his original description of ‘Victoria Morley’, Stephen Morley records a cross between Sarracenia × mitchelliana and S. leucophylla. He describes a variable group of seedlings, from which one plant was selected and subsequently distributed by division.

That history separates three things: the cross, the selected plant and its cultivar name. Repeating the cross would produce another seedling population. It would not, merely by sharing the same parent combination, recreate the identity of that selected plant.

Before applying a cultivar name, consult its original description, any nomenclatural standard and its documented propagation requirements. A nomenclatural standard is a reference specimen or image used to interpret a cultivar name; the RHS explanation of standards describes why those references matter.

Registration records are another part of the evidence. ICPS publishes lists linking cultivar names to their descriptions, such as its 2022–2023 registration list. Quotation marks on a sales label alone do not establish that a name is registered.

Do seedlings inherit a cultivar name?

Do not automatically put the parent’s cultivar name on its seedlings. Record the actual cross where both parents are known. If only the seed parent is known, record that fact and retain the uncertainty about the pollen parent.

Propagation requirements depend on the cultivar. Many named Sarracenia selections are maintained vegetatively, but it is too broad to claim that every cultivar of every plant must be a single clone. Follow the description and requirements of the particular name rather than relying on a general slogan.

For collection management, a division of a documented plant and a seedling raised from that plant should have distinguishable records. Sharing a parent is not the same as being a division of it.

Why two sources may use different names

Classification and naming are related, but different questions. Taxonomy asks how plants should be grouped. Nomenclature concerns the application of names. A correctly published name may be treated as a synonym rather than an accepted taxon in a particular modern reference.

For example, Kew currently accepts Sarracenia rosea and lists S. purpurea var. burkii among its synonyms. It also places the name S. rosea f. luteola in synonymy under the species. A specialist grower may still find the form designation useful when discussing that variation, provided its taxonomic status is made clear.

When updating a collection record, preserve the name under which the plant arrived. Add the current identification, the reference used and the date. That leaves a traceable history instead of making an older label disappear.

Localities, clone codes and descriptive labels

A locality label can preserve valuable origin information. A clone code can connect a plant to an individual in a grower’s collection. Neither should be expanded into a formal taxonomic name without evidence.

Suppose a supplier’s label reads “red throat, clone 7”. Keep that wording with the supplier’s name and the acquisition date. Do not convert it into ‘Red Throat’ as a cultivar, invent a wild locality, or assume that another grower’s “clone 7” means the same plant.

Likewise, keep a nursery stock identifier separate from the botanical name. It may identify an offer, size or production format rather than a distinct botanical identity. A good record lets the plant’s name, provenance and sale format each do their own job.

A practical record for your own collection

  • Name as received: copy the supplier’s complete wording, including brackets, codes and uncertainty.
  • Current identification: record the name you use now and the source supporting it.
  • Origin: keep the supplier, acquisition date and any documented locality or breeding history.
  • Propagation: distinguish seedling, division and other methods where known.
  • Individual reference: give your plant a stable collection number.
  • Evidence: retain label photographs, mature-plant photographs, descriptions and correspondence relevant to identity.

If you later revise an identification, add a dated note. If a plant produces divisions, carry its documented identity with them. If you raise seedlings, start records for the offspring and preserve the cross information separately.

Common label mistakes to avoid

  • Treating every red, green or unusually large plant as a named botanical form.
  • Changing a botanical variety into a cultivar by adding quotation marks.
  • Assuming that all seedlings from one cross are the same clone.
  • Reading a hybrid formula as a complete pedigree when generations or individual parents were not recorded.
  • Using a photograph alone to claim a cultivar identity or precise locality.
  • Replacing an old name without retaining the original label and the reason for the change.

For the Nano Nursery encyclopedia, this means every profile will distinguish the accepted name used in that article, alternative names, the evidence for any cultivar identity and the limits of what is known. You will be able to follow an unfamiliar label without having to guess which kind of name it contains.

Next in the series: Growing Sarracenia in Australia: The Complete Foundation Guide.

Last reviewed: 22 September 2026. Sources are linked beside the relevant explanations. Botanical rank and hybrid provisions cited here are from IAPT’s online Shenzhen Code text; current accepted-name examples were checked against the linked references.

Back to blogs