Suggestions

To be able to have a route planner that allows us to plan loads and better distribute each day's work.

Currently, the customer's credit when placing an order is validated against the available one they have, it would be better if it could be validated against the total allotted to be able to pick up the order, and the delivery person already charges and delivers it to the customer.

It would be very nice to have on the collection ticket the delivery number paid with the collection made

Currently the discounts are shown on the ticket and are very good, even so it would be even better to show the amount of discount that is being given for each product.

It would be great if products whose promotion is not completed due to lack of inventory were not allowed to get in the way and even if the product cannot be delivered, it is confusing because it appears on the screen for the mobile user.

Currently using the /api/v2/priceList/ {priceListCode} endpoint I can specify one or more products in the “items” array to change their price for a certain “price list”; however, the server response contains the entire price list, including products that were not modified. This behavior places an unnecessary burden on the response, which can affect performance, especially when working with large price lists. It would be very useful to have an additional endpoint (or an improvement on the current one) that allows you to update one or more products without the server returning the entire list, but only the products that were edited. This would significantly improve the efficiency of the process on both the client and server sides.

While on the street, the preventive worker is the one who keeps and maintains the customer base, the delivery person should not be able to move this data because it can cause conflicts and mismatches.

The suggestion is to add the delivery number to the receipt associated with it in the billing report, in this way it would be much easier to track it without having to review delivery by delivery.

Be able to have an integration with SAP B1 and connect it with Handy.

The suggestion is to add new roles in Handy, one so that you can move account information without having to give the account administrator permission and another that can see data but without moving anything, so that you can take data to analyze, but without being able to influence the operation.