Shopify shifts inventory analytics to on-hand quantity from Sept 1, 2026 — what merchants must do now

Table of Contents

1. Key Highlights
2. Introduction
3. Why on-hand versus available matters: clarifying the two measures
4. Practical example: how numbers can change in one snapshot
5. Which Shopify reports and models will reflect the change
6. How the change affects ShopifyQL queries and saved analytics
7. KPI impacts: what moves and why
8. Accounting, finance, and audit implications
9. Operational and supply chain impacts
10. Integrations and external systems: where conflicts arise
11. Preparing your analytics and dashboards: practical steps
12. Policy and governance: documenting the change for teams and auditors
13. Common pitfalls and how to avoid them
14. Real-world scenarios: how different business models are affected
15. Step-by-step checklist for the 90 days before September 1, 2026
16. Communication templates and messaging suggestions
17. Measuring success and validating the transition
18. Tools and techniques for reconciliation and diagnostics
19. Long-term benefits of aligning analytics with physical inventory
20. FAQ

Key Highlights

• Beginning September 1, 2026, Shopify’s inventory analytics models will report on-hand quantity (all units physically at a location) instead of available quantity (units available to sell).
• Reports and ShopifyQL queries that read FROM inventory or FROM inventory_by_location will show higher inventory counts where units are committed or marked unavailable; historical data before the change remains unchanged.
• Merchants must audit dashboards, update automations and reorder settings, reconcile with accounting systems, and communicate the change to operations and finance teams to avoid misinterpretation of KPI shifts.

Introduction

Shopify is changing how inventory is measured inside its analytics stack. Starting September 1, 2026, the platform will treat "on-hand quantity"—every unit physically present at a location—as the standard input for its inventory analytics models. Until now, many reports used "available quantity," which excludes units already committed to orders or otherwise unavailable for sale. The shift affects core reports such as sell-through rates, days-of-inventory remaining, month-end valuations, and any metric derived from the inventory models. The technical trigger is simple: any ShopifyQL query that uses FROM inventory or FROM inventory_by_location will now reflect on-hand counts for dates on or after September 1, 2026.

This change aligns analytics with what warehouses and counting systems physically hold. It also creates immediate reporting and operational implications. Merchants who treat inventory numbers as actionable—feeding reorder rules, driving finance close processes, or firing automated purchases—must prepare now to avoid disruptions and misreads in their KPIs.

The sections that follow explain the difference between on-hand and available, list exactly which reports change, show how ShopifyQL queries will behave, outline downstream impacts on accounting, forecasting, and automation, and provide a practical, time-phased checklist that operations, analytics, and finance teams can implement in the months leading up to the switch. Real-world examples and common pitfalls are included so teams can reconcile numbers, adjust thresholds, and preserve decision continuity across the transition.

Why on-hand versus available matters: clarifying the two measures

Inventory language is precise because small differences in definitions change business decisions. Two terms drive this update:

• On-hand quantity: Every unit physically present at a location. This includes items that are reserved against open orders, items quarantined for quality control, and units otherwise unavailable for sale.
• Available quantity: Units that are free to sell—on-hand quantity minus units committed to orders or explicitly marked unavailable.

Both metrics matter. Available quantity helps front-facing systems show what customers can buy. On-hand quantity is the ground truth for warehouse planning, month-end valuation, and understanding actual physical stock positions. Until now, Shopify’s analytics used available quantity in many reports—producing metrics that reflected sellable stock rather than what the business physically held. The platform’s pivot to on-hand quantity aims to align analytics with physical reality.

Why that alignment matters: finance and operations reconcile inventory counts against physical stock during cycle counts or monthly snapshots. When analytics present a figure equal to what physically exists, investigating discrepancies becomes simpler. Planners and demand forecasters also benefit because committed and unavailable stock still consumes space, triggers handling costs, and should influence procurement decisions.

Yet the change has collateral effects. When analytics start reporting higher inventory by including reserved or quarantined units, common KPIs will shift. Teams will see higher days-of-inventory, lower sell-through rates, and increased month-end values without any actual change in receipts or sales. Understanding and managing that interpretive gap is the core operational challenge of the transition.

Practical example: how numbers can change in one snapshot

A concrete example makes the impact visible.

Consider a product with the following position on August 31, 2026 (analytics using available quantity):

• Physical stock at location: 100 units
• Committed to open orders: 20 units
• Unavailable (quality hold, reserved for a promotion): 10 units
• Available quantity (sellable): 70 units

On August 31, Shopify reports 70 units in analytics that use available quantity.

On September 1, Shopify’s analytics model switches to on-hand quantity for new snapshots. The same product would be reported as:

• On-hand quantity: 100 units

Reports that previously showed 70 units will now show 100 units for a comparable snapshot date. That 30-unit difference will change ratio-based KPIs and monetary valuations. If your reorder rules or dashboards were tuned to act when available quantity drops below 50 units, seeing 100 units instead of 70 could delay replenishment unless thresholds are adjusted.

A few small numbers produce large downstream effects across dozens of SKUs, and those effects magnify in aggregate financial statements.

Which Shopify reports and models will reflect the change

Shopify has identified specific reports and analytic models that will switch to on-hand as their stock input from September 1 onward. The change will be visible wherever the analytics models read from the inventory models. Key impacted reports include:

• Products by sell-through rate
• Products by days of inventory remaining
• Inventory adjustment changes
• Inventory sold daily by product
• ABC product analysis
• Month-end inventory value
• Inventory transfer orders and shipments
• Month-end inventory snapshot

Any custom reports or dashboards that derive values from the platform’s core inventory analytics will also reflect on-hand counts. That includes internal dashboards that combine Shopify’s analytics with external data sources where the inventory measure is pulled from Shopify.

Reports dated before September 1 remain unchanged. Shopify retains historical data as reported under the old definition (available quantity), so trend charts spanning the change date will show a discontinuity unless teams normalize or annotate them.

How the change affects ShopifyQL queries and saved analytics

Queries that use FROM inventory or FROM inventory_by_location will now return on-hand values for snapshots taken September 1 or later. For merchants and analysts who use ShopifyQL:

• Existing saved queries that do not explicitly filter for time will now return on-hand numbers when run against dates on or after September 1.
• Queries that combine Shopify inventory fields with external inputs must be revalidated to ensure both sources use compatible measurement definitions.
• Any automated extracts that feed BI systems (for instance, nightly exports) will begin delivering on-hand values for the new dates.

Recommended immediate actions for those who regularly use ShopifyQL:

• Identify all saved queries and dashboards that reference FROM inventory or FROM inventory_by_location.
• Run baseline exports for a representative set of SKUs before September 1 and again after the change to compare outputs.
• Annotate any dashboards or time-series charts that span the change date to explain the shift in inventory definition to end users.

Avoiding misinterpretation is the primary objective. A simple, documented comparison for your top SKUs makes conversations with stakeholders factual: the numbers did not change because of stock movement; the analytic input definition changed.

KPI impacts: what moves and why

Switching from available to on-hand moves several metrics in predictable ways. Teams must adjust thresholds and re-evaluate the meaning of those KPIs.

Sell-through rate

• Effect: Sell-through rates will typically appear lower after the switch, since the denominator increases when reserved and unavailable units are included.
• Why it matters: Marketing and replenishment teams that use sell-through for product performance scoring should recalibrate thresholds for classification or promotion eligibility.

Days of inventory remaining (DOIR)

• Effect: DOIR will increase for SKUs with a material number of committed or unavailable units.
• Why it matters: DOIR influences purchasing cadence and carrying cost estimates. Increased DOIR could signal excess stock when the real issue is reserved inventory.

Inventory turnover

• Effect: Turnover ratios may decline because inventory on hand rises while sales remain unchanged.
• Why it matters: Turnover is often tracked by finance and used in covenants or performance reviews. A visible change requires explanation and possibly re-benchmarking.

Month-end inventory value

• Effect: Monetary valuations based on on-hand quantities will likely be higher for period-end snapshots that include reserved/unavailable units.
• Why it matters: Accounting teams must reconcile valuation outputs to cost accounting and reconcile with ERP or general ledger entries. The distribution of when units are considered in analytics versus financial records needs alignment.

Inventory adjustments and transfer reports

• Effect: Reports that show adjustments, transfers, and shipments will be computed against on-hand quantities, making audit trails more aligned with physical stock movements.
• Why it matters: Discrepancies caused by committed or quarantined units will be easier to identify, but automation that assumes available counts might need retuning.

ABC product analysis

• Effect: SKU classification by inventory value or quantity may shift. Products with reserved stock can move between classes.
• Why it matters: Prioritization, allocation of working capital, and shelf-space decisions are often derived from ABC analysis. Teams should re-run classifications after the transition to understand changes.

Inventory sold daily by product

• Effect: Sales rates are unchanged; however, the relationship between sales and inventory will change visually because inventory snapshots will now be larger.
• Why it matters: Visual dashboards that compare sales to inventory should annotate the change date to avoid false conclusions.

Accounting, finance, and audit implications

Analytics and financial accounting often operate on different definitions; this change narrows one gap but introduces transition mechanics that finance teams must manage.

Historical continuity

• Shopify preserves prior data. Figures dated before September 1 remain reported as available quantity. The platform will not retroactively change historical numbers. This prevents altering past financial reports but introduces a break in trends.

Reconciliations

• Month-end processes that compare Shopify analytics to the ERP or general ledger must update reconciliation scripts. Differences may appear if the ERP uses available quantity or a different on-hand definition.
• If accounting recognizes inventory based on physical counts or receipt/issue records, make sure month-end snapshots are taken on consistent definitions and times.

Valuation methods

• The inventory valuation method (FIFO, LIFO, weighted average) remains independent of the inventory quantity definition. Teams must ensure that the monetary unit cost is applied consistently to the on-hand counts reported by Shopify.
• Where inventory is quarantined or classified as damaged, accounting teams must consider whether those units should be fully valued, impaired, or tracked separately when preparing financial statements.

Audit trails and internal controls

• Stock counts, cycle counts, and audit adjustments will align more directly with analytics that show physical stock positions. That reduces time spent reconciling booked but unavailable quantities.
• Internal controls tied to inventory triggers—such as automated write-offs or approvals—should be reviewed. Controls that trigger based on available counts may no longer behave as expected.

Regulatory and tax considerations

• The change to analytics reporting does not alter legal ownership or tax treatment of inventory. However, management should document the analytics definition change for auditors and ensure consistent presentation in reports that rely on Shopify outputs.

Practical steps for finance

• Map where Shopify analytics feed into financial close processes, then update reconciliation templates to compare like-for-like definitions.
• Ensure auditors and external accountants receive documentation about the definition change and any adjustments made during the transitional month.
• Consider running a controlled parallel reconciliation for the first two months after the switch to capture edge cases.

Operational and supply chain impacts

Warehouse teams, fulfillment providers, and supply planners feel this change quickly because it tracks the units they physically handle.

Reorder points and automated purchases

• Risk: Automated replenishment rules based on analytics that formerly used available quantity may delay or accelerate orders if thresholds are not recalibrated.
• Action: Reconfirm reorder points and safety stock calculations using on-hand as the inventory input. Where possible, isolate replenishment logic from a single source-of-truth and make sure that source now reflects the new definition.

Pick and pack operations

• Visibility: On-hand reporting will include units reserved for orders in the analytics layer, but warehouse pick systems and order management should still rely on live reservation statuses for picking.
• Coordination: Ensure fulfillment and warehouse teams understand that analytics numbers include committed stock and that picking screens continue to show true pickable inventory.

Cycle counting and physical audits

• Alignment: Cycle counts should reference on-hand metrics to reduce variance explanations. If the count workflow previously compared to available quantities, update count sheets and variance thresholds.
• Frequency: Consider increasing cycle count frequency during the transition month to identify mismatches between analytic snapshots and physical counts.

Fulfillment partners and 3PLs

• Interface review: Confirm how 3PL feeds and EDI messages map to Shopify’s on-hand concept. If third parties report available quantities, reconcile mapping in integration logic.
• SLA adjustments: Contracts or SLAs that use inventory KPIs for service-level calculations should be reviewed and reworded if they implicitly reference available quantities.

Warehouse management and quality holds

• Quarantines and unavailable stock: The inclusion of unavailable units in on-hand counts highlights quarantined inventory in analytics. Teams should maintain clear status taxonomy—quarantined, reserved, damaged—so downstream analytics accurately reflect handling needs.
• Space planning: On-hand analytics helps with space allocation and labelling, because reserved and unavailable units still occupy space and resources.

Integrations and external systems: where conflicts arise

Many merchants use third-party ERP, WMS, or BI systems that ingest Shopify inventory data. Differences in inventory definitions between systems will create mismatches unless reconciled.

Common integration mismatches

• ERPs that pull "available" stock from Shopify APIs may continue to show the previous view if they map to the older definition. Confirm the API fields and their semantics with your integration vendor.
• WMS solutions often operate in real time and track reservations separately. When combining WMS feeds with Shopify analytics, ensure both streams are normalized to the same inventory definition before driving decisions.
• BI platforms that join Shopify exports with purchase orders or supplier lead times must be checked for assumptions tied to available quantities.

Mitigation steps

• Conduct an inventory definition audit across all endpoints that consume Shopify inventory data.
• Update ETL scripts to tag whether the ingested Shopify snapshot uses "available" or "on-hand" and make transformations explicit.
• For mission-critical automations, implement a one-month parallel run where both available and on-hand figures are stored and compared.

Vendor communication

• Notify integration vendors, 3PL partners, and other data consumers about the change and request that they confirm how they map Shopify fields into their systems.
• If you rely on a managed service for analytics or inventory orchestration, request a timeline for their adjustments and testing.

Preparing your analytics and dashboards: practical steps

Teams should treat this change like a schema migration for inventory. Follow a structured plan to minimize surprises.

Inventory analytics playbook — a phased approach

1. Discovery (Now)
   • Inventory all dashboards, reports, saved ShopifyQL queries, automations, and scripts that reference inventory.
   • Flag all items that use FROM inventory or FROM inventory_by_location, or that do not explicitly document which stock definition they use.
2. Baseline snapshot (4–6 weeks before change)
   • Export current available quantity outputs for a representative SKU set and store them.
   • Capture corresponding financial and operational metrics.
3. Update test queries (2–4 weeks before change)
   • Where possible, create test queries or test views that can run against a sandbox or a staging feed to preview on-hand outputs.
   • If no staging is available, plan for a controlled run on Sept 1 with comparison scripts.
4. Recalibrate thresholds and automations (1–3 weeks before change)
   • Adjust reorder points, safety stock, and alert thresholds to accommodate larger on-hand numbers.
   • Update automated purchase orders and rules that rely on inventory counts.
5. Communicate (1–2 weeks before change)
   • Inform operations, finance, product, and executive teams of the date and expected effects. Share comparison examples.
   • Prepare FAQs and a brief training packet for internal teams.
6. Switch-over and verification (Sept 1)
   • Run comparison exports for a small set of SKUs and validate that on-hand numbers align with physical counts.
   • Monitor dashboards and alerting systems for unexpected triggers.
7. Post-change stabilization (first 30–60 days)
   • Continue parallel monitoring, adjust thresholds further if needed, and finalize documentation.

Visualization recommendations

• Add an annotation line on time-series charts at the September 1 boundary to call out the analytics definition change.
• Where possible, preserve both metrics—available and on-hand—in dashboards used for decision-making so users can toggle views.
• Introduce meta-metrics that show reserved and unavailable units explicitly; reporting both available and reserved slices clarifies the composition of inventory.

Policy and governance: documenting the change for teams and auditors

Create a short governance memo that records:

• The precise effective date (September 1, 2026).
• The definition of on-hand used by Shopify analytics.
• A list of all affected dashboards, automations, and downstream consumers.
• Contacts for analytics, operations, and finance who own remediation.
• A change-log entry in the analytics governance repository.

This memo serves auditors, third-party integrators, and new team members. It also reduces repeated explanations and prevents misclassification of KPI changes later.

Common pitfalls and how to avoid them

Several predictable mistakes recur when systems change the metric foundation. Address these in advance.

Pitfall: Ignoring saved automations and triggers

• Symptom: Automated purchase orders fail to trigger or trigger at the wrong time after the switch.
• Avoidance: Audit all automations and update threshold logic before Sept 1.

Pitfall: Misreading KPI trends

• Symptom: Leaders misinterpret the abrupt changes in DOIR or sell-through as a deterioration in performance.
• Avoidance: Add prominent annotations and include both pre- and post-change narratives in executive dashboards.

Pitfall: Divergent definitions across systems

• Symptom: ERP reports show one number while Shopify analytics show another, causing reconciliation disputes.
• Avoidance: Align definitions across systems; if alignment is impossible quickly, store both versions and document the use-case for each.

Pitfall: Relying on static documentation

• Symptom: Teams refer to old documentation and fail to adjust processes.
• Avoidance: Use living documentation in shared spaces and mark it with the change date and owners.

Pitfall: Delaying communication

• Symptom: Front-line staff first encounter surprise metrics during a business-critical period.
• Avoidance: Communicate early and frequently with operations, finance, marketing, and customer success teams.

Real-world scenarios: how different business models are affected

Different types of merchants will feel the shift in unique ways. These scenarios highlight concrete effects and practical changes.

Case 1 — High-volume consumer electronics retailer

• Situation: The retailer holds large quantities of pre-ordered stock, much of which is committed to subscriptions or pre-orders.
• Impact: On-hand counts increase materially compared to available counts. Sell-through rate appears depressed because pre-orders reserve units.
• Action: Separate pre-order reserved quantities in reporting to measure true customer demand velocity; keep on-hand for warehousing and valuation.

Case 2 — Multi-channel brand with third-party logistics (3PL)

• Situation: Inventory is split across multiple 3PL partners and a Shopify-hosted warehouse. Some warehouses report available stock more frequently than others.
• Impact: Analytics consolidation now reflects on-hand inclusively. Integration mismatches may surface where 3PLs do not report unavailable/reserved flags consistently.
• Action: Standardize status taxonomy across 3PLs and implement ETL normalization to align feeds.

Case 3 — Subscription box company

• Situation: Large pools of inventory are reserved for upcoming scheduled shipments.
• Impact: On-hand reporting shows higher stock because reserved units are included. Available stock for single-order customers may be low despite high on-hand.
• Action: Report both on-hand and available to different stakeholders: operations uses on-hand; sales and storefronts rely on available.

Case 4 — International seller with cross-border transfers

• Situation: Inventory in transit is tracked but not available for sale until received.
• Impact: On-hand at origin decreases when transfers are shipped; on-hand at destination increases only upon receipt. Transfer reports will now reflect on-hand behavior accurately where local quarantines exist.
• Action: Sync transfer-order workflows and reconcile shipment in-transit flags with analytics snapshots.

Step-by-step checklist for the 90 days before September 1, 2026

90–60 days out

• Inventory audit: Identify all systems and stakeholders that consume Shopify inventory analytics.
• Saved query inventory: Export and list every ShopifyQL saved query that references FROM inventory or FROM inventory_by_location.
• Stakeholder mapping: Create a list of owners for dashboards, automations, and integrations.

60–30 days out

• Baseline exports: Run and store baseline available-quantity exports for a representative sample of SKUs.
• Integration review: Contact integration vendors and 3PL partners to confirm mapping and testing schedules.
• Threshold review: Review reorder points, safety stock, and triggered automations tied to inventory counts.

30–14 days out

• Run test comparisons: For queries that can be rerun in a controlled way, compare outputs and quantify differences by SKU and location.
• Communication plan: Finalize an internal communication that includes date, expected impacts, and an FAQ.
• Training: Provide short training sessions for finance, ops, and customer service teams on interpreting post-change reports.

14–1 days out

• Update dashboards: Add annotations or toggle options showing available vs. on-hand where appropriate.
• Freeze risky changes: Pause any non-critical inventory rule changes near the change date to avoid compounding variables.
• Confirm on-call roster: Assign owners to monitor dashboards and address incidents in the first 48–72 hours after the change.

Day 0 (September 1)

• Run validation exports for a short representative set of SKUs and reconcile to physical counts where practical.
• Monitor alerts and dashboard anomalies; triage unexpected triggers.
• Communicate to stakeholders that the change has taken place and provide initial comparison findings.

30–90 days after

• Stabilize: Finalize updates to thresholds and automations.
• Reconcile: Ensure finance and operations complete reconciliation across the period end.
• Document lessons learned and update governance materials.

Communication templates and messaging suggestions

Clear, concise communication prevents confusion. Below are examples of short messages for different audiences.

Email to operations/warehouse teams Subject: Shopify inventory reporting change effective Sept 1 — what operations needs to know Body (summary):

• On Sept 1, Shopify will change analytics to report on-hand quantity (all physically present units) rather than available quantity.
• Expect dashboards to show higher inventory for SKUs with reserved or quarantined units.
• Continue using pick/pack systems for live picking decisions. We will update stock thresholds and run validation counts on Sept 1 morning.
• Contact [name] for any anomalies observed.

Email to finance and accounting Subject: Shopify analytics definition update — impact on month-end inventory reporting Body (summary):

• Effective Sept 1, Shopify analytics will use on-hand quantity for reports dated that day and later. Historical data prior to Sept 1 remains unchanged.
• Expect increases in reported month-end inventory value if reserved or unavailable units exist at locations.
• We will perform a parallel reconciliation for September and document adjustments for auditors.
• Please coordinate any accounting recognition questions with [owner].

Slack message to BI and analytics

• Heads up: Shopify switches inventory analytics to on-hand on Sept 1. Review saved queries referencing FROM inventory/ FROM inventory_by_location. We'll run comparison exports and flag dashboards that need annotations.

Customer-facing messaging

• Retailers generally should not need to inform customers of this backend analytics change unless customers are impacted by fulfillment visibility. If customers use storefront inventory counts, confirm that storefront availability continues to reflect sellable stock.

Measuring success and validating the transition

Define success criteria in advance and measure against them during the post-change period.

Suggested success criteria

• All critical dashboards updated and annotated by Sept 7.
• No automated purchase orders triggered improperly in the first two weeks.
• Finance successfully reconciles month-end valuations without material audit adjustments.
• Less than X% variance between analytics on-hand and physical cycle counts for a representative SKU set (choose an acceptable variance based on business context).

Validation activities

• Run SKU-level comparisons between baseline exports and post-change exports.
• Reconcile inventory valuations and investigate individual SKUs where the delta exceeds a pre-defined threshold.
• Collect feedback from warehouse, customer service, and finance for two weeks post-change.

If objectives are not met, escalate to a cross-functional working group and consider temporary mitigations such as pausing automated replenishment or reintroducing manual checks for high-value SKUs until adjustments are complete.

Tools and techniques for reconciliation and diagnostics

Use practical diagnostics to accelerate troubleshooting.

Sample reconciliation approach

1. Select a sample set of SKUs representing high-volume, high-value, and low-velocity items.
2. Export available quantity (pre-change snapshot) and on-hand quantity (post-change snapshot) for each.
3. Break down the difference into components:
   • Units reserved in open orders
   • Units in quality holds or quarantines
   • Units in-transit or in transfer between locations (if Shopify treats those as part of on-hand)
4. Adjust dashboards to show these components explicitly for future visibility.

Diagnostic queries and automation

• Automate a daily delta report for the first 30 days that calculates percent difference between available and on-hand for top SKUs and alerts when deltas exceed normal thresholds.
• Build a crosswalk table that stores both quantities with timestamps for audit and trend analysis.

Visualization tips

• Use stacked bars that show how on-hand splits into available + reserved + unavailable. Readers grasp compositional differences faster than single numbers.
• Highlight the change date and include a short note on the visualization explaining why the composition changed.

Long-term benefits of aligning analytics with physical inventory

Short-term work enables long-term gains.

Better alignment with physical processes

• Warehouses and auditors benefit from analytics that mirror physical stock, which simplifies investigations and reduces reconciliation cycles.

Improved capacity and space planning

• On-hand visibility shows the full burden of inventory on warehouse space, enabling smarter slotting and labor planning.

Cleaner audit trails

• Including reserved and quarantined units in analytics improves the traceability of adjustments and the visibility of exception handling for auditors.

More realistic working-capital metrics

• Finance teams can base working capital forecasts on on-hand counts to reflect the capital tied to inventory physically in possession, regardless of sellability.

FAQ

Q: Will historical data change? A: No. Shopify does not change historical reports. Data dated before September 1, 2026 will continue to reflect the previous standard (available quantity). Only reports and snapshots dated on or after September 1 will use on-hand quantity.

Q: Which reports will show the new on-hand figures? A: Reports that derive their inventory figures from Shopify’s inventory analytics models will now use on-hand. Shopify explicitly lists affected reports such as products by sell-through rate, days of inventory remaining, inventory adjustment changes, inventory sold daily by product, ABC product analysis, month-end inventory value, inventory transfer orders and shipments, and the month-end inventory snapshot. Any custom report that queries FROM inventory or FROM inventory_by_location will also reflect on-hand for snapshots taken on or after September 1.

Q: How will this affect my sell-through rate and days of inventory remaining? A: Sell-through rates will generally appear reduced because the denominator (inventory) increases when reserved and unavailable units are included. Days of inventory remaining will typically rise for SKUs with material reserved or quarantined units. These are changes in reported context rather than changes in underlying physical sales or receipts.

Q: Do I need to update my ShopifyQL queries? A: Review saved queries that use FROM inventory or FROM inventory_by_location. While the SQL-like syntax remains the same, the underlying inventory field semantics for dates on or after September 1 will be on-hand. Revalidate query logic, exports, and any downstream transformations.

Q: Will my storefront availability change for customers? A: No. This change affects analytics models. Storefront availability should still present sellable quantities (available to buy). Confirm that any storefront inventory APIs or displays remain tied to the available quantity if that is the intended behavior.

Q: What should finance and accounting teams do differently? A: Update reconciliation templates, treat the analytics definition change as a documented accounting policy event for auditors, and run parallel reconciliations for the first month after the change. Confirm cost application methods remain consistent when performing month-end valuations.

Q: How should I update automations and reorder rules? A: Re-evaluate reorder points and safety stock levels using on-hand as the input. Where automations drive replenishment based on analytics, test and adjust thresholds in a controlled manner to prevent over- or under-ordering.

Q: My integrations show different numbers after the change. What now? A: Conduct an integration audit to map which system consumes available vs. on-hand counts. Update ETL scripts or mapping logic to normalize definitions. If immediate alignment is not practical, preserve both quantities in your data warehouse and use them explicitly where appropriate.

Q: Who should I notify internally about the change? A: Operations, warehouse managers, finance and accounting, business intelligence, product managers, and any teams that use inventory analytics for decisions should be notified. Also inform integration vendors and fulfillment partners.

Q: What if I discover major discrepancies between on-hand analytics and physical counts? A: Follow your normal variance investigation process: isolate the SKU and location, examine reservation and unavailable flags, check recent transfers and adjustments, and audit pick-and-pack records. If discrepancies persist, escalate to cross-functional teams for root cause analysis.

Q: Where can I get help performing an audit or updating dashboards? A: Internal BI and operations teams should lead the initial audit. For complex integrations, coordinate with your ERP, WMS, or 3PL vendors. Consider engaging a Shopify partner or consultant experienced in inventory data migrations for a time-bound project.

Q: Will on-hand include items in transit between locations? A: The practical inclusion of in-transit items depends on how Shopify models transfers and whether the in-transit location is considered a counted location. Confirm with Shopify’s API and transfer documentation and with your transfer workflows to understand whether items marked in-transit are treated as on-hand at either origin or destination during different phases of transit.

Q: Is this change reversible? A: Shopify will apply the on-hand definition for analytics from September 1 onward. Historical data remains unchanged. Reverting analytics definitions retroactively would undermine historical continuity. If you need different views for decision-making, maintain both available and on-hand in your internal reporting schema.

Q: How do I explain the change to executives who are focused on KPIs? A: Provide side-by-side examples for representative SKUs and top-level metrics, annotate dashboards with the change date, and present a short impact summary that quantifies typical KPI shifts. Stress that the underlying operations did not change; only the analytic lens did.

---

Adopt a pragmatic approach: document what changed, show quantified examples, adjust automations and thresholds, and treat the first month after September 1 as a controlled observation window. Aligning analytics to physical inventory brings clearer warehouse visibility and cleaner audit trails, but it requires coordinated work across analytics, operations, and finance to prevent misreadings and maintain smooth decision-making.