> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Product Order

Look up the current status of a product order placed with order-product. Returns the order status, line items, final price breakdown (once complete), estimated delivery, and shipment tracking numbers — tracking numbers appear once the order ships. Ideal for: order tracking workflows, shipment notifications, verifying delivery progress.

Catalog action Integrations

Look up the current status of a product order placed with order-product. Returns the order status, line items, final price breakdown (once complete), estimated delivery, and shipment tracking numbers — tracking numbers appear once the order ships. Ideal for: order tracking workflows, shipment notifications, verifying delivery progress.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `get-product-order` |
| Category | Integrations |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `shopping`, `order`, `status`, `tracking`, `ecommerce`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `orderId` | `string` | Yes | Order identifier returned by order-product. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `orderId` | `string` | Yes | Order identifier. |
| `status` | `string` | Yes | Current order status. |
| `items` | `array` | Yes | Line items on the order. |
| `trackingNumbers` | `array` | Yes | Shipment tracking numbers — these appear once the order ships. |
| `priceComponents` | `object \| null` | Yes | Final price breakdown in integer cents — null until the order completes. |
| `estimatedDelivery` | `string \| null` | No | Estimated delivery date, when available. |
| `errorType` | `string \| null` | No | Failure reason when the order failed, otherwise null. |
| `merchantOrderIds` | `array` | Yes | Retailer-side order identifiers, once placed. |

## Examples

**Workflow node**

```json
{
  "type": "get-product-order",
  "payload": {
    "orderId": "example-orderId"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/get-product-order/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "orderId": "example-orderId"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.