order-processing-pipeline

order-processing-pipeline is a skill for Claude Code, Codex from finsilabs/awesome-ecommerce-skills. It costs 27 tokens per session (2,638 once invoked), scanned A, original, MIT.

An order state machine tracks an online order as it moves from payment through fulfillment, shipping, and delivery. Webhooks notify other systems when each status changes.

In plain words
What is it for?
It is for connecting a store or custom storefront to fulfillment providers, ERP systems, shipping services, and returns workflows.
Why use it?
It prevents order statuses from getting out of sync and keeps fulfillment, inventory, emails, and tracking updates coordinated.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex; mentions Gemini CLI; mentions OpenCode.

Good fit It is for connecting a store or custom storefront to fulfillment providers, ERP systems, shipping services, and returns workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add finsilabs/awesome-ecommerce-skills --skill order-processing-pipeline
Clone the repo
git clone --depth 1 https://github.com/finsilabs/awesome-ecommerce-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for order-processing-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline/github.svg)](https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline)
Your own site
<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for order-processing-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/order-processing-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,638 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.02638
Opus 5 $0.00014 $0.01319
Sonnet 5 $0.00005 $0.00528
Haiku 4.5 $0.00003 $0.00264

Measured 9d ago against content hash 9e2777a25e1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

order-processing-pipeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/payments-checkout/order-processing-pipeline/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Order Processing Pipeline

Overview

Every ecommerce order follows a lifecycle: placed → payment confirmed → fulfillment started → shipped → delivered. Shopify, WooCommerce, and BigCommerce each implement this as a built-in order status system with webhook events at each transition. The goal is to configure these transitions correctly, wire your 3PL or fulfillment system to the right webhooks, and automate side effects (confirmation emails, inventory deduction, tracking notifications) at each stage.

Custom state machine code is only needed for headless storefronts or complex multi-step B2B workflows that platforms cannot handle natively.

When to Use This Skill

  • When order statuses become inconsistent (e.g., fulfilled orders showing as pending)
  • When implementing automated order routing to a 3PL or fulfillment provider
  • When adding order status webhooks for ERP, shipping, or returns integrations
  • When building a custom headless order management system

Core Instructions

Step 1: Understand your platform's order statuses and transitions

Platform Order Statuses Transition Mechanism
Shopify Open → Partially Fulfilled → Fulfilled → Cancelled; Financial: Pending → Authorized → Paid → Refunded Shopify Admin + webhooks; automated by Shopify Payments and fulfillment apps
WooCommerce Pending → Processing → On Hold → Completed → Cancelled → Refunded → Failed WooCommerce status system; transitions via admin, plugins, or wc_update_order_status()
BigCommerce Pending → Awaiting Payment → Awaiting Fulfillment → Awaiting Shipment → Shipped → Completed + others BigCommerce Admin + Orders API webhooks
Custom / Headless Define your own state machine Build with explicit transition validation

Step 2: Configure order processing automation


Shopify

Configure payment → order confirmation flow:

  1. Shopify automatically moves orders from Open to Paid when Shopify Payments confirms the charge
  2. Go to Settings → Notifications to verify the Order confirmation email is enabled — this fires automatically on payment
  3. For non-Shopify payment methods, verify the gateway sends a payment success signal to Shopify; if orders stay Pending payment after payment, check your gateway settings

Read the full file on GitHub · 223 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 223 lines · 27 tokens per session scan A 9e2777a25e1d

Subscribe to this mod's changes

order-processing-pipeline is a skill published in the GitHub repository finsilabs/awesome-ecommerce-skills (52 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 2,638 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.