ActionBigCommerceUpdated May 2026

How do I update a BigCommerce product?

Short answer: Drop the "BigCommerce → Update Product" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 10 BigCommerce actions

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
Product ID product_id	string	Required	The Product ID assigned by Bigcommerce. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Name name	string	Optional	—
Price price	string	Optional	—
Inventory Level inventory_level	string	Optional	—
Description description	string	Optional	—

Sample request

{
  "product_id": "{{trigger.product_id}}",
  "name": "{{trigger.name}}",
  "price": "{{trigger.price}}",
  "inventory_level": "{{trigger.inventory_level}}",
  "description": "{{trigger.description}}"
}

Returns

{
  "data": {
    "id": 123,
    "name": "Tee",
    "price": 19.99
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Update Product.

Any of these apps can fire this action as part of a workflow.

Google Sheets → BigCommerce

2 Google Sheets triggers

HubSpot → BigCommerce

18 HubSpot triggers

FAQ

Questions about Update Product.

What does the Update Product action do in BigCommerce?

Partial update on a product — change price, inventory, description, categories. For bulk catalog updates, prefer the batch endpoint via HTTP action. Useful for "ERP price update → push to storefront" sync workflows.

What inputs does Update Product require?

Required: Product ID. 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 Product support batch operations?

Yes. Run Update Product 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