ActionBigCommerceUpdated May 2026
How do I change a BigCommerce order's status?
Short answer: Drop the "BigCommerce → Update Order Status" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Order ID order_id | string | Required | The Order ID assigned by Bigcommerce. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
New Status status_id | options | Required | — |
Sample request
{"order_id": "{{trigger.order_id}}","status_id": "{{trigger.status_id}}"}
Returns
{"id": 100,"status": "Shipped","status_id": 2}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Order Status.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Order Status.
What does the Update Order Status action do in BigCommerce?
Transitions an order to a new status (e.g., Pending → Shipped, Shipped → Completed). Useful for "external fulfilment provider confirmed shipment → update BigCommerce status" workflows.
What inputs does Update Order Status require?
Required: Order ID, New Status. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if BigCommerce returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update Order Status support batch operations?
Yes. Run Update Order Status inside a Loop node to process arrays. Tiny Command handles BigCommerce's rate limits automatically so you don't have to throttle manually.
More actions
Other BigCommerce actions.
Action
Create Customer
Creates a new customer in BigCommerce with email (dedupe key), name, addresses, customer group. Useful for "B2B account provisioning from CRM → BigCommerce" workflows where pre-creating customers gates self-serve checkout.
ActionCreate Product
Creates a new product with name, SKU, price, description, categories, weight, dimensions. For high-volume catalog management, prefer the batch endpoint via HTTP action. Optional variants array for products with size/colour options.
ActionGet Order
Returns the order by ID with customer, line items, totals, status, shipping/billing addresses. The standard lookup for workflows that received an order ID via webhook and need richer detail before fulfilment.
ActionGet Product
Returns a product by ID with all configured fields, current inventory, categories, custom attributes. Useful for "sync product changes to external CDN" or "validate product exists before linking from another tool" workflows.
ActionList Categories
Returns the category tree — each category's name, parent, child count, visibility. Useful for resolving category IDs in product-create workflows or for "audit which categories have stale activity" maintenance.
ActionList Orders
Paginated orders with filters by status, customer, date range, total. The base query for "this morning, list yesterday's orders" daily-summary digests and for backfill workflows that catch orders missed during webhook downtime.
Send update order status from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
