Admin / Changed

Two modes for inventory adjustment: Set To and Adjust By
Every change records who moved it, when, and where

The inventory adjustment popover in the admin has been redesigned. It explicitly separates overwriting quantities from "moving" them, and the adjustment history now retains the source, destination, who performed it, and the date/time.

What's on this page
  1. What actually changed (understand it in 30 seconds)
  2. The two modes: Set To / Adjust By
  3. How it works: the flow after you move inventory
  4. The 4 items that get recorded
  5. Relationship with the Bulk Editor
  6. When to use which
  7. 5 points developers should know
  8. 3 use cases you can apply to your operations
  9. A one-line summary you can use in proposals

1What actually changed

In the admin's inventory adjustment popover, two modes—"Set To" (set the quantity) and "Adjust By" (move it up or down)—now sit side by side.
Regardless of the mode, every adjustment with its source, destination, who performed it, and date/timeis kept in the history.
No record

Before: you couldn't trace what happened

Even when you rewrote a quantity, who moved it, why, and from where wasn't kept in the history—or it wasn't clear how to keep it. Tracing the cause of stocktake errors was difficult.

From now on: every adjustment is logged automatically

Whether Set To or Adjust By, every action is tied to a source, destination, operator, and timestamp. You can check it anytime from the history view.

2The two modes: Set To / Adjust By

MODE A

Set To: "overwrite" the quantity

98 to the number you enter 120

How to use : just enter the quantity. Shopify records the difference automatically.

Good for : Operations where you only know the final value, such as applying stocktake results.

MODE B

Adjust By: Records it as a "transfer"

Source Warehouse A +10 Destination Store B

How to use : Choose a source (from where) and a destination (to where), then enter the increase or decrease.

Good for : Operations where you want a record of where stock moved from, such as transfers between locations, damage, returns, and restocking.

3How it works: The flow after moving inventory

Staff Make an adjustment Inventory adjustment popover Set To Adjust By Quantity / Transfer Pick a mode and enter values Automatic log source / dest user / timestamp Shopify records it Adjustment history view +10 / Warehouse A → Store B Set 120 / Stocktake adjustment −3 / Damage +50 / Received Viewable anytime

4The 4 items that get recorded

Source
Where it moved from
Destination
Where it moved to
Operator
Who made the change
Date and time
When the change was made
Regardless of the mode (whether Set To or Adjust By), these 4 items are always recorded.You can open the history view at any time, so you can trace past operations.

5Relationship with the Bulk Editor

Where you do itBehaviorSource / Destination
Inventory adjustment popover
(Set To)		 After the change Enter quantity + automatically log the difference Not required (automatic)
Inventory adjustment popover
(Adjust By)		 New Choose a source/destination and log it as a transfer Required
Bulk Editor Unchanged Set the available inventory directly. Behavior is the same as before. Not required
Bulk Editor is unchanged : You can keep bulk-overwriting available quantities just as before. No source/destination input is required.

6Which to use when

1
Final value only

Applying stocktake results → Set To

When you only know "how many there are in the end." Enter the number and confirm.

2

Inter-location transfers and restocking → Adjust By

Operations where you want to record "where it came from and where it went." Traceability-focused.

3

Bulk overwrite of many products → Bulk Editor

Large-scale edits that don't require individual history. Same as your current workflow.

7Five points engineers should know

2 MODES

1. The UI entry point is split into two modes: Set To / Adjust By

A design that switches modes within the same popover. On the implementation side, you'll need to update user-training documentation (e.g., screenshots in manuals).

LOG

2. Every adjustment is tied to four fields (source / destination / user / time)

These are recorded regardless of mode. Teams that previously tracked "who and when" separately (e.g., in spreadsheets) may be able to retire that workaround.

API ?

3. No changes to API/Webhook specifications are mentioned

The article describes only admin UI behavior. Any impact on GraphQL specs such as InventoryLevel/InventoryAdjustment should be confirmed separately in the help and developer documentation.

4. Bulk Editor is not changed

The flow for bulk-overwriting available inventory is the same as before. Because it doesn't require a source/destination, your operational scripts and procedures can stay as they are.

5. The history view is explicitly "viewable any time." Viewing scope, permissions, and exportability are not mentioned.

The article only states "view your full adjustment history any time."Who can view it / whether you can export to CSV / retention periodneed to be confirmed in the help documentation. Sites with audit requirements must verify this in advance.

8Three use cases you can apply to your operations

Warehouse Store +10 / Warehouse→Store Yamada / 5/7 10:32
USE CASE 1

Creating an audit trail for inter-location transfers in multi-location stores

Challenge
In operations that frequently move inventory between warehouse ↔ store ↔ pop-up, you can't track who moved what and when, so you waste time hunting down the cause of stock discrepancies and losses.
Action
Moves always use Adjust ByMake it an operational rule to , entering the source and destination every time.
Impact
When a stock discrepancy occurs, the cause can be identified just by tracing the history. Per-staff operation patterns also become visible, providing useful training material.
Technical notes
Document the distinction between Set To and Adjust By in your procedures. Preparing a manual and short staff-facing videos is key to making the practice stick.
Stocktake sheet
USE CASE 2

Standardize the stocktake flow on Set To to eliminate dual management

Challenge
Reflecting stocktake results is done twice—entering them into Shopify and recording the who and when in Excel or Google Sheets—which inflates the workload.
Action
Apply stocktake results using Set To only. Since the operator and timestamp are recorded automatically, history management in an external spreadsheet can be retired.
Impact
Reduces the workload of stocktake operations. The authoritative record is consolidated within Shopify, shortening the lead time to look things up.
Technical notes
Check the help docs on whether history can be exported. If accounting-audit integration is required, it is safer to set up a practice of screenshotting or saving the history view as a PDF in advance.
Damage −3 / Tanaka Damage −1 / Tanaka Damage −5 / Tanaka Pattern: anomaly detection
USE CASE 3

Use adjustment history as a signal for detecting fraud and loss

Challenge
The reasons for inventory decreases (damage / theft / system inconsistency) are unknown, making it impossible to act on loss-reduction measures.
Action
Enforce a practice of adding reasons such as "damage" or "sample outbound" to the destination via Adjust By when making adjustments, and review the history regularly.
Impact
You can discover decrease patterns tied to a specific staff member, SKU, or time slot, enabling early detection of stocktake loss and internal fraud.
Technical notes
If history can be retrieved via the API, you can also connect it to BI (Looker / BigQuery) to build an anomaly-detection dashboard. The article does not mention the API specification.

9A one-line summary you can use in proposals

"Inventory adjustments now offer two modes: Set To (overwrite) / Adjust By (move) .
With either one, the source, destination, operator, and timestamp are recorded in the history automatically, and the Bulk Editor stays as-is."
on-siteshelf-count discrepancy tracking, audit trails for inter-location transfers, and loss detection—all with no additional tools."