What product content does an ecommerce website need?

Define structured fields before writing pages

Start with product types and the information customers need to distinguish one item from another. Common fields include product name, summary, description, category, specifications, materials, dimensions, compatibility, care, variants, identifiers, price, availability, delivery, returns, media, and related products.

Do not force every product into one undifferentiated description field. Structured data can support filters, comparison, accessibility, feeds, search, translations, consistent layouts, and updates across channels. Record which system owns each field and which values are required.

Write for the questions that block a purchase

Explain what the product is, who it is for, what problem it solves, what is included, how options differ, and what the customer should expect after ordering. Put critical constraints near the choice they affect rather than hiding them in a general policy page.

Specifications should use consistent names, units, and order. Claims need evidence and approval. Avoid repeating manufacturer language that does not help a specific buyer decide. Collection cards, search results, comparison views, and product pages need different amounts of the same trusted information.

Plan an image set around evaluation, not decoration

List the views needed for each product type: clear primary image, alternate angles, scale, detail, packaging, variants, context of use, and any movement or assembly that requires video. Define dimensions, crop behavior, backgrounds, file naming, alternatives, and how unavailable media will be handled.

Match media to truthful variants so a selection does not imply a finish or feature the customer will not receive. Design galleries for touch, keyboard, zoom, captions, and different image proportions. Product media production belongs on the critical path, not after the template is approved.

Include the information that completes the order

Customers need accurate availability, lead times, delivery restrictions, taxes or duties where relevant, payment options, returns, warranty, support, and order communication. The source may be a platform, inventory system, ERP, manual process, or combination; the website must make the resulting promise clear.

Map variant and stock rules carefully. Decide what happens when an option is unavailable, backordered, made to order, or sold only in certain markets. The guide to ecommerce website requirements places product content within the wider buying and service journey.

Audit content before designing the system

• Types: group products that share fields and customer decisions.
• Fields: define names, formats, required values, and source systems.
• Coverage: measure missing, inconsistent, and outdated information.
• Media: specify shot lists, variants, crops, alternatives, and owners.
• Workflow: assign creation, approval, import, updates, and quality control.
• Sample: prepare simple, typical, and difficult products for design testing.