Omuni - compliance check

[sandeepshahi]

/on_search

• invalid split timings for store provided (fixed timings can be used in this scenario)
• "@ondc/org/statutory_reqs_packaged_commodities" is mandatory for the provided category
• name,building,door,country attributes are not required in /bpp/providers/locations/address

/on_select

• "quantity" and "location_id" attributes are not required in order/items
• order/ttl is invalid attribute
• Standard Delivery from Delhi to Bengaluru can't be fulfilled in 32 Hrs
• Why are 2 fulfillments created if delivery TAT and pickup location are same?

/on_confirm

• store name /fulfillments[1]/start/location/descriptor/name can't change (check /on_search for provider name)

/on_status (Order-picked-up)

• /fulfillments/0/end/time/timestamp (delivery time) should not be present until order is delivered
• /fulfillments/1/end/time/timestamp (delivery time) should not be present until order is delivered
• Why are two invoices provided with same url? (only 1 invoice should be provided per order)

/on_status (Order-Delivered)

• delivery timestamp (/end/time/timestamp) can't be equal to the pickup timestamp (start/time/timestamp)

all the applicable return states should be provided for verification

Flow 2

• How can the same location be both serviceable/non-serviceable?
• invalid cancellation flow; should be initiated by seller

Flow 3

• invalid flow; seller rejection should be through /on_update call

Flow 4

• unit price must be present for out-of-stock items in quote/breakup
• invalid flow; check test case scenario document (part fill flow is missing)

Flow 5

• invalid flow; why every flow is shown as non-serviceable; refer to test case scenario document for exact requirements

@gowtham2307

[gautham0703]

Hi @bluecypher @Rishabh-ondc Please find the latest PR attached below : https://github.com/ONDC-Official/verification-logs/pull/952 Flow 1 : /on_search

1. invalid split timings for store provided (fixed timings can be used in this scenario)-> We are using fixed time as mentioned in the document : Log reference for the same : “time”: { “days”: “1,2,3,4,5,6,7”, “schedule”: { “frequency”: “PT24H”, “holidays”: [], “times”: [ “0000”, “2359" ] } } Fixed in the latest version : https://github.com/ONDC-Official/verification-logs/pull/952
2. “@ondc/org/statutory_reqs_packaged_commodities” is mandatory for the provided category -> Updated in the latest version : https://github.com/ONDC-Official/verification-logs/pull/952
3. name,building,door,country attributes are not required in /bpp/providers/locations/address -> Will be updated in the fix PR : https://github.com/ONDC-Official/verification-logs/pull/952

/on_select: “quantity” and “location_id” attributes are not required in order/items => Fixed in the updated version : https://github.com/ONDC-Official/verification-logs/pull/952 order/ttl is invalid attribute -> fixed in the updated version : https://github.com/ONDC-Official/verification-logs/pull/952 Standard Delivery from Delhi to Bengaluru can’t be fulfilled in 32 Hrs -> this is test environment, actual tat for the delivery will be picked from our courier partners. : https://github.com/ONDC-Official/verification-logs/pull/952 Why are 2 fulfillments created if delivery TAT and pickup location are same? -> each unique items will be created as a consignment at our end which will be shipped based on the best sourcing logic. -> As discussed this is the business construct. /on_confirm store name /fulfillments[1]/start/location/descriptor/name can’t change (check /on_search for provider name) -> provider descriptor is the seller, and the fullfilment start location would be the fulfilment location names present inside the seller. -> As discussed this is the business construct.

/on_status (Order-picked-up) /fulfillments/0/end/time/timestamp (delivery time) should not be present until order is delivered -> Fixed in the updated version : https://github.com/ONDC-Official/verification-logs/pull/952 /fulfillments/1/end/time/timestamp (delivery time) should not be present until order is delivered -> Fixed in the updated version : https://github.com/ONDC-Official/verification-logs/pull/952 Why are two invoices provided with same url? (only 1 invoice should be provided per order) -> Since if there are multiple shipments that are getting shipped based on sourcing, invoice for order can have at each shipment level. -> As discussed this is a business construct. /on_status (Order-Delivered) delivery timestamp (/end/time/timestamp) can’t be equal to the pickup timestamp (start/time/timestamp) -> Fixed in the updated version : https://github.com/ONDC-Official/verification-logs/pull/952

Flow 2 How can the same location be both serviceable/non-serviceable? -> if some of the items are not serviceable from the same store it is will be shown at item level. invalid cancellation flow; should be initiated by seller -> https://github.com/ONDC-Official/verification-logs/pull/952 Flow 3 invalid flow; seller rejection should be through /on_update call -> https://github.com/ONDC-Official/verification-logs/pull/952 Flow 4 unit price must be present for out-of-stock items in quote/breakup -> invalid flow; check test case scenario document (part fill flow is missing) -> https://github.com/ONDC-Official/verification-logs/pull/952 Flow 5 invalid flow; why every flow is shown as non-serviceable; refer to test case scenario document for exact requirements -> https://github.com/ONDC-Official/verification-logs/pull/952

[sandeepshahi]

Avoid using placeholder values; use cases must be realistic and feasible

/on_search

• bpp/descriptor/symbol must include the link of the logo/image of seller app
• Why both the store locations have same GPS address?
• None of the items are mapped to location "TCNS_W706". Is this intentional?

/on_select

• Delivery from Delhi to Bengaluru can't be fulfilled in 28 Hours using Standard Delivery (use suitable fulfillment category)
• "@ondc/org/provider_id" is not a valid attribute

/on_init

• locations is not a valid attribute in /provider

/on_confirm

• symbol, images, short_desc, long_desc are not required in /fulfillments/start/location/descriptor

/on_status

• estimated pickup and drop time ranges can't be same
• Invoice URLs can't be the same for both the fulfillment
• separate unsolicited calls should be initiated to track the status of both the fulfillment

/on_update

• Return_Initiated: Why is refund trail added to settlement details (Return isn't even approved yet)?
• All the applicable return states should be provided for verification

Flow 2

• Why item is getting out of stock in case of location non-serviceability
• seller initiated cancellation is still missing

Flow 3,4

• All the issues identified by the utility must be rectified (issues in /on_status and /on_update)

Flow 4,5

/on_select

• Invalid Flow (check test case scenario document)
• unit price of the item must be present for out-of-stock items

@gowtham2307

[gowthamam0703]

Hi @bluecypher @Rishabh-ondc Please find the latest PR attached below : https://github.com/ONDC-Official/verification-logs/pull/1122

[sandeepshahi]

Common Issues

/on_search

• short_desc and long_desc should have valid values in descriptor
• geocoding of store location is invalid; gps and address mismatch

/on_select

• TAT of more than 24 hours should be converted into days

/on_update (Return_Picked)

• /fulfillments/2/state/descriptor/code must be equal to Order-picked-up
• returned item must be present in quote/breakup with remaining count i.e. 0
• object for refund details should only be appended in "@ondc/org/settlement_details" once received from the buyer app

Flow 5

• check previously raised issues

@gowthamam0703

[gowthamam0703]

Hi @bluecypher @Rishabh-ondc, As discussed, Flow 5 for partial quantity serviceability is not being supported by Business use case of Omuni, For rest of the issues will be updating the lates PR.

[gowthamam0703]

Hi @bluecypher @Rishabh-ondc, As discussed, Flow 5 and 4 for partial quantity serviceability is not being supported by Business use case of Omuni, Lates PR attached with new flows of Flow1, Flow2 and Flow 3 with the below PR : https://github.com/ONDC-Official/verification-logs/pull/1201 Please verify and let us know if there are any issues.

[sandeepshahi]

@gowthamam0703, For Flows 4 and 5, you may include scenarios where one of the items is completely out of stock.

[gowthamam0703]

https://github.com/ONDC-Official/verification-logs/pull/1216/files# Hi @bluecypher @Rishabh-ondc, Please find the above PR where we have updated the latest logs.

[sandeepshahi]

@gowthamam0703, all the previously identified issues must be resolved before resubmitting logs.

[gowthamam0703]

Hi @bluecypher @Rishabh-ondc All the issues have been resolved as per disucssion and updated the latest PR : https://github.com/ONDC-Official/verification-logs/pull/1239 Please verify and let us know if any issue. Thanks & Regards.

[sandeepshahi]

/on_search

• incorrect mapping of SKU, images and category_id (eg. women's kurta is mapped to "Infant Bath Accessories" with images of Tshirts)
• value of net_quantity_or_measure_of_commodity_in_pkg in "@ondc/org/statutory_reqs_packaged_commodities" is invalid
• "month_year_of_manufacture_packing_import" can't be empty
• items/short_desc should have valid values

/on_select

• item id: 8903017060383 is unavailable as per the catalog; seller app must repond with proper NACK
• @ondc/org/TAT should be in minimalistic format (P7D instead of P7DT0H0M)

/on_update (Return_Approved)

• estimated time range for Reverse QC fulfillment should be feasible

/on_update (Return_Picked)

• /fulfillments/2/state/descriptor/code must be equal to Order-picked-up

@gowthamam0703