Where should shipping, returns, and sizing information appear?
Give practical buying questions a consistent place on the product page without burying the product story under repeated policy text.
Product descriptions and buying information have different jobs. The description should help someone understand the product. Shipping, returns, sizing, care, and warranty details should remove practical uncertainty before the purchase.
Putting everything in one long description makes both jobs harder. The product story becomes difficult to scan, while recurring policies are copied into dozens of places that must be found again when something changes.
List the questions that delay a decision
Begin with questions customers ask before buying, not with every field the store could display. For many products, the first three are enough:
- When will it ship or arrive?
- Can it be returned or exchanged?
- Which size, material, or care method applies?
Put the most decision-critical answer first. A fashion store may lead with size and returns. A made-to-order store may lead with preparation time. The order should follow the customer’s uncertainty rather than an arbitrary policy list.
Give recurring answers a reusable source
Storewide shipping and return information should not need to be pasted into every product description. A reusable block gives the answer one maintained source and a consistent position on the page.
Reusable does not mean universal. A linen care guide does not belong on leather products, and one vendor’s warranty may not apply to another. Show each block by product type, tag, vendor, or another dependable catalog distinction when the answer is only true for part of the store.
Use the smallest truthful scope. Share an answer across the catalog when it is genuinely shared; narrow it when the product changes the policy or instruction.
Choose a format that matches the answer
A short return note may need one paragraph. A size guide may need a list or link. Technical products may need a manual. International storefronts may need the same information structure in several languages.
Accordions work well when they keep secondary information available without forcing every shopper to scroll through it. They become less useful when each collapsed section hides information that nearly everyone needs, or when the page contains so many headings that choosing one becomes another task.
Place practical answers near the buying controls
A shopper deciding between sizes should not have to leave the product page. Put practical answers close enough to the variant selector and add-to-cart control that they can resolve doubt without losing context.
Keep the styling quiet and consistent with the theme. Clear headings, readable contrast, restrained icons, and comfortable spacing matter more than making the component visually dominant.
Treat maintenance as part of the design
Before creating a block, decide who owns its wording and what event should cause it to change. Temporary notices should have an end date. Policy links should be checked when the policy changes. Translations should follow updates to the source content.
Start with the few answers that remove the most uncertainty. If three clear, reusable blocks solve the problem, stop there. The purpose is not to fill every available space—it is to make the next buying decision easier.