Find WooCommerce processing orders that contain a mix of in-stock and out-of-stock/backordered items. For each such order, identify which items can ship now versus which must wait. Exports a split-shipment plan so fulfillment teams can send partial shipments immediately. Read-only — no orders are modified.
Prerequisites
WooCommerce store with REST API enabled
Consumer Key with Read scope
Stock management must be enabled per product
Minimum WooCommerce version: 3.5.0
Parameters
Parameter
Type
Required
Default
Description
store_url
string
yes
—
Base URL of the WooCommerce store
consumer_key
string
yes
—
WooCommerce REST API consumer key (ck_...)
consumer_secret
string
yes
—
WooCommerce REST API consumer secret (cs_...)
dry_run
bool
no
false
No effect — read-only skill
format
string
no
human
Output format: human or json
order_status
string
no
processing
Order status to scan
Authentication
WooCommerce uses OAuth 1.0a for HTTP and Basic Auth over HTTPS.
For each order: compare line item quantities against available stock.
Items where stock_quantity >= line_item.quantity → can ship now
Items where stock_quantity < line_item.quantity → backorder
Flag orders with at least one shippable and one non-shippable item as split-shipment candidates.
Step 4 — Export plan
API Endpoints Used
GET /wp-json/wc/v3/orders — processing orders
GET /wp-json/wc/v3/products/{id} — product stock
GET /wp-json/wc/v3/products/{id}/variations — variation stock
Pagination Strategy
WooCommerce REST API uses page/per_page pagination (not cursor-based).
Standard pattern:
page = 1
while True:
response = GET /endpoint?per_page=100&page=page
process(response)
if len(response) < 100: break
page += 1
Maximum per_page is 100 for most endpoints.
The X-WP-Total and X-WP-TotalPages response headers report totals.
Always read X-WP-TotalPages on the first request to estimate job size.
Session Tracking
Claude MUST emit the following output at each stage. This is mandatory.