> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/changelog/upcoming-improvements.md).

# Upcoming Improvements

See what improvements and fixes are coming next in Struct PIM. Most items are driven by customer feedback and grouped by expected release month.

Struct PIM is continuously evolving.

On this page, you’ll find an overview of the smaller improvements and fixes we’re currently planning to release in the coming months. Most of these items are based directly on customer feedback and everyday use of the platform.

We’ve grouped the planned changes by expected release month to give you visibility into what’s coming next. Please note that these timelines are estimates and may shift as we refine, prioritize, and test new improvements.

{% hint style="info" %}
If you have suggestions or feedback, we’d love to hear from you — many of the updates below started as ideas from our customers.
{% endhint %}

{% @jira-integration/jira-integration fullWidth="false" %}


---

# 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://docs.struct.com/changelog/upcoming-improvements.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.