hdls Inventory

hdls Inventory is a headless, MCP-native inventory & stock backend. It manages items, stock levels, and locations, operated entirely through named tools your AI assistant calls. It stands in for tools like inFlow, Cin7 — same job, no UI to run.

💬 Just ask

"Add 50 units of SKU-123 and show me what's low on stock."

You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.

How Inventory is organized

The headline entity is the item — start there, then attach the rest to it. Records connect by reference: a stock_level links to an item and a location. The stock_movement table is an append-only timeline — every change and note lands there and is never edited or deleted.

Entity	Purpose	Relates to
`item`	A stock-keeping product (SKU) with costing, pricing, and reorder policy.	—
`location`	A physical or logical place stock is held: warehouse, store, bin, transit, supplier, customer.	—
`stock_level`	On-hand and reserved quantity of one item at one location (unique per item+location).	`item`, `location`
`stock_movement`	Append-only ledger of every inventory change (receipt, shipment, transfer, adjustment, count, return).	`item`

Common workflows

Each line is one real sequence of tool calls — your assistant chains them for you.

Set up an item end to end: create_item → adjust_stock → transfer_stock

Tools

Call these at https://hdls.ai/api/mcp/inventory. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.

Create

Tool	What it does	Required	Optional
`create_item`	Create a new item.	`sku`, `name`	`description`, `category`, `unit`, `barcode`, `status`, `cost`

Update & advance

Tool	What it does	Required	Optional
`adjust_stock`	Adjust stock.	`item_id`, `quantity`	`from_location_id`, `to_location_id`, `movement_type`, `unit_cost`, `reference`, `note`
`transfer_stock`	Transfer stock between locations.	`item_id`, `quantity`	`from_location_id`, `to_location_id`, `movement_type`, `unit_cost`, `reference`, `note`

Find & read

Tool	What it does	Required	Optional
`search_items`	Search items by free-text and/or column filters (tenant-scoped, paginated).	—	`search`, `filters`, `limit`, `orderBy`
`low_stock_report`	Report on stock.	—	—

Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.

Field reference

Every field you can set on each record. Custom fields you add live alongside these in data.

`item`

Field	Type	Required	Notes
`sku`	text	Yes
`name`	text	Yes	Display name.
`description`	text
`category`	text
`unit`	text
`barcode`	text
`status`	text		Lifecycle state.
`cost`	numeric(14,2)
`price`	numeric(14,2)
`currency`	text
`reorder_point`	numeric(14,3)
`reorder_qty`	numeric(14,3)
`data`	json		Free-form JSON — custom fields live here.

`location`

Field	Type	Required	Notes
`name`	text	Yes	Display name.
`code`	text
`loc_type`	text
`address`	text
`is_active`	true / false
`data`	json		Free-form JSON — custom fields live here.

`stock_level`

Field	Type	Required	Notes
`item_id`	id	Yes	Links to an `item`.
`location_id`	id	Yes	Links to a `location`.
`quantity`	numeric(14,3)
`reserved`	numeric(14,3)
`data`	json		Free-form JSON — custom fields live here.

Tailor it with custom fields

Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.

Roles & safety

Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass tenant_id, and you can only ever see your own data (enforced by Postgres row-level security).
Role-gated. Permissions run reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner.
History is append-only. The stock_movement timeline is never edited or deleted — it's your audit trail.

Connect

On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "inventory" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/inventory as a connector in your assistant — see Connect your assistant.

A worked example

The literal call your assistant makes when you ask it to create the headline record:

Tool: create_item
Arguments: {
  "sku": "example",
  "name": "Acme Corp"
}

See All products · Connect your assistant · Automation