Give a product story something to stand on

A product description can travel a long way from the records that first supported it. A supplier sends a specification. Someone summarizes it for a product page. A campaign writer shortens the sentence again. Months later, the wording sounds certain, but nobody is sure which item it covers or where the original evidence lives.

You can start fixing that with one description. Copy the current text into a working document, mark every statement a reader could reasonably understand as factual and connect each one to a source. The goal is to make the product story easier to check and maintain, while keeping the published language within what the records actually support.

Pull apart the sentences

A short sentence can contain several claims. “Locally made from recycled material for years of daily use” says something about place, composition and durability. Each part needs its own review. A source supporting one part does not automatically support the others.

Separate concrete statements from opinion. A color name or an aesthetic description may be a creative choice. Dimensions, material percentages, country of manufacture and performance statements are factual matters. Some wording sits between the two, so ask what a normal reader might take it to mean in the context of the page.

For US advertising, the FTC’s advertising substantiation policy states that objective claims need a reasonable basis before publication. That principle is a useful reason to check evidence early. The kind of support required depends on the claim and circumstances; a simple content audit does not replace specialist review where that is needed.

Make a separate row for each claim. Keep the original wording, its location and the exact product or range it appears to describe. Include packaging, retailer copy and campaign material when they repeat the statement. You may discover that a narrow claim has gradually become a broad one.

Build a small evidence register

For each row, record the source document, the person or organization that supplied it, the date, the products or batches covered and any limitation. Link to the actual file in your approved storage location. A note saying “supplier confirmed” will be difficult for the next person to evaluate.

Distinguish kinds of evidence. An invoice records a transaction. A specification describes agreed characteristics. A test report records a test with a method and scope. A supplier statement reports what the supplier says. Each can be useful, but they do different jobs.

A photograph may show a process or an item. It usually needs context: who took it, when, where and which product it depicts. Avoid assuming that an attractive workshop image proves every item was made there. Preserve its caption and provenance when moving it between folders.

Give each record an owner. That person should know when to check whether the source is still applicable. A register without ownership can become another archive that looks complete while the product has moved on.

Check identity, dates and scope

The first question is whether the source refers to the thing being sold. Similar model names, changed suppliers and different production runs can make this less obvious than it sounds. Match the identifier on the evidence to the identifier used in the product record.

Next, check the dates. A current product page may rely on a report prepared before a material or process change. The old evidence may remain useful for earlier items, but the team needs to determine whether it supports the current version.

Finally, inspect the scope. A statement about one component should not become a statement about the whole product. A test under one set of conditions should not become an unrestricted promise about every use. Write the limits in the working register so the editor can see them before choosing language.

GS1’s explanation of EPCIS describes event records in terms of what happened, when, where and the business context. That structure is useful when organizing a product history. It helps you ask which event a record describes, although using those fields alone does not verify the event or authenticate the source.

Work through a sample description

Imagine a maker selling a side table. The draft description says the table is made in a local workshop, uses reclaimed timber and has a finish that lasts for years. The available folder contains a workshop production note, a material invoice and a finish supplier’s care sheet.

The production note may support where a specified batch was assembled, provided the product identity and date match. The material invoice may help establish what was purchased, but the team still needs to confirm which material went into this item and what the supplier’s terminology means. The care sheet gives maintenance instructions; it does not by itself establish a broad durability promise.

The editor can then revise the description to match the supported details and hold the unresolved statements for review. The resulting copy might identify the workshop, describe the documented material source more precisely and provide the approved care instructions. The exact wording depends on what the records establish.

This is a hypothetical example, not a finding about a real product. Its value is the sequence: identify the claim, inspect the source, confirm the connection and adjust the wording. The evidence should guide the sentence rather than being selected afterward to defend it.

Make gaps actionable

Use simple review states such as supported for this use, clarification needed, specialist review required or remove from publication. A gap should have a next action and an owner. “Needs evidence” is a starting point, but “ask the supplier which production batches this statement covers” is something a person can do.

If a statement cannot be supported in time, narrow or remove it. Do not fill the space with another broad term that creates the same problem. The product may have plenty of useful details to describe: dimensions, materials that are documented, intended use, care, repair options or the process the maker can actually explain.

Keep customer-facing material readable. Buyers do not need to see your entire evidence register. They need accurate wording, meaningful detail and access to supporting information when it helps them make a decision. Store confidential records privately and publish only material you are authorized to share.

Review the story when the product changes

Add the evidence check to the moments when descriptions are likely to become stale: a supplier change, a new material, a revised process, a new test or a broader marketing campaign. The person updating the product should know which statements depend on the changed detail.

Preserve previous versions with dates. If a retailer asks about an older item, you should be able to identify the description that applied to it. A single overwritten page can erase distinctions that matter later.

Finish the first audit by selecting one owner for the approved wording and one location for the supporting register. Share the final description with the people who publish it elsewhere, including retailers or agencies where relevant. Ask them to retire the superseded version.

Your next step is to audit one product description this week. Pick a product with a manageable history, separate its factual statements and follow each one back to a record. The exercise will show where your story is well supported, where it needs a more careful sentence and where the team needs better information before publishing.