Currently the mobile apps load the tenant's adhoc charge configurations and allow the user to edit the values of those adhoc charges in various views across the app.
e.g. when viewing the details of Sale Orders, Purchase Orders & Consignments, when submitting a POD, when submitting a Consignment Error, when finishing packing a Sale Order etc.
Recently an additional requirement around the use of customer-specific adhoc charges was identified through a support ticket raised by a CC customer (https://support.cartoncloud.com/browse/CC-10620).
The issue is that customer-specific changes to whether an adhoc charge is enabled or disabled are not reflected in the mobile apps.
e.g. if an adhoc charge is disabled on the tenant level but enabled on the customer level, this adhoc charge will not be displayed on the mobile app, even if for example a Sale Order for that particular customer is being viewed.
This also applies vice versa.
The suggestion is to always use the adhoc charges defined for the customer rather than the tenant's (as the customer adhoc charges will also include all tenant adhoc charges, but with potential customer-specific changes).
This will require a fair bit of rework around the mobile app adhoc charge loading functionality (e.g. database changes; considering when to load those adhoc charges to not cause additional payloads unnecessarily) as well as additional endpoints from the backend.
