On this page本页目录
Product return analysis compares each SKU or variant using return count, return rate, net return loss, reason mix, and sample size. Rank products by more than one metric: count favors bestsellers, rate can exaggerate small samples, and loss identifies financial exposure. A product should become a review priority only after its sales denominator, cohort, costs, and evidence are verified.
商品退货分析，是按退货次数、退货率、净退货损失、原因构成和样本量比较每个 SKU 或变体。商品不能只按一个指标排名：次数偏向畅销品，比例可能放大小样本，损失则反映财务风险。只有在核验销量分母、订单群组、成本和证据后，商品才应进入优先复核名单。
Return count alone does not identify a bad product只看退货次数不能识别问题商品
A bestseller can create the most returned units while performing normally relative to sales volume.
畅销品可能产生最多退货件数，但相对销量的表现仍属正常。
Three returns from ten units is 30%, but the estimate is too unstable for a costly decision without more evidence.
10 件中退回 3 件是 30%，但在缺少更多证据时，该估计不足以支持高成本决策。
A costly, bulky, or low-recovery product can deserve priority even when its rate is not the highest.
高货值、大体积或低回收率商品即使退货率不是最高，也可能应该优先处理。
A product average can hide one problematic size, color, supplier batch, or fulfillment path.
商品平均值可能掩盖某个有问题的尺码、颜色、供应商批次或履约路径。
Use five metrics for product return analysis商品退货分析应同时使用五项指标
| Metric指标 | Formula or definition公式或定义 | Main caution主要注意点 |
|---|---|---|
| Returned units退货件数 | Physical units returned for the SKU该 SKU 实体退回件数 | Reflects volume, not relative risk反映规模，不代表相对风险 |
| SKU return rateSKU 退货率 | Returned units ÷ eligible sold or delivered units × 100退货件数 ÷ 符合口径的已售或已送达件数 × 100 | Cohort, window, and small sample must be shown必须显示群组、窗口与小样本 |
| Net return loss净退货损失 | Consistently allocated revenue, processing, write-down, and recovery impact按一致口径分配的收入、处理、减值和回收影响 | Avoid refund and inventory double counting避免重复计算退款和库存 |
| Reason mix原因构成 | Returned units by normalized reason ÷ SKU returned units按标准原因统计的退货件数 ÷ SKU 退货件数 | Reason is a hypothesis, not proven cause原因只是待验证假设，不是已证实成因 |
| Returns-adjusted contribution退货调整后贡献利润 | Net sales − SKU variable costs − net return-related loss净销售额 − SKU 变动成本 − 净退货相关损失 | Finance must approve allocations分配口径需财务确认 |
Worked example: three rankings identify three priorities完整示例：三种排名得到三个不同优先项
This synthetic example uses one completed sales cohort and one loss definition. It demonstrates method only.
以下假设示例使用同一已完成销售群组和同一损失定义，仅用于演示方法。
| SKU | Eligible units符合口径件数 | Returns退货件数 | Return rate退货率 | Net return loss净退货损失 |
|---|---|---|---|---|
| SKU-A | 1,000 | 100 | 10% | $3,000 |
| SKU-B | 200 | 40 | 20% | $3,200 |
| SKU-C | 40 | 12 | 30% | $720 |
SKU-B is the first financial review. SKU-C needs more evidence or a stability warning. SKU-A may be a volume-management opportunity rather than the worst product.
SKU-B 应首先接受财务复核；SKU-C 需要更多证据或稳定性提示；SKU-A 可能是规模管理机会，而不一定是最差商品。
Show sample size beside every SKU return rate在每个 SKU 退货率旁显示样本量
Never hide the denominator. Set a documented minimum eligible-unit threshold for ranking, display exact counts, and use a confidence interval or shrinkage method when the decision warrants it. There is no universal minimum: the threshold should reflect decision cost, baseline rate, category, and required precision.
不能隐藏分母。应为排名设置有记录的最低符合口径件数，显示实际数量；当决策重要时，使用置信区间或收缩估计。不存在通用最低样本量，阈值应根据决策成本、基准退货率、类目和精度要求确定。
Practical display rule: place “12 returns / 40 eligible units” beside 30%. Mark it as a small sample instead of presenting 30% as a stable product truth.
实用展示规则：在 30% 旁同时显示“12 件退货 / 40 件符合口径商品”，并标记为小样本，而不是把 30% 当作稳定结论。
Calculate product profitability after returns without double counting避免重复计算退货后的商品盈利
Choose one accounting bridge. Do not subtract the refund in net sales and then add the same refund again as a return cost. Define return-related loss with the cost-of-returns method, and obtain finance approval before calling a SKU unprofitable.
应选择一种会计桥接方式。不能先在净销售额中扣除退款，再把同一退款作为退货成本重复加入。使用退货成本方法定义退货相关损失，并在认定 SKU 不盈利前获得财务确认。
Analyze returns by size and color at variant level在变体层级按尺码和颜色分析退货
A product-level average can hide a single unstable variant. Build a size-by-color matrix using a unique variant ID or SKU, eligible units, returned units, reason mix, and loss. Compare within the same product first; cross-product size labels are not automatically equivalent.
商品平均值可能掩盖单个异常变体。应使用唯一变体 ID 或 SKU、符合口径件数、退货件数、原因构成和损失建立尺码×颜色矩阵。先在同一商品内部比较，因为跨商品的尺码标签并不必然等价。
Shopify recommends unique SKUs for effective inventory tracking and sales reporting and treats each size/color combination as a separate variant. Duplicate or missing SKUs must be resolved or disclosed before joining returns.
Shopify 建议使用唯一 SKU 以提高库存跟踪与销售报告准确性，并把每种尺码/颜色组合视为独立变体。连接退货数据前，应解决或披露重复、缺失 SKU。
Run supplier quality return analysis only when the fields exist只有字段存在时才进行供应商质量退货分析
Supplier conclusions require supplier ID, purchase order or batch, received date, SKU/variant, return reason, inspection result, and eligible units. Compare the same product specification across suppliers when possible. If supplier or batch is missing, report that the dimension cannot be evaluated—do not infer it from SKU text.
供应商结论需要供应商 ID、采购单或批次、收货日期、SKU/变体、退货原因、质检结果和符合口径件数。条件允许时，应比较不同供应商提供的同一商品规格。若供应商或批次字段缺失，应明确该维度无法判断，不能从 SKU 文本中猜测。
Do not label every high-return product a quality failure不要把所有高退货率商品都定性为质量问题
High returns can reflect fit, product-detail expectations, fulfillment, delivery, policy, promotion mix, or measurement changes. Use the return reason analysis method to connect customer labels to inspection, content, warehouse, carrier, supplier, and batch evidence before assigning ownership.
高退货可能来自合身、详情页预期、履约、配送、政策、促销结构或测量变化。使用退货原因分析方法，把客户标签连接到质检、内容、仓库、承运商、供应商和批次证据，再确定负责人。
Build a product return dashboard that exposes the denominator建立公开分母的商品退货看板
| Required block必要模块 | Fields字段 |
|---|---|
| Identity身份 | Product ID, variant ID, SKU, title, size, color, category |
| Exposure暴露量 | Eligible units/orders, cohort dates, return window, channel |
| Returns退货 | Returned units, rate, reasons, resolution, condition, disposition |
| Economics经济性 | Net sales, COGS, return loss, recovered value, contribution |
| Evidence quality证据质量 | Missing joins, duplicate SKU, sample flag, estimated fields, last refresh |
Analyze product returns in six reviewable steps用六个可审核步骤分析商品退货
- Define the grain.确定粒度。 Choose product, variant, or unique SKU and document duplicate handling.选择商品、变体或唯一 SKU，并记录重复值处理。
- Build the cohort.建立群组。 Use eligible sold or delivered units and wait for the declared return window.使用符合口径的已售或已送达件数，并等待声明的退货窗口。
- Join returned line items.连接退货订单行。 Connect reason, refund, condition, disposition, warehouse, carrier, and supplier fields.连接原因、退款、状况、处置、仓库、承运商和供应商字段。
- Calculate comparable metrics.计算可比指标。 Report count, rate, loss, contribution, and sample size with one scope.在同一范围报告次数、比例、损失、贡献利润和样本量。
- Rank and segment.排名并分组。 Compare count, rate, and loss; then inspect size, color, reason, supplier, and channel.比较次数、比例和损失，再检查尺码、颜色、原因、供应商和渠道。
- Verify before action.行动前核验。 Assign an owner, evidence request, decision threshold, and review date.指定负责人、证据要求、决策阈值和复核日期。
Prepare SKU-level files and find products that need review准备 SKU 级文件，定位需要复核的商品
Prepare product and variant IDs, unique SKU, size, color, eligible units, order and return dates, returned quantity, normalized reason, refund and cost fields, recovered value, condition, disposition, channel, supplier and batch when available, plus missing-data flags. Then use Return Compass to organize available files and identify products for human review. Confirm current inputs, security requirements, login conditions, pricing, and product-analysis capability before use; missing supplier or variant fields must not be invented.
准备商品与变体 ID、唯一 SKU、尺码、颜色、符合口径件数、下单与退货日期、退货数量、标准原因、退款和成本字段、回收价值、状况、处置、渠道，以及存在时的供应商与批次，并加入缺失数据标记。再使用逆向罗盘整理已有文件，定位需要人工复核的商品。使用前应确认当前输入格式、安全要求、登录条件、收费方式与商品分析能力；缺失的供应商或变体字段不能编造。
Open Return Compass打开逆向罗盘Already use InfiniSynapse? Log in.
已在使用 InfiniSynapse？登录。
Download the product-return analysis starter下载商品退货分析起始模板
Use this vendor-neutral CSV to preserve source identifiers, event distinctions, metric inputs, cost fields, coverage, evidence and ownership. Its example row is synthetic; remove it before loading authorized data and approve definitions with the responsible owners.
使用此厂商中立 CSV 保留来源标识、事件区别、指标输入、成本字段、覆盖、证据与责任。示例行为模拟数据；加载授权数据前请删除，并由相关负责人批准定义。
Download CSV starter下载 CSV 起始模板 ↓Sources, method, and commercial disclosure来源、方法与商业披露
The formulas and three-SKU example are transparent editorial definitions, not universal accounting rules or merchant benchmarks. Each business must reconcile source systems and obtain finance approval for cost allocation.
本页公式和三个 SKU 示例属于透明编辑定义，不是通用会计规则或商家基准。每家企业都应对账源系统，并由财务确认成本分配。
- Shopify Help Center: Using SKUs — recommends unique SKUs for tracking and reporting and distinguishes product variants.
- Shopify Help Center: Sales reports — defines returned quantity rate and variant-level reporting boundaries.
- Shopify Help Center: Profit reports — documents variant gross profit and the need for product cost data.
- Shopify Developer Documentation: InventoryItem — connects product variants, SKUs, inventory, and unit cost.
- National Retail Federation: 2025 Retail Returns Landscape — U.S. market context only, not a SKU benchmark.
- Shopify 帮助中心：使用 SKU——建议使用唯一 SKU 进行跟踪与报告，并区分商品变体。
- Shopify 帮助中心：销售报表——定义退回数量率和变体级报告边界。
- Shopify 帮助中心：利润报表——说明变体毛利及商品成本数据要求。
- Shopify 开发者文档：InventoryItem——连接商品变体、SKU、库存和单位成本。
- 美国零售联合会：2025 零售退货报告——仅用于美国市场背景，不是 SKU 基准。
Commercial disclosure: InfiniSynapse publishes this educational page and promotes Return Compass. Product statements come from the supplied planning brief and are not an independent review. The example is synthetic. The page does not promise lower returns, recovered loss, automatic product-quality diagnosis, or any unverified feature.
商业披露：本教育页面由 InfiniSynapse 发布，并推广逆向罗盘。产品说明来自提供的规划简报，不属于独立评测。案例为假设数据。本页不承诺降低退货、追回损失、自动诊断商品质量或任何未经核实的功能。
Frequently asked questions常见问题
It compares returns by SKU or variant using count, rate, loss, reason, and sample size to identify products that need review.
它按次数、比例、损失、原因和样本量比较 SKU 或变体，识别需要复核的商品。
Divide physically returned SKU units by eligible sold or delivered units from the same cohort, then multiply by 100.
用同一群组中实体退回的 SKU 件数除以符合口径的已售或已送达件数，再乘以 100。
Use both, plus loss and sample size. Each metric answers a different question and can mislead alone.
应同时使用二者，并加入损失和样本量。每个指标回答不同问题，单独使用都可能误导。
Calculate SKU contribution after net sales, COGS, fulfillment, payment/platform fees, net return loss, and consistently allocated variable costs.
计算扣除净销售额冲销、COGS、履约、支付/平台费、净退货损失和一致分配变动成本后的 SKU 贡献利润。
Yes, only when returned line items reliably contain variant attributes and supplier or batch IDs. Disclose missing fields.
可以，但退货订单行必须可靠包含变体属性及供应商或批次 ID；缺失字段必须披露。
Publish the denominator and sample size beside every SKU在每个 SKU 旁发布分母和样本量
A credible product return dashboard lets another analyst reproduce the ranking. Keep the grain, cohort, eligible units, return window, count, rate, loss basis, cost allocation, missing joins, sample flag, and last refresh beside each result. Connect the reviewed outputs to the broader ecommerce returns analytics workflow.
可信的商品退货看板应允许另一位分析人员复算排名。把分析粒度、群组、符合口径件数、退货窗口、次数、比例、损失口径、成本分配、缺失连接、样本标记和最后刷新时间放在每个结果旁，再连接到完整的电商退货分析流程。