Skill

acp-fulfillment

Implements ACP fulfillment options: shipping, digital delivery, in-store pickup, local delivery. Covers selection, rate calculation, delivery windows, tracking, and order updates per OpenAI commerce specs.

OpenAI

REST API

api-development

backend

Install

npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerce

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGrepGlobWebSearchWebFetch

Preview

**Fetch live docs**:

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

claude-code-plugin-release

1 file

Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.

claude-mem

64.7k

Stats

Parent Repo Stars14

Parent Repo Forks9

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

ACP Fulfillment

Before writing code

Fetch live docs:

Fetch https://developers.openai.com/commerce/specs/checkout/ — fulfillment options are part of the checkout spec
Web-search site:github.com agentic-commerce-protocol spec json-schema FulfillmentOption for the schema
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

Create session — Merchant returns available fulfillment_options[] based on items and address
Agent selects — Agent (or buyer) picks a fulfillment_option_id
Update session — Agent sends the chosen fulfillment_option_id in an update
Merchant recalculates — Totals update to include fulfillment cost
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.