> For the complete documentation index, see [llms.txt](https://lmile.gitbook.io/lmile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lmile.gitbook.io/lmile-docs/resources/roadmap.md).

# Roadmap

## 未整備

* [ ] Partner API Key 発行 UI（現在は管理者が手動発行）
* [ ] Rate Limit 導入
* [ ] OpenAPI 3.1 スキーマ公開
* [ ] バッチ処理の並列化・チャンク対応
* [ ] dry\_run モード（Inventory API。Products / Order Line Master は対応済）

## 完了

* [x] Ingestion API（Products / Inventory Levels / Order Line Master）
* [x] 商品・在庫の変更ログ自動記録 + 日次在庫スナップショット
* [x] 受注ルーティング（出荷元判定・出荷指示生成・WMS dispatch）
* [x] Fulfillment（在庫確保・配送ラベル・ピッキングリスト・宛先住所リカバリ）
* [x] 売越し対応（oversell / reallocate / 売越しケース / 出荷元変更）
* [x] Webhooks（在庫変動通知・出荷ステータス通知）
* [x] マーチャント単位の API キー（shop スコープ）


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lmile.gitbook.io/lmile-docs/resources/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.