| Table of Contents |
|---|
...
Fulfillment service aggregating all fees into delivery fee for orders from food aggregators (eg. glovo, uberEats)
This is part of the first implementation that we can see here :Code Block language typescript const deliveryFees = input.charges?.fees?.reduce((acc, fee) => { if (fee.type === PartnerFeeType.DELIVERY_FEE) { acc = fee.total?.amount ?? 0; } return acc; }, 0);DMP never receive the fees associated with the order
Although DMP calculates the delivery fee in the WL during the quote workflow, this information does not persist when the order is created. Besides that, no information regarding the other fees is received by it, as we can see in the create delivery webhook documentation.
...
A simple solution is fixing the delivery fee in fulfillment calculation and altering the delivery integration to receive this information. Fixing the calculation is important since the fees returned for the POS will be used by them to create the delivery later (to be confirmed).
IMPORTANT CONSIDERATIONS:
The proposed solution assumes that the POS will send the fee breakdown, either on the commitOrder endpoint or the submitOrder. This was proposed by Winrest and the ground work is already laid off in partners API given the list of fees it receives.
The exact fee structure may change to include new fields in the near future, so this feature should be implemented after
is done.Jira Legacy server System JIRA serverId 255417eb-03fa-3e2f-a6ba-05d325fec50d key IBFEC-1467 Although the POC focuses on aggregators, the changes will work for WL orders as well, since the create delivery process is the same.
...