Catch paid Shopify orders that still haven't shipped after 48 hours

Every weekday: paid Shopify orders still unfulfilled after 48 hours, oldest first, with any hold reason, and a question on what is holding them.

Runs
Weekdays at 9:00
Uses
Shopify
Posts
Asks you

From your apps to your board

How the skill works: your agent reads paid orders that haven't shipped from Shopify; store domain, shipping promise from What you tell it, weekdays at 9:00, and gives you a question for you and a telegram ping and the report in the chat.

Reads

  • ShopifyPaid orders that haven't shipped
  • What you tell itStore domain, Shipping promise
reads
Your agentClaude Code, Codex, Cursor or GeminiWeekdays at 9:00
posts

You get

  • A question for youOn your board, answered with a tap
  • A Telegram pingOnly when it needs your answer, if you connect Telegram
  • The report in the chatEvery run, with or without Briefkin

What you get

  • Paid orders waiting past 48 hours, with their total value and the age of the oldest.
  • The list, oldest first: order, placed, amount, status, and the hold reason or location.
  • By cause: on hold, partly shipped, and waiting per location.
  • The ask: what is holding them, and whether to tag them for follow-up.

The card on the right is a sample. Yours shows your own numbers and updates in place every run.

What lands on your board

Acme StoreShopify unfulfilled orders · Claude Code

9 paid orders waiting over 48 hours

What is holding these orders, and should I tag them for follow-up?

9 paid orders worth $1,412 have not shipped after 48 hours. The oldest, #4821, is 6 days old and on hold for an incorrect address.

OrderPlacedAmountStatusReason or location
#48216 days ago$184.00On holdIncorrect address
#48365 days ago$96.50UnfulfilledMain warehouse
#48404 days ago$212.00Partly shippedMain warehouse
#48524 days ago$138.00UnfulfilledPartner 3PL
#48573 days ago$74.00On holdOut of stock
#48613 days ago$259.00UnfulfilledMain warehouse
#48663 days ago$118.50UnfulfilledPartner 3PL
#48702 days ago$162.00UnfulfilledMain warehouse
#48742 days ago$168.00UnfulfilledMain warehouse

5 of the 9 are assigned to Main warehouse. The two on hold need a decision from you before anyone can ship them.

Resolve
An example with made-up numbers. Your agent posts your real ones.

What it does

An order that sits unshipped for four days usually turns into a "where is my order" email on day five. The Orders page can filter for it, but nobody checks it on a busy morning, and orders on hold for an address problem wait for someone to notice.

Every weekday the agent lists the paid orders that are still unfulfilled after 48 hours, oldest first, with the location they are assigned to and any hold reason. Store owners and ops leads answer one question: is it stock, the warehouse, or something to tag and follow up.

How it works

  1. 1Find paid orders that haven't shipped

    Query orders(first: 100, sortKey: CREATED_AT, query: "financial_status:paid fulfillment_status:unfulfilled status:open created_at:<2026-10-15T09:00:00Z") with the cutoff 48 hours ago, then the same with fulfillment_status:partial and fulfillment_status:on_hold. Request name, createdAt, displayFulfillmentStatus, totalPriceSet and lineItems { sku quantity unfulfilledQuantity }.

  2. 2See where each one is stuck

    For each order read fulfillmentOrders(first: 5) { nodes { status assignedLocation { name } fulfillmentHolds { reason reasonNotes } } }. A fulfillment order with status ON_HOLD carries the hold reason; otherwise the assigned location tells you whether it is waiting at your warehouse or a 3PL.

  3. 3

    3Sort and flag

    Sort oldest first and flag anything over 5 days. Group by cause: on hold (with the reason), partly shipped, and waiting at each location, so a warehouse that has fallen behind shows up as one line rather than nine.

  4. 4Ask, then tag

    Post the list as an ask. If you choose to tag them, call tagsAdd on each order with fulfillment-delay so support can find them; nothing else changes.

  5. Post it to the board

    With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.

Install and run it

Pick your agent, where the data comes from and how to schedule it; the commands below follow.

Agent
Data
Schedule
  1. Install the skill

    One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.

    shellcurl -fsSL https://briefkin.dev/skills/shopify-unfulfilled-orders/install | sh
  2. Run it

    Ask Claude Code:

    promptRun the shopify-unfulfilled-orders skill

    Or paste the prompt instead of installing:

    promptUsing the Shopify Admin GraphQL API, find orders that are paid, open, and unfulfilled, partly fulfilled or on hold, created more than 48 hours ago. For each give the order name, age, total, fulfillment status, and from its fulfillment orders the assigned location and any hold reason. Sort oldest first, flag anything over 5 days, and group them by cause. Then ask me what is holding them and whether to add the tag fulfillment-delay. Change nothing until I answer.
  3. Put it on a schedule

    Weekdays at 9:00, from cron on any machine where Claude Code is signed in:

    crontab0 9 * * 1-5 claude -p "Run the shopify-unfulfilled-orders skill"

    Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.

  4. Send it to your board

    Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a question for you. How setup works

View the SKILL.mdRaw file
SKILL.md---
name: shopify-unfulfilled-orders
description: "Every weekday: paid Shopify orders still unfulfilled after 48 hours, oldest first, with any hold reason, and a question on what is holding them. Use when the user asks for this, or when it runs on a schedule."
---

# Shopify unfulfilled orders

Every weekday: paid Shopify orders still unfulfilled after 48 hours, oldest first, with any hold reason, and a question on what is holding them.

An order that sits unshipped for four days usually turns into a "where is my order" email on day five. The Orders page can filter for it, but nobody checks it on a busy morning, and orders on hold for an address problem wait for someone to notice.

Every weekday the agent lists the paid orders that are still unfulfilled after 48 hours, oldest first, with the location they are assigned to and any hold reason. Store owners and ops leads answer one question: is it stock, the warehouse, or something to tag and follow up.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- Shopify Admin API access with `read_orders` and `read_merchant_managed_fulfillment_orders` (add `read_third_party_fulfillment_orders` if a 3PL app fulfills), plus `write_orders` only if the agent should tag orders.
- Your shipping promise, for example "ships in 2 business days", if 48 hours is not it.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Find paid orders that haven't shipped** (Shopify): Query `orders(first: 100, sortKey: CREATED_AT, query: "financial_status:paid fulfillment_status:unfulfilled status:open created_at:<2026-10-15T09:00:00Z")` with the cutoff 48 hours ago, then the same with `fulfillment_status:partial` and `fulfillment_status:on_hold`. Request `name`, `createdAt`, `displayFulfillmentStatus`, `totalPriceSet` and `lineItems { sku quantity unfulfilledQuantity }`.
2. **See where each one is stuck** (Shopify): For each order read `fulfillmentOrders(first: 5) { nodes { status assignedLocation { name } fulfillmentHolds { reason reasonNotes } } }`. A fulfillment order with status `ON_HOLD` carries the hold reason; otherwise the assigned location tells you whether it is waiting at your warehouse or a 3PL.
3. **Sort and flag**: Sort oldest first and flag anything over 5 days. Group by cause: on hold (with the reason), partly shipped, and waiting at each location, so a warehouse that has fallen behind shows up as one line rather than nine.
4. **Ask, then tag** (Shopify): Post the list as an ask. If you choose to tag them, call `tagsAdd` on each order with `fulfillment-delay` so support can find them; nothing else changes.

## Route B: the browser

### What you need

- Signed in to the Shopify admin as the owner or a staff member with the Orders permission (and Edit orders if the agent should add tags).

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://admin.shopify.com/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Filter the Orders page**: admin.shopify.com lists your stores; open the store and go to **Orders**. Add filters: **Payment status** `Paid`, **Fulfillment status** `Unfulfilled`, `Partially fulfilled` and `On hold`, and **Status** `Open`. Sort by **Date** with the oldest first.
2. **Keep the ones past 48 hours**: Read down the list until the order date is within the last 48 hours and stop there. For each older order note the order name, placed date, total and fulfillment status. Flag anything older than 5 days.
3. **See where each is stuck**: Open each order. The fulfillment card names the location it is assigned to (your warehouse or a fulfillment service), and an order on hold shows the hold reason there. Group the orders by cause: on hold with its reason, partly shipped, and waiting per location.
4. **Ask before tagging**: Post the list and the question. If the answer is to tag them, select the orders on the Orders page and use **Add tags** with `fulfillment-delay`; touch nothing else. Save the filter as a view so next weekday is one click.

Note: The Orders list shows 50 orders a page; past a hundred waiting orders, **Export** the filtered list as CSV and read that instead. The hold reason and assigned location only show on the order page, so each order takes one more click. The Orders page keeps older orders in view, unlike the API without read_all_orders.

## The report

- **Paid orders waiting** past 48 hours, with their total value and the age of the oldest.
- **The list**, oldest first: order, placed, amount, status, and the hold reason or location.
- **By cause**: on hold, partly shipped, and waiting per location.
- The ask: what is holding them, and whether to tag them for follow-up.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "shopify-unfulfilled-orders/<date of this run, e.g. 2026-10-16>",
  "item_key": "shopify-unfulfilled-orders",
  "project": "Acme Store",
  "source": "Shopify unfulfilled orders skill",
  "kind": "action",
  "title": "9 paid orders waiting over 48 hours",
  "summary": "**9** paid orders worth **$1,412** have not shipped after 48 hours. The oldest, #4821, is 6 days old and on hold for an incorrect address.",
  "action": {
    "request": "What is holding these orders, and should I tag them for follow-up?",
    "options": [
      "Tag all as delayed",
      "Stock issue, list SKUs",
      "Warehouse is behind",
      "Leave them"
    ]
  },
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Order",
          "Placed",
          "Amount",
          "Status",
          "Reason or location"
        ],
        "align": [
          "left",
          "left",
          "right",
          "left",
          "left"
        ],
        "rows": [
          [
            "#4821",
            "6 days ago",
            "$184.00",
            "On hold",
            "Incorrect address"
          ],
          [
            "#4836",
            "5 days ago",
            "$96.50",
            "Unfulfilled",
            "Main warehouse"
          ],
          [
            "#4840",
            "4 days ago",
            "$212.00",
            "Partly shipped",
            "Main warehouse"
          ],
          [
            "#4852",
            "4 days ago",
            "$138.00",
            "Unfulfilled",
            "Partner 3PL"
          ],
          [
            "#4857",
            "3 days ago",
            "$74.00",
            "On hold",
            "Out of stock"
          ],
          [
            "#4861",
            "3 days ago",
            "$259.00",
            "Unfulfilled",
            "Main warehouse"
          ],
          [
            "#4866",
            "3 days ago",
            "$118.50",
            "Unfulfilled",
            "Partner 3PL"
          ],
          [
            "#4870",
            "2 days ago",
            "$162.00",
            "Unfulfilled",
            "Main warehouse"
          ],
          [
            "#4874",
            "2 days ago",
            "$168.00",
            "Unfulfilled",
            "Main warehouse"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "5 of the 9 are assigned to Main warehouse. The two on hold need a decision from you before anyone can ship them.",
        "tone": "warn"
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Weekdays at 9:00 (`0 9 * * 1-5`). From cron, with the agent signed in on that machine:

```bash
0 9 * * 1-5 claude -p "Run the shopify-unfulfilled-orders skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/shopify-unfulfilled-orders#schedule

Source: https://briefkin.dev/skills/shopify-unfulfilled-orders

What your agent needs

  • Shopify Admin API access with read_orders and read_merchant_managed_fulfillment_orders (add read_third_party_fulfillment_orders if a 3PL app fulfills), plus write_orders only if the agent should tag orders.

  • Your shipping promise, for example "ships in 2 business days", if 48 hours is not it.

Connecting Shopify

  1. Shopify AI Toolkit. Shopify's plugins for Claude Code, Codex and Cursor run store tasks through Shopify CLI's authenticated store context. Its Dev MCP server (npx -y @shopify/dev-mcp@latest) covers docs and API schemas, not your store's orders; for store data, community MCP servers exist.
  2. Admin API with an app token. Create an app for the store, install it with read scopes such as read_orders, read_products and read_inventory, and store SHOPIFY_STORE_DOMAIN (acme.myshopify.com) and SHOPIFY_ACCESS_TOKEN. Requests go to https://acme.myshopify.com/admin/api/2026-10/graphql.json with the X-Shopify-Access-Token header. Orders older than 60 days also need read_all_orders.

Request only read_ scopes when you install the app; Shopify enforces them per token, so the agent can't edit products, refund or cancel orders.

Questions

Can it count business days instead of 48 hours?

Yes. By default it counts clock hours since the order was placed, so a Friday evening order shows up on Monday. Tell the skill your promise, for example 2 business days, and it skips weekends and your holidays when it works out the cutoff.

What about orders older than 60 days?

Without the read_all_orders scope, the Admin API only returns the last 60 days of orders, so an order stuck longer than that drops off the list. The skill warns about anything over 30 days, well before that happens.

Do I need Briefkin to use the Shopify unfulfilled orders skill?

No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a asks you, so you can glance at it instead of asking again.

Which agents can run it?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.

Can it work without an API or MCP server, from my browser?

Yes. Switch the data source to "Your browser" and the steps change to the Shopify pages themselves: the agent opens admin.shopify.com in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.

Answer your agents from one board, or from Telegram

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Free during the open beta. No card.