Bitsila (TSP) - compliance check
Closed this issue · 7 comments
BLR-0118 commented
Flow 1
- /on_search:
- all item prices should be capped at 2 decimal places;
- provider.locations.address - street & locality are same & incorrect;
- what does serviceability of 0 km mean?
- fulfillment.contact & email can't be empty;
- timestamp for /on_search & /select is same - how?
- /select response is 5 secs - why?
- /on_status - pickup & delivery time not provided;
- order.updated_date should be updated to timestamp of order update; all APIs from /on_confirm are showing same updated_date as in /confirm;
BLR-0118 commented
BLR-0118 commented
- /on_status1 to /on_status5:
- invoice should be generated only after order is picked up;
- isn't there an Order-picked-up state? I didn't see any of the /on_status showing this?
- order.updated_at shows the same timestamp from /on_status2 to /on_status5 even though order states have changed during this transition;
- if payment.type = "ON-FULFILLMENT" (i.e. after delivery), why isn't the payment.status changed to "PAID" when order is delivered?
BLR-0118 commented
BLR-0118 commented
- Isn't there a fulfillment state for "Order-picked-up"? It's going straight from Packed to Out-for-delivery;
- Logic for updating order.updated_at needs to be checked:
- /on_status3: pickup time is 05:56:16 but order.updated_at is 05:54:22
- /on_status4: delivery time is 05:59:00 but order.updated_at is 05:55:20
how??
BLR-0118 commented
BLR-0118 commented
logs cleared
dashbitla commented
ThQ Supriyo
On Sun, Aug 13, 2023 at 6:49 PM Supriyo Ghosh ***@***.***> wrote:
Closed #463 <#463> as
completed.
—
Reply to this email directly, view it on GitHub
<#463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA33OQPYCLSBVXWATEOZMDXVDH4PANCNFSM6AAAAAA3N2BIRM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Best Regards
Dasharatham Bitla
Ph: +1 (408) 607-5079