Demander App Version 5.1.0 - 08/07/2026

This article presents a list of new features, improvements and corrections made available in the App Demander version.

News/Improvements: View modes in customer and order lists

We added the predefined Standard, Summary and Detailed to the Customer and Order listings, in addition to those already existing in the Product listing.
Switching between presets and deselecting discards the change without modifying the listing. Only by clicking Apply will the chosen visualization be saved.
The viewing preference persists and is loaded automatically when reopening the screen.

Excellent product — Validation and display of inconsistencies when finalizing the order

We implemented visual history alert indicators in the rows of order items, with chips and an orange border, signaling products with a quantity or price outside the customer’s historical purchasing average.
Products never purchased by the customer are also highlighted when the alert setting is active.
In order view only mode, alerts are not displayed, keeping the list clean.
Quantity and price tolerances are read from the company’s actual configurations, respecting the limits defined by management.

Flex balance policy — Calculation by basis and criteria

The Demander App now considers the base value and calculation criteria fields of the level 3 price policy to calculate the flex balance moved in the order item.
We added four calculation criteria: Standard (transacts debit and credit), Debit only, Credit only and Does not calculate.
The default values fully preserve the current behavior of the flex balance, with no impact for companies that do not use the new parameterization.

General discount per order value

The general discount dialog now allows you to apply discounts both by percentage and by monetary value directly on the order.
Synchronization between percentage and value is automatic based on the gross value of the products.
When the order has no items or a zero value, the discount fields and the Apply button are blocked, preventing invalid calculations.

Inventory query by branch when adding items

We provide stock query by branch in the order item row menus, both on mobile and on the web.
In the product/item detail, we include a dedicated section with the balance of each branch, following the order type’s inventory control settings.
We implemented the configuration to display only the stock of the order branch, aligned with Android behavior, in addition to the option to list all active branches.

Corrections: Calculation of credit limit default

Situation: The offline calculation of the value of outstanding bonds considered only the principal value of the bond, without including fines and interest. This underestimated the total owed by the customer and could release a credit limit greater than the correct one.
Solution: We corrected the local query to add fines and interest charges to the value of the title when applicable. Titles with zero or zero charges maintain the calculation of the principal value. The available credit limit now reflects the actual value of outstanding bonds.

Display of inactive grids in iOS

Situation: In iOS Flutter, product grids marked as inactive kept appearing on the grid selection screen when adding a product to the order.
Solution: Adjusted the local grid query to return only active grids. Inactive grids no longer appear when selecting the order item, maintaining the same behavior that already exists in native Android.

Purchase history filter by order type

Situation: The purchase history listed orders of all types, including those that should not appear in the latest sales, such as bonuses and gifts.- Solution: We have added the Sales Orders Only filter, enabled by default, which only displays orders of types configured as relevant to purchase history. The filter is available both in history by product and by customer, with a badge indicating when active.

Customer filling in delivery address

Situation: When registering a new delivery address on the Demander Flutter App, the fields remained empty for manual filling, requiring the seller to enter all the data from scratch.
Solution: We implemented confirmation to automatically fill in the new address with the customer’s data, exactly as happens in native Android. When creating a new address, the app asks if you want to copy the data and fills in the street, number, neighborhood, zip code, contact, telephone numbers, CPF/CNPJ and city. Refusal keeps the registration empty for manual filling.

Ordering of financial securities in the customer register

Situation: The list of financial securities accessed through the customer registration tab did not display the Sorting option in the Options menu, available only in the main list of securities.
Solution: We have also added the Sort option to the financial securities listing menu in the customer registration, allowing you to sort by maturity and value in the same way already available on the main securities screen.

Visual indication of negative stock

Situation: When issuing a web order, the negative stock balance was no longer displayed in red when the company’s configuration was set only to alert the seller about a lack of stock, making it difficult to visually identify products with an insufficient balance.
Solution: We have corrected the stock balance components in the order item row to apply the color red whenever available stock is negative, regardless of the stock validation mode configured. The rule for allowing or blocking product inclusion remains unchanged.

Quantity in NFe printing with XML decimal places

Situation: When printing NFe/NFC-e in Flutter, the quantity of the item was displayed with zeros on the right (e.g.: 3.0000 UN), which could be incorrectly interpreted in the coupon.
Solution: We corrected the XML conversion so that decimal values such as 3.0000 are converted to an integer (3 UN), preserving the decimal places only when the quantity is fractional (e.g.: 1.5 UN). Tax identifiers such as NFe key, CNPJ and invoice number remain as text, without changes.

Delivery date in order row

Situation: The order listing row only displayed the issue date, without showing the expected delivery date, which is relevant information for the seller’s planning.
Solution: We added the delivery date to the order row, respecting the visibility configuration of the listing fields, so that the seller can quickly see when each order should be delivered.

Version release schedule

Also check out the news on Demander’s other platforms: