Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
40rty-ai avatar

Shopify Admin Restock On Return

  • 2 installs
  • 173 repo stars
  • Updated June 26, 2026
  • 40rty-ai/shopify-admin-skills

shopify-admin-restock-on-return is a Claude Code skill that restocks Shopify inventory for approved or closed returns by adjusting on-hand quantities at the return location using inventoryAdjustQuantities.

About

This skill walks recently approved or closed Shopify returns and restocks inventory for each returned line item at the return's destination location. It adjusts the available quantity using inventoryAdjustQuantities with a restock reason and a reference back to the return record. Ops teams use it when warehouse processing lives in a separate system or when manual restock needs a catch-up run. It skips defective items by default and defaults to a dry run.

  • Restocks inventory for approved or closed Shopify returns by adjusting on-hand quantities at the return location
  • Uses the Shopify Admin GraphQL returns query and inventoryAdjustQuantities mutation with reason restock
  • Skips DEFECTIVE returns by default and defaults to dry_run:true to prevent oversells from unsalable stock

Shopify Admin Restock On Return by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #1,839 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 1, 2026 (Skillselion catalog sync)
At a glance

shopify-admin-restock-on-return capabilities & compatibility

Free; requires an authenticated Shopify store session with read_returns, read_inventory, write_inventory, and read_locations scopes

Capabilities
inventory restock · returns processing · inventory adjustment
Works with
github
Use cases
database
Pricing
Free
From the docs

What shopify-admin-restock-on-return says it does

For approved/closed returns, restocks inventory at the return location by adjusting on-hand quantities for each returned line item.
SKILL.md
Restocking damaged or unsalable inventory inflates available stock and causes oversells.
SKILL.md
npx skills add https://github.com/40rty-ai/shopify-admin-skills --skill shopify-admin-restock-on-return

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars173
Last updatedJune 26, 2026
Repository40rty-ai/shopify-admin-skills

What it does

Restock Shopify inventory for approved or closed returns by adjusting on-hand quantities at the return location.

Who is it for?

Catch-up restocking when warehouse processing posts in a separate system from Shopify

Skip if: Restocking defective or unsalable inventory, which is excluded by default to avoid oversells

When should I use this skill?

You need to restock inventory for a batch of completed Shopify returns

What you get

Sellable returned items are restocked at the correct location with an audit entry linking each adjustment to its return.

  • Restock plan preview and inventory adjustments per returned line item

By the numbers

  • 2 GraphQL operations (returns query, inventoryAdjustQuantities mutation)
  • Default lookback window of 14 days
  • Default return_status CLOSED

Files

SKILL.mdMarkdownGitHub ↗

Purpose

Walks through recently approved or closed returns and restocks inventory for each returnLineItem whose physical item has been received and inspected. Adjusts the available quantity at the return's destination location using inventoryAdjustQuantities with reason restock and a referenceDocumentUri linking to the return record. Use when warehouse processing posts in a separate system from Shopify, or when manual restock has been deferred and needs a clean catch-up run.

Prerequisites

  • Authenticated Shopify CLI session: shopify store auth --store <domain> --scopes read_returns,write_inventory,read_locations
  • API scopes: read_returns, read_inventory, write_inventory

Parameters

ParameterTypeRequiredDefaultDescription
storestringyesStore domain (e.g., mystore.myshopify.com)
formatstringnohumanOutput format: human or json
dry_runboolnotruePreview restock plan without executing inventory mutations
days_backintegerno14Lookback window for recently completed returns
return_statusstringnoCLOSEDOnly restock returns in this status: CLOSED, OPEN, or ANY
location_idstringnoIf set, restock only returns whose inventory destination matches this location GID
restock_only_return_reasonsarraynoIf set (e.g., ["UNWANTED", "SIZE_TOO_SMALL"]), restock only items returned for these reasons; DEFECTIVE is excluded by default
skip_defectiveboolnotrueExclude returnLineItem.returnReason: DEFECTIVE items from restock

Safety

⚠️ Step 2 executes inventoryAdjustQuantities mutations that immediately add units to the available count at the destination location. Restocking damaged or unsalable inventory inflates available stock and causes oversells. The default is dry_run: true — review the preview CSV to confirm each return line item is genuinely sellable before committing. By default skip_defective: true excludes DEFECTIVE returns. Each restock posts a permanent entry in Shopify's inventory activity log with reason restock.

Workflow Steps

1. OPERATION: returns — query Inputs: query: "status:<return_status> updated_at:>='<NOW - days_back days>'" (use updated_at:>='...' only when return_status:ANY), first: 250, select id, name, status, closedAt, order { id name }, returnLineItems(first: 50) { quantity, returnReason, fulfillmentLineItem { lineItem { variant { id sku inventoryItem { id tracked } } } } }, reverseFulfillmentOrders(first: 5) { reverseDeliveries(first: 5) { deliverable { ... on ReverseDeliveryShippingDeliverable { label { ... } } } }, location { id name } }, pagination cursor Expected output: Returns with their line items, return reasons, inventory item IDs, and destination location

2. Build the restock plan: for each returnLineItem not previously restocked, where returnReason is allowed by params and inventoryItem.tracked: true, group by (inventoryItemId, locationId) summing quantity deltas. Skip items where the variant is missing, where tracked: false, or where the return has no destination location.

3. OPERATION: inventoryAdjustQuantities — mutation Inputs: input.reason: "restock", input.name: "available", input.referenceDocumentUri: "shopify://returns/<return_id>", input.changes: [{ inventoryItemId, locationId, delta: +<quantity> }, ...] Expected output: inventoryAdjustmentGroup.changes with quantityAfterChange per item; userErrors

GraphQL Operations

# returns:query — validated against api_version 2025-01
query ReturnsForRestock($query: String!, $after: String) {
  returns(first: 250, after: $after, query: $query) {
    edges {
      node {
        id
        name
        status
        closedAt
        order { id name }
        returnLineItems(first: 50) {
          edges {
            node {
              id
              quantity
              returnReason
              returnReasonNote
              fulfillmentLineItem {
                lineItem {
                  id
                  title
                  variant {
                    id
                    sku
                    inventoryItem { id tracked }
                  }
                }
              }
            }
          }
        }
        reverseFulfillmentOrders(first: 5) {
          edges {
            node {
              id
              reverseDeliveries(first: 5) { edges { node { id } } }
            }
          }
        }
      }
    }
    pageInfo { hasNextPage endCursor }
  }
}
# inventoryAdjustQuantities:mutation — validated against api_version 2025-01
mutation RestockOnReturn($input: InventoryAdjustQuantitiesInput!) {
  inventoryAdjustQuantities(input: $input) {
    inventoryAdjustmentGroup {
      id
      reason
      referenceDocumentUri
      changes {
        name
        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: Restock on Return                    ║
║  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):

══════════════════════════════════════════════
RESTOCK ON RETURN
  Returns scanned:        <n>
  Line items eligible:    <n>
  Skipped (defective):    <n>
  Skipped (untracked):    <n>
  Units restocked:        <n>  (or "skipped — dry_run")
  Adjustment groups:      <n>
  Errors:                 <n>
  Output:                 restock_on_return_<date>.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "restock-on-return",
  "store": "<domain>",
  "started_at": "<ISO8601>",
  "completed_at": "<ISO8601>",
  "dry_run": true,
  "outcome": {
    "returns_scanned": 0,
    "line_items_eligible": 0,
    "skipped_defective": 0,
    "skipped_untracked": 0,
    "units_restocked": 0,
    "adjustment_groups": 0,
    "errors": 0,
    "output_file": "restock_on_return_<date>.csv"
  }
}

Output Format

CSV file restock_on_return_<YYYY-MM-DD>.csv with columns: return_id, return_name, order_name, sku, product_title, quantity_restocked, return_reason, location_name, quantity_after, inventory_item_id, status

Error Handling

ErrorCauseRecovery
THROTTLEDAPI rate limit exceededWait 2 seconds, retry up to 3 times
inventoryItem.tracked: falseTracking disabled on variantLog and skip; require manual enable
userErrors from inventoryAdjustQuantitiesInvalid location or itemVerify GIDs match the return's destination
Return has no destination locationNo reverse delivery confirmed yetSkip the return; rerun after delivery is confirmed
Variant deletedProduct removed after saleSkip line item; log for review

Best Practices

  • Always run with dry_run: true first and audit the preview CSV — restocking damaged units inflates inventory and causes oversells downstream.
  • Keep skip_defective: true for normal operations. Set it to false only after explicitly inspecting defective units and confirming they're refurbishable.
  • Use restock_only_return_reasons: ["UNWANTED", "SIZE_TOO_SMALL", "SIZE_TOO_LARGE", "STYLE", "COLOR"] to focus on reasons that almost always yield resalable inventory.
  • Set location_id when running per-warehouse — it constrains the run to one site's reverse logistics workflow.
  • Cross-reference the post-run output with multi-location-inventory-audit to confirm restocked SKUs reconcile cleanly.
  • For active returns where physical inspection has not occurred, defer restock until status: CLOSED (default) — never restock on OPEN returns based solely on customer claim.

Related skills

FAQ

Does it restock defective items?

No; skip_defective defaults to true, so DEFECTIVE returns are excluded to prevent inflating available stock and causing oversells.

Is the adjustment logged?

Yes; each restock posts a permanent entry in Shopify's inventory activity log with reason restock and a reference to the return record.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.