search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Sector content and pathways

    Retail: a catalogue that helps customers choose

    A useful catalog is not measured by the number of published references. It must make it possible to distinguish the products, to understand the variants and to check the methods of order or withdrawal without manufacturing an availability that the merchant does not control.

    These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.

    All sectoral files
    Shelves of products in a small shop
    AI-generated illustration

    Explore all 28 review cases — Stock changes during checkout

    Standardize product information

    Define fields by family: dimensions, material, compatibility, delivered contents and references. Keep units and identifiers. An unknown characteristic must remain to be verified; It should not be deduced from a photo or copied from another variant. Distinguish vendor data and trade-confirmed information.

    Manage variants and availability

    Explain the choice of size, color or packaging before adding to the basket. Define what it means available, on order or on hold. If the stock is not synchronized, announce the confirmation procedure. An amount of demonstration should never be presented as a real stock.

    Make the comparison relevant

    Compare criteria that change a decision: use, dimensions, compatibility or maintenance. Do not repeat the same slogans in all files. The filters must follow the available fields and distinguish between absence of information and absence of a characteristic. Document the necessary accessories without suggesting that they are included.

    Test difficult order cases

    Check an unavailable variant, a change in quantity, a product removed and a payment interruption as provided by the service provider. The summary should remain consistent with the choices. Distinguish confirmation of request, payment authorization and order accepted according to the actual operation of the service.

    Organize the reference cycle

    Assign the validation of descriptions, prices and availability. Decide how to process a stopped product: relevant alternative, unavailability information or withdrawal. Keep track of feature changes. Control translations when a variant or unit changes, rather than only translating the title.

    Information to gather before writing

    • Stable identifiers and variants
    • Units and confirmed characteristics
    • explicit availability statuses
    • Order or withdrawal conditions
    • Photos of the reference presented

    For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.

    A case for preparing the content

    Separate sale packs from stock units

    Fictional case: one pack contains 3 units. The snapshot shows 8 units available; the basket requests 3 packs.

    Fictional teaching exercise: these texts and values describe no real business, course or product.

    Path to check

    1. Read the pack
    2. Convert to units
    3. Compare with stock
    4. Explain the result

    Compare the wording

    Avoid in this example

    3 packs available immediately.

    More precise wording

    With 8 units, only 2 complete packs of 3 can be assembled at this snapshot.

    Scroll the table horizontally if needed. With a keyboard, focus the table and use the arrow keys.

    Three checks based on the supplied information
    Starting informationWhat it establishesWhat still needs checking
    1 pack = 3 unitsSales and stock units differDoes the basket state the pack contents?
    8 units in stock2 complete packs, with 2 units leftIs the stock figure still current?
    3 packs requested9 units neededDoes the journey explain the one-unit shortfall?

    The snapshot reserves no stock: confirm availability during actual validation.

    See complete packs and the remainder

    Eight units make two complete packs of three, leaving two units. The remainder is not a third pack. A request for three packs needs nine units, so this snapshot is one unit short.

    State the pack contents and the unit used for the quantity field on the product page. Reflect packaging changes in the basket and availability messages. The diagram explains quantities; it neither reserves stock nor confirms an order.

    This workshop uses its own fictional snapshot. Do not combine its figures with those of another example on the page.

    Blocks represent individual units: two groups of three, then two separate units.

    The diagram values are listed below with their labels.

    Find the values behind the diagram
    MeasureValue
    Available units8
    Units per pack3
    Complete packs2
    Remaining units2
    Requested packs3
    Required units9
    Missing units1
    A person preparing mug gift packs in a small shop’s stockroom.

    Keep the information consistent

    When to review
    Pack contents or stock changes
    Who validates
    The catalogue owner aligns units, packs and basket.
    Journey to replay
    Try requesting 2 packs, then 3 packs.

    Prepare a consistent catalogue →

    Understand an indicator

    Separate created orders from validated payments

    Fictional teaching example: these figures are neither market statistics nor measured client results. They illustrate a calculation and its limits.

    A fictional shop creates 40 distinct orders during a defined period. Payment is confirmed for 30 at the reporting time. Others are pending, abandoned or declined.

    The proportion in this example

    75%30 / 40 × 100

    Orders with validated payment at reporting time
    30
    Distinct orders created
    40

    What this figure means

    75% of created orders have validated payment. This is not a visitor conversion rate: visits and baskets without an order are not in the denominator.

    Define the count before comparing

    Count each order ID once. Define the payment status used, then distinguish refunds, dispatch and delivery.

    The 40 orders could comprise 30 validated payments, 4 pending payments, 3 refusals and 3 journeys abandoned after order creation. Two subsequent refunds among those 30 payments do not change their initial validation; record them in a separate refund measure.

    A practical check on the website

    Test return journeys after accepted, declined and interrupted payments. A page refresh or repeated notification must not create a second order.

    What the calculation cannot establish

    Validated payment proves neither delivery nor retained revenue after refunds. Keep the reporting cut-off date.

    Try with your own counts

    Use two counts from the same group and period, with the same unit. The selected cases must belong to the reference total. Leave unknown values blank.

    Whole counts only, up to one billion. Formula: selected cases ÷ reference total × 100. The displayed percentage is rounded to one decimal place.

    These values stay in this page without being sent or saved. The calculation provides no benchmark, prediction or quality score.

    To document real data, keep its origin, scope and quality limitations clear. Method reference : W3C · Data on the Web Best Practices (in English) · Consulted on . This source does not supply the fictional figures above.

    A content model to maintain

    Comparison starts with an identifiable variant and characteristics expressed in consistent units. For the exercise, use one item sold in two sizes and two pack configurations. Selection should remain understandable from filtering to the basket; a common photograph or shortened name cannot establish what will be ordered.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    A content model to maintain
    InformationContent to retainConsistency check
    Variant referenceAssociate a durable identifier with the combination actually sold: size, colour or pack configuration. Retain it when correcting display wording.Select two similar variants, return to the record and change quantity. Check that basket and summary still identify the same combination.
    Comparable valuesRetain value, unit and scope: product or package dimensions, quantity per pack and included accessories. Define an explicit unknown value.Filter two records using different units and inspect a missing value. Missing data should become neither zero nor an artificial equivalence between products.
    OfferAmount, currency, availability state and confirmed conditions.The displayed amount belongs to the selected variant.
    MediaProduct or variant photo, rights and useful alternative text.A generic image does not imply that an accessory is included.
    Shop collectionExplain the collection location, required confirmation and handling of unavailable items.Try a basket with an unavailable item: no message should imply that collection is confirmed.

    A focused next step

    Choose a fictional item with two pack configurations and correct a dimension on the working copy. Check filters, comparison, record and basket without making a real purchase. If order tracking still uses an earlier reference, preserve its mapping; improving a commercial name should not make history unintelligible.

    Schema.org: Product — a reference for describing information, not evidence of a particular business or a guarantee of search features. · Source consulted

    A review case to reproduce

    Stock changes during checkout

    Situation to examine
    A product is available on its page but cannot be supplied when the order is completed. Visitors cannot tell what was retained.
    Proposed check
    Change availability of a demonstration product between viewing and submission. Check the message, basket and alternative selection without losing other items. Identify the stock source and update timing.
    Evidence to retain
    Keep before and after states and the test order result. Confirmation only describes what was actually accepted.
    Fictional finding example
    Demonstration product: blue/M = 2 units; blue/L = 0. The product total is 2, but size L remains purchasable in the form.
    Interpret this outcome
    Validate the selected variant at submission, not just the product total. Stock for M must not authorise an order for L.

    Method reference : W3C WAI — User Notification · Source consulted

    Learning scenario

    A scenario for planning the user journey

    Preparation exercise: A visitor finds a product, compares two variants and then wants to know if he can buy, withdraw or request availability. Use test references and indicate that they are educational. Separate an informative catalog from a shop that really cashes in. Test an exhausted variant and a stopped product. The course must explain what is known, which requires confirmation and when the customer engages.

    Documents and information to prepare

    • References and variants with stable identifiers
    • Characteristics and dimensions from a validated source
    • Origin and frequency of stock update
    • Prices and conditions of withdrawal or delivery
    • authorized visuals corresponding to the correct reference

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. The change of variant updates the associated information.
    2. An unsynchronized stock is presented as to be confirmed.
    3. A stopped reference offers an explanation or a linked product.
    4. Units and dimensions remain consistent between variants.
    5. The method of withdrawal or delivery is announced before commitment.
    6. An atmospheric photo differs from the photo of the product sold.

    Understand pre-launch checks

    Ongoing management and handover

    Prepare a rule for processing deleted references: keep an information sheet, propose a relevant replacement or remove the page according to its usefulness. Keep one responsible for the stock and another for the descriptions if the systems differ. When importing, check identifiers, units, variants and photos before publication. A translation should not modify a technical reference.

    Organize site maintenance

    Compare two approaches

    Choose a promise the shop can fulfil: displaying products, helping customers plan a visit, reserving an item or accepting an order. These workflows require different data and responsibilities.

    Catalogue with an availability contact request

    When to choose it
    Suitable when stock changes quickly or is not connected to the website. Visitors review the specifications, then ask whether an item is available.
    What to plan for
    Explain that an contact request does not automatically reserve the product. Include a product reference and a response for unavailable variants.

    Confirmed order or collection

    When to choose it
    Useful when variants, stock and handover arrangements can be checked before confirmation. Display the information for the exact item selected.
    What to plan for
    Organise stock updates and interrupted orders. Test stockouts, variant changes and missed collections against the shop’s approved rules.

    A risk to anticipate

    A detailed product page with incorrect stock makes the workflow unreliable. Identify the authoritative data source and avoid conflicting availability across pages.

    How to decide

    Start with a product family containing an unavailable variant. Check that the team can handle contact requests without ambiguous data re-entry.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare products, variants, images and genuinely needed ordering functions. Price catalogue import, stock connections and simple product presentation separately.
    Recurring operation
    Distinguish hosting, extensions and catalogue upkeep. Document variable payment or volume charges separately; the calculator predicts neither sales nor service usage.
    Exit and handover
    Check export of references, variants, authorised media and relevant orders. Plan identifier mapping, redirects and replacement functions; a raw CSV is not a migrated shop.

    Compare the costs of three web solutions

    Frequently asked questions

    What should be shown when a product specification is unknown?

    Identify the missing information and how to confirm it. Do not turn an unknown dimension into zero or missing data into an absent feature. Ensure filters and comparisons preserve this distinction for the chosen product and variant.

    How should a required accessory that is not included be presented?

    Separate supplied items from accessories needed for the described use. Publish compatible references only after validation and place the information near product selection. Images, comparison and the summary should preserve this distinction even when the accessory has a separate product page.

    How does an alternative differ from an equivalent replacement?

    Compare criteria relevant to use, such as dimensions, interfaces, supplied items or another verified constraint. Present an alternative with its differences. Claim equivalence only within the confirmed scope; a visually similar product may not suit the intended installation.

    Must a local shop offer every product online?

    A useful selection can be better when the full catalogue cannot be maintained. Explain what is included and how to check other products. Avoid promising completeness or immediate availability unless those claims are verified.

    Further reading

    Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.

    Browse other resources