# Feature request process and pricing

We understand that customers may have needs beyond the extensive set of features already available in Flow Retail.

We receive feature requests from customers every week, and those identified as valuable for the broader platform are prioritized on our roadmap, developed into the core system, and released to all our clients.

Requests that are defined as very customer-specific are typically delivered as separate extensions, ensuring the core platform remains clean and maintainable.

{% hint style="warning" %}
We have a strict policy of never limiting features to specific clients, even if they have funded the development. In exceptional cases, we may agree on limited availability for up to three months on F100 tasks. See the [F100 requests](#f100-requests-and-other-clients) section below for details.
{% endhint %}

### Transparent model

We believe in full transparency, and work closely with our clients to build the best retail commerce platform. As a rule of thumb, we share the cost of developing requests, depending on their nature, as described below.

<table><thead><tr><th width="222.22265625">Type of request from client</th><th width="189.3984375">Timeline</th><th>Price</th><th>Estimation</th></tr></thead><tbody><tr><td>Feature requests with no urgency.</td><td>Added to our roadmap and implemented at our discretion.</td><td>Included, unless implemented as an extension.</td><td>N/A</td></tr><tr><td>Feature requests with a required ETA of maximum 3 months.</td><td>Added to our roadmap, but fast-tracked and implemented according to agreement with one or multiple clients.</td><td><p>50% of the development cost – in practice 50% discount on the hours spent.</p><p></p><p>We call this F50.</p></td><td>Simple estimation, without any commitment.</td></tr><tr><td>Feature requests with a required ETA of 1-8 weeks – basically needs to be started on immediately.</td><td>Normally started on immediately.</td><td>100% of the time spent.<br><br>We call this F100.</td><td>No estimation. We usually skip detailed estimates for such requests, as it’s more efficient to invest that time directly into development.</td></tr><tr><td>Integration development.</td><td>As agreed in each case.</td><td>Any custom integration development work towards other systems is charged by the time spent.<br><br>We call this F100. </td><td>Simple estimation, without any commitment.</td></tr><tr><td>Bugs/improvements in existing features.</td><td>ASAP depending on severity.</td><td>Included, however bugs in tasks defined as F100 are normally charged. </td><td>Normally no estimation, as they simply just needs to be done.</td></tr></tbody></table>

### F100 requests and other clients

If a client has covered the cost of developing a specific F100 request and another client later (typically within < 6 months) wants the same feature, we may, at our discretion, require the new client to contribute a portion of the original development cost. This amount will then be credited to the first client as ‘free’ hours for future requests, rather than being refunded.

### Rates

Per 01.01.2025, the hourly rate for any development work is NOK 1480. This also includes general consultancy and project management related to the request.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flowretail.com/docs/developers/feature-request-process-and-pricing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.