Which branches will stock out first?
Surface replenishment risk across locations before someone discovers the problem by phone or missed sale.
AI Workflows
Ask inventory questions in plain English. Get answers your team can act on.
Stocklyst gives operators and internal tools a practical AI layer for inventory work. Ask what is low, what is stale, what moved, or which branches are at risk, then turn the answer into reports, alerts, and follow-up actions.
Ask stock questions directly
Skip the manual export step when the team just needs a usable answer now.
Turn answers into reports
Use the response in alerts, summaries, dashboards, or scheduled workflows.
Keep access controlled
Company-scoped keys and deliberate access rules make AI useful without making it loose.
Start with real operator use cases
Low stock, branch risk, stale inventory, and exception reporting are where this becomes valuable fast.
01 — Questions operators already ask
This is about faster decisions, not AI theater.
The best AI workflows are not abstract. They answer the stock questions teams already ask every day and remove the manual checking that slows decisions down.
What is low across all warehouses right now?
Get one clear answer instead of building ad hoc filters and exports every time the question comes up.
Which SKUs have not moved in 60 days?
Find stale inventory early enough to act before excess stock turns into wasted cash.
What should I review before I reorder?
Use AI to narrow the list so managers focus on the items that actually need a decision.
02 — From question to action
The useful answer is the one that changes what happens next.
The point is not getting a clever response. The point is getting something a manager, operator, or report workflow can use immediately.
Example operator question
Show low stock items by branch Which branches are at risk this week? List stale items that have not moved in 60 days
Why this matters operationally
- Ask in plain language instead of building a one-off export first.
- Get a response that can feed dashboards, alerts, or management review.
- Keep company context explicit so the answer stays operationally safe.
- Use the same pattern for quick questions and repeatable reporting workflows.
Technical guardrails
- Query Builder: 30 requests/minute
- Reports: 20 requests/minute
- Exports: 10 requests/minute
- Company-scoped context required
03 — Technical proof
The workflow is real because the technical surface is real.
For teams that want to connect internal tools or automations, Stocklyst exposes a practical API surface for querying, reporting, and controlled access.
Natural-language endpoint
/api/v1/ai/query
Convert operational prompts into inventory responses.
Flexible query engine
/api/v1/query/builder
Build structured requests for deeper reporting logic.
API key management
/api/v1/api-keys
Create and manage scoped keys for scripts and assistants.
OpenAPI contract
/api/v1/openapi
Inspect the available surface before building automations.
04 — Where AI earns its keep
Use AI where repeated checking wastes operator time.
The best use cases are low-stock review, branch health checks, stale inventory checks, and scheduled reporting. That is where AI removes repeated manual work without introducing operational risk.
Daily low-stock review
Give managers a clear starting point for replenishment instead of making them build the same report every morning.
Branch risk checks
Compare locations quickly and spot the branches that need attention before stock issues spread.
Stale inventory review
Find dead stock earlier so the team can act before storage and cash costs keep growing.
Exception reporting without report-building friction
Generate useful summaries from plain-language prompts instead of relying on ad hoc spreadsheets and one-off exports.
05 — FAQ
Frequently asked questions
What AI functionality is available today in Stocklyst?
Stocklyst provides natural-language inventory querying through /api/v1/ai/query, a flexible query engine through /api/v1/query/builder, plus report and export endpoints for automation workflows.
Can I use Claude or OpenAI-based tools with Stocklyst?
Yes. Any client that can call REST APIs can work with Stocklyst. Teams commonly connect Claude Code, Cursor, internal scripts, and custom operator tools.
How is access secured?
Access is controlled with API keys generated inside Stocklyst, explicit company context, and endpoint-level rate limits for safer operations.
Can AI workflows run reports and exports?
Yes. Report and export endpoints can be called by scheduled automations or operator-triggered workflows for inventory insight, exception reporting, and downstream analysis.
Ready to move past
38 MCP tools · works with Claude · ChatGPT · Cursor