ONDC-Official / v1.2.0-logs

Retail and Logistics Logs for 1.2.0

9 stars 248 forks source link

Closed abhinavv245 closed 6 months ago

abhinavv245 commented 6 months ago

All Flows

/search

/init

/confirm

ttl is missing in context
fulfillments/end/instructions/code must be equal to one of the allowed values (1,2,3)
billing/created_at and updated_at mismatches in /billing in /init and /confirm
linked_order/order/weight/value Payload weight mismatches from /search
order/tags not to be sent as bpp_terms are not applicable yet
Average Pickup Time (fulfillments/start/time/duration) mismatches from the one provided in /on_search
instructions/tags to be removed

/track and /cancel

Note: One of the flows should have deferred RTS in /update, and only Group B logs to be submitted

@harshmohta1611

harshmohta1611 commented 6 months ago

We aren't supporting deferred RTS and will be sending RTS : true in /confirm itself @abhinavv245

harshmohta1611 commented 6 months ago

abhinavv245 commented 6 months ago

/init

billing/created_at and updated_at is not recorded correctly w.r.t context/timestamp
for POST-FULFILLMENT, payment will be collected by BAP, thus settlement details need not be sent by LBNP (will be sent by LSP, though optional)

/confirm

start/instructions/short_desc should not have more than 6 alphanumeric (also for OTP, code will be 4, short_desc will not be provided, OTP will be sent via authorization object later via /update)
end/instructions/short_desc PCC should not be same as DCC \"87527572\"
price is not required in /items (already present in quote, refer to example in contract document)

/update

in case of authorization with OTP, LBNP need to provide OTP and its validity via /update call once the order is packed i.e. ready_to_ship=yes, and for delivery OTP to be provided once the LSP is out for delivery (via /update call)

@harshmohta1611

BLR-0118 commented 6 months ago

/cancel - reason code 010 is invalid for LBNP (only valid code for LBNP is 007 as per this current list);

BLR-0118 commented 6 months ago

@harshmohta1611 - pls fix the above; clearing LBNP v1.2.0 logs subject to the above fix;