Demander App Version 5.28.0 - 06/01/2026

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

News/Improvements: Validation of load capacity and number of pallets

Situation: The Demander App did not support the Load Capacity field or validate the quantity of pallets in the order according to the selected record.
Solution: We implemented the Load Capacity field in the order, with synchronization, configurable mandatory and integration with Order Field Policy. We added validation of the quantity of pallets in the order in relation to the limit defined in the selected record, with a visual indication of the quantity used and the maximum allowed. The field can also be displayed in the order list depending on the visibility configuration.

Maintenance of the issuing seller when editing orders

Situation: When editing an order issued by another seller (common scenario between parent and agent seller), the Demander App changed the seller issuing the order to the logged-in seller.
Solution: We adjusted the editing flow to preserve the original seller issuing the order. New orders and duplicate orders continue to register normally with the issuing seller according to the current flow.

Alphanumeric CNPJ support

Situation: With the evolution of the CNPJ format by the Federal Revenue, the CNPJ field in the app only accepted numbers, preventing the registration and consultation of alphanumeric documents.
Solution: We adjusted the CNPJ field to accept letters and numbers, with automatic formatting in the XX.XXX.XXX/XXXX-XX standard and validation of check digits according to the new rule, maintaining compatibility with traditional numeric CNPJs.

Rules for consulting CPF/CNPJ in customer registration

Situation: The Demander App did not apply the company’s configuration that defines how the CPF/CNPJ query should work when registering new customers, generating different behavior than expected and from Demander Web.
Solution: We implemented the flow controlled by configuration comportamentoConsultaDocumentoCliente, with three modes of operation: optional query when online (allowing offline registration), mandatory query with editable fields after return, and mandatory query with protection of returned fields (except telephone numbers and emails). The system also validates, at the time of saving, whether the protected fields remain equivalent to the data originally consulted.

Configurable nomenclature of the Additional Fee

Situation: Several places in the app displayed the fixed label “Additional Tax”, ignoring the custom name configured by the company in the Name of additional tax rate key.
Solution: We adjusted all display points to use the name configured by the company, including order registration, financial summary, item details, order list, details modal and configuration of visible fields. When the configuration is not defined, the app maintains the default name “Additional Fee”.

Corrections: Asset filter in the listing of financial securities

Status: The list of financial securities did not have a filter by active/inactive status, making it difficult to consult when there were inactive records in the database.
Solution: We added an active filter to the list of financial securities, allowing you to view only active records or include inactive ones as needed.

Product Observation Policy did not render HTML tables

Situation: Product observations configured with HTML content containing tables (HTML table) were not displayed correctly in the app.
**Solution:**We adjusted the rendering of the HTML content of the Product Observation Policy to correctly display tables and other elements formatted.

Grade products shipped with quantity zero

**Situation:**When issuing orders with grid products, items with zero quantity were included in the export/synchronization of the order.
**Solution:**We adjusted the flow so as not to send grid products with zero quantity, avoiding unnecessary records in the order exported.

Exclusion of the company logo in the synchronization

**Situation:**When the company logo was removed or changed on the server, the app kept the old image in the local cache after the synchronization.
**Solution:**We implemented logic to delete the locally stored company logo when it is no longer available in synchronization, ensuring display updated.

Product photos not updating on app

**Status:**After synchronization, the product photos updated on the server continued to display the old image on the app.
**Solution:**We fixed the product image update flow to correctly replace local photos when there is a change in sync.

Selected seller lost when switching between offline and online

**Situation:**When issuing orders, when switching between offline and online mode, the selected seller was lost and needed to be chosen again.
**Solution:**Adjusted the flow to persist the selected seller when switching between offline and online modes while issuing the order.

Release schedule Version

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