For: Product teams that want faster publishing without sending raw supplier data straight to the store.
What you can do after reading: Define Product Draft states, fields, and approval rules.
A Product Draft is an internal workspace between a supplier item and a live Shopify listing. It is not a Shopify Draft Order, and it is not the same as the Draft status on a Shopify product. SonarFulfill uses the record to prepare and update a product. Shopify uses product status to control publication.
Why the middle layer matters
Supplier data tells you what the item is. A store still has to decide whether it suits the customer, whether the title and description fit the brand, whether the images can be used, whether variants are complete, whether the price makes sense, whether the catalog already contains the item, and whether the operation should create or update a product.
Shopify products can be Active, Draft, or Unlisted. Shopify notes that a duplicated product set directly to Active is published to the same sales channels as the original. If the merchant needs to choose channels, Shopify recommends keeping it in Draft first.[1]
A minimum data model
Source identity
- Supplier name and supplier product ID
- Original URL
- First-added and last-refreshed times
Product content
- Internal and customer-facing titles
- Description, images, variants, options, specifications, and attributes
Commercial information
- Cost, shipping range, pricing multiplier, price preview, and supplier risk notes
Shopify relationship
- Shopify product and variant IDs
- Sales channels, last-published time, and update status
Three core states
Draft: The item is unpublished and can be edited, compared, or rejected.
Published: The record is linked to a Shopify product. Later changes should target that product.
Update: Supplier data has changed and is waiting for review. A difference does not mean the live field must be overwritten.
State rules
| Current | Trigger | Next |
|---|---|---|
| Draft | Content and pricing approved | Published |
| Draft | Product rejected | Rejected or removed |
| Published | Supplier field changes | Update |
| Update | Selected differences approved | Published |
| Update | Supplier change rejected | Published with current content |
What Product Drafts should prevent
- Unapproved changes to a live product
- Repeated records for one supplier product
- Confusion between supplier cost and profit
- Claims about planned automated purchasing or fulfillment as current capability
- Loss of the Shopify relationship
- Using title similarity as the product ID
A practical approval rule
Before publication, confirm source identity, category, title, description, images, variants, cost, price preview, duplicates, sales channels, owner, and approval time.
SonarFulfill Product Drafts connect product selection, editing, pricing, and publication. The point is not another draft list. It is a record of the current state and the person responsible for the next decision.
Create one Product Draft today
Choose an unpublished item and fill in the supplier ID, source, customer-facing title, cost, price preview, variants, and planned sales channels. Ask another person to review it. Leave one condition unresolved on purpose and confirm that the product cannot be treated as ready. Keep the record as an example for the next draft.
References
SonarFulfill connects product discovery, draft review, pricing, and publishing in a controlled workflow.
