New Features
Page type: Operational procedure — describes the process for requesting and prioritizing new features. This is not a catalog of existing features.
Requests for new features, significant changes, or demands outside the contracted scope must be registered through Axia's official request form.
When to use this process
Use this process when:
- The desired feature does not exist on the current platform.
- The demand involves structural changes to existing modules that go beyond minor adjustments.
- The requested development is not included in the scope of the current contract.
To activate features that have already been delivered in a release, see the Updates process.
How to request
Access the official request form and fill it in with as much detail as possible: problem context, desired behavior, estimated business impact, and — if available — examples or references.
Request link:
https://forms.office.com/r/nn8yPZtEAi
What happens after submission
After receiving the request, Axia's product and technology team performs a technical and feasibility analysis. The outcome may be:
| Outcome | Description |
|---|---|
| Roadmap inclusion | The feature is added to the platform roadmap and delivered in a future release |
| Module evolution | The demand is addressed as an extension of an existing module, within the contracted scope or through an addendum |
| Custom project | The feature is developed as a specific project with a separate commercial proposal |
| Not approved | The request does not align with the product direction or is not technically feasible at this time |
Submitting a request does not imply an obligation to implement. Axia commits only to analysis and a formal response.
Response timeframe
Requests are analyzed and answered within 10 business days from the confirmation of receipt.