Suggestions

Add a “take 6 and pay 5” promotion that allows you to combine any product in the catalog, without being limited to specific products or families. When the customer adds 6 products to the order, Handy must automatically identify the one with the lowest price and apply a 100% discount to it. That is, the customer wears all 6 products, but pays only 5. The promotion must be able to be applied again for each group of 6 products; for example, if the customer buys 12 products, the corresponding 2 lower-priced items must be discounted. Currently, promotions require defining activating products or families and a fixed reward product, so it is not possible to configure this mechanic.

Currently, when a product shortage is detected during the liquidation of a route, it is not possible to record the corresponding sale from Handy. This prevents charging the seller and correctly reflecting the movement in inventory. It is requested to incorporate a “Generic Sale Due to Shortage” option within the liquidation process, which allows: Record the product and the missing quantity. Generate the amount to be charged to the seller. Reflect the corresponding adjustment in the route inventory. Preserve the traceability of the movement, identifying it as a shortage registered in liquidation. With this, these cases can be controlled without affecting the consistency of the inventory or the closing of the cash register.

Add a Unit column to sales and delivery tickets, next to Description, Quantity, Unit Price and Amount. Expected example: Cracker Marías 185 g | 1 | Piece | $ 14.00 | $ 14.00. Currently, the ticket already shows a description, quantity, price and amount, but it does not make the sales unit explicit. This can cause errors when stocking or delivering products with similar descriptions or that are sold in different presentations (part, box, package, etc.).

I understand that we don't handle this flow, however, I didn't think it hurt to add the request because it can help customers who need to liquidate routes considering operating expenses. The customer needs an option to record expenses incurred during the route, since operators can take money from the sale of the day to pay for fuel, booths, food or other expenses. The request is to add a simple field called “Expenses” within the route or settlement, where the total amount spent can be captured. This amount should be subtracted from the total to be liquidated, so that the closing of the route correctly reflects how much money the seller/operator must deliver. A single amount field for expenses would be enough, there is no need to separate by type of expense in this first version.

It would be nice to have a map to be able to easily reassign customers, taking into account route amounts.

It is necessary to handle negative inventory in the warehouse during road loading, so that the process allows loading even if the stock available in the warehouse is below zero when the operation so requires.

It would be good if when scheduling visits using rules they are always shown by seller and not everyone's, since it's a lot of information and takes a long time to load, it could also be that you can save several rules with a single save button and not one by one

It must be possible to assign the container that contains it to a product and to count the number of packages with each customer. Management of packaging returns, sale of containers and other scenarios. He is interested in several Adam's breweries.

Have the option of setting goals per product family