For: Teams monitoring supplier cost, specifications, images, and shipping without giving suppliers control of the live listing.
What you can do after reading: Set refresh triggers, field risk levels, and an approval matrix.
A supplier refresh should fetch and compare new source data. It should not automatically change the Shopify product. Refresh and publish update are separate actions. Combining them gives a supplier an indirect path to edit the live page.
When to refresh
Event triggers
- The supplier reports a cost change.
- Availability or variants change.
- The shipping range changes.
- A customer says the specification does not match the item.
- The team plans a promotion or restarts advertising.
- An old product is being considered for publication again.
Time triggers
Check high-volume or high-risk products more often. Stable long-tail products can use a slower schedule. Refresh an old unpublished draft before publication. One frequency does not fit every product.
Classify field risk
| Risk | Examples | Action |
|---|---|---|
| High | Cost, variants, specifications, safety | Human review required |
| Medium | Shipping range, images, packaging | Compare and approve |
| Low | Internal tags and private notes | Rule-based update may be suitable |
A published product usually carries more risk because saved Shopify changes can affect the live page immediately.[1]
Use an approval matrix
Cost increase
Update the supplier cost and recalculate the price preview. Do not change the live price automatically. The pricing owner decides.
New variant
Confirm that it can be sold, then check images, specifications, inventory, and option naming before adding it to the linked product. Shopify treats each combination of option values, such as size and color, as a variant.[2]
Description change
Compare the new source with the store's current copy. Keep reviewed brand language, extract new verified facts, and do not replace the whole description.
Image change
Check watermarks, rights, proportions, and variant links. Do not delete the current set automatically. Let the content owner decide the order.
Record every refresh
Save the time, source, changed fields, old and new values, reviewer, decision, and Shopify application time. This record explains why a field changed and supports rollback.
Example
A published product changes in three ways: cost rises from $18 to $21, a Green color appears, and the supplier description adds "100% waterproof." Send the cost to pricing review without changing the live price. Review the Green variant with its images and inventory. Do not publish the waterproof claim without evidence. Keep the existing brand description and apply approved fields to the same Shopify product.
SonarFulfill's current boundary
SonarFulfill currently supports manual refreshes for drafts and related product data. New supplier information enters a reviewable Update state before approved fields reach Shopify. It does not automate purchasing or fulfillment. The aim is controlled product data, not perfect real-time copying of the supplier page.
Refresh one published product today
Choose a high-volume or high-risk product. Fetch the latest supplier data and list every changed field with its old value, new value, and source. Assign a risk level and mark each change approved, rejected, or waiting. Do not overwrite the product as one block.
References
- Shopify Help Center: Adding and updating products
- Shopify Help Center: Variants
- Shopify Help Center: Product details page
SonarFulfill connects product discovery, draft review, pricing, and publishing in a controlled workflow.
