ONDC-Official / v1.2.0-logs

Retail and Logistics Logs for 1.2.0
9 stars 272 forks source link

Ref-Buyer (RET10, RET11, RET12) - compliance check #13

Open sandeepshahi opened 1 year ago

sandeepshahi commented 1 year ago

Full Catalog Pull

/on_search

Incremental Pull

/search

/on_search (store closed temporarily)

/select

/on_select

/init

/confirm

/on_confirm

@wemakshaychavan

sandeepshahi commented 1 year ago

Buyer App Issues:

inc_search

/select

Seller App Issues:

Catalog

/on_select

@wemakshaychavan

sandeepshahi commented 1 year ago

inc_search

/select

Seller App Issues:

inc_on_search

/on_search

/on_select

/on_init

/on_confirm

@wemakshaychavan

shubhamuengage commented 1 year ago

on_select

delivery tat is same as time_to_ship because this merchant is doing self delivery therefore its time to ship and delivery tat will be same

@bluecypher

shubhamuengage commented 1 year ago

@bluecypher in on_select regarding oos whats the issue i am unable to understand.

sandeepshahi commented 1 year ago

@shubhamuengage

sandeepshahi commented 1 year ago

Reference Buyer App

/search

/confirm

/update

/cancel

Krenai Seller App

/on_search

/on_select

/on_init

/on_confirm

/on_status

/on_update

/on_cancel

@wemakshaychavan

sandeepshahi commented 8 months ago

several issues in the seller app; pls test with their latest build.

Flow 1

/on_search

Flow 2

/select

/on_init

/track

Flow 3

/select1

Flow 6

/on_update

@wemakshaychavan

BLR-0118 commented 7 months ago

RET10 logs:

  1. Pls check issues reported here for flows 2, 4 & 5 for Kiko Live;
  2. from the above, these issues need to be fixed: uniqueness check for message_id, invalid keys;
  3. for Flow 6, in /updatep1 & /updatep2, refund will be using same mode of payment as used by the buyer for placing the order; I hope we're not hardcoding anything here
BLR-0118 commented 7 months ago

@wemakshaychavan - pls check the above

BLR-0118 commented 7 months ago

RET12 logs:

BLR-0118 commented 7 months ago

@wemakshaychavan

BLR-0118 commented 7 months ago

RET11

  1. Flow 5 /on_cancel* is invalid (communicated to Uengage); are we NACK'ing this?
  2. Flow 6 /update is invalid - for make-to-order items, you need to send the item & customization(s) in same return request;
  3. Are we enforcing min/max for nested customizations e.g. in flow 2, customization 2455698/2455705 have nested customization groups 128078 / 128074 / 128075 / 128076 / 128068 - min is 0 for all (flow 2 is thus ok), but if min is 1 for one or more of these, are we forcing buyer to select the min no of customizations?
BLR-0118 commented 7 months ago

@wemakshaychavan - pls check above for RET11

BLR-0118 commented 7 months ago

RET13

  1. /on_search:
    • unitized qty for item ENGFLFRPKT18 should be "18 ml" but is blank; what are we showing?
BLR-0118 commented 7 months ago

@wemakshaychavan - pls see comment for RET13 above

BLR-0118 commented 7 months ago

@wemakshaychavan - as discussed today morning, pls respond to issues raised above for RET10/11/12

wemakshaychavan commented 7 months ago

RET:10

Flow 1 /on_search

values of colour attributes are invalid (either empty values or hex value without "#"); variant groups are defined based on the size and colour attributes. How is the catalog processed? - Adding this as a validation where we do not get color with # then will send NACK. context/city STD code mismatches with store's area_code - Fixed Flow 2 /select

city/code must map with the delivery location (/fulfillments/end/location) - Fixed /on_init

invalid settlement terms (settlement_basis, settlement_window, withholding_amount ) provided; should be provided by collector (BNP here) /track inprogress

tracking is set as false and no tracking info is provided in /on_status; Flow 3 /select1 seller had updated qty during log generation

items out of stock should not be allowed to be selected again Flow 6 /on_update fixed

invalid schema; quote/price should be in string format; BNP must respond with a NACK

wemakshaychavan commented 7 months ago

RET:11

Flow 5 /on_cancel* is invalid (communicated to Uengage); are we NACK'ing this? We are sending NACK Flow 6 /update is invalid - for make-to-order items, you need to send the item & customization(s) in same return request; Please share the valid sample request for the same @BLR-0118 Are we enforcing min/max for nested customizations e.g. in flow 2, customization 2455698/2455705 have nested customization groups 128078 / 128074 / 128075 / 128076 / 128068 - min is 0 for all (flow 2 is thus ok), but if min is 1 for one or more of these, are we forcing buyer to select the min no of customizations? Yes

wemakshaychavan commented 7 months ago

RET12:

quote.price.value should be string (strange that's wrong only here); Fixed quote entries are incorrect: quote.price.value should be "4000", quote.breakup[] has 2 entries for item "7803924_L" for qty 2 & 1 (not sure why the qty 1 entry is here as that was part cancelled earlier); Adding this as a part of validation