A shopper likes the photo of a shirt but can't tell whether it will fit, so they close the tab right there. Product page design means arranging information and choices so the customer can decide without guessing. A good page answers plainly: will this work for me, what will it cost in the end, when will it arrive, and what are the terms if I send it back?
What questions should product page design answer for the buyer?
Short answer: four groups of questions. Fit, final cost, availability and the risk of buying. In product page design, leaving any one of them unanswered delays the purchase or stops it altogether.
Say you're looking at a cotton shirt in an online store. The photos are professional, and the lighting and the model's pose are flawless. But there's no size chart. You can't tell whether this brand's L matches other brands' L, and there isn't a single line about exchanges. This page isn't short on decoration. Its problem is ambiguity at the moment of decision.
That's why I define product page design this way: organizing information and selection controls in service of one buying decision. A selection control is any tool the shopper uses to pick an option, like color and size buttons. This is different from the feature list of the whole store. Search, filters, the cart and payment methods belong to the site as a whole. You'll find how to prioritize those in our checklist for choosing and prioritizing online store features.
Question group | Example buyer question | Where the page answers it |
|---|---|---|
Fit | Will it fit me? Does it work with my phone? | Title, photos, spec summary, size guide |
Final cost | How much is it with shipping? | Next to the price, near the buy button |
Availability | Is it in stock? When will I get it? | Below the color and size selectors |
Purchase risk | What if it doesn't fit or arrives faulty? | Return terms summary next to the buy button |
The priority rule is simple: information without which a choice is impossible sits above supplementary details. Still, no single order works for every product. For a shirt, the size question comes up early. For a charger, it's compatibility with the device.
What information should an online store product page include?
The minimum for product page design in a store looks like this: an exact title, clear photos, the specs that affect the choice, and a price with its currency. Color or size options, stock for each option, delivery time and cost, return terms and a clear buy button belong on the same list. Add credible reviews and answers to common questions too, because they clear up whatever doubts remain.
Not all of these product page features carry the same weight, though. Essential purchase information is anything whose absence makes buying impossible or risky. Customer reviews are supplementary. They're valuable, but not having them yet shouldn't hold back the launch of a new product.
To gather the essential information for a product page, I suggest a four-column table. Each row is a buyer question, and next to it go three things: the answer, who supplies it, and where on the page it appears.
Buyer question | Answer | Who supplies it | Where it appears |
|---|---|---|---|
What's the fabric? | Cotton with a little stretch fiber | Purchasing team or supplier | Spec summary |
Will it work with my laptop? | Charging standards and compatible devices | Technical specialist | Next to model selection |
When will it arrive? | Estimate based on city and shipping method | Warehouse and shipping | Below the option selectors |
What if it doesn't fit? | Exchange terms under the store's policy | Support | Next to the buy button |
The hidden benefit of this table is that it shows which answers have no owner. If nobody's name sits next to “Will it work with my laptop?”, that question eventually lands on support, and only after the purchase. A lot of product page design problems start right here, not in the graphics. If you haven't settled the structure of the whole store yet, our guide to ecommerce website design and choosing well before you commission it is a better place to start. Here we'll stay with the product page itself.
How should the title, images and specs fit together?
In product page design, the title, images and specs have to say the same thing, about the same product and the same option the shopper has picked. The title states exactly what the item is. The photos and specs show it and back it up.
A good title has three parts: product type, model and the deciding feature. For example, “Men's long-sleeve cotton shirt, Arman model, button-down collar” or “65W wall charger with two USB-C ports.” Words like “amazing” and “best-seller” can't stand in for an exact name. On top of that, they make the product harder to find in search.
Each photo should answer one specific question:
Hypothetical shirt: front and back views, a close-up of the fabric weave, and a flat-lay shot with real measurements such as chest width and length.
Hypothetical charger: a close-up of the ports, a shot that shows its size next to a familiar object, what's in the box, and a list of compatible devices or standards.
The photos also need to stay in sync with the selected option. If the shopper picks navy and the gallery still shows light blue, they may believe they've ordered the light blue one. No photo of the other color? At least add a caption saying which color is shown.
Split the specs in two: a summary of three to five decisive features next to the price and buy button, and the full table further down. Technical products come with a common trap here. Rated wattage alone doesn't prove compatibility. A charger that doesn't support your device's fast-charging standard may charge it slowly despite its high wattage.
Take image alt text seriously as well. In a few words, it says what useful thing the photo shows. A screen reader, the software that reads a page aloud, announces this text to blind users. “Close-up of two USB-C ports” is useful; repeating the product name isn't. And never publish the spec table only as an image, because neither screen readers nor search engines can read it.
How should price and color or size options be displayed?
The shopper should understand the price without doing any math, and every color or size choice should immediately update the price, photo and stock. State the currency explicitly. In markets where two units are in everyday use, like toman and rial in Iran, people still mix them up. Make the unit of sale clear too: one item, a pair or a pack of three?
If the price depends on the option, show a price range. But once the shopper picks an option, the range should give way to that option's exact price.
For color, don't rely on a swatch alone. Someone with color vision deficiency can't tell “olive” from “khaki” by a small dot. A phone in bright sunlight creates the same problem. So write the color name next to the swatch, and mark the selected state with something other than color, like a bold border or a check mark.
The size guide belongs next to the size selector, not on a separate page or in a footnote, because that's exactly when the shopper needs it. In the guide, keep three things apart:
Body measurements: the shopper's own chest, waist or hips.
Garment measurements: the chest width or shirt length you measured flat on a table.
How to measure: where to place the tape and how snug to pull it.
A tidy look is useless without consistency, though. This part of product page design is more about logic than graphics. Every time an option changes, the price, photo, stock and preparation time must change together. Until the new data arrives, temporarily disable the buy button or show a loading state. Otherwise the shopper reaches the cart carrying the previous option's price and gets an unpleasant surprise there.
A product page's job isn't to persuade. It's to remove the doubts that are holding the purchase back.
Error messages are part of product page design too. If the shopper taps the button without choosing a size, show the message next to the size control, not at the top of the page. Review default selections as well; if the system pre-selects a size, some people will buy it without noticing. And a struck-through price that was never the real price destroys trust.
Where should stock, delivery time and return terms go?
In product page design, a summary of stock, preparation time and the main return condition belongs next to the buy button. The details can live in a section that opens with a tap. But at the moment of decision, the shopper shouldn't have to scroll to the bottom of the page to find out whether they can send it back. For the hypothetical shirt, the summary could look like this:
In stock in navy, size L
Leaves the warehouse: tomorrow; arrival depends on your city
Size exchange with tags intact (see full terms)
Careful, though: dispatch time isn't delivery time. “Ships tomorrow” means the parcel leaves the warehouse tomorrow, not that it reaches a customer in another city tomorrow. Tie the delivery estimate to the city, the shipping method and the time the order is placed, and say so explicitly.
If the shipping cost can't be known without the destination, don't hide it. Say the cost will be calculated once the address is entered, or put a simple city selector next to the price. Either approach is fine. But “Shipping: 0” should never appear when the real cost isn't zero.
Return terms should fit the type of product. For clothing, tag condition and the limits on size exchanges matter, for instance that an exchange is only possible if the other size is in stock. For technical products, separate three things: change of mind, faults in the first few days, and warranty service. Take the wording for each from the store's actual policy, not from a ready-made template.
On the technical side, this is where product page design connects to the inventory system. Re-check stock at the moment an item is added to the cart. The number on the page is really a snapshot from a few moments earlier, and it doesn't reserve the item for anyone. If a product sells out between viewing and buying, show a clear message with an alternative, not a vague error at the payment step.
How should customer reviews and Q&A be structured?
Every review should carry a date and show which variant the reviewer bought, meaning which color and size. What use is “runs small” to the next shopper if they can't tell which size the reviewer picked? Keep the Q&A section separate from reviews. And only show a “verified purchase” label when there's a real order behind it in the system.
A clothing size question and a charger compatibility question, for example, are different in kind. Other buyers' experience can answer the first; the second needs technical knowledge. So separate support replies from user reviews with a label like “Store answer,” so the shopper knows which reply to rely on.
Don't hide relevant critical reviews. A page with nothing but five-star ratings usually raises more suspicion than trust. A way to report inappropriate content and a clear removal policy keep the review section clean. And don't fabricate reviews for a new product; it's unethical, and sooner or later it gets found out.
Don't throw away repeated questions. For product page design, they're the most precise signal of weak spots. If several people have asked “Does it come with a cable?”, the answer isn't in the right place and needs to move into the main specs. An important answer shouldn't get buried under dozens of reviews.
What about a product with no reviews yet? An honest empty state works best: “No reviews yet. Got a question? Ask us.” That beats a row of empty stars or hiding the whole section.
How should the buy button and key information be checked on mobile?
The best approach is a simple one: before any visual work, sketch a mobile wireframe for a real product and walk through the buying path on it. A wireframe is a bare layout that only shows where information and controls go, without colors, fonts or final images.
The first thing I usually do at this stage of product page design is sketch two hypothetical examples side by side, one for the shirt and one for the charger. Seeing them together quickly shows that no single order fits every product. The table below gives the suggested order from the top of the page down, along with the question each area has to answer.
Area (from top) | Hypothetical shirt | Hypothetical charger |
|---|---|---|
1 | Image and fabric: “What does it look and feel like?” | Model and ports: “Which charger is this, exactly?” |
2 | Price: “How much is it?” | Compatibility and power: “Will it work with my device?” |
3 | Size and size guide: “Which size fits me?” | Price: “How much is it?” |
4 | Exchange terms: “What if it doesn't fit?” | What's included: “Do I need to buy a cable separately?” |
5 | Buy button: “Did my choice register correctly?” | Buy button: “Did my choice register correctly?” |
The different order in the two columns is deliberate. For the charger, the price means nothing until compatibility is clear. For the shirt, price filters shoppers earlier, and size is the next question.
A sticky button, one that stays fixed at the bottom of the screen as you scroll, is optional. If you use one, show the price and the selected option on it, like “Add to cart – Navy, L.” And make sure it doesn't cover the size guide, error messages or the content at the end of the page.
To evaluate product page design on mobile, test these criteria one at a time:
Color and size can be chosen without relying on color perception.
The options and the buy button can be reached and activated with a keyboard too; some users navigate with a keyboard or assistive tools.
Text is readable without zooming in.
Touch targets, the areas a finger has to hit, are large enough and far enough from neighboring targets.
After adding to cart, the shopper gets clear feedback that it worked.
Don't limit testing to a new phone on fast internet; check the page on a small phone with a slow connection as well. The details behind these criteria are in the Web Content Accessibility Guidelines quick reference, which is worth reading once. On the other hand, you don't have to cram everything into the first screen. It's enough for the shopper to understand what the product is and where the rest of the answers can be found.
What should you do with out-of-stock or discontinued products?
First, work out which situation you're in: one option has sold out, the whole product is temporarily unavailable, or it's been discontinued for good. Each one needs a different response. Yet in product page design, these states are usually the last thing the team gets around to.
For example, if only size XL has sold out, don't mark the whole page as out of stock. Disable that one size with an “Out of stock” label and keep the other sizes available to buy.
When the whole product is out of stock, a well-designed product page does three things:
It states the situation clearly and accurately, right where the buy button would be.
It keeps the specs and photos, because the shopper may still need them for comparison.
It suggests a relevant alternative, like a model with the same compatibility or the same fabric.
One of the worst cases is the exact opposite: an “Add to cart” button that looks active but throws an error in the cart.
Only add a “Notify me when it's back” button if the system really sends the message and the user has opted in. And don't guess at restock dates; a promise that doesn't come true is worse than silence.
Permanent discontinuation is a different story. Start by asking whether the page is still useful to anyone. People who already own the product may come looking for specs, the manual or warranty terms. Even when the sales are over, product page design isn't. And temporary unavailability is never a reason to take a page's URL down.
A permanent redirect (301) automatically sends visitors and search engines to a new URL. It's only the right move when the replacement is genuinely equivalent, like a newer version of the same charger with the same ports. If you've removed a product with no replacement, the page should respond that it doesn't exist, for example with a 404 or 410 status. Sending everyone to the homepage confuses users, and search engines usually treat it as a missing page anyway.
How should you evaluate product page improvements?
Evaluating product page design happens in two stages: before development, usability testing on a prototype; after launch, data on how shoppers behave. Neither replaces the other, because each shows something the other can't see.
Usability testing means watching someone carry out a real task without any guidance from you. For this, build a clickable prototype for both products, a version that only clicks through and hasn't been coded yet. Write the tasks precisely and with concrete data, because “buy a shirt” teaches you almost nothing:
Clothing: “Your chest measures 102 cm. Choose the right size and tell us what you'd do if it doesn't fit.”
Technical product: “Your laptop is the model written on this card. Will this charger work with it? What's in the box?”
In this test, success means the right choice plus a correct explanation of the purchase terms, not just tapping the button. Note every pause, every wrong choice and every request for help. This logging template, shown with two hypothetical rows, makes the job easier:
Task | Result | Point of confusion | Severity | Suggested fix |
|---|---|---|---|---|
Choosing a size with a 102 cm chest | Picked M; the right size was L | The chart only showed garment width | High; leads to a wrong purchase | A separate column for body measurements |
Finding what comes with the charger | Found it, after a long pause | The list was at the end of the spec table | Medium | Move the list into the summary next to the price |
A participant who puts the wrong size in the cart hasn't failed. The page has.
Still, a handful of observation sessions is no basis for statistical claims. Call your findings “observed problems,” not “X percent of users.” This kind of test is for finding ambiguity, not measuring it.
After launch, it's the data's turn. An event is the record of one specific user action, like choosing a size or tapping Add to cart. Follow the path from product view to variant selection, add to cart and completed order to see where shoppers drop off.
Conversion rate is the share of visits that reach the target action, such as a completed order. When you compare before and after, account for stock status, device type and traffic source. A rise in add-to-cart on its own isn't success; the problem may simply have moved one step further along. Suppose add-to-cart goes up but orders don't. Maybe the shipping cost is now catching people off guard in the cart.
Also keep in mind that the product page is just one stop on the buying journey. To see where shoppers came from and where they stopped after the page, read How to increase conversion rate with customer journey analysis.
Where should you start improving your product page?
Start with two pages, not the whole store: one high-traffic product and one with complex options. Before touching the visuals, write down a list of ambiguities for each. Take that list seriously, because product page optimization without it usually ends with someone changing the button color.
Then work in this order:
Remove the purchase blockers first: a price that doesn't match the selected option, a selector that doesn't work properly, a cost that shows up too late.
Use frequent support questions as input for prioritizing; every repeated question is an answer the page failed to give.
Write a small brief, a short written description of the work, that sets out the goal, the data needed, who owns the content, who owns the implementation, and the acceptance criteria.
Make visual improvements after all of that, in small rounds.
An acceptance criterion is a sentence that tells you whether the work is done. For example: “After the size changes, the page shows the price and stock for that option, and the cart records that same option.” Designers, developers and testers all read a sentence like that the same way.
In practice, the cycle has three steps: observe, make a limited fix, test again. If you change every element at once, you can no longer tell which change produced the result. That's why patience is the most overlooked part of product page design.
If you don't have an in-house team for this cycle, or the problem goes back to the structure of the whole store, Niasa's ecommerce website design team can work alongside you. My suggestion for starting the conversation is simple: bring one of your product pages, together with a list of the questions it still leaves unanswered. That list is the agenda for the first meeting.
اگر برای تعیین اولویت اصلاحها به همراهی نیاز دارید، نشانی یک صفحه محصول و مهمترین ابهام خریدارانش را برای گفتوگو با نیاسا آماده کنید.
Frequently asked
4Should every product spec be at the top of the page?
No. Show first the information without which a choice is impossible. Supplementary specs can sit lower down, as long as the section heading and the way to reach it are clear.
How many photos does a product page need?
A fixed number for every product doesn't help. Each photo should answer a new question about appearance, size, detail or what's included. Several near-identical shots can't replace one essential view.
Is a sticky buy button on mobile essential?
On long pages it can make buying easier to reach, but it isn't always needed. If it covers the size selector or an error message, change where it sits or how it appears.
Does better product page design guarantee more sales?
No. Price, demand, stock and the quality of incoming traffic all affect purchases. Clear design reduces ambiguity and selection mistakes, and its effect should be checked across the whole ordering path.





