/shopify-admin-inventory-transfer-between-locations
Moves inventory units from one location to another by decrementing the source and incrementing the destination.
$ npx -y skills add 40rty-ai/shopify-admin-skills --skill shopify-admin-inventory-transfer-between-locations --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/shopify-admin-inventory-transfer-between-locations
Context preview
The summary Claude sees to decide when to auto-load this skill.
Moves inventory units from one location to another by decrementing the source and incrementing the destination.
SKILL.md
shopify-admin-inventory-transfer-between-locations.SKILL.mdname: shopify-admin-inventory-transfer-between-locations
role: merchandising
description: "Moves inventory units from one location to another by decrementing the source and incrementing the destination."
toolkit: shopify-admin, shopify-admin-execution
api_version: "2025-01"
graphql_operations:
- locations:query
- inventoryItems:query
- inventoryAdjustQuantities:mutation
status: stable
compatibility: Claude Code, Cursor, Codex, Gemini CLI
Purpose
Transfers a specified quantity of inventory from a source location to a destination location using paired inventory adjustments (decrement source, increment destination). Used for inter-warehouse rebalancing, pre-positioning stock before a sale, or redistributing inventory after a location change. Replaces manual inventory transfer in Shopify Admin.
Prerequisites
- Authenticated Shopify CLI session: `shopify store auth --store <domain> --scopes read_products,write_inventory,read_inventory`
- API scopes: `read_products`, `read_inventory`, `write_inventory`
- Both source and destination must be active Shopify locations
Parameters
| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | source_location_id | string | yes | — | GID of the location to move stock FROM | | destination_location_id | string | yes | — | GID of the location to move stock TO | | transfers | array | yes | — | List of `{sku, quantity}` objects to transfer | | dry_run | bool | no | true | Preview adjustments without executing mutations | | format | string | no | human | Output format: `human` or `json` |
Safety
> ⚠️ `inventoryAdjustQuantities` directly modifies inventory levels. Decrementing the source below zero is possible if the quantity exceeds available stock — the skill will warn but Shopify does not block negative adjustments. Run with `dry_run: true` to verify available quantities at the source before committing. This does NOT create a transfer order record in Shopify; it is a direct adjustment.
Workflow Steps
1. **OPERATION:** `locations` — query **Inputs:** `first: 50` **Expected output:** All locations with `id`, `name` — validate source and destination IDs exist
2. **OPERATION:** `inventoryItems` — query **Inputs:** Batch lookup by SKU to get `inventoryItem.id` for each transfer SKU **Expected output:** Inventory items with current quantities at source location
3. Validate: for each SKU, confirm `available >= quantity` at source. Warn if not but proceed if `dry_run: false`
4. **OPERATION:** `inventoryAdjustQuantities` — mutation **Inputs:** Two changes per SKU: `{ inventoryItemId, locationId: source, delta: -quantity, reason: "correction" }` and `{ inventoryItemId, locationId: destination, delta: +quantity, reason: "correction" }` **Expected output:** `inventoryAdjustmentGroup { changes { delta, location } }`, `userErrors`
GraphQL Operations
# locations:query — validated against api_version 2025-01
query ActiveLocations {
locations(first: 50, includeInactive: false) {
edges {
node {
id
name
isActive
fulfillsOnlineOrders
}
}
}
}# inventoryItems:query — validated against api_version 2025-01
query InventoryLevelsAtLocation($ids: [ID!]!) {
nodes(ids: $ids) {
... on InventoryItem {
id
sku
inventoryLevels(first: 20) {
edges {
node {
location {
id
name
}
quantities(names: ["available", "on_hand"]) {
name
quantity
}
}
}
}
}
}
}# inventoryAdjustQuantities:mutation — validated against api_version 2025-01
mutation InventoryAdjustQuantities($input: InventoryAdjustQuantitiesInput!) {
inventoryAdjustQuantities(input: $input) {
inventoryAdjustmentGroup {
createdAt
reason
changes {
delta
quantityAfterChange
item {
id
sku
}
location {
id
name
}
}
}
userErrors {
field
message
}
}
}Session Tracking
**Claude MUST emit the following output at each stage. This is mandatory.**
**On start**, emit:
╔══════════════════════════════════════════════╗
║ SKILL: Inventory Transfer Between Locations ║
║ Store: <store domain> ║
║ Started: <YYYY-MM-DD HH:MM UTC> ║
╚══════════════════════════════════════════════╝
**After each step**, emit:
[N/TOTAL] <QUERY|MUTATION> <OperationName>
→ Params: <brief summary of key inputs>
→ Result: <count or outcome>If `dry_run: true`, prefix every mutation step with `[DRY RUN]` and do not execute it.
**On completion**, emit:
For `format: human` (default):
══════════════════════════════════════════════
OUTCOME SUMMARY
SKUs transferred: <n>
Total units moved: <n>
Warnings (low stock): <n>
Errors: <n>
Output: inventory_transfer_<date>.csv
══════════════════════════════════════════════
For `format: json`, emit:
{
"skill": "inventory-transfer-between-locations",
"store": "<domain>",
"started_at": "<ISO8601>",
"dry_run": true,
"source_location": "<name>",
"destination_location": "<name>",
"outcome": {
"skus_transferred": 0,
"units_moved": 0,
"warnings": 0,
"errors": 0,
"output_file": "inventory_transfer_<date>.csv"
}
}Output Format
CSV file `inventory_transfer_<YYYY-MM-DD>.csv` with columns: `sku`, `product_title`, `inventory_item_id`, `source_location`, `destination_location`, `quantity_transferred`, `source_qty_before`, `source_qty_after`, `destination_qty_before`, `destination_qty_after`
Error Handling
| Error | Cause | Recovery | |-------|-------|----------| | `THROTTLED` | API
Read more
name: shopify-admin-inventory-transfer-between-locations role: merchandising description: "Moves inventory units from one location to another by decrementing the source and incrementing the destination." toolkit: shopify-admin, shopify-admin-execution api_version: "2025-01" graphql_operations: - locations:query - inventoryItems:query - inventoryAdjustQuantities:mutation status: stable compatibility: Claude Code, Cursor, Codex, Gemini CLI
Purpose
Transfers a specified quantity of inventory from a source location to a destination location using paired inventory adjustments (decrement source, increment destination). Used for inter-warehouse rebalancing, pre-positioning stock before a sale, or redistributing inventory after a location change. Replaces manual inventory transfer in Shopify Admin.
Prerequisites
- Authenticated Shopify CLI session: `shopify store auth --store <domain> --scopes read_products,write_inventory,read_inventory`
- API scopes: `read_products`, `read_inventory`, `write_inventory`
- Both source and destination must be active Shopify locations
Parameters
| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | source_location_id | string | yes | — | GID of the location to move stock FROM | | destination_location_id | string | yes | — | GID of the location to move stock TO | | transfers | array | yes | — | List of `{sku, quantity}` objects to transfer | | dry_run | bool | no | true | Preview adjustments without executing mutations | | format | string | no | human | Output format: `human` or `json` |
Safety
> ⚠️ `inventoryAdjustQuantities` directly modifies inventory levels. Decrementing the source below zero is possible if the quantity exceeds available stock — the skill will warn but Shopify does not block negative adjustments. Run with `dry_run: true` to verify available quantities at the source before committing. This does NOT create a transfer order record in Shopify; it is a direct adjustment.
Workflow Steps
1. **OPERATION:** `locations` — query **Inputs:** `first: 50` **Expected output:** All locations with `id`, `name` — validate source and destination IDs exist
2. **OPERATION:** `inventoryItems` — query **Inputs:** Batch lookup by SKU to get `inventoryItem.id` for each transfer SKU **Expected output:** Inventory items with current quantities at source location
3. Validate: for each SKU, confirm `available >= quantity` at source. Warn if not but proceed if `dry_run: false`
4. **OPERATION:** `inventoryAdjustQuantities` — mutation **Inputs:** Two changes per SKU: `{ inventoryItemId, locationId: source, delta: -quantity, reason: "correction" }` and `{ inventoryItemId, locationId: destination, delta: +quantity, reason: "correction" }` **Expected output:** `inventoryAdjustmentGroup { changes { delta, location } }`, `userErrors`
GraphQL Operations
# locations:query — validated against api_version 2025-01
query ActiveLocations {
locations(first: 50, includeInactive: false) {
edges {
node {
id
name
isActive
fulfillsOnlineOrders
}
}
}
}# inventoryItems:query — validated against api_version 2025-01
query InventoryLevelsAtLocation($ids: [ID!]!) {
nodes(ids: $ids) {
... on InventoryItem {
id
sku
inventoryLevels(first: 20) {
edges {
node {
location {
id
name
}
quantities(names: ["available", "on_hand"]) {
name
quantity
}
}
}
}
}
}
}# inventoryAdjustQuantities:mutation — validated against api_version 2025-01
mutation InventoryAdjustQuantities($input: InventoryAdjustQuantitiesInput!) {
inventoryAdjustQuantities(input: $input) {
inventoryAdjustmentGroup {
createdAt
reason
changes {
delta
quantityAfterChange
item {
id
sku
}
location {
id
name
}
}
}
userErrors {
field
message
}
}
}Session Tracking
**Claude MUST emit the following output at each stage. This is mandatory.**
**On start**, emit:
╔══════════════════════════════════════════════╗ ║ SKILL: Inventory Transfer Between Locations ║ ║ Store: <store domain> ║ ║ Started: <YYYY-MM-DD HH:MM UTC> ║ ╚══════════════════════════════════════════════╝
**After each step**, emit:
[N/TOTAL] <QUERY|MUTATION> <OperationName>
→ Params: <brief summary of key inputs>
→ Result: <count or outcome>If `dry_run: true`, prefix every mutation step with `[DRY RUN]` and do not execute it.
**On completion**, emit:
For `format: human` (default):
══════════════════════════════════════════════ OUTCOME SUMMARY SKUs transferred: <n> Total units moved: <n> Warnings (low stock): <n> Errors: <n> Output: inventory_transfer_<date>.csv ══════════════════════════════════════════════
For `format: json`, emit:
{
"skill": "inventory-transfer-between-locations",
"store": "<domain>",
"started_at": "<ISO8601>",
"dry_run": true,
"source_location": "<name>",
"destination_location": "<name>",
"outcome": {
"skus_transferred": 0,
"units_moved": 0,
"warnings": 0,
"errors": 0,
"output_file": "inventory_transfer_<date>.csv"
}
}Output Format
CSV file `inventory_transfer_<YYYY-MM-DD>.csv` with columns: `sku`, `product_title`, `inventory_item_id`, `source_location`, `destination_location`, `quantity_transferred`, `source_qty_before`, `source_qty_after`, `destination_qty_before`, `destination_qty_after`
Error Handling
| Error | Cause | Recovery | |-------|-------|----------| | `THROTTLED` | API
Community-maintained AI agent skills for operating Shopify stores — workflows, optimization, reports and more
Other skills on shopify-admin-skills.
- /shopify-admin-agentic-crawler-access
Edit the theme's robots.txt.liquid to explicitly allow AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Amazonbot) so AI assistants are permitted to read the catalog.
Open skill - /shopify-admin-agentic-description-enrichment
Rewrite thin product descriptions into structured, fact-rich copy (materials, fit, use-cases, the words shoppers actually type) so AI agents have something concrete to quote and match.
Open skill - /shopify-admin-agentic-image-alt-text
Generate and set descriptive alt text on product images so AI agents (which can't 'see' pixels) can understand and recommend what each product looks like.
Open skill - /shopify-admin-agentic-llms-txt
Generate and publish an /llms.txt guide (brand summary, flagship products, key policies, contact) via a theme template so AI assistants get a curated, machine-readable map of the store.
Open skill - /shopify-admin-agentic-metafields-setup
Define and populate agentic-commerce metafields (material, attributes, key features, specs, sizing) so AI agents can filter and match products to specific shopper requirements.
Open skill - /shopify-admin-agentic-organization-schema
Inject an Organization JSON-LD block (name, logo, sameAs social links, contactPoint) into the theme so AI agents can verify the store is a real, trusted brand and link it to its public identity.
Open skill

