Order Notes And Attributes Report
Read-only: extracts and tabulates order notes and custom attributes for ops review of gift messages and special instructions.
shopify-admin-order-notes-and-attributes-report
Purpose
Queries recent orders and extracts order-level notes and custom line item attributes (e.g., gift messages, personalization text, special instructions, engraving text). Produces a report for ops and fulfillment teams to act on special requests during pick/pack. Read-only — no mutations.
Prerequisites
shopify store auth --store --scopes read_orders read_ordersParameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| store | string | yes | — | Store domain (e.g., mystore.myshopify.com) |
| days_back | integer | no | 1 | Lookback window (default: last 24 hours for daily ops use) |
| attribute_keys | array | no | [] | Specific line item attribute keys to extract (e.g., ["gift_message", "engraving"]); empty = all |
| only_with_notes | bool | no | false | Only include orders that have a note or attributes |
| format | string | no | human | Output format: human or json |
Safety
> ℹ️ Read-only skill — no mutations are executed. Safe to run at any time.
Workflow Steps
orders — query Inputs: query: "created_at:>=', first: 250, select note, customAttributes, lineItems { customAttributes }, pagination cursor
Expected output: Orders with notes and custom attributes; paginate until hasNextPage: false
only_with_notes: true: filter to orders with non-empty note or non-empty customAttributesattribute_keys specified: filter line item attributes to matching keys onlyGraphQL Operations
# orders:query — validated against api_version 2025-01
query OrderNotesAndAttributes($query: String!, $after: String) {
orders(first: 250, after: $after, query: $query) {
edges {
node {
id
name
createdAt
displayFulfillmentStatus
note
customAttributes {
key
value
}
lineItems(first: 20) {
edges {
node {
id
title
quantity
variant {
sku
}
customAttributes {
key
value
}
}
}
}
shippingAddress {
firstName
lastName
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}
Session Tracking
Claude MUST emit the following output at each stage. This is mandatory.
On start, emit:
╔══════════════════════════════════════════════╗
║ SKILL: Order Notes and Attributes Report ║
║ 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>
On completion, emit:
For format: human (default):
══════════════════════════════════════════════
ORDER NOTES & ATTRIBUTES REPORT (<days_back> day(s))
Orders queried: <n>
Orders with notes: <n>
Orders with attributes: <n>
#<name> <customer> [<status>]
Note: "<note text>"
Line: "<product>" gift_message: "Happy Birthday!"
Output: order_notes_<date>.csv
══════════════════════════════════════════════
For format: json, emit:
{
"skill": "order-notes-and-attributes-report",
"store": "<domain>",
"period_days": 1,
"orders_queried": 0,
"orders_with_notes": 0,
"orders_with_attributes": 0,
"output_file": "order_notes_<date>.csv"
}
Output Format
CSV file order_notes_ with columns:
order_name, order_id, created_at, fulfillment_status, customer_name, order_note, line_item_title, line_sku, attribute_key, attribute_value
Error Handling
| Error | Cause | Recovery |
|---|---|---|
THROTTLED | API rate limit exceeded | Wait 2 seconds, retry up to 3 times |
| No orders with notes | Quiet period or no note collection | Exit with 0 results if only_with_notes: true |
Best Practices
days_back: 1) so pickers/packers have a printed list of special instructions before starting.attribute_keys: ["gift_message"] to focus on just gift orders during holiday season.