fulfillment-sop

Document Figurio order fulfillment procedures from release to delivery.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/cellarwood/figurio --skill fulfillment-sop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulfillment-sop
Source: https://github.com/cellarwood/figurio/tree/main/skills/fulfillment-sop
Command: npx skills add https://github.com/cellarwood/figurio --skill fulfillment-sop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, auditable operational procedure to ensure paid orders move from release through packaging, shipment, tracking, exception resolution, and final support handoff without ambiguity or conflicting records.

Core Features & Use Cases

  • Establishes a single owner, explicit current state, and next action for every order to remove ambiguity.
  • Standardizes production handoffs, packaging checks, carrier selection, tracking updates, and exception classification for MCAE and other fulfillment partners.
  • Includes exception handling paths (delays, address issues, damage, lost parcels, wrong item) and a consistent support handoff format to preserve the decision trail.
  • Use case: operations staff perform daily queue reviews and escalate orders at risk of missing promised ship dates using this SOP.

Quick Start

Write a fulfillment SOP for a paid Figurio order covering pre-release checks, production handoff to MCAE, packaging standards, carrier selection and tracking, exception paths, and support handoff requirements.

Frequently Asked Questions about fulfillment-sop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a standard operating procedure for order fulfillment and shipping?

To create an order fulfillment SOP, document each stage from release to delivery including production handoffs, packaging verification, carrier tracking, and exception handling. This ensures paid orders move through shipment without ambiguity or conflicting records.

What is the best way to handle fulfillment exceptions like lost parcels or wrong items?

The best way to handle fulfillment exceptions is to define specific classification paths for delays, address issues, damage, lost parcels, and wrong items. This standardizes resolution and preserves the decision trail for support handoff.

How do I manage production handoffs to fulfillment partners without losing order state?

Manage production handoffs by maintaining a single authoritative order record with explicit owner and state fields. This removes ambiguity and ensures the next action is clear during transitions to external fulfillment partners.

Can I use this fulfillment SOP for daily operations queue reviews and escalation?

Yes, operations staff can use this SOP for daily queue reviews to escalate orders at risk of missing promised ship dates. It establishes a consistent support handoff format to track decisions and resolve exceptions.

Do I need shipment and tracking integration to operationalize order fulfillment procedures?

Yes, shipment and tracking integration is required to operationalize order fulfillment. The SOP relies on these integrations alongside a single authoritative order record to document handoffs and manage exception artifacts.

Why does order ambiguity occur in fulfillment and how do I resolve it?

Order ambiguity occurs when multiple conflicting records exist without a clear owner. Resolve it by establishing a single authoritative order record with explicit current state and next action fields for every order.