π Item Updated
Update item availability per branch
π§© JSON Payload
{
"brand_id": "5000",
"event_time": "2025-01-01 00:00:00",
"event": "item.updated",
"branch_id": "xx1",
"product_id": "11",
"is_stock": "false"
}
π Field Descriptions
Field | Type | Description |
---|---|---|
event | String | Always "item.updated"β type of event |
event_time | Timestamp | Timestamp of when the toggle action occurred |
brand_id | String | The ID of the brand triggering the update |
branch_id | String | The branch where the item status was changed |
product_id | String | The ID of the item being updated |
is_stock | Boolean | "true" if in stock, "false" if out of stock |
π§ Behavior
- Blend sends this webhook to toggle an item's visibility (in stock / out of stock) per branch.
- The POS should reflect this visibility in the branch's front-of-house system or aggregator.
π§ Example Use Cases
- An admin marks a product as unavailable in Blend for a certain branch.
- A product goes out of stock in the kitchen, and the visibility is updated in Blend.
- Re-enabling a previously hidden product sends the same event with "is_stock": "true".
β
Notes
- product_id refers to the SKU, not the internal product database ID.
- is_stock is always a string ("true" or "false"), not a boolean.
- Blend includes an Authorization Bearer token in the header β it must be validated.
- This event is branch-specific. If an item is hidden across multiple branches, the webhook is sent for each one individually.
Updated 10 days ago