ucp-fulfillment
Implement the UCP Fulfillment extension — shipping and pickup methods, destinations, fulfillment groups, selectable options, and estimated delivery. Use when adding shipping/pickup logic to a UCP checkout.
Best use case
ucp-fulfillment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement the UCP Fulfillment extension — shipping and pickup methods, destinations, fulfillment groups, selectable options, and estimated delivery. Use when adding shipping/pickup logic to a UCP checkout.
Teams using ucp-fulfillment should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ucp-fulfillment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ucp-fulfillment Compares
| Feature / Agent | ucp-fulfillment | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement the UCP Fulfillment extension — shipping and pickup methods, destinations, fulfillment groups, selectable options, and estimated delivery. Use when adding shipping/pickup logic to a UCP checkout.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# UCP Fulfillment Extension ## Before writing code **Fetch live spec**: Web-search `site:ucp.dev specification fulfillment` and fetch the page for the exact fulfillment schema, method types, group structure, and configuration options. ## Conceptual Architecture ### Extension Relationship Fulfillment **extends** `dev.ucp.shopping.checkout`. It is pruned from negotiation if the Checkout capability is not in the intersection. Declared as `"extends": "dev.ucp.shopping.checkout"` in the schema. ### Key Concepts - **Methods**: `shipping` or `pickup`. Each method is tied to specific line items via `line_item_ids`. - **Destinations**: Where items go. For shipping: postal addresses. For pickup: retail locations. - **Groups**: Business-generated packages/shipments. Each group belongs to a method and contains selectable options. - **Options**: Individual fulfillment choices within a group (e.g., "Standard Shipping 5-7 days", "Express 1-2 days"). Each has a title, carrier, estimated delivery window, and cost totals. - **Available Methods**: Alternative fulfillment methods the buyer can switch to, with `fulfillable_on` indicating availability (`"now"` or an ISO date). ### Configuration The fulfillment extension has two configuration scopes: **`platform_config`** (set by the platform, describes platform-level behavior): - `supports_multi_group`: Whether the platform supports handling multiple fulfillment groups/shipments **`merchant_config`** (set by the merchant/business, describes business-level behavior): - `allows_multi_destination`: Whether multiple shipping addresses are supported (per method type) - `allows_method_combinations`: Which method types can be combined (e.g., `[["shipping", "pickup"]]`) ### Flow 1. Platform creates checkout with line items 2. Business returns fulfillment methods with empty destinations and groups 3. Platform updates checkout with shipping address(es) 4. Business recalculates and returns fulfillment groups with selectable options 5. Platform selects an option per group (or lets user choose) 6. Business updates totals to include fulfillment costs 7. Checkout becomes `ready_for_complete` ### Implementation Guidance Fetch the exact current schema from the live spec before implementing. The fulfillment data model has nested structures (methods → destinations → groups → options) that evolve across spec versions. Also check the sample server at https://github.com/Universal-Commerce-Protocol/samples for reference fulfillment implementation.
Related Skills
spree-shipping-fulfillment
Build and customize Spree's shipping and fulfillment — ShippingMethod, ShippingCategory, Zone/ZoneMember, ShippingRate, the Stock::Estimator service, StockLocation/StockItem/StockMovement, multi-shipment orders, ShippingCalculator classes (FlatRate, FlatPercentItemTotal, PerItem, FlexiRate), shipment state machine, returns (ReturnAuthorization → CustomerReturn → Reimbursement → Refund), and integrating carrier APIs (UPS, FedEx, ShipStation). Use when configuring shipping rules, building fulfillment integrations, or debugging shipping-rate calculations.
medusa-fulfillment
Implement Medusa v2 fulfillment — fulfillment module, provider interface, shipping options, fulfillment sets, shipping profiles, and multi-warehouse support. Use when adding fulfillment providers.
acp-fulfillment
Implement ACP fulfillment options — shipping, digital delivery, in-store pickup, and local delivery. Use when building fulfillment selection, rate calculation, delivery window management, or tracking integration.
woo-testing
Test WooCommerce extensions — PHPUnit unit/integration tests, WP test suite, WooCommerce test helpers, E2E with Playwright, and WP-CLI test scaffolding. Use when writing tests for WooCommerce plugins or setting up a test environment.
woo-shipping
Build WooCommerce shipping methods — WC_Shipping_Method, shipping zones, shipping classes, rate calculation, tracking, and integration with carriers. Use when creating custom shipping integrations or configuring shipping logic.
woo-setup
Install WooCommerce, configure the development stack, and set up a local dev environment with WP-CLI, Docker, or wp-env. Use when setting up a new WooCommerce project or development environment.
woo-security
Implement WooCommerce security — nonces, capabilities, input sanitization, output escaping, data validation, PCI compliance considerations, and WordPress security best practices. Use when hardening a WooCommerce store or reviewing security posture.
woo-plugin-dev
Create WooCommerce extensions/plugins — file structure, main plugin file, activation/deactivation hooks, custom database tables, autoloading, and WordPress plugin API. Use when building new WooCommerce extensions or structuring plugin code.
woo-performance
Optimize WooCommerce performance — object caching, transients, HPOS, database optimization, Action Scheduler, lazy loading, and query optimization. Use when improving store performance or diagnosing slowness.
woo-payments
Build WooCommerce payment gateways — WC_Payment_Gateway, direct/redirect/hosted integrations, tokenization, subscriptions support, refunds, and PCI compliance. Use when creating custom payment method integrations.
woo-hooks-filters
Master the WordPress hook system for WooCommerce — actions, filters, hook priorities, WooCommerce-specific hooks, and extensibility patterns. Use when adding functionality via hooks or understanding the WooCommerce execution flow.
woo-frontend
Customize WooCommerce frontend — template overrides, theme integration, shortcodes, hooks for product/cart/checkout display, and WooCommerce block themes. Use when modifying the storefront appearance or building WooCommerce themes.