BestFeed AI is live — review and improve product content for AI discovery.Explore BestFeed →
Home/Blog/How to prevent duplicate Shopify products after supplier updates
SonarFulfill

How to prevent duplicate Shopify products after supplier updates

Link supplier IDs, internal drafts, and Shopify product IDs so an update changes the right listing instead of creating another one.

For: Teams with frequent supplier updates, duplicate product pages, or broken catalog relationships.

What you can do after reading: Build a three-level identity map and decide whether a change should create, update, or do nothing.

Duplicate products usually appear because the system cannot tell whether a supplier record and a Shopify product describe the same commercial item. Titles, images, and cost all change, so none of them works as the sole identity.

Use three identity levels

Supplier identity

Store supplier_id, supplier_product_id, supplier_variant_id, and source_url.

Internal draft identity

Store internal_draft_id, current status, first-added time, last refresh, and reviewer.

Shopify identity

Store shopify_product_id, shopify_variant_id, current sales channels, and last publish time.

The expected relationship is one supplier product to one internal master record to one linked Shopify product. If several suppliers sell the same item, create a sourcing relationship instead of a separate customer page for every supplier.

Decide between create and update

SituationAction
New supplier ID and no matching commercial itemCreate a Draft
Known supplier ID with a Shopify relationshipMove to Update
Only a new color or sizeConsider a Variant
The product itself changedReview whether it is a new item
Only cost or shipping changedUpdate supplier data without overwriting the live page

Shopify says Duplicate creates a new product. A new color or size should normally be added as a variant.[1]

Compare fields before applying an update

Show the old value, new value, field type, risk, recommended action, and approval. Do not stop at "supplier product updated."

FieldCurrentSupplierAction
Cost$18$21Review the price preview
ImagesBrand-edited setNew supplier setDo not overwrite automatically
ColorsBlack, BlueBlack, Blue, GreenReview the Green variant

Protect the listing that already has value

Before deleting a duplicate, check which product has orders, reviews, advertising and external links, the correct URL, and complete inventory and variant data. Then decide whether to merge, redirect, archive, or keep it. Deletion can affect reports and existing links.

Run duplicate checks more than once

Check when a candidate enters Draft, before Shopify publication, and before a supplier update is applied. Use stable IDs, GTIN, brand, model, important specifications, and human review. Title similarity is a clue, not a decision.

SonarFulfill uses Draft, Published, and Update relationships to connect supplier changes to an existing listing. An approved update changes selected fields on that product instead of creating another copy.

Map ten recent supplier updates today

Place the supplier product ID, internal draft ID, and Shopify product ID side by side for ten items. Work on missing links first. Decide whether each record belongs to an existing product, a new Draft, or human review. Do not merge on title similarity or delete a suspected duplicate before the mapping is complete.

References

Learn more about SonarFulfill

SonarFulfill connects product discovery, draft review, pricing, and publishing in a controlled workflow.

View product →

适用读者: 供应商经常更新商品,Shopify 目录已经出现重复页面或关联混乱的团队。

读完可以完成: 建立三层商品身份映射,并决定一次变化应该新建、更新还是忽略。

重复商品的根本原因通常不是标题相同,而是系统不知道供应商记录和 Shopify 商品之间是否代表同一个商业对象。 标题、图片和成本都会变化,因此不能作为唯一身份依据。

三层身份模型

1. 供应商身份

记录:

  • supplier_id
  • supplier_product_id
  • supplier_variant_id
  • source_url

2. 内部草稿身份

记录:

  • internal_draft_id
  • 当前状态
  • 首次添加时间
  • 最近刷新时间
  • 审核负责人

3. Shopify 身份

记录:

  • shopify_product_id
  • shopify_variant_id
  • 当前发布渠道
  • 最近发布时间

核心关系是: 一个供应商商品 → 一个内部主记录 → 一个已关联的 Shopify 商品 如果同一商品有多个供应商,需要额外建立 sourcing relationship,而不是为每个供应商重复创建顾客页面。

新建还是更新:决策规则

情况 建议操作
供应商 ID 新,且无相同商业商品 建立新 Draft
供应商 ID 已存在,已有 Shopify 关联 进入 Update
只是增加颜色或尺寸 评估增加 Variant,不复制商品
产品本质发生变化 人工判断是否建立新品
仅成本或配送信息变化 更新供应商数据,未批准前不覆盖线上

Shopify 官方说明,Duplicate 会创建新的商品;如果只是为现有商品增加颜色或尺寸,应添加 Variant,而不是复制商品。[1]

更新前做字段级比较

不要只显示“供应商商品已更新”。应列出:

  • 原值
  • 新值
  • 字段类型
  • 风险等级
  • 建议行动
  • 是否批准

示例:

字段 现有值 供应商新值 行动
成本 \$18 \$21 重新预览售价
图片 品牌处理版 供应商新图 不自动覆盖
颜色 Black, Blue Black, Blue, Green 审核新增 Variant

保护已经产生价值的 Shopify 商品

发现重复商品时,不要直接删除其中一个。先检查:

  • 哪个商品已经产生订单
  • 哪个商品有评价
  • 哪个商品被广告和外部链接引用
  • 哪个商品使用正确的 URL
  • 哪个商品拥有完整库存与变体数据

随后决定合并、重定向、归档或保留。删除可能影响历史报表和现有链接。

去重检查不应该只做一次

建议在三个时间点运行:

  1. 候选商品进入 Draft 时
  2. 发布到 Shopify 前
  3. 供应商更新准备应用时

检查信号可以包括稳定 ID、GTIN、品牌、型号、关键规格和人工判断。标题相似只能作为提示,不能作为最终依据。 SonarFulfill 通过 Draft、Published 和 Update 关系,把供应商变化连接到既有 Shopify listing。批准更新应替换关联商品的指定字段,而不是再创建一份副本。

今天可以先核对 10 个最近更新的商品

选出最近被供应商更新的 10 个商品,为每个商品并排填写 supplier product ID、internal draft ID 和 Shopify product ID。 先处理身份链缺失的记录:判断它应当关联现有商品、建立新 Draft,还是需要人工确认。不要因为标题相似就合并,也不要在核对前删除疑似重复商品。 当天的产出是一张三层身份映射表,以及需要修复的缺失关联清单。它比一次全店模糊去重更容易验证。

参考资料

继续了解 SonarFulfill

专注于把商品发现、草稿审核、定价和发布连接成可控流程。

查看产品 →

SonarFulfill Team
SonarFulfill connects product discovery, draft review, pricing, and publishing in a controlled workflow. The team publishes one practical article each week.