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.
Best use case
acp-fulfillment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using acp-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/acp-fulfillment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How acp-fulfillment Compares
| Feature / Agent | acp-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 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.
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
# ACP Fulfillment ## Before writing code **Fetch live docs**: 1. Fetch `https://developers.openai.com/commerce/specs/checkout/` — fulfillment options are part of the checkout spec 2. Web-search `site:github.com agentic-commerce-protocol spec json-schema FulfillmentOption` for the schema 3. Web-search `site:github.com agentic-commerce-protocol rfcs orders fulfillment` for fulfillment in orders ## Conceptual Architecture ### Four Fulfillment Types | Type | Use Case | Key Fields | |------|----------|------------| | **shipping** | Physical delivery to address | Carrier, tracking number/URL, delivery windows | | **digital** | Downloads, licenses, access | Access URL, license key, expiration date | | **pickup** | In-store or locker collection | Location, ready-by window, pickup-by deadline | | **local_delivery** | Same-day/local service delivery | Service area, delivery window | ### How Fulfillment Works in Checkout 1. **Create session** — Merchant returns available `fulfillment_options[]` based on items and address 2. **Agent selects** — Agent (or buyer) picks a `fulfillment_option_id` 3. **Update session** — Agent sends the chosen `fulfillment_option_id` in an update 4. **Merchant recalculates** — Totals update to include fulfillment cost 5. **Post-purchase** — Merchant emits order updates with tracking and delivery details ### FulfillmentOption Object Each option includes: - `id` — Unique identifier for this option - `type` — One of the four types above - `title` — Display name (e.g., "Standard Shipping") - `subtitle` — Additional info (e.g., "5-7 business days") - `carrier` — Carrier name for shipping - Delivery window (estimated dates/times) - Pricing — Cost of this fulfillment option ### Delivery Windows Time-based constraints: - **Estimated delivery** — Date range for when buyer can expect delivery - **Ready-by** (pickup) — When the order will be ready for collection - **Pickup-by** (pickup) — Deadline to collect before order is returned - **Delivery window** (local delivery) — Time slot for delivery ### Fulfillment in Orders After checkout completion, fulfillment details appear in order webhook events: - Tracking number and tracking URL - Carrier name - Shipment status updates - Delivery confirmation ### Best Practices - Return all available fulfillment options on session create (not just the cheapest) - Compute fulfillment costs based on actual address (not estimates) - Include realistic delivery windows — agents present these to buyers - Update tracking information in real-time via order webhooks - Support multiple fulfillment groups for split shipments - Handle address validation before computing fulfillment options Fetch the checkout spec and JSON schema for exact FulfillmentOption field names, types, and required fields before implementing.
Related Skills
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.
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.
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.