Before connecting Shopify to a product management system, decide where descriptions, images, prices, and inventory should be edited and which way each field should flow. A sync that updates product information as a group may replace a description you have improved in Shopify with content from another system. Keeping price and inventory updates running while preserving that description requires rules for each field.
The starting point is the same whether you use a spreadsheet or a business management system. The tables below help ecommerce, product, and inventory teams agree on those rules before setting up a connection.
Why an edited description returns to its old version
Imagine an external product spreadsheet contains a short description. An ecommerce team member adds headings and usage guidance in Shopify. If a nightly sync sends the spreadsheet description to Shopify every time, those additions will be overwritten by the next morning. This is an illustrative workflow.
Editing the description again in Shopify will not resolve the problem while the sync keeps sending the same text. Check both which version is newer and which system is supposed to hold the version you want to keep.
| Stage | External product spreadsheet | Shopify description |
|---|---|---|
| Before editing | Short description | Short description |
| After the ecommerce team edits it | Still the short description | Headings and usage guidance added |
| After a sync that overwrites the description | Still the short description | Back to the short description |
Start by checking the integration settings and processing history to see whether descriptions are included in updates. Scheduled updates and a “sync now” action may update different fields. Confirm the scope of each action in the tool you use.
Assign an editing source and an owner to each field
The editing source is where a team member makes a change. Every field does not need to share the same source. This example assumes the ecommerce team manages descriptions and images, while other teams manage prices and inventory.
| Field | Editing source and destination | When to update | Owner and check |
|---|---|---|---|
| Product description | Edit in Shopify; exclude external overwrites | When content needs revising | Ecommerce team checks the product page |
| Product images | Add and reorder in Shopify | When photography is ready | Ecommerce team checks images and display order |
| Regular price | External product spreadsheet to Shopify | After a price change is approved | Product team checks the products and resulting prices |
| Inventory | Inventory system to the corresponding Shopify location | Agree on timing alongside stock movements and order processing | Inventory team checks what the quantity means and when it was last updated |
Regular prices and temporary discounts may have different owners and update methods. Give them separate rows if needed. For images, record where deletions and reordering take place as well as where files are added, so team members follow the same rule.
Also separate initial product creation from later updates. If you want to send an external description once and edit it in Shopify thereafter, check whether your tool can make that distinction. A rule written in the table is not a guarantee that your current tool supports it.
Match products, SKUs, and warehouses
Correct field rules will not help if an update targets the wrong product. Check which Shopify product and variant correspond to each external product. For products with colors or sizes, compare the option combination as well as the product name.
If your integration matches products by SKU, check that both systems use the same SKU and look for blanks or duplicates. If it uses internal product IDs, changing a SKU alone may not change the connection. Confirm which identifier the tool uses to match records.
Inventory also needs a warehouse mapping. If the external system separates Warehouse A and Store B, decide which Shopify location receives each quantity. Record whether you are sending quantities for individual sites or a total across several sites.
Agree on what the inventory quantity means
Shopify distinguishes inventory physically on hand at a location from inventory available to sell. On hand is the total of Available, Committed, and Unavailable. Incoming inventory is not part of Available. Shopify’s guide to inventory states
When planning an integration, establish what the external system’s “stock quantity” represents. Does it already subtract units needed for orders? Does it include items awaiting inspection? The answers determine which Shopify quantity it corresponds to. Agreeing to “sync inventory” does not settle this.
Check when orders are sent to the external system and when inventory is sent back to Shopify. Record which orders each system has included at each point, so the integration can avoid counting an order-related reduction twice or sending an older quantity again.
Plan for manual corrections and failed updates
Decide what the next sync should do after an urgent price or inventory correction. Normally, make corrections in the agreed editing source. If someone must edit Shopify directly, the exception procedure should identify who pauses and resumes the integration and who corrects the source system.
| What happened | What to check | What to agree in advance |
|---|---|---|
| A manual correction was overwritten | The source of the value and the sync time | Where the correct value should be kept and who fixes it |
| Only some products failed to update | Product matching and error details | Which records to resend and who resends them |
| Inventory updates stopped | The last successful update and current quantities | Who decides whether sales can continue and who must be contacted |
| The sync says it is complete, but the content is wrong | The actual values for the intended product, field, and location | When to request an investigation and what records to keep |
“Sent,” “processing finished,” and “Shopify contains the expected value” are separate checks. Before resending every product after a failure, establish which products and fields were updated. If a retry also changes descriptions or images, check its effect on those fields.
When using a CSV file
Decide which fields to update before importing a CSV. When overwriting products with matching handles in Shopify’s product CSV import, a blank cell in an optional column clears the existing value. Omitting that optional column preserves it. Required and variant-related columns have additional conditions, so check the official guidance before removing columns. Shopify’s product CSV guidance
Even when you only intend to change prices, check whether descriptions, images, or other fields remain in the file. Save the data before making changes, and review both the fields you plan to update and those you intend to leave unchanged before importing.
What your team can prepare before asking for help
Your team can list the editing source, owner, and update timing for each field, together with the tools you currently use. If a value has reverted, keep the content before and after editing, the times, and the action that was performed. These records make it easier to trace which integration changed what.
If you are unsure whether a sync can be separated by field, several apps update the same field, or order and inventory quantities do not agree, the next step is to review the settings and data flow together. Contact Popaz with the tools you use and the edits you want to preserve.
