Nomenclature of Coordination Compounds

Look at a bottle labeled potassium hexacyanidoferrate(II). Without ever seeing the formula, you can reconstruct it exactly. There is one potassium counterion per unit charge. The iron center is in the +2 oxidation state. Six cyanide ligands are bound through carbon. There is an overall complex anion. That single string of syllables encodes stoichiometry, connectivity, and electronic state. It is a compression of chemical information that ordinary organic naming rarely achieves. This is the point of systematic nomenclature: a name is not decoration but a coded structure. Coordination compounds are especially demanding to name. They carry more independent variables than typical molecules. There is a central metal with a formal oxidation state. There is a set of ligands that can be anionic, cationic, or neutral. There is a coordination number. Sometimes a geometry or chirality must also be flagged. Ancient names like "Prussian blue" or "cisplatin" survive as trade names. But they tell you nothing about what is bonded to what. The Coordination Compounds: Fundamental Concepts article establishes what a complex is. A central atom has donor atoms arranged around it. This article establishes what to call it. It follows the rules codified by IUPAC. These were most recently consolidated in the 2005 "Red Book" recommendations, with periodic updates. The big picture is a small number of ordering and formatting conventions. They are applied with total consistency. Ligands are cited alphabetically regardless of charge type. Multiplying prefixes distinguish simple ligands from substituted or polydentate ones. The oxidation state of the metal is given in Stock notation as a Roman numeral. The whole complex ion takes a suffix ("-ate") only when it is anionic. Once these rules are internalized, naming becomes mechanical. It is closer to parsing a formula than composing a sentence. Crucially, it becomes reversible. Given a rigorous name, a competent chemist reconstructs the formula with no ambiguity. This article works through the full rule set. It covers ligand naming and alphabetization, multiplying prefixes and their disambiguation, oxidation-state and overall-charge notation, anionic suffixes, and the ordering of cation/anion in ionic compounds. Worked examples range from a textbook complex to a bridged polynuclear cluster. It sets up Ligands and Denticity concepts already learned. It prepares the ground for Coordination Numbers and Geometries, where the same names will be assigned three-dimensional shapes.

Key takeaways

Ligands are cited in a single alphabetical list inside the name, regardless of whether they are anionic, cationic, or neutral.
Multiplying prefixes are di-, tri-, tetra-... for simple ligand names, and bis-, tris-, tetrakis-... for substituted or polydentate ligands whose own names already contain a multiplying prefix or would be ambiguous.
Anionic ligands take the suffix -o (chlorido, cyanido, oxido); neutral ligands mostly keep their molecular names, with aqua, ammine, carbonyl, and nitrosyl as memorized exceptions.
The metal's oxidation state is written as a Roman numeral (including 0) in parentheses immediately after the metal name, with no space.
If the complex ion is anionic overall, the metal name takes the suffix -ate (often with a Latin root: ferrate, argentate, plumbate); cationic and neutral complexes keep the ordinary element name.
In naming an ionic salt, the cation is named before the anion exactly as in simple ionic compounds, independent of which one is the complex ion.
Key idea: a coordination name is a fully determined encoding — alphabetize ligands, prefix their counts, suffix anionic ligands with -o, bracket the whole thing with a Roman-numeral oxidation state, and suffix the entire complex with -ate only if it is an anion.

Where this lives today

Rigorous nomenclature is not a museum exercise — it is load-bearing in registries, patents, and safety documentation. Chemical Abstracts Service (CAS) numbers and IUPAC names must uniquely map to structure so that a pharmaceutical patent for a platinum anticancer complex, an agrochemical containing a chelated micronutrient, or an MRI contrast agent built around a gadolinium chelate can be unambiguously identified across languages, regulatory jurisdictions, and decades of literature. Cisplatin's official chemical name, distinguishing it by the italic cis locant from the clinically useless trans isomer, is a direct, high-stakes illustration: two compounds with the identical molecular formula and near-identical mass spectra are told apart only by a coordination-geometry descriptor embedded in the name. Ambidentate-ligand notation (κ-locants distinguishing thiocyanato-S from isothiocyanato-N binding, or nitrito-N from nitrito-O) matters directly in catalysis and materials design, where the donor atom controls electronic structure, catalytic activity, and even color, while leaving the molecular formula unchanged — nomenclature is the only textual place this distinction survives outside of a full crystal structure. Multinuclear and cluster nomenclature, of the kind exercised in the bridged-chromium example above, underlies the naming of biologically vital metalloclusters such as the iron–sulfur clusters of ferredoxins and the oxygen-evolving Mn₄CaO₅ cluster of photosystem II, where bridging oxide and hydroxide ligands (denoted with μ-prefixes) connect metal centers whose formal oxidation states must be assigned correctly to understand the redox chemistry. Coordination polymers and metal–organic frameworks (MOFs), now central to gas storage and catalysis research, rely on the same bridging-ligand and multiplying-prefix conventions scaled up to extended, repeating three-dimensional lattices. In every one of these settings, the naming conventions developed here are the shared language that lets structure, oxidation state, and connectivity travel intact from one laboratory, patent, or textbook to the next.

:::quiz[In K₃[Fe(C₂O₄)₃], what is the oxidation state of iron?]

+2
+3 ✓
+6
0

:::quiz[A complex ion has formula [Co(NH3)4Cl2]+. What is the correct treatment of the -ate suffix?]

The metal name takes -ate because two anionic chlorido ligands are present
The metal name takes -ate because cobalt always uses -ate in complexes
No -ate suffix is used because the complex ion is net cationic, not anionic ✓
No -ate suffix is used because ammine is neutral

Ask the tutor: How would the name change if one ammine ligand in cisplatin were replaced by a bridging hydroxido connecting it to a second platinum center?

The physical picture

A coordination name is built from four independent pieces of information, each with its own formatting rule, assembled in a fixed order. Understanding why the order and formatting are fixed — rather than memorizing them as arbitrary — makes the system far easier to retain.

Piece 1: the ligands, alphabetized. Unlike organic nomenclature, where substituents are sometimes ordered by complexity or locant, coordination nomenclature alphabetizes ligands purely by the first letter of the ligand name itself, ignoring any multiplying prefix. This is because the name must be constructible without first knowing the formula — alphabetical order is the only ordering that doesn't require prior structural knowledge. "Ammine" (NH₃) comes before "chlorido" (Cl⁻) which comes before "cyanido" (CN⁃), regardless of how many of each are present or which one binds "first" in any synthetic sense.

Piece 2: the multiplying prefixes. Simple ligands (one word, no internal numerical prefix) use di-, tri-, tetra-, penta-, hexa-. But if a ligand's own name contains a number-word already (e.g., ethylenediamine, which contains "di"), or if the ligand name is a substituted or composite phrase (e.g., triphenylphosphine, or a chelating anion like oxalato), the plain prefixes would create ambiguity — "dichloroethylenediamine" could misparse as "(dichloroethylene)diamine." IUPAC solves this by switching to bis-, tris-, tetrakis-, pentakis-, hexakis-, and enclosing the ligand name in parentheses: bis(ethylenediamine), tris(oxalato).

Piece 3: the metal, its oxidation state, and the -ate suffix. The oxidation state is deduced by charge balance (ligand charges known, overall complex charge known) and written as a Roman numeral in parentheses directly after the metal name — Stock notation. Oxidation state zero is written (0), not omitted. If the complex ion carries a net negative charge, the metal's name is modified with the suffix -ate; several metals use their Latin-derived stem for this (iron → ferrate, silver → argentate, tin → stannate, lead → plumbate, gold → aurate, copper → cuprate) while most others simply add -ate to the English name (cobaltate, nickelate, platinate, zincate).

Piece 4: cation before anion, whole compound. Once the complex ion itself is named, it is slotted into the broader ionic-compound convention exactly like any salt: cation named first, then anion, as separate words, with no additional punctuation. Whether the complex is the cation or the anion, this outer ordering never changes.

Figure

Anatomy of a coordination name, piece by piece

Compare this with a cationic complex, where the metal name is left unmodified and the counter-anion is named after it:

Figure

Cationic complex: no -ate suffix, ligands alphabetized regardless of charge type

Note how the two examples mirror each other structurally but differ in exactly the two places the rules predict: the -ate suffix appears only on the anionic complex, and the counterion identity/position flips accordingly.

The core ideas

The entire naming system reduces to bookkeeping relationships. The most useful one to internalize is the charge-balance identity that lets you determine (and verify) oxidation state from a name or formula:

\text{(charge of complex ion)} = \sum_i n_i q_i^{\text{ligand}} + z_{\text{metal}}

where:

$n_i$ is the number of ligands of type $i$ ,
$q_i^{\text{ligand}}$ is the charge of that ligand (0 for neutral ligands like NH₃, H₂O, CO; −1 for chlorido, cyanido, hydroxido; −2 for oxalato, carbonato; etc.),
$z_{\text{metal}}$ is the oxidation state (Stock number) of the central metal,
and the sum runs over all distinct ligand types bound to that one metal center.

Reading: this is nothing but oxidation-state bookkeeping applied to a single coordination sphere — every ligand is assigned a conventional ionic charge (as if fully dissociated), those charges are summed, and whatever is "left over" is assigned to the metal. It is the same logic used to assign oxidation states in any inorganic formula, just packaged for polyatomic ligand sets. A second relationship governs the outer, ionic-compound level — the requirement that the whole salt be neutral:

p\,(z_{\text{cation}}) + q\,(z_{\text{anion}}) = 0

where:

$p$ and $q$ are the numbers of cation and anion formula units respectively,
$z_{\text{cation}}$ and $z_{\text{anion}}$ are the charges of the cation and anion (one of which is typically the whole complex ion, the other a simple counterion),
and the equation is simply the statement that a bulk salt must be net-neutral.

Reading: this relationship is what fixes the subscripts in the formula (and hence the multiplying prefix on the counterion, though counterions like Cl⁻ or K⁺ are not usually given multiplying prefixes in the name — the charge balance is implicit, recovered by the reader). It is the same rule used for every ionic solid, from NaCl to Al₂(SO₄)₃, merely applied with a complex ion playing the role of one partner.

Derivation AFrom a formula to a fully IUPAC-compliant name

Goal. Given the formula K₃[Fe(C₂O₄)₃] (potassium trioxalatoferrate(III), the classic resolvable chiral complex), construct the name from first principles and show every rule invoked.

Step 1 — Identify the complex ion and its charge. The species in brackets, [Fe(C₂O₄)₃]³⁻, is the complex. Outside the brackets there are three K⁺ ions. For the salt to be neutral,

3(+1) + z_{\text{complex}} = 0 \ \Rightarrow\ z_{\text{complex}} = -3 .

The complex ion is a trianion.

Step 2 — Assign ligand charges and back out the oxidation state. Oxalato (C₂O₄²⁻, the deprotonated dianion of oxalic acid) is bidentate and carries charge −2. There are three of them:

z_{\text{complex}} = 3(-2) + z_{\text{Fe}}

-3 = -6 + z_{\text{Fe}} \ \Rightarrow\ z_{\text{Fe}} = +3 .

Iron is in the +3 oxidation state — Stock notation (III).

Step 3 — Name and order the ligands. There is only one ligand type, oxalato, present three times. Because "oxalato" is a substituted/composite ligand name (and, more practically, because IUPAC treats bidentate carboxylate-type ligands with the bis/tris convention to avoid the reader mistaking a plain "tri-" for part of the ligand's own name), the multiplying prefix is tris, and the ligand name is enclosed in parentheses: tris(oxalato). Since there is only one ligand type there is no alphabetization step to perform, but had a second ligand been present (say, a substituted analogue), it would be alphabetized by first letter, ignoring "tris".

Step 4 — Name the metal with the anionic suffix. Because the complex ion is anionic overall (charge −3), the metal must carry the -ate suffix, and because iron has a Latin stem in general use, the Latin-derived form applies:

\text{iron} \longrightarrow \text{ferrate}

appended with the oxidation state in parentheses: ferrate(III).

Step 5 — Assemble the complex-ion name, then the whole salt. Ligand prefix + ligand name + metal-ate + oxidation state, all as one word for the complex portion:

\text{tris(oxalato)ferrate(III)}

Finally, cation before anion, as two separate words:

\text{potassium tris(oxalato)ferrate(III)}

This matches the accepted name for K₃[Fe(C₂O₄)₃] exactly, and every syllable traces back to a specific rule: three ligands (tris, because oxalato is a composite name), −2 charge per ligand times three ligands fixes Fe at +3, the −3 net charge on the complex triggers -ate, and potassium is written first as the simple cation.

Go deeper · Derivation B · 2 minFrom a name to a formula — the reverse operation, worked on a mixed-ligand cation

Derivation BFrom a name to a formula — the reverse operation, worked on a mixed-ligand cation

Goal. Given the name tetraamminechloridonitrito-κN-cobalt(III) chloride — a slightly more elaborate case including a linkage-isomerism flag — reconstruct the formula and verify internal consistency.

Step 1 — Split outer ionic-compound structure. The name has two "words" separated by a space: the complex-ion portion (everything up to "cobalt(III)") and the simple counterion "chloride." By the cation-before-anion convention, and because the complex portion carries no -ate suffix (it ends in the bare metal name plus oxidation state, not "cobaltate"), the complex is the cation and the trailing chloride is a simple anion counterion.

Step 2 — Parse ligand prefixes and identities, respecting alphabetical order. Reading left to right: "tetraammine" (4 × NH₃, neutral), "chlorido" (1 × Cl⁻, anionic ligand, since no prefix is given the implicit count is one), "nitrito-κN" (1 × NO₂⁻ bound through nitrogen — the nitro linkage isomer, as flagged by the κN locant). Checking alphabetical order of the ligand names themselves (ignoring multiplying prefixes): ammine (a) → chlorido (c) → nitrito (n). This is correctly alphabetical, confirming the name is well formed.

Step 3 — Assign ligand charges and verify oxidation state. Ammine is neutral (0), chlorido is −1, nitrito (as NO₂⁻) is −1. With cobalt at the stated Stock number (III):

z_{\text{complex}} = 4(0) + 1(-1) + 1(-1) + (+3) = +1 .

The complex ion is [Co(NH₃)₄Cl(NO₂-κN)]⁺, a monocation.

Step 4 — Balance the outer salt. A monocationic complex requires exactly one chloride counterion for neutrality:

1(+1) + q(-1) = 0 \ \Rightarrow\ q = 1 .

Step 5 — Write the full formula.

[\text{Co(NH}_3)_4\text{Cl(NO}_2\text{-}\kappa N)]\text{Cl}

Every piece of the name is now accounted for: four ammine, one chlorido, one nitrito bound via nitrogen (distinguished from the O-bound "nitrito-κO" linkage isomer, which would be named differently and would change the color and reactivity of the complex without changing its formula), cobalt(III) fixed by the +1 net charge on a complex carrying two anionic ligands, and a single chloride counterion completing the neutral salt. As a limiting-case check: if the nitrito ligand were instead replaced by a second neutral ligand of charge 0, the complex charge would become +2, and two chlorides would be required outside the bracket — exactly the kind of consistency check that catches transcription errors in either direction.

Worked examples

Example 1 — Foundational: [Cu(NH₃)₄]SO₄. The bracketed unit [Cu(NH₃)₄]²⁺ contains four neutral ammine ligands and copper. Sulfate outside the bracket is SO₄²⁻, a well known simple anion, so

z_{\text{complex}} + (-2) = 0 \ \Rightarrow\ z_{\text{complex}} = +2 .

With four neutral ligands, $4(0) + z_{\text{Cu}} = +2$ , giving $z_{\text{Cu}} = +2$ , i.e., copper(II). Since the complex is cationic, no -ate suffix is used, and copper keeps its ordinary name. There is only one ligand type, so no alphabetization decision is needed, and the multiplying prefix is the simple "tetra" (ammine is not a composite name requiring bis/tetrakis — though note "ammine," with two m's, is itself a fixed exception spelling for coordinated ammonia, not to be confused with organic "amine"). The complex-ion name is tetraamminecopper(II); the full salt name, cation then anion, is:

\textbf{tetraamminecopper(II) sulfate}

As a sanity check on formatting: had the counterion instead been a complex anion (say, if this were paired with a ferrate anion in some hypothetical double salt), the same cation name would be retained unchanged in front of it — the rule for naming a cation never depends on what its partner anion happens to be.

Example 2 — Applied: cisplatin and its geometrical name, cis-diamminedichloridoplatinum(II). Cisplatin, the anticancer drug, has the formula $[\text{PtCl}_2(\text{NH}_3)_2]$ , a neutral square-planar complex with two chlorido and two ammine ligands arranged so that identical ligands are adjacent (cis) rather than opposite (trans). Ligand charges: chlorido is −1 (two of them), ammine is 0 (two of them). Since the whole species is neutral overall (no counterion at all — this is a rare but important case, a neutral complex),

z_{\text{complex}} = 2(-1) + 2(0) + z_{\text{Pt}} = 0 \ \Rightarrow\ z_{\text{Pt}} = +2 .

Platinum is in the +2 oxidation state. Alphabetizing the ligand names: ammine (a) precedes chlorido (c), so ammine is cited first in the name despite the formula conventionally writing anionic ligands before neutral ones (formula-writing order and name alphabetization are independent conventions and need not match). Both ligands occur twice, using the simple prefix "di" for each (both are simple, non-composite ligand names): diammine, dichlorido. Because the complex is neutral, no -ate suffix applies, and because there is no counterion, the name terminates directly at platinum(II):

\textbf{diamminedichloridoplatinum(II)}

The geometry-descriptor prefix cis- is prepended, italicized, and set off by a hyphen, giving the full stereo-descriptive name cis-diamminedichloridoplatinum(II) — distinguishing the potent drug from its clinically inactive trans isomer, transplatin, which has an identical molecular formula and would otherwise be named identically apart from the descriptor. This is a case where nomenclature alone — the italic locant — is the only textual signal separating a chemotherapy agent from an inert isomer, foreshadowing why geometry, taken up under Coordination Numbers and Geometries, must eventually be layered onto these names for square-planar and octahedral cases with more than one distinct arrangement.

Example 3 — Exam/competition level: a bridged, mixed-ligand, mixed-oxidation-state dinuclear cation. Consider the cationic complex $[(\text{NH}_3)_5\text{Cr}(\mu\text{-OH})\text{Cr}(\text{NH}_3)_4(\text{H}_2\text{O})]\text{Br}_5$ , a hydroxo-bridged dichromium species with one bridging hydroxido ligand connecting two inequivalent chromium centers — one bearing five ammines, the other bearing four ammines plus one aqua ligand. This tests bridging-ligand notation, multi-metal oxidation-state assignment, and full alphabetization across a more crowded ligand set. First, determine total complex charge from the five bromide counterions (each −1, requiring the complex charge to be +5):

z_{\text{complex}} = 5(+1)\ \text{per Cr contributions} \ldots

handled properly by summing ligand charges and both metal oxidation states directly. Ligands present: nine ammine total (0 each), one bridging hydroxido (−1, shared between both metals but counted once), one aqua (0). Assume, as is standard for this classic ion, that both chromium centers are Cr(III) (charge +3 each, total +6):

z_{\text{complex}} = 9(0) + 1(-1) + 1(0) + 2(+3) = -1 + 6 = +5 .

This matches the requirement of five bromide counterions exactly, confirming both metals are indeed Cr(III) — a self-consistent result rather than an assumption, since no other combination of common chromium oxidation states reproduces +5 with this ligand set (Cr(III)/Cr(III) is the only pairing from common integer states {+2, +3, +6} that fits: e.g., +2/+3 would give total metal charge +5, and $-1 + 5 = +4$ , too low; +3/+3 gives $-1+6=+5$ , correct). Now assemble the name. The bridging hydroxido ligand is cited with the italic prefix μ- (mu) and is alphabetized by "h" (hydroxido), placed among the other ligand types. Because the two chromium environments are different, IUPAC's additive nomenclature for such asymmetric bridged species lists the ligands on each metal explicitly, grouped by locants (primed and unprimed) identifying which chromium each set belongs to. A defensible full systematic name is:

\textbf{pentaamminechromium(III)-}\mu\textbf{-hydroxido-tetraamminaquachromium(III) pentabromide}

read as: one Cr(III) center bearing five ammines, bridged through a single shared hydroxido ligand (μ-hydroxido, alphabetized among that metal's local environment as needed by convention) to a second Cr(III) center bearing four ammines and one aqua ligand, the whole dication—here in fact a +5 cation—balanced by five bromide ions as pentabromide. The exercise demonstrates that even a structurally intricate, asymmetric, bridged polynuclear ion is fully decomposable by the same charge-balance and alphabetization logic used in the simplest mononuclear cases; only the bookkeeping becomes longer, never conceptually different.

Limiting cases, scope & common traps

Situation	Rule that applies	Frequent error
Metal oxidation state is zero	Still write (0) explicitly, e.g. tetracarbonylnickel(0)	Omitting the parenthetical zero entirely
Ligand name already contains a numerical prefix (ethylenediamine, bipyridine)	Use bis-, tris-, tetrakis- with parentheses	Using "di-ethylenediamine" without parentheses, creating ambiguity
Complex ion is neutral overall	No -ate suffix, no counterion at all	Adding an unnecessary "-ate" or inventing a spurious counterion
Two or more different metals in one cluster	Name each metal's local ligand set with locants (primed/unprimed or numbered)	Merging all ligands into one alphabetized list without attributing them to a specific metal
Ambidentate ligand (NO₂⁻, SCN⁻)	Specify binding atom with κ (kappa) notation or classical -nitro/-nitrito, -thiocyanato/-isothiocyanato pairs	Naming the ligand without specifying donor atom, losing linkage-isomer information
Simple monatomic anionic ligand (F⁻, Cl⁻, Br⁻, I⁻, O²⁻)	Suffix -ido: fluorido, chlorido, oxido	Using older "fluoro/chloro/oxo" forms, still common in casual use but superseded in current IUPAC recommendations
Alphabetizing ligands with multiplying prefixes present	Alphabetize by the ligand name itself, ignoring di/tri/bis/tris	Alphabetizing by the first letter of the written prefix, e.g. putting "dichlorido" before "ammine" because "d" precedes... (wrong: prefixes are ignored)

The chemist behind it

Systematic coordination nomenclature as used today descends most directly from the conceptual breakthrough of Alfred Werner, whose coordination theory (1893) first proposed that a metal center has a fixed "coordination number" of ligands arranged geometrically around it, distinct from its ordinary valence. Before Werner, complexes like $\text{CoCl}_3\!\cdot\!6\text{NH}_3$ were written as loosely associated addition compounds with no structural interpretation; Werner argued, based on the number of ionizable chloride ions detected by conductivity and precipitation experiments, that the compound was in fact $[\text{Co(NH}_3)_6]\text{Cl}_3$ — an octahedral cation with three chloride counterions, all three of which precipitate instantly with silver nitrate, in contrast to $[\text{Co(NH}_3)_5\text{Cl}]\text{Cl}_2$ , where only two of the three chlorides precipitate because one is bound directly to cobalt inside the coordination sphere. This distinction between "ionizable" and "coordinated" chloride is precisely what modern nomenclature encodes structurally: coordinated chlorido appears inside the bracket portion of the name, ionizable chloride appears as the separate counterion word outside it.

Origins · 1 minAlfred Werner and how this was discovered

Alfred Werner

1866–1919 · Founder of coordination theory, University of Zurich

Werner, a chemist trained partly under mentors emphasizing physical and structural organic chemistry, turned to inorganic complexes at a time when they were considered structurally opaque "molecular compounds." Using solution conductivity (to count the number of dissociated ions), stoichiometric precipitation of silver halide (to count ionizable versus bound halide), and — decisively — the resolution of optically active octahedral complexes containing no carbon at all, he demonstrated that metal centers adopt definite three-dimensional coordination geometries with a fixed coordination number, independent of and superimposed upon classical valence. He received the Nobel Prize in Chemistry in 1913, the first inorganic chemist honored with the prize, for establishing the structural basis that all subsequent coordination nomenclature encodes.

History

- 1798: Tassaert prepares

\text{CoCl}_3\!\cdot\!6\text{NH}_3

, the first well-characterized "complex salt," with no structural explanation available.

- 1893: Alfred Werner publishes his coordination theory, proposing fixed coordination numbers and geometric arrangement around metal centers.

- 1913: Werner is awarded the Nobel Prize in Chemistry for his work on the linkage of atoms in molecules, primarily coordination theory.

- 1940s–1960s: IUPAC's inorganic nomenclature committees formalize Stock notation (Roman-numeral oxidation states) and systematic ligand-naming rules for widespread chemical literature use.

- 2005: IUPAC publishes the consolidated "Red Book" (Nomenclature of Inorganic Chemistry), codifying current recommendations including -ido suffixes for anionic ligands and κ (kappa) locants for donor-atom specification.

Why do anionic ligands end in -o (or, in current usage, -ido) rather than keeping their ionic name?

The -o/-ido ending is a dedicated nomenclature marker signaling "this species is acting as a ligand," distinct from its free-ion name. "Chloride" is the free Cl⁻ ion; "chlorido" (or the older "chloro") specifically denotes Cl⁻ coordinated to a metal center. This distinction matters because the same species can appear in one formula as a free counterion (named "chloride," outside the bracket) and as a coordinated ligand (named "chlorido," inside the bracket) — as in $[\text{Co(NH}_3)_5\text{Cl}]\text{Cl}_2$ , which contains chlorido once and chloride twice. Using different suffixes for the two roles removes any ambiguity about which chlorides are bound to the metal and which are simply ionic counterions in the lattice.

Does the multiplying prefix ever get alphabetized along with the ligand?

No. Multiplying prefixes (di, tri, tetra, bis, tris, tetrakis, and so on) are never counted when placing ligands in alphabetical order; only the ligand's own name matters. For example, in a hypothetical complex with both "dichlorido" and "ammine," ammine is cited first because "ammine" starts with "a," even though "dichlorido" would come first if the "d" of "di-" were mistakenly counted. This rule exists precisely because the prefix is structural bookkeeping (how many), not part of the ligand's chemical identity, and alphabetization is meant to sort chemical identities.

How do you name a complex that has zero net charge and thus no counterion at all?

Neutral complexes, such as cisplatin $[\text{PtCl}_2(\text{NH}_3)_2]$ or nickel tetracarbonyl $[\text{Ni(CO)}_4]$ , are named exactly like the cationic branch of the rules: ligands alphabetized with appropriate prefixes, then the metal name (unmodified, no -ate suffix, since the complex is not anionic) followed by its oxidation state in parentheses. There is simply no second word for a counterion, since none exists. Tetracarbonylnickel(0) is a clean example: four carbonyl ligands (neutral CO, hence oxidation state 0 contributes nothing), and the metal's oxidation state is 0, which must still be written explicitly rather than omitted.

Why does iron become "ferrate" and not "ironate" in anionic complex names?

A handful of metals retain their historical Latin (or Latinized) stem specifically for use with the -ate suffix in anionic complex nomenclature, a holdover from Latin element names still used in some contexts (compare "ferrous/ferric" for iron oxidation states). Iron → ferrate, silver → argentate, gold → aurate, tin → stannate, lead → plumbate, and copper → cuprate are the standard set. Most other metals simply append -ate to their ordinary English name without modification: cobalt → cobaltate, nickel → nickelate, zinc → zincate, platinum → platinate, manganese → manganate. There is no general rule predicting which metals use Latin stems; this short list must simply be memorized, though it maps closely onto the metals with long-established Latin names in classical chemistry.

Can a single complex require both bis/tris prefixes and ordinary di/tri prefixes in the same name?

Yes, routinely, whenever a complex contains both simple and composite ligands simultaneously. Consider a complex with two chlorido ligands and two ethylenediamine ligands: chlorido is simple, so it takes "di" (dichlorido), while ethylenediamine already contains an internal "di," so it must take "bis" with parentheses (bis(ethylenediamine)) to avoid ambiguity. Alphabetized correctly (ignoring both prefixes), "chlorido" (c) precedes "ethylenediamine" (e), giving dichloridobis(ethylenediamine) as the ligand portion of the name — each ligand type independently chooses its own prefix family based on its own name's structure.

How does nomenclature distinguish a bridging ligand from a terminal one?

A bridging ligand — one that connects two or more metal centers simultaneously, such as a hydroxido or oxido group linking two chromium or iron atoms — is flagged with an italic Greek mu (μ) directly before its name, sometimes with a subscript indicating how many metals it bridges (μ₃- for a triply bridging ligand capping three metals, for instance). This single symbol communicates a real structural fact — shared connectivity — that would otherwise require drawing the full structure to convey, and it is essential in naming metal clusters, extended coordination polymers, and biologically important multi-metal cofactors correctly.

Is the older "-o" ending (chloro, oxo, hydroxo) simply wrong now?

It is not "wrong" in the sense of being unrecognizable — it remains widespread in textbooks, journal archives, and casual laboratory speech, and chemists reading it will understand it correctly. However, current IUPAC recommendations (from the 2005 Red Book onward) specify -ido as the systematic ending for anionic ligands (chlorido, oxido, hydroxido) to standardize the ending across the periodic table and avoid occasional clashes with unrelated organic suffixes. When writing for a modern audience or for formal documentation, -ido is the recommended form, but recognizing both forms is a practical necessity given decades of existing literature.