surveymonkey nps range -100 to 100 is the canonical Net Promoter Score scale: SurveyMonkey calculates NPS as the percent of promoters (9–10) minus the percent of detractors (0–6), giving you a score that can fall anywhere between -100 and 100. For a Shopify DTC merchant running a post-purchase survey, that single number is useful as a quick health check, but the real work is wiring the responses into flows that actually move repeat purchase rate.

Why the scale matters for a Shopify DTC post-purchase survey

The numeric bounds matter because they force you to think in percentages, not raw averages: an NPS of 30 means 30% more promoters than detractors, not “3 out of 10.” SurveyMonkey explicitly shows the gauge from -100 to 100 and calculates promoters minus detractors automatically, so your implementation should focus on sampling, timing, and actions tied to promoter/detractor cohorts. (help.surveymonkey.com)

Below are seven concrete insights a Shopify operator can act on this week, each tied to a real merchant motion and including gotchas and edge cases.

1. Use timing to target meaningful moments: pick the right post-purchase trigger

• What to ship: send the NPS question 7 to 21 days after delivery confirmation for consumables and replenishment SKUs, or 3 to 7 days after delivery for apparel and accessories so the customer has real product experience.
• Merchant scenario: a DTC skincare brand with a 30-day routine should wait at least two weeks to capture an informed rating; a socks brand can ask sooner because customers wear immediately.
• Implementation details: place a link to the SurveyMonkey NPS from a Klaviyo or Postscript flow that is triggered by the Shopify order.fulfilled event, and include order ID and SKU in the survey link UTM or query params so you can map answers back to the product.
• Gotcha: ask too early and you’ll get artificially high scores from “delight with arrival” bias; ask too late and response rates plummet.

2. Keep the canonical NPS question, then follow up for why

• Wording that converts: “How likely are you to recommend [brand name] to a friend or colleague?” 0 to 10 scale, then branching follow-up: For 0–6: “What would we need to do to earn a higher rating?” For 9–10: “What did you like most?”
• Why: SurveyMonkey and NPS practice use 0–10 and the promoter/detractor buckets that produce a -100 to 100 score. Use the follow-up free text to capture product issues, fit problems, or delivery complaints that explain detractors. (surveymonkey.com)
• Implementation: enable branching so detractors immediately see a quick multi-choice checklist (fit, quality, shipping, price) plus one free-text line. Store answers in Shopify customer metafields or in Klaviyo profile properties.

3. Turn NPS bands into automation rules that move repeat purchase rate

• Concrete mapping: promoters go into a “Promoter 2x” Klaviyo segment and get VIP cross-sell offers (no discount, early access). Detractors get a 1:1 support flow: immediate apology, return label, and a product replacement or refund offer.
• Example: a DTC leggings brand tags promoters as promoter=true and sends a targeted cross-sell 14 days later; detractors are routed to CS with order notes attached. This split reduces churn risk and targets incentives more efficiently.
• Edge case: incentives can inflate short-term repeat purchases but depress long-term margin; always A/B holdout the incentive.

4. Sample bias and response rates shape the -100 to 100 interpretation

• Concrete numbers: if 50 orders produced 10 responses with 8 promoters and 2 detractors, NPS = (8/10100) - (2/10100) = 60; but that 60 is noisy because the respondent base is 20% of purchasers.
• Practical fix: aim for at least a 10% response rate per cohort and track rolling windows of 200+ responses before making platform-level decisions.
• Gotchas: email-only surveys bias toward engaged customers; on-site thank-you page surveys bias toward immediate reaction. Use both and compare.

5. Use SKU-level NPS to find product-led retention levers

• How to run it: send the post-purchase NPS with SKU metadata and maintain per-SKU NPS in a reporting dashboard. For replenishment products, correlate SKU-NPS to reorder intervals.
• Merchant scenario: a coffee DTC sees overall NPS = 25, but the single-origin roast has NPS = -5. That SKU-level insight should trigger product QA, packaging checks, or a targeted re-engagement email offering a sample swap.
• Implementation: push survey responses into Shopify customer metafields and create a saved Shopify report or use Klaviyo to create product cohorts.

6. Expect NPS to predict short-run change, not absolute future revenue

• Evidence and limitation: academic analysis shows that changes in NPS over time can predict short-term sales growth, but NPS alone is not a guaranteed long-term revenue predictor; treat it as a signal, not a SLA. (link.springer.com)
• Operational takeaway: prioritize moving NPS delta for cohorts you can influence quickly, for example by improving shipping communication or fixing frequent return reasons, and measure whether those deltas correlate with lift in repeat purchase rate in a holdout test.

7. Measure the end-to-end loop: close the feedback action chain

• The loop: collect NPS, tag customers in Shopify and Klaviyo, run tailored flows, measure repeat purchase lift after 30/60/90 days, and iterate.
• Concrete metric targets: for many DTC merchants a realistic lift from a tightened post-purchase recovery flow is +6 to +12 percentage points in repeat purchase over 90 days; case studies show larger lifts when flows are comprehensive. One case reported repeat purchase rate rising from 18% to 31% after segmented Klaviyo flows and a linked survey loop. Use holdouts to attribute. (weproms.com)
• Edge case: if your baseline repeat purchase rate is already very high, marginal gains require product changes not just emails.

Quick math: how NPS is calculated (practically)

• Example: 200 survey responses, 120 promoters (9–10), 40 passives (7–8), 40 detractors (0–6).
• Calculation: promoter % = 120/200 * 100 = 60, detractor % = 40/200 * 100 = 20, NPS = 60 - 20 = 40.
• Keep this calculation in your dashboards; SurveyMonkey will produce it for you, but make sure your exports include raw counts for cohort analysis. (help.surveymonkey.com)

People also ask

What does a SurveyMonkey NPS range -100 to 100 mean for my Shopify store?

It means your store’s NPS is the percent of promoters minus percent of detractors, producing a score anywhere from -100 to 100; for Shopify merchants this number is a cohort-level signal that must be tied back to order data and SKU-level causes. Use the range to prioritize which cohorts to intervene on: a low negative score signals systemic problems, while a small positive score can hide SKU-level negative pockets. (help.surveymonkey.com)

How do I calculate NPS from SurveyMonkey responses?

SurveyMonkey computes NPS automatically from the classic 0–10 question by subtracting the percentage of detractors (0–6) from promoters (9–10); export the raw response counts to verify and to calculate per-SKU or per-fulfillment-partner scores in your own spreadsheet. (surveymonkey.com)

Can NPS predict repeat purchase rate for DTC brands?

NPS can indicate short-term shifts that correlate with future purchases, especially when you track changes over time and segment by customer type, but academic studies find mixed evidence for long-term prediction, so run A/B holdouts and measure actual repeat purchase changes rather than assuming causality. (link.springer.com)

Practical playbook for the next 7 days

• Day 1: pick the trigger and question text, instrument the survey link to include order ID and SKU. Use a Klaviyo flow or Postscript to send the link after fulfillment.
• Day 2: configure branching: detractors see a short checklist plus free-text, promoters see a “tell us what you loved” prompt, passives see a neutral follow-up asking how to improve.
• Day 3: wire responses into Shopify customer tags and Klaviyo profile properties, create two segments: Promoters and Detractors.
• Day 4: build two flows: promoter experience (VIP cross-sell, early access) and detractor remediation (fast CS contact, return/replace offer).
• Day 5–7: run a 50/50 holdout for the remediation flow to measure repeat purchases at 30 and 60 days, and be prepared to iterate on question timing or copy.

Common pitfalls and how to avoid them

• Low response rates: boost response by sending SMS links to mobile-friendly SurveyMonkey forms and using order-specific personalization; don’t over-incentivize because incentives distort scores.
• Too few responses per SKU: collapse SKUs into meaningful families (e.g., “cleanser, moisturizer”) for statistical power.
• Channel mismatch: email-only surveys miss buyers who only interact via SMS or the Shop app; tie multiple channels to the same survey landing page or duplicate a shorter on-site version.

Operational metrics to track weekly

• Response rate by channel and by SKU
• NPS overall, promoter %, detractor %
• Repeat purchase rate for promoter and detractor cohorts at 30/60/90 days
• Volume of detractor tickets routed to CS and mean time to resolution

Caveat: when NPS does not help

• If you have a small catalog with one core hero product and renewals are driven by subscription behavior, subscription health metrics and churn analysis may give clearer levers than NPS. NPS adds value when you sell multiple SKUs and need to prioritize product or fulfillment fixes tied to repeat purchases.

How Zigpoll handles this for Shopify merchants

Step 1: Trigger — Set Zigpoll to fire a post-purchase survey on the Shopify order thank-you page for non-subscription SKUs and/or send an automated survey link via Klaviyo or Postscript N days after the order.fulfilled event (choose 7–14 days for apparel, 14–21 days for consumables). Use the same survey ID for both triggers so responses aggregate in one place.

Step 2: Question types — Start with the NPS question: “How likely are you to recommend [brand] to a friend?” 0 to 10. Add branching follow-ups: for scores 0–6 show “What went wrong? (fit, quality, shipping, other) — select all that apply” plus a one-line free-text; for 9–10 show “What did you like most?” as a short free-text. Optionally add a CSAT star rating for delivery experience.

Step 3: Where the data flows — Map Zigpoll responses into Klaviyo profile properties and segments (Promoter/Detractor), push customer tags or metafields into Shopify for order-level joins, and send detractor responses to a Slack channel or the Zigpoll dashboard for CS action. From Klaviyo, trigger targeted flows for promoters and a remediation sequence for detractors so you can measure repeat purchase lift by cohort.