Chain Length Attributes: How to Record Jewelry Chain Length

A chain length attribute is the measured length of a necklace, bracelet or anklet chain, stored as a number with a unit (for example, 18 inches) and a clear rule for what that number includes. Get the rule right once, apply it to every SKU, and your catalog stops producing returns, “does this include the clasp?” emails and mismatched feeds. This guide shows how to define the attribute, what to count, how to handle inches and centimeters, and how to keep fit descriptions like “collarbone” or “choker” from muddying the data.

TL;DR

• Store chain length as a number plus a unit, measured the same way on every product. Put style or fit words (choker, princess, opera) in a separate field.
• Decide and document whether the stated length is the usable length, whether it includes the clasp, and whether it includes an extender. Record adjustable chains as a range.
• Convert with 1 inch = 2.54 centimeters, keep full precision while calculating, and round once at the end.
• Pair every nominal length with a tolerance so you and your suppliers can settle disputes with data instead of opinion.
• Structured feeds make all of this enforceable, because a rule written into the attribute definition applies to every vendor the same way.

Table of Contents

• What a chain length attribute actually is
• What counts toward the stated length
• How to measure so everyone gets the same number
• Inches, centimeters and conversions
• Measured length vs. style and fit descriptions
• Tolerances: the field most catalogs skip
• Putting chain length into a feed
• Common mistakes to avoid
• Where this fits in the JewelCloud platform
• How JewelCloud helps you apply this
• FAQ
• Sources

What a chain length attribute actually is

In a jewelry catalog, chain length is one of the most-filtered and most-misread fields. Shoppers use it to decide whether a necklace will sit at the collarbone or lie on the chest. Retailers use it to compare vendors, and suppliers use it on spec sheets. If each of those parties reads the number differently, the same 18 in the data becomes three different pieces of jewelry.

A well-built attribute has four parts:

1. A numeric value, such as 18 or 17.5.
2. A unit, inches or centimeters.
3. A measurement rule, stating what is included (clasp, extender, pendant).
4. A tolerance, the acceptable variation from the nominal value.

Most catalogs capture only the first one or two. The other two are where the confusion comes from.

What counts toward the stated length

The biggest source of inconsistency is the question of what the number covers. A published product-measurement guide for jewelry sellers, written for vendor submissions, recommends recording the usable length of the chain: leave the clasp out when it adds nothing to the length you can actually wear, and include the extender when the piece has one.

That gives you a working rule you can adapt to your own catalog. Whatever you choose, write it down and apply it everywhere.

Clasps

Some retail size guides count the clasp in the quoted length, others do not. Neither is wrong, but mixing them in one catalog is. A lobster clasp adds a fraction of an inch, which is enough to move a piece between two filter buckets or make a customer feel a necklace came up short. Pick one rule per attribute, publish it in your data dictionary, and require vendors to follow it.

Extenders

An extender is a short length of chain at the closure that lets the wearer lengthen the piece. The usable-length guidance says to include it when applicable. In practice, the cleaner approach is to store the base length and the extender length as two separate attributes, then derive the maximum length from them. That way a filter for “16 to 18 inches” can behave sensibly, and a vendor who lists a 16-inch chain with a 2-inch extender is not forced to choose between 16 and 18.

Adjustable chains

For chains with several connecting rings or notched closures, the same guide advises measuring the shortest and longest positions and stating the length as a range. Model this with a minimum length and a maximum length field rather than a text string like “16-18 in”. Strings cannot be sorted, filtered or converted.

Pendants and drops

On a pendant necklace, the chain length describes the chain, and the pendant hangs below it by its own drop. Record the drop separately, usually in the pendant’s dimensions. Suspended-disc and bar necklaces are the exception where the overall measurement may include the disc or bar, jump rings, chain and clasp, so state the rule on those product types explicitly.

How to measure so everyone gets the same number

The same guidance recommends a flat, accurate metal ruler, with the chain laid out straight. Cloth tapes stretch and curve, and a chain held up by one end will stretch under its own weight. A practical measurement protocol for your team or your suppliers:

1. Lay the chain flat on a hard surface, fully straightened, with no twists.
2. Fasten it open and flat, not looped, so you measure the same condition every time.
3. Measure from the agreed start point to the agreed end point (for instance, from the end of one jump ring to the end of the other, clasp excluded).
4. Record the value. If it is not exact, the guide suggests rounding down to the nearest 1/16 inch, which keeps you from overstating length.
5. Photograph the measurement for the vendor file if the piece is high value or custom.

Rounding down is a sensible defensive habit. A piece that measures a hair over 18 inches and is listed as 18 is a promise you kept. One listed as 18 that measures just under is a complaint waiting to happen.

Inches, centimeters and conversions

U.S. shoppers expect inches, and many suppliers around the world send centimeters. Your catalog should store one canonical unit per attribute and convert for display, not store both by hand.

The conversion factor is exact: 1 inch equals 2.54 centimeters, per the National Institute of Standards and Technology’s weights and measures handbook. The agency’s guidance on unit conversion also says to use exact factors where they exist, avoid rounding the quantities used in the calculation, and round only the final result.

For chain length, that translates to a few simple rules:

• Store the value in the unit it was measured in, at full precision.
• Convert for display only, and round the displayed figure once. For example, 45 cm is 17.717… inches, shown as 17.7 inches.
• Never convert a rounded figure back and forth. A vendor who sends 18 in, a feed that converts to 46 cm, and a storefront that converts it back to 18.1 in has just invented a new product.
• Keep the standard retail sizes in the market’s native unit. In the U.S., that means 16, 18, 20 and 24 inches are the sizes shoppers search for, so a supplier’s 45 cm chain should be flagged for review rather than silently relabeled as 18 inches.

A quick conversion reference

These are straight multiplications by 2.54. The displayed column is rounded once, at the end.

Measured length vs. style and fit descriptions

The second major cause of messy data is that a single field is asked to do two jobs. “18 inches” is a measurement. “Princess length” or “sits at the collarbone” is a description of how that measurement tends to look on a body. They belong in different attributes.

Retail size guides generally describe lengths along these lines:

• Around 14 to 16 inches: close to the neck, often called a choker length.
• Around 17 to 18 inches: at or near the collarbone, the length shoppers most often reach for.
• Around 20 to 24 inches: lower on the chest, below the collarbone and approaching the neckline.
• Around 28 to 36 inches and beyond: long enough to wear doubled or layered.

Treat those as conventions, not facts about every wearer. Guides across the trade say that fit depends on the person and what they are wearing: a 24-inch necklace hangs differently on a petite wearer than on a taller one. That is exactly why the style label cannot stand in for the measurement.

A clean way to model it

Use separate fields:

With that structure, your site can offer a filter by measured length for shoppers who know their size, and a filter by style label for shoppers who browse by look. Neither corrupts the other.

Tolerances: the field most catalogs skip

Chains are manufactured, and manufactured goods vary. A nominal length should always travel with an acceptable tolerance range, rather than assuming a universal tolerance that every maker follows. The trade guidance on this is sensible: the same guide that covers measurement also says to address length tolerance for large links during design, because bigger links make the final length jump in larger increments.

When a retailer and a manufacturer disagree about a length, the fastest resolution is to confirm three things before arguing about the number:

• Both are measuring the same feature (clasp in or out, extender in or out).
• Both are looking at the same revision of the product or spec.
• Both are measuring the piece in the same condition, open and flat versus closed.

A tolerance field, plus a documented rule, answers all three before the dispute begins. For example, a spec of “18 in, usable length, clasp excluded, open and flat, ±0.25 in” leaves very little room to misunderstand.

Putting chain length into a feed

A spreadsheet column labeled “Length” with entries like “18”, “18 in”, “18"”, “45cm” and “16-18” is the typical starting point. Normalization turns that into clean fields. The steps below work whether you are a retailer cleaning inbound data or a supplier preparing an outbound feed.

1. Define the attribute. Write the rule: value, unit, what is included, tolerance.
2. Parse and standardize. Split numbers from units, strip symbols, and map variants to one canonical unit.
3. Separate extender and range data. Move “16-18” into min and max fields and “+2 ext.” into the extender field.
4. Validate. Flag lengths outside plausible ranges for the product type (a 4-inch necklace, a 70-inch bracelet) and values that convert to unusual inch sizes.
5. Version the rule. If you change how length is counted, record the change so older data is not misread.

For a deeper walk-through on getting suppliers’ attributes into a valid shape, see our guide to creating a valid jewelry data feed. If you are building the governance layer around these fields, attribute-first data governance covers who owns each rule. And once your length fields are clean, they feed directly into search visibility: our schema markup rollout for jewelers shows how structured attributes become machine-readable product data.

The retailer side matters too. When you pull in vendor products, a consistent length rule is what lets you compare like with like, and our piece on supplier integration for retailers explains how to keep that comparison reliable as vendor count grows.

Common mistakes to avoid

• Mixing counting rules. Half the catalog includes the clasp, half does not. Fix it at the attribute level.
• Storing text. “18 inch chain” cannot be sorted or filtered. Store the number and unit separately.
• Using style labels as measurements. “Princess” does not tell you whether the length is 17 or 19 inches.
• Dropping the extender. A 16-inch chain with a 2-inch extender is a different shopping decision than a flat 18.
• Converting twice. Round once, at display time.
• Ignoring pendant drop. The chain length does not tell the shopper where the pendant will land.
• Skipping tolerance. Without it, every small variation becomes a quality argument.

Where this fits in the JewelCloud platform

This is the kind of problem we built JewelCloud to take off your plate. Our product data is structured and standardized for the complexities of jewelry, so attributes like chain length arrive as defined fields instead of free text, ready to flow into your site.

We have seen the same pattern across catalogs of every size: the chain length column is the first place inconsistency shows up, because everyone assumes the number means the same thing to everyone else. It rarely does. One vendor includes the clasp, another adds the extender, a third sends centimeters rounded to the nearest five.

Our view is that a catalog is a living thing, and its attributes need rules that outlast any one spreadsheet. That is why we argue for structured feeds where each attribute has a definition, a unit and a tolerance, and where the data travels from supplier to retailer without being retyped. When the rule lives in the feed, you stop policing it by hand. Your shoppers get filters they can trust, and you get fewer returns caused by a number that meant something different to the seller than to the buyer.

If you take only one step from this article, make it this: write down what your chain length number includes, and require it of every vendor you source from.

Anthony

How JewelCloud helps you apply this

If you sell online and want vendor product data that arrives structured, the JewelCloud Product Feed is where we start. It brings standardized attributes, including measurements like chain length, from participating brands and suppliers into your storefront, so you can expand your assortment without carrying the inventory.

Suppliers can list wholesale through the Silver vendor membership at $1,500 per month, which puts your structured catalog in front of qualified retail partners. If you would rather talk through your data first, start from the JewelCloud home page and we will point you to the right fit.

FAQ

Does chain length include the clasp?

It depends on the rule you set, and that is the point. A published jewelry measurement guide recommends recording usable length, excluding the clasp when it does not add to the wearable length. Other retailers include it. Choose one rule for your catalog, write it in the attribute definition, and apply it to every product.

Should I include the extender in the chain length?

The most useful approach is to store the base length and the extender as separate attributes. The usable-length guidance says to include the extender where applicable, and a separate field lets you show both the base and the maximum length without losing either number.

How do I convert chain length from inches to centimeters?

Multiply inches by 2.54, which is the exact conversion factor published by NIST. Keep full precision during the calculation and round only the displayed result. For example, 18 inches is 45.72 cm, shown as 45.7 cm.

Is “princess length” the same as 18 inches?

Not as a data point. Princess is a style label that usually points to lengths around the collarbone, while 18 inches is a measurement. Store the measurement in the length field and the label in a separate style field, since fit varies with the wearer and the neckline.

What tolerance should I list for a chain?

There is no single industry-wide figure, so set one with your supplier and record it next to the nominal length. Larger links usually mean a coarser final length, so agree on the tolerance during design and note whether the figure applies open and flat.

Sources

• QxH Jewelry Product Measurement & Sizing
• 2023 NIST Handbook 44, Appendix C
• Unit Conversion, NIST Office of Weights and Measures

Recommended

• Style Number System for Jewelry: How to Build One That Scales
• 6 Step Jewelry Attribute Mapping Playbook for Retailer PIMs
• Suppliers: Create a Valid Jewelry Feed by Normalizing Attributes