Selling on Amazon: The More Features You Stack, the Worse Customer Reviews May Get — Smart Watches Category Analysis

Many sellers have a misconception when defining a product: they think the more features, the better, and that they need more features than competitors to attract customers. They stuff seven or eight feature words into the product title, list a pile of selling points in every bullet point, and wish the product could integrate a hundred features. People generally believe more features means better value for money, and that users will see it as worth it and place an order.

But when you scroll through the review section, you find an interesting phenomenon: the more features a product has, the more polarized its reviews become. Some say it is fully featured and a great value; others say it cannot even do a basic function well. On the same listing, positive and negative reviews seem to be talking about two completely different products, and the cause is often exactly this piling on of features.

I recently did product research in the smart watch category, and this feeling was especially strong. If you scroll through most listings in this category, the product titles look almost the same: 1.83-inch HD screen, Bluetooth calling, IP68 waterproofing, 120 sports modes, heart rate monitoring, blood oxygen monitoring, sleep tracking, message alerts, music control, camera remote control. Count them, and one product can list more than a dozen features. Everyone is piling on features, most products have nearly the same feature list, and after scrolling three pages, users feel every watch is the same.

But then look at the reviews for these products, and the polarization is severe. The top item in positive reviews is 'cheap and has many features,' accounting for 28%. These users buy exactly on this logic — spend thirty or forty dollars, and the watch can make calls, measure heart rate, and record exercise; that is a great deal. They have no requirements for feature accuracy; as long as it works, they are satisfied. One person wrote, 'this watch does everything at this price, can't complain,' meaning at this price, what more could you ask for.

But what about the negative reviews? The top complaint is short battery life, at 22%. Second is inaccurate data, at 20%. Third is short device lifespan, at 16%. Fourth is Bluetooth disconnection, at 15%.

If you think carefully, you will see that these negative reviews complain about exactly the features that were piled on. Bluetooth calling is a selling point, right? But 15% of negative reviews curse Bluetooth disconnection — the call goes silent while you are walking. Heart rate and blood oxygen are selling points, right? But 20% of negative reviews complain that the data is inaccurate, a notch worse than a fitness band. 120 sports modes are a selling point, right? But more features mean a heavier chip load, and running all sensors drains power, so 22% of negative reviews curse that the battery cannot last even one day.

This is the first problem with feature stacking: every feature you add is one more part that can go wrong.

If a watch only tells time and records steps, it has no Bluetooth module, so it will not disconnect; it has no optical heart rate sensor, so the data will not drift; and with a low chip load, the battery can last a week. But when you add Bluetooth calling, add heart rate and blood oxygen, add GPS, and add music playback, every module becomes a potential source of negative reviews.

Users will not write you a positive review just because you have 120 sports modes, but they will give you a one-star rating directly because Bluetooth disconnected once or the heart rate was wrong once.

The second problem is that the more features there are, the less cost and effort each feature gets. For a thirty- or forty-dollar watch, the BOM cost is what it is. You need to make an HD screen, add GPS, add Bluetooth calling, add heart rate and blood oxygen, and add waterproofing; every feature costs money. But while chasing a lower cost, the end result of feature stacking is that every feature only reaches 60 points — the screen works but is not clear enough, Bluetooth connects but is unstable, heart rate can be measured but the error is large. Users spend money and expect these features to at least work, but each one is slightly off, so negative reviews come naturally.

When you look at products with high ratings, they are often not the ones with the most features. Instead, the feature-focused ones — focused on long battery life, comfortable wear, or simple and easy use — have more stable ratings. Because they concentrate cost and effort on a few core features and get them above 80 points, users are not annoyed when using them.

The third problem, and the most interesting one: the more features there are, the more divided the user base and the more different the expectations. If a product only has exercise tracking, the people who buy it come for exercise, and their expectations are very uniform.

But when your watch can make calls, measure blood oxygen, act as a remote control, and store music, the people who buy it come from all walks of life. Some buy it just to check their pace when running; they do not care if you add Bluetooth calling, and they can tolerate a shorter battery. Some buy it to answer calls at work; for them, a Bluetooth disconnection is a disaster. Some buy it to monitor sleep; if the data is inaccurate, they feel cheated. Some buy it for elderly people, who want simple, large text; you stuff in 120 sports modes that they will never use, and they just find the operation complicated.

The same product faces four or five completely different user groups, and each group defines 'easy to use' differently. You meet the needs of exercise users, and users who bought it for calls are unhappy; you optimize heart rate monitoring, and users who bought it for calls feel the battery life is short again. In the end, positive and negative reviews are severely polarized, and the rating is very hard to raise.

This is why, when features are piled on to a certain point, reviews become divided — you think more features will please everyone, but in fact you please no one fully.

So should products stop having features? Of course not. Doing core features well is the foundation of product definition; the question is what logic you use to decide on features.

Many sellers use this logic for features: whatever competitors have, I make; if a competitor adds 120 modes, I add 120 modes; if a competitor adds blood oxygen, I add blood oxygen. This is benchmarking-style feature stacking, not starting from user needs. When you add these features, you do not think about whether your users will actually use them, whether they need them, or whether they are willing to sacrifice other experiences for them.

The right approach is to first figure out who your core users are and which two or three features they care about most when buying this product, then make those two or three the best; for other features, cut them if you can and simplify them if you can.

For example, if you make a running watch, the core users are runners, and what they care about most is whether GPS is accurate, whether battery life is long enough, and whether it is comfortable to wear. So take these three things to the extreme; for a feature like Bluetooth calling, a basic version is enough, do not spend too much cost on it, and you can even leave it out. Your users will not refuse to buy because you do not have a camera remote, but they will return it because GPS drifts.

For another example, if you make a health watch for elderly people, the core users are the elderly and their children, and what they care about most is whether heart rate and blood oxygen are accurate, whether a fall can trigger an alarm, and whether operation is simple. 120 sports modes are just noise to them; it would be better to make the font larger, make charging simpler, and make the strap softer.

The same logic applies at the Amazon listing level. Many sellers write bullet points where the first bullet lists five features and the second lists five features, a dense pile. Users cannot remember any of it after reading, and they do not know what is actually good about your product. It is better to focus.

Use the first bullet to talk about your most core selling point and explain it thoroughly. For example, if you focus on long battery life, write that one charge lasts 14 days, how you optimized battery life, and in what scenarios users do not need to charge every day. Use the second bullet for the second core selling point, such as comfortable wear: what material you use, and how it does not shift or dig in when you run. For other features, just mention them briefly; do not let them take over.

When users buy something, the decision cost is very high. Give them twenty feature points, and they will not remember one. Give them three points that truly move them, and instead they remember them and place an order.

The same logic applies to images and A+ Content. Do not make one image that lists many feature icons; it looks comprehensive but conveys nothing. Make several images, each explaining one core scenario thoroughly. One image shows GPS recording pace while running, one shows how much battery is left after wearing the watch for a day, and one shows how comfortable the watch feels against the wrist. When users finish looking, they know who this watch is made for and what problem it solves; that is better than looking at a pile of icons.

The smart watch category is stuck at this stage right now. Everyone is piling on features — a hundred-plus modes, Bluetooth calling, blood oxygen and heart rate — and in the end all products look exactly the same. Users do not know whom to buy from and can only compare prices.

Actually, whoever understands this first, dares to cut some features, and makes the core experience thorough will be the one who stands out.

Users do not need a watch that can do everything but does nothing well; users need a watch that is good enough at the one point they care about most.

Making a product is like being a person: people who want everything often do nothing well. If you stack too many features, there is a high chance each one is half-baked, users run into problems everywhere, and reviews naturally will not be good. It is better to focus on a few things and satisfy the people who truly need them; the rating will instead be stable.