ActionBigCommerceUpdated September 2026

How do I update a BigCommerce product?

Short answer: You can update product in BigCommerce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the BigCommerce Update Product action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Product in BigCommerce — start free All 10 BigCommerce actions

Update Product in BigCommerce — start free

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 run history shows the failed step with its input and the error message BigCommerce returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Product support batch operations?

Run Update Product inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within BigCommerce's rate limits.

More actions