Topolo Docs Topolo Platform
Open workspace

Update Inventory item

Update an existing item and return its aggregate stock. Descriptive fields omitted from input are preserved, but omitting status sets active and therefore reactivates an archived item.

Outcome

Update an existing item and return its aggregate stock. Descriptive fields omitted from input are preserved, but omitting status sets active and therefore reactivates an archived item.

Before you start

  • Verify the authenticated identity, exact environment and pinned approved organization context before preparing an action.
  • The published application permission is workspace:write. Discover a granted Inventory workspace and bind that exact resource. Supplied identifiers do not grant access.
  • Authorize the documented inventory, review, import, notification, metering, privacy or archival effects before CLI --confirm or MCP confirm:true.

Discover the target

topolo whoami --json
topolo actions get app_topolo_inventory.items.update --detail --json
topolo resources topolo-inventory --json
topolo workspaces list topolo-inventory --json
  • Select the exact granted workspace id as INVENTORY_WORKSPACE_ID. Fixture ids authorize no live operation.
  • Discover item ids through items.list or the reviewed items.create response in this workspace.

Request

PATCH /api/items/{itemId}

Save action input as payload.json. Inspect the plan for the exact path, query and body. Set INVENTORY_WORKSPACE_ID from granted resource discovery.

Inspect and test this action in the signed action console, then perform the verification below.

Input fields

FieldRequiredTypeConstraints
nameOptionalstringOptional nonblank replacement name; omitted value is retained.; {"minLength":1}
skuOptionalstringOptional replacement SKU subject to workspace uniqueness; omission preserves it.; {"minLength":1}
descriptionOptionalstringOptional trimmed replacement; blank text clears the description.; {}
unitOptionalstringOptional nonblank replacement unit; omission preserves it.; {"minLength":1}
lowStockThresholdOptionalnumberOptional nonnegative replacement threshold; does not emit a notification on its own.; {"minimum":0}
itemIdRequiredstringExisting item id from this granted workspace.; {"minLength":1}
statusOptionalstringExplicit active or archived. Omission writes active, including for previously archived records.; {"enum":["active","archived"]}

View the complete input schema in the action console. The same schema is available through CLI and MCP action discovery.

Effects

  • Updates the existing row in the organization and verified workspace; stock is still derived from movements and cannot be overwritten here.
  • Omitted name, SKU, description, unit and threshold retain prior values. Explicit blank description clears it; nonblank unit is trimmed.
  • status is archived only when explicitly supplied as archived; active or omitted status writes active. Changing the threshold does not emit a stock notification.

Interpret the response

Use response path $.item.id for inventory_item. An empty list does not discover a target.

Read items.get after updating and compare every intended field, especially status. When editing an archived item without reactivation, explicitly pass status archived.

The success schema was checked against captured handler responses. Delegated Auth profile and canonical widget context fields can vary; exact Inventory projections and all six raw SQL export stores are source-reviewed. Error examples retain their actual refusal shapes.

View the complete success schema in the action console. The worked examples below retain complete captured responses; action discovery supplies the exact schema.

Worked examples

Captured exported Worker responses use both real local SQLite D1 databases with all six committed migrations, synthetic Auth/workspace grants and simulated Notify/Nexus/archive transport. They prove local handler shapes and scoped behavior, not live authorization, notification delivery, metering acceptance or environment deployment. Large 100-row list/capped-dashboard captures are retained in local evidence; committed tests verify those limits while worked guides use smaller complete responses. Refused examples demonstrate boundaries and must not be executed as successful workflows.

Successful request

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Notify/Nexus/archive transport. No live delivery, billing or environment deployment proof. Captured scenario: explicit archive status survives patch.

Input · payload.json:

{
  "itemId": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
  "description": "",
  "status": "archived"
}

CLI:

topolo actions validate app_topolo_inventory.items.update --data @payload.json --json
topolo actions plan app_topolo_inventory.items.update --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.items.update --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_inventory.items.update",
    "input": {
      "itemId": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
      "description": "",
      "status": "archived"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "item": {
    "id": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
    "workspaceId": "ws_inventory_fixture",
    "sku": "KRAFT-MAILER-240X320",
    "name": "Kraft mailer 240x320",
    "description": "",
    "unit": "unit",
    "status": "archived",
    "lowStockThreshold": 20,
    "quantityOnHand": 0,
    "createdByUserId": "usr_inventory_fixture",
    "createdByEmail": "operator@example.test",
    "createdAt": "2026-10-04T05:46:36.190Z",
    "updatedAt": "2026-10-04T05:46:36.343Z"
  }
}

HTTP 200. Read items.get after updating and compare every intended field, especially status. When editing an archived item without reactivation, explicitly pass status archived.

Another supported request

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Notify/Nexus/archive transport. No live delivery, billing or environment deployment proof. Captured scenario: omitted status reactivates archived item.

Input · payload.json:

{
  "itemId": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
  "lowStockThreshold": 20
}

CLI:

topolo actions validate app_topolo_inventory.items.update --data @payload.json --json
topolo actions plan app_topolo_inventory.items.update --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.items.update --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_inventory.items.update",
    "input": {
      "itemId": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
      "lowStockThreshold": 20
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "item": {
    "id": "invitem_b29c4494-14e0-43dd-87e6-e33856f732af",
    "workspaceId": "ws_inventory_fixture",
    "sku": "KRAFT-MAILER-240X320",
    "name": "Kraft mailer 240x320",
    "description": "",
    "unit": "unit",
    "status": "active",
    "lowStockThreshold": 20,
    "quantityOnHand": 0,
    "createdByUserId": "usr_inventory_fixture",
    "createdByEmail": "operator@example.test",
    "createdAt": "2026-10-04T05:46:36.190Z",
    "updatedAt": "2026-10-04T05:46:36.316Z"
  }
}

HTTP 200. Read items.get after updating and compare every intended field, especially status. When editing an archived item without reactivation, explicitly pass status archived.

Refused request · HTTP 404

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Notify/Nexus/archive transport. No live delivery, billing or environment deployment proof. Captured scenario: update missing item.

Input · payload.json:

{
  "itemId": "invitem_missing",
  "name": "Missing"
}

CLI:

topolo actions validate app_topolo_inventory.items.update --data @payload.json --json
topolo actions plan app_topolo_inventory.items.update --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 404:

{
  "error": "not_found"
}

HTTP 404. The handler refused this request. Resolve its exact cause before retrying; input validation can reject an invalid fixture before it reaches the handler.

Verify the result

  • Read items.get after updating and compare every intended field, especially status.
  • When editing an archived item without reactivation, explicitly pass status archived.

Errors and recovery

  • invalid_action_input (HTTP 400): Correct only the exact fields reported by the published schema validator. An invalid input can be refused before its handler.
  • action_permission_required (HTTP 403): Stop when the verified credential lacks the published action permission. Resource identifiers and organization ownership do not grant that permission.
  • organization_required (HTTP 403): Use the specifically authorized organization context; personal scope cannot act on organization-owned Inventory data.
  • workspace_required (HTTP 400): Discover an authorized Inventory workspace and pass its exact separate resource binding; bootstrap does not select a workspace.
  • workspaces_unavailable (HTTP 503): Retain the request id and report unavailable canonical workspace discovery; do not invent a default workspace.
  • not_found (HTTP 404): Discover the resource through the appropriate authorized list or creation response; a foreign or absent identifier is not accessible.
  • name_required (HTTP 400): Provide a nonblank name when changing it; preserve the old name by omitting this field.

Auth, action-input validation and platform resource resolution can refuse a request before its handler. Retain the exact error, request id and context; requesting another context is not a legitimate way to bypass a refusal.

Recovery boundary

Capture items.get before the update, then call items.update with every previous descriptive field and explicit previous status. This compensates state but produces a new updatedAt and does not erase history or prior notifications.

  • Get Inventory item: Read one item in the granted workspace with descriptive fields, archive status and quantityOnHand computed from all its movements. Archived items remain readable; missing or foreign items return not_found.

Evidence

Captured exported Worker responses use both real local SQLite D1 databases with all six committed migrations, synthetic Auth/workspace grants and simulated Notify/Nexus/archive transport. They prove local handler shapes and scoped behavior, not live authorization, notification delivery, metering acceptance or environment deployment. Large 100-row list/capped-dashboard captures are retained in local evidence; committed tests verify those limits while worked guides use smaller complete responses. Capture digests and test scenarios are retained in the source fixture records.