<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>PerkStack Blog</title>
    <link>https://blog.perk-stack.com</link>
    <atom:link href="https://blog.perk-stack.com/rss.xml" rel="self" type="application/rss+xml" />
    <description>Honest comparisons, practical playbooks, and behind-the-scenes notes on loyalty and reviews for Shopify stores, written by the people building PerkStack.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Jul 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>PerkStack now speaks seven languages</title>
      <link>https://blog.perk-stack.com/posts/perkstack-now-speaks-seven-languages</link>
      <guid isPermaLink="true">https://blog.perk-stack.com/posts/perkstack-now-speaks-seven-languages</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>PerkStack Team</dc:creator>
      <description>Your loyalty and reviews widgets — and the whole admin — now work in Spanish, French, German, Italian, Portuguese, and Romanian. Here&apos;s how to turn it on, plus a way to run the admin in a different language than your storefront.</description>
      <category>product</category>
      <content:encoded><![CDATA[<p>PerkStack now speaks seven languages. As of today, both the storefront widgets your shoppers see — the loyalty launcher, the loyalty page, and the review display, form, and carousel — and the entire admin app you work in are fully translated into:</p>
<ul>
<li>English</li>
<li>Español (Spanish)</li>
<li>Français (French)</li>
<li>Deutsch (German)</li>
<li>Italiano (Italian)</li>
<li>Português (Portuguese)</li>
<li>Română (Romanian)</li>
</ul>
<p>Every visible string is translated, not just the headlines. And we did one thing most apps don't: we let your <strong>admin language and your storefront language be different</strong>. More on that below, because it's the part that matters if you're, say, a Portuguese founder selling into the US.</p>
<h2 id="the-storefront-translates-with-your-store"><a href="#the-storefront-translates-with-your-store">The storefront: translates with your store</a></h2>
<p>Your shoppers should never see a loyalty widget in a language they don't read. So the storefront side is automatic.</p>
<p>PerkStack's widgets follow the language your shopper is viewing your store in. If a customer switches your store to French, the launcher, the loyalty page, and the review widgets all render in French right alongside your theme. You don't pick a language inside PerkStack for the storefront — it inherits the one Shopify is already serving.</p>
<h3 id="how-to-turn-it-on"><a href="#how-to-turn-it-on">How to turn it on</a></h3>
<ol>
<li>In your Shopify admin, go to <strong>Settings → Languages</strong> (or <strong>Online Store → Languages</strong>).</li>
<li><strong>Add and publish</strong> the language you want to sell in — for example, Français or Deutsch.</li>
<li>That's it. The next time a shopper views your store in that language, the loyalty launcher, loyalty page, and every review element render translated automatically.</li>
</ol>
<p>If you sell across multiple markets with multiple published languages, each shopper sees PerkStack in their own. There's no per-language setup in PerkStack and nothing to copy-paste — the six new languages ship built in.</p>
<blockquote>
<p>One small polish while we were in here: we fixed a grammar bug where the balance label used to glue a translated word onto your points name (things like "Al tău points"). Non-English stores now show your points name cleanly.</p>
</blockquote>
<h2 id="the-admin-pick-your-own-language"><a href="#the-admin-pick-your-own-language">The admin: pick your own language</a></h2>
<p>The whole PerkStack admin — settings, loyalty, reviews, customers, onboarding, analytics, integrations, the customize pages, everything — is translated too.</p>
<p>By default, PerkStack follows your <strong>Shopify account language</strong>. If your Shopify account is set to Italian, PerkStack's admin comes up in Italian without you doing anything.</p>
<h2 id="running-the-admin-in-a-different-language-than-your-store"><a href="#running-the-admin-in-a-different-language-than-your-store">Running the admin in a different language than your store</a></h2>
<p>Here's the case we really wanted to solve. Say you're based in Portugal, you think in Portuguese, but you sell into the US and run your storefront in English. Your Shopify account might be in English to match the market — but you'd rather manage your loyalty program in Portuguese.</p>
<p>That used to be an either/or. Now it isn't. PerkStack has a per-shop <strong>Admin language</strong> override that's completely independent of your Shopify account language and your storefront language.</p>
<h3 id="how-to-activate-the-manual-override"><a href="#how-to-activate-the-manual-override">How to activate the manual override</a></h3>
<ol>
<li>In PerkStack, open <strong>Settings</strong>.</li>
<li>On the <strong>General</strong> tab, find the <strong>Admin language</strong> card.</li>
<li>Pick your language — <strong>Português</strong>, in our example — from the dropdown.</li>
<li>Save. The admin now runs in Portuguese for this shop, regardless of what your Shopify account or storefront are set to.</li>
</ol>
<p>Leave it on <strong>Automatic</strong> and PerkStack keeps following your Shopify account language like before. Set it to a specific language and that choice wins everywhere in the admin.</p>
<p>So the Portuguese-founder-selling-to-the-US setup looks like this:</p>
<table>
<thead>
<tr>
<th>Surface</th>
<th>Language</th>
<th>Set where</th>
</tr>
</thead>
<tbody>
<tr>
<td>Storefront widgets</td>
<td>English (your shoppers' language)</td>
<td>Shopify → Languages</td>
</tr>
<tr>
<td>Shopify account</td>
<td>English</td>
<td>Shopify account settings</td>
</tr>
<tr>
<td>PerkStack admin</td>
<td>Português</td>
<td>PerkStack → Settings → General → <strong>Admin language</strong></td>
</tr>
</tbody>
</table>
<p>Three surfaces, three independent choices. Your shoppers get a native store; you get a native dashboard.</p>
<h2 id="a-note-on-quality"><a href="#a-note-on-quality">A note on quality</a></h2>
<p>We didn't want "technically translated." Every language is checked for key parity in our test suite — meaning if a string exists in English, it has to exist, correctly, in all six other languages, plurals included, before the build passes. Romanian, for instance, has its own plural rules that English doesn't; the tests hold each language to its own grammar, not English's.</p>
<p>That's the bar: if you switch PerkStack to Romanian, you should never hit a stray English string or an "N reviews" that doesn't agree with the number in front of it.</p>
<h2 id="the-short-version"><a href="#the-short-version">The short version</a></h2>
<ul>
<li><strong>Storefront</strong> translates automatically — just publish the language in Shopify.</li>
<li><strong>Admin</strong> follows your Shopify account language by default.</li>
<li><strong>Admin language override</strong> in Settings → General lets you run the dashboard in any of the seven languages, independent of your store and account.</li>
</ul>
<p>Publish a language, and if you like, pick your own for the admin. That's the whole thing. More soon.</p>]]></content:encoded>
    </item>
    <item>
      <title>PerkStack vs Smile.io: which one fits your store?</title>
      <link>https://blog.perk-stack.com/posts/perkstack-vs-smile</link>
      <guid isPermaLink="true">https://blog.perk-stack.com/posts/perkstack-vs-smile</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
      <dc:creator>PerkStack Team</dc:creator>
      <description>A fair look at PerkStack and Smile.io for Shopify loyalty, including the cases where Smile is the better pick.</description>
      <category>comparisons</category>
      <content:encoded><![CDATA[<p>If you're shopping for a Shopify loyalty app, Smile.io is probably already on your list. It's been around a long time and a lot of stores run it happily. We build PerkStack, so we're not exactly neutral here. But a comparison that only makes us look good is useless to you, so we've tried to be straight about it, including where Smile is the smarter choice.</p>
<h2 id="the-short-version"><a href="#the-short-version">The short version</a></h2>
<p>Smile is a loyalty and referrals app. PerkStack does loyalty, reviews, and referrals together, with a dashboard that ties them to actual revenue.</p>
<p>So the real question isn't "which loyalty app is better." It's whether you want loyalty and reviews living in one place. If you're already happy with a separate reviews app and only need points, Smile is a solid, proven option. If you'd rather not run two apps and pay two bills, that's the whole reason PerkStack exists.</p>
<h2 id="side-by-side"><a href="#side-by-side">Side by side</a></h2>
<table>
<thead>
<tr>
<th></th>
<th>PerkStack</th>
<th>Smile.io</th>
</tr>
</thead>
<tbody>
<tr>
<td>Points and rewards</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>VIP tiers</td>
<td>3 tiers, per-tier multipliers</td>
<td>Yes</td>
</tr>
<tr>
<td>Referrals</td>
<td>Two-sided</td>
<td>Yes</td>
</tr>
<tr>
<td>Product reviews</td>
<td>Built in, unlimited on every plan</td>
<td>Not included</td>
</tr>
<tr>
<td>Reviews can earn points</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Revenue dashboard</td>
<td>Yes</td>
<td>Limited</td>
</tr>
<tr>
<td>Shopify Flow</td>
<td>19 triggers, 14 actions</td>
<td>Partial</td>
</tr>
<tr>
<td>Klaviyo sync</td>
<td>Two-way</td>
<td>Two-way (higher plans)</td>
</tr>
<tr>
<td>AI / MCP server</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Free plan</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</tbody>
</table>
<p>The row that tends to change people's minds is reviews. With Smile you'll pair it with a reviews app and pay for both. With PerkStack, a customer can leave a photo review, earn points for it, and see that review show up on the product page with the markup Google likes, all in the same tool.</p>
<h2 id="where-smile-is-the-better-call"><a href="#where-smile-is-the-better-call">Where Smile is the better call</a></h2>
<p>A few cases where we'd point you to Smile without hesitation:</p>
<ul>
<li>You love your current reviews app and have no plans to switch. Our reviews engine would just be value you don't use.</li>
<li>You want the most established name with the deepest partner ecosystem, and that matters to your team.</li>
<li>You're running a large, very custom loyalty setup and want the most battle-tested option for that specific job.</li>
</ul>
<h2 id="where-we-think-perkstack-wins"><a href="#where-we-think-perkstack-wins">Where we think PerkStack wins</a></h2>
<ul>
<li>Reviews and loyalty in one app, one dashboard, one bill, with reviews that actually feed your points program.</li>
<li>A home screen that opens with one number: roughly how much money the app made you this month, split across repeat buyers, review-influenced first orders, and referrals.</li>
<li>Automation that's ready on day one. 19 Flow triggers and 14 actions, with a kill switch so nothing fires when you don't want it to.</li>
<li>You can run the whole thing from Claude or ChatGPT through our built-in MCP server, with scoped tokens and an audit log for every action.</li>
<li>Light storefront widgets (under 15KB gzipped) so your theme stays fast.</li>
</ul>
<blockquote>
<p>If you're worried about losing your review history, don't be. PerkStack imports from Judge.me, Loox, and Yotpo, so moving doesn't mean starting your social proof over.</p>
</blockquote>
<h2 id="how-to-actually-decide"><a href="#how-to-actually-decide">How to actually decide</a></h2>
<p>Three questions usually settle it:</p>
<ol>
<li>Do you want reviews and loyalty from one vendor? If yes, PerkStack saves you a second app and bill.</li>
<li>Do you need to show someone (a founder, a finance lead) that this is paying off? The revenue dashboard was built for that exact conversation.</li>
<li>Are you happy with your reviews app and only need points? Smile is a great fit, go with it.</li>
</ol>
<p>There's no single right answer. There's just the one that matches how your store is set up.</p>
<h2 id="try-them-both"><a href="#try-them-both">Try them both</a></h2>
<p>Honestly, the fastest way to choose is to install both on a dev store and run the same loop: a purchase, a review, a redemption. You'll feel which one takes fewer clicks pretty quickly. PerkStack has a free plan with unlimited reviews, so you can poke at the reviews side without spending anything.</p>]]></content:encoded>
    </item>
    <item>
      <title>PerkStack vs Judge.me: reviews on their own, or reviews that earn points?</title>
      <link>https://blog.perk-stack.com/posts/perkstack-vs-judgeme</link>
      <guid isPermaLink="true">https://blog.perk-stack.com/posts/perkstack-vs-judgeme</guid>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <dc:creator>PerkStack Team</dc:creator>
      <description>Judge.me is a great reviews app. Here&apos;s how we compare when you want reviews and loyalty working together, plus how to bring your Judge.me history along.</description>
      <category>comparisons</category>
      <content:encoded><![CDATA[<p>Judge.me is one of the most popular reviews apps on Shopify, and for good reason. It's genuinely good at collecting and showing reviews. So why look at PerkStack? Because we treat reviews as one half of a loop, not a feature on its own.</p>
<h2 id="the-difference-in-one-line"><a href="#the-difference-in-one-line">The difference in one line</a></h2>
<p>Judge.me is a reviews app. PerkStack is a loyalty and reviews app, where leaving a review can hand a customer points, and those points pull them back for the next order.</p>
<p>If reviews are all you need, Judge.me is a great choice, and we actually sync with it (more on that in a second). If you want reviews that feed a loyalty program, that's where we come in.</p>
<h2 id="side-by-side"><a href="#side-by-side">Side by side</a></h2>
<table>
<thead>
<tr>
<th></th>
<th>PerkStack</th>
<th>Judge.me</th>
</tr>
</thead>
<tbody>
<tr>
<td>Unlimited reviews</td>
<td>Yes, every plan</td>
<td>Yes</td>
</tr>
<tr>
<td>Photo and star reviews</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Verified-purchase gating</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Rich snippet markup</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Review-request emails</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Points for leaving a review</td>
<td>Yes, native</td>
<td>No</td>
</tr>
<tr>
<td>VIP tiers and rewards</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Referrals</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Revenue dashboard</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Two-way Judge.me sync</td>
<td>Yes</td>
<td>n/a</td>
</tr>
</tbody>
</table>
<h2 id="we-work-with-judgeme-not-just-against-it"><a href="#we-work-with-judgeme-not-just-against-it">We work with Judge.me, not just against it</a></h2>
<p>Most comparison posts skip this part, so here it is up front: PerkStack has a live two-way Judge.me sync. You can publish, reply, and import reviews without leaving PerkStack. If you've spent years building up Judge.me reviews, you don't have to walk away from them to add loyalty.</p>
<p>There's also a one-click CSV import from Judge.me, Loox, and Yotpo, so the social proof you've already earned comes with you.</p>
<h2 id="where-judgeme-is-the-better-pick"><a href="#where-judgeme-is-the-better-pick">Where Judge.me is the better pick</a></h2>
<ul>
<li>You only want reviews and have no plans for a loyalty program. A focused tool is less to think about.</li>
<li>You're deep into review-specific integrations that matter to your workflow.</li>
</ul>
<h2 id="where-we-think-perkstack-wins"><a href="#where-we-think-perkstack-wins">Where we think PerkStack wins</a></h2>
<ul>
<li>Reviews that pay customers back. A photo review can earn points, and points are a reason to come back and spend them.</li>
<li>One vendor and one bill for reviews, loyalty, and referrals.</li>
<li>A dashboard that shows how much of your revenue reviews actually influenced, instead of leaving you to guess.</li>
<li>You can even moderate pending reviews from Claude or ChatGPT through our MCP server, if that's how you like to work.</li>
</ul>
<blockquote>
<p>A review on a product page is social proof. A review that earns points is the start of a second order. That second order is the whole point of PerkStack.</p>
</blockquote>
<h2 id="our-honest-take"><a href="#our-honest-take">Our honest take</a></h2>
<p>If you're reviews-only and content, stay on Judge.me, and connect it to PerkStack later if you ever add loyalty. If you're trying to build something where reviews and points feed each other, start with PerkStack and bring your Judge.me history with you.</p>]]></content:encoded>
    </item>
    <item>
      <title>Hello, and welcome to the blog</title>
      <link>https://blog.perk-stack.com/posts/welcome-to-the-perkstack-blog</link>
      <guid isPermaLink="true">https://blog.perk-stack.com/posts/welcome-to-the-perkstack-blog</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <dc:creator>PerkStack Team</dc:creator>
      <description>What this blog is for, what we&apos;ll write about, and the kind of stuff we promise not to do.</description>
      <category>product</category>
      <content:encoded><![CDATA[<p>Hi. This is the blog for PerkStack, the Shopify app that puts loyalty and reviews in one place.</p>
<p>We started PerkStack because splitting loyalty and reviews across two apps, two dashboards, and two bills always felt like a tax on growth. They're really the same loop: a good review brings in a new buyer, points bring that buyer back, and the next visit is another chance for a review. This blog is where we write about building that loop.</p>
<h2 id="what-well-write-about"><a href="#what-well-write-about">What we'll write about</a></h2>
<ul>
<li><strong>Comparisons.</strong> Straight, specific breakdowns like PerkStack vs Smile.io and PerkStack vs Judge.me, including the cases where the other tool is the better fit.</li>
<li><strong>Playbooks.</strong> Real guidance on points structures, VIP tiers, when to send review requests, and referral mechanics that actually move repeat purchases.</li>
<li><strong>Product notes.</strong> How features like the revenue dashboard, Cap-Recovery, and our MCP server work, and how to get more out of them.</li>
</ul>
<h2 id="what-we-wont-do"><a href="#what-we-wont-do">What we won't do</a></h2>
<p>No guilt-trippy copy, no fake countdown timers, no rewarding people specifically for five-star reviews. That stuff is bad for shoppers, and on Shopify it's against the rules anyway. We hold the blog to the same bar as the app.</p>
<blockquote>
<p>The number we care about is revenue. Every post here comes back to one question: did this make the store more money?</p>
</blockquote>
<h2 id="where-to-start"><a href="#where-to-start">Where to start</a></h2>
<p>If you're sizing up loyalty apps, the comparison posts are the quickest way to get your bearings. If you already run PerkStack, the playbooks will help you squeeze more out of it.</p>
<p>Thanks for reading. More soon.</p>]]></content:encoded>
    </item>
  </channel>
</rss>