Purchasing already works in Google Sheets: supplier lead times, pack sizes and order approvals sit there. FlexSync's two-way connection lets that team work beside Shopify inventory and make deliberate supported updates from the spreadsheet. The crucial distinction is which cells describe current stock and which merely recommend a purchase. Availability questions answered through Algoshop AI Sales Chatbot depend on the current-stock side of that distinction.
FlexSync connects Shopify inventory and Google Sheets with two-way synchronization. Its useful distinction is that supported spreadsheet edits can become store updates, rather than remaining in a disconnected export. This guide explains the setup, field choices and formula controls—and keeps a purchasing recommendation separate from inventory actually received.
What FlexSync changes about inventory spreadsheets
A CSV export answers “what did inventory look like when I downloaded it?” Synchronization supports a different task: keeping the operational information that staff use connected to the store.
The FlexSync listing describes two-way inventory synchronization, multi-location management, bulk editing and formula-driven stock updates. That is most useful when the spreadsheet is already part of the team's operations: stock review, pricing preparation and approved catalog edits can use the same familiar interface.
The key distinction is two-way access. A report reader may only need stock visibility. An operations editor may intentionally change inventory from a spreadsheet. These jobs should not automatically receive identical editing permissions.
Bring selected Shopify records into the spreadsheet your team already uses.
This can be useful when purchasing already happens in Sheets: supplier notes, lead times and planned quantities can sit beside inventory rather than being retyped into a new export. The team still needs to understand which quantity and location each row represents.
Inventory is not the only task in the listing: product and variant details and prices are also included. Merchandising can prepare catalog updates while purchasing reviews replenishment. However, do not assume every exported field is editable in both directions. The bidirectional sync guide distinguishes lavender-colored editable columns from gray columns that do not currently write back.
The practical advantage is continuity. A merchandiser can work on a selected group of products instead of downloading another full catalog, editing a disconnected file and wondering whether its quantities are still current. Product filtering helps keep the working set relevant; formula-driven updates can serve repeatable rules when those cells are deliberately configured to write back.
Swipe horizontally to read the full table.
| Spreadsheet job | Useful connection | Keep this decision explicit |
|---|---|---|
| Inventory review | Selected stock and location records | Which quantity the row represents |
| Catalog maintenance | Supported product and variant fields | Which edits are approved to reach Shopify |
| Repricing | Supported price fields and configured formulas | Whether the formula is a proposal or a live update |
| Purchasing plan | Stock beside merchant-maintained lead times | A suggested purchase is not stock received |
For a large catalog, the number of synchronized SKUs and formula-driven cells can affect plan choice independently. A sheet with many read-only rows and few writeback formulas has a different requirement from a smaller sheet that actively updates prices and quantities. Check both limits in the current listing before building the operating workbook.
Design the report around variants and locations
Identify the variant and inventory location, not simply the product title. A medium shirt and a large shirt are different purchasing decisions. Do not assume stock at one location is available at another, or redesign the connected tab into a row layout that breaks the app's mapping.
The configuration guide identifies Product ID, Variant ID, Inventory Item ID and Location ID as required, non-editable columns. Preserve those records and select the optional fields needed for the task. Keep SKU as a human-readable label, but investigate blank or reused SKUs before treating them as unique keys.
Swipe horizontally to read the full table.
| Cell responsibility | Fields in the teaching report | What the team may do |
|---|---|---|
| Synchronized record | Variant, location and the selected available-quantity field | Read current stock and verify the exact mapped record |
| Merchant planning | Defined daily sales estimate, supplier lead time, safety stock and reorder formula | Evaluate a buying recommendation without changing Shopify stock |
| Approved writeback | A separately designated supported editable field | Apply an intentional update through the configured connection and inspect the result |
These are workbook responsibilities, not an exported FlexSync template. Daily demand and supplier lead time need defined sources; they should not be inferred from an inventory quantity alone.
Separate synchronized columns from planning columns. Staff should recognize which cells describe Shopify and which express a purchasing assumption without opening another document.
Filters narrow the working set using a field, operator and value. The guide describes them as visibility/sync-scope controls, not product deletion. Apply dashboard configuration changes with Export & Continue; that step is separate from ongoing spreadsheet synchronization. Start with the product group the team actually needs instead of exporting everything and hiding rows manually.
Calculate a complete reorder example
An inventory connection supplies stock data; it does not automatically supply a purchasing policy. A complete reorder calculation requires the merchant's demand estimate, replenishment lead time, safety-stock choice and expected incoming deliveries. Use the team's actual figures, not a fictional SKU treated as an app demonstration.
What a purchasing calculation needs
Demand during replenishment
Use a defined sales period and supplier lead time. Consider whether a promotion or stockout makes that period unrepresentative.
Stock you can use
Read the intended location and quantity. A purchase order awaiting receipt is not automatically available stock.
Incoming deliveries
Record when goods are expected, not just how many were ordered. An arrival after the required date may not solve an immediate shortage.
A buying decision
Review the suggested quantity against supplier pack sizes and minimums. Keep that approval separate from a live inventory update.
This is a merchant planning framework, not a native FlexSync forecast or a customer result. It becomes useful when the workbook makes its inputs and owner visible. If the demand estimate is missing, show that gap rather than presenting a precise-looking recommendation.
Separate report formulas from stock updates
Formula-driven updating is useful when a formula is meant to change Shopify. Purchasing calculations usually serve a different purpose: helping a person choose an order quantity.
Use the connected sheet for supported product edits, not just another export.
Keep reorder suggestions out of stock-writeback columns. A planned purchase is not stock received. The eventual inventory update should follow the merchant's receipt process and verified field/location mapping, rather than copying a target-stock calculation into an editable quantity.
The formula feature guide documents the Allow Sheet Formula control and updates to Shopify every five minutes. A formula result can appear immediately in Sheets while the store waits for the next scheduled update. That is different from assuming every formula recalculation reaches Shopify instantly.
The guide's supplier-data workflow uses an external sheet, an intermediate tab and the connected Products tab. IMPORTRANGE requires access permission before data can flow. Validate the supplier's row mapping and the destination field before enabling live formula updates; permission to read a supplier file is not approval to publish all its values.
Apply the same principle to prices. A margin calculation can evaluate a proposed price, but evaluating it is not authorizing publication. A spreadsheet shared by several teams should not quietly become an unrestricted product-editing interface.
Run a small synchronization pilot
The getting-started guide walks through Google authorization, a generated or existing spreadsheet, selected product data and the supplied Apps Script. The script must be saved, run and authorized; simply exporting rows is not the full bidirectional setup. The dashboard shows connection, spreadsheet and script status so the team can locate a disconnected step.
Use one location and a small set of variants before connecting a large catalog. The following checks are a proposed merchant rollout process, not a test we ran in a live store.
- Record the variant, location and current quantity in Shopify.
- Confirm the corresponding row in Sheets.
- Make one deliberate change through the supported synchronization workflow.
- Verify the result in the other system.
- Restore the intended operating quantity if the test was temporary.
- Confirm that report formulas did not overwrite inventory.
The configuration guide distinguishes Auto Sync from Manual Sync: with Auto Sync disabled, supported edits wait for a manual trigger. Choose that behavior deliberately before staff start bulk editing. Also check formula scheduling separately; changing a cell manually and changing its calculated result are different update paths.
Assign one owner to failed updates. A correct purchasing formula is still unhelpful when the inventory input is wrong and nobody is responsible for fixing it.
Turn the report into a purchasing decision
Review actual stock, incoming deliveries and supplier constraints before approving a purchase. Preserve the difference between calculated need and the chosen purchase quantity, so later reviewers can understand why the team bought more or less than the workbook suggested.
Another useful operation is documented in the cost and inventory-policy guide. Cost Per Item can be maintained from Sheets, while Inventory Policy controls whether a variant continues selling at zero stock: DENY stops out-of-stock sales and CONTINUE permits them. Changing that policy is a selling decision, not replenishment; it does not create physical stock.
Official pages currently differ on order-sync availability: the listing includes it, while an older setup guide still marks orders upcoming. Confirm the data source and editable fields shown in the installed app before planning an order-management workflow. Likewise, an inventory report built by the merchant is not proof that every advertised report or alert is a ready-made template.
FlexSync fits teams that want Sheets to remain part of operations while reducing manual exports. Copying data across separate Shopify stores is a different problem; see the multi-store data guide.
Before rollout, check current SKU and formula limits, choose permissions and pilot one representative location. Explore FlexSync on Shopify or its official website with a specific report in mind, rather than a request to “sync everything.”
