How to Reply to Reviews in the Samsung Galaxy Store

Yes, you can reply to Samsung Galaxy Store reviews. Sign in to Samsung Seller Portal, open Assistance > Buyer Comments, find the review, and click Add Reply. Your response posts publicly under that user's comment. The catch worth knowing up front: you get exactly one reply per comment, and the reply is capped at 1,400 bytes, not 1,400 characters, which matters a lot if you're answering in Korean or Japanese.

The Galaxy Store is the third store most developers forget they're on. If you ship an Android APK to Samsung devices, you have a listing, a rating, and a stream of buyer comments in the Seller Portal that nobody is reading. Here's how to answer them, the rules Samsung enforces, the API if you want to automate it, and an honest note on where Galaxy Store fits next to Apple and Google.

Samsung splits your feedback into two things that look alike but aren't. Ratings are the star scores with no text; buyer comments are the reviews with an actual written complaint or compliment attached. You can only reply to the second kind, and both live under the same menu.

In Seller Portal, go to Assistance > Buyer Comments. You'll see every written review across all your apps, filterable by app, country, and star rating, alongside the ratings-and-statistics view for the aggregate picture. On a company account, replying is a permission a manager grants per-person, so a teammate may see the comments but not the Add Reply button until they're assigned the role.

The flow is short once you're on the Buyer Comments screen. Here's the whole thing end to end.

That reply names the device, the OS version, the build, and the next step, all inside the byte budget. It's the same shape of reply that works on any store: acknowledge, diagnose specifically, point to the fix, offer an escape hatch. If the review is a rough one and you want the full playbook for turning a one-star into an edit, [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) breaks down exactly what earns the rating bump.

Galaxy Store's reply mechanics sit somewhere between Apple's and Google's, and the specifics are easy to trip over. The ones that bite:

You can. Samsung's Content Publish API exposes an endpoint for posting a reply to a buyer comment programmatically, which is how you'd wire replies into your own tooling instead of clicking through the portal. You authenticate with a Seller Portal access token, then POST the app's content ID, the comment ID, the country code, and your reply text.

The API mirrors the portal's rules: one reply per comment, same byte limit. It's the right tool for internal automation, but maintaining a Galaxy Store pipeline yourself (token refresh, pagination, de-duping, sizing replies to the byte cap per language) is a project, not an afternoon. For a cross-store view of which stores expose what, [the app review reply mechanics reference](/blog/app-review-reply-mechanics-reference) lays out the endpoints and limits side by side.

Worth being honest about priorities. For most developers the Galaxy Store is a smaller slice of installs than the App Store or Google Play, so spend reply effort proportionally. But the case for replying is strong on every store that allows it. Google reported at I/O 2019 that developers who respond see an average lift of about 0.7 stars. A study of over four million reviews by Hassan et al. found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no reply), and McIlroy et al. (IEEE, 2017) found that when a rating changed after a response, 38.7% of those changes were increases. Those studies ran on Apple and Google data, but the behavior of a reviewer feeling heard and revising up isn't platform-specific.

The rules do differ by store, though, and if you split time across all three it pays to know them cold. Google Play caps replies at a hard 350 characters and lets you edit freely; Apple publishes no official character limit (community testing suggests a few thousand characters) and notifies the reviewer when your reply posts; Samsung gives you 1,400 bytes and one reply per comment. We mapped the whole matrix in [reply rules for every app store](/blog/reply-rules-for-every-app-store), and put the two biggest stores head-to-head in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

This is the point where doing it by hand quietly stops happening. Two live stores plus Samsung, in more than one language, week after week, is a lot of reading and re-typing, and the store you're least likely to keep up with is the third one. So here's the straight version of where [ReplyArgus](/features) fits: it watches your Apple App Store and Google Play reviews in one inbox and drafts a grounded, on-brand reply for each written review in the reviewer's own language (100+ supported, both directions), already sized to each store's limit, with approve-in-a-click or opt-in rule-based auto-publish. It does not connect to the Samsung Galaxy Store today. We only claim the two stores we actually publish to, and Samsung isn't one of them. What it buys you is time: automating the two stores that carry most of your reviews frees you to give the Galaxy Store the manual pass it still needs, instead of neglecting all three.

So the answer is yes, and it's a two-minute job per review once you know the path: Seller Portal, Buyer Comments, Add Reply, one shot, 1,400 bytes. Give the Galaxy Store the manual attention it deserves, and stop letting your Apple and Google reviews pile up while you're doing it. [Start free with ReplyArgus](/signup) (no card) and Argus drafts your first App Store and Google Play reply in minutes, so the stores that carry most of your volume run themselves while you keep Samsung on a tidy weekly pass.