Motta Industries Blog

The customer did not order the wrong product deliberately. The photograph looked right, the description sounded reassuring, and the size seemed close enough. Only after opening the box did they discover that the fitting was different, the accessory was missing, or the attractive container could not hold the item they already owned.

A product page cannot prevent every return. Preferences change, parcels get damaged, and some products genuinely need trying. But a page can answer foreseeable questions before a purchase becomes an avoidable surprise. For a small retailer, that means treating product information as part of fulfillment rather than decorative copy added after the photographs.

Begin with the question behind the return

Read return reasons and pre-purchase questions together. A label such as unsuitable does not reveal whether the customer misunderstood a measurement, expected another component, or simply changed their mind. Where appropriate, ask staff to categorize recurring misunderstandings without copying private customer details into a public content brief.

Separate information problems from other causes. If a parcel arrived broken, rewriting the product description will not repair the packaging process. If the customer expected a cable that was never included, the page may need a clearer contents statement. Assign each issue to the process capable of addressing it rather than making the website responsible for everything.

For a fictional garden shop, repeated questions about planters could reveal several different decisions: whether a nursery pot fits inside, whether water can drain, whether a saucer is included, and whether the surface underneath needs protection. A generic paragraph about brightening a room answers none of those practical questions.

Use Motta Industries’ ecommerce strategy service to connect recurring questions with the buying journey and available product records. The useful output is a prioritized information plan, not a longer description for every item regardless of what customers need to decide.

Distinguish the product from its packaging

A measurement is only useful when the buyer understands what was measured. The outer width of a planter is not necessarily its usable opening. A shipping carton is not the assembled product. A folded textile measurement is not its size when laid flat. Label the state and measurement direction instead of presenting an unexplained string of numbers.

The June 2022 GS1 Package and Product Measurement Standard distinguishes measurement contexts and provides conventions for communicating dimensions. It is a useful reference for consistent product data, not proof that any particular retailer’s measurements are accurate. Select the relevant approach for the item and verify the resulting record.

Suppose a fictional planter has an outside diameter of 180 millimeters and a usable circular opening of 150 millimeters. A rigid nursery pot measuring 160 millimeters across cannot pass through that opening merely because it is narrower than the planter’s outside dimension. The example illustrates why the customer’s intended use matters more than a single prominent size.

State units consistently and identify meaningful variation. If a handmade item varies within an approved range, explain that range using verified supplier or production information. Do not invent precision because the catalog template requires a number. If a measurement is uncertain, obtain it or remove the unsupported claim before inviting reliance on it.

Show what arrives, not only what looks attractive

A styled photograph can show a planter with flowers, a saucer, and a stand even when only the planter is sold. List the included components and identify important exclusions near the decision. Customers should not have to inspect a lifestyle image for clues about the actual contents of the box.

Use photographs for different information jobs. A general view establishes appearance; another view can show a connector, underside, closure, or scale. Where a feature is difficult to describe, a clear detail view may be more useful than another decorative angle. Ensure the pictured variant corresponds to the option selected.

Do not use an illustration as evidence of a real product’s condition, dimensions, or supplied accessories. Actual retail pages need accurate imagery and descriptions tied to the goods being offered, including any relevant differences between variants.

Plan those relationships through ecommerce development rather than relying on staff to remember every dependency. Selecting a finish or size may need to update photographs, dimensions, contents, price, and availability together. A page that changes the label but leaves another variant’s details visible can create a new misunderstanding.

Put limitations beside the claim they qualify

A headline such as suitable outdoors may require a meaningful explanation about exposure, maintenance, temperature, or other conditions. Avoid broad promotional language that the supporting information cannot substantiate. The right wording depends on the product and the evidence available, not on what sounds most persuasive in a sales banner.

The FTC’s March 2013 .com Disclosures guidance discusses clear, conspicuous disclosures and their proximity to the claims they qualify. It is staff guidance, not a complete legal opinion or safe harbor. Its practical relevance is straightforward: a qualification hidden elsewhere may not communicate what the shopper needs to understand.

Where possible, make the primary statement accurate without requiring a rescue paragraph. If a product has a specific compatibility boundary, state that boundary clearly. Do not expect a footer disclaimer to correct an overbroad claim beside the purchase button. Seek appropriate advice when safety, regulated claims, warranties, or legal obligations are involved.

Review the narrow screen as well as the desktop layout. A detail that appears adjacent to a claim in a large mockup may sit far away after the page stacks on a phone. The customer still needs the relevant qualification before making the decision, not after reaching an unrelated section or opening a separate policy page.

Make variant choices understandable

Color, finish, capacity, and fit may be independent choices, or one choice may restrict another. Name the options in language customers can understand and show the consequences of a selection. Do not force people to infer a variant from a tiny swatch whose meaning disappears without its color.

If two sizes have different fittings or accessories, keep the difference visible while the customer compares them. Where a combination is unavailable, explain the state rather than leaving a purchase button that fails later. A confusing selector can undo otherwise accurate product information by applying it to the wrong option.

WCAG 2.2 includes criteria relevant to labels, instructions, non-text content, and input errors. Those criteria provide a technical reference for evaluating the interface. Adding a label or alternative text alone does not establish complete accessibility or legal compliance; assess the actual task and relevant conditions.

For a store using WooCommerce, Motta’s WooCommerce design service can help organize the presentation and behavior of product options. The merchant remains responsible for approved product facts. A developer should not guess a missing specification or silently infer compatibility from a similar item.

Explain ownership after the purchase

Some surprises concern use rather than initial fit. Assembly requirements, care, consumables, replacement parts, and ordinary limitations may affect whether a product suits the buyer. Prioritize information that changes the purchase decision, then provide supporting instructions in a form customers can locate again after delivery.

Separate verified requirements from helpful suggestions. If installation requires a particular fitting, say so accurately. If a care tip is optional, do not present it as a warranty condition unless that is the approved policy. Keep supplier documentation, editorial advice, and contractual terms distinguishable so staff do not accidentally create new promises while simplifying the page.

Make return and support information findable without turning the description into a legal document. Explain the relevant route and point to approved terms where appropriate. Product-specific restrictions need appropriate review; this article does not prescribe a universal return period or tell merchants which exclusions are legally valid.

An honest page may help someone decide not to buy. That is not necessarily a content failure. A product that does not suit the customer’s situation can create more work after purchase than an informed decision to choose another item or ask a question first.

Build a repeatable product information record

For each product family, define the fields needed to support the decision. A planter and an electrical accessory will need different information. Keep a shared structure for common facts while allowing category-specific details. A single enormous template can bury the important distinctions just as easily as an empty description can omit them.

Record where important facts come from and who can approve changes. Supplier updates, a new production run, or a different included accessory should trigger review of the affected page. Reusing old copy without checking the current item can preserve an error long after the original photograph or specification has changed.

Pilot the record on a set of products with known questions. Ask someone unfamiliar with the catalog to explain what they believe is included, what the measurements describe, and which option suits an invented situation. Treat their interpretation as feedback, not proof that every future buyer will understand.

After release, watch the relevant questions and return explanations over a suitable period. Keep other influences in view, including product mix, seasonality, damage, and changed policies. Do not attribute every improvement to the page or announce a reduction in returns without a sound comparison and actual evidence.

A comparison can also expose missing information. Put two similar items beside each other and check whether the same important fields are available for both. If one page gives usable capacity while the other gives only package size, the customer cannot make a fair comparison even though each page contains several numbers.

Do not fill that gap by copying a competitor’s specifications or assuming that products with similar photographs share the same construction. Verify the item you sell. If the supplier cannot confirm a consequential detail, tell the responsible buyer or product manager what remains unresolved and decide whether the claim should be withheld.

Finally, make the route for a remaining question specific. An enquiry should identify the relevant product and selected option where appropriate, without forcing the customer to reconstruct the page in a message. Staff can then answer the actual uncertainty and feed a verified answer back into the product record. The contact route complements clear information; it should not become an excuse to omit it.

Sell a clearer expectation

The strongest product description is not necessarily the longest or most enthusiastic. It helps the right buyer understand the right item, its limits, and what will arrive. Give practical information the same care as the sales photograph, and keep it connected to the selected variant.

That is how product pages can become more useful before and after checkout. Start with the misunderstandings staff repeatedly resolve, verify the facts behind them, and make those answers part of the decision. The goal is a better-informed purchase, not a promise that no customer will ever send anything back.