nstore (BA) - compliance check

[sahil-ondc]

Flow 1

search (full catalog)

• Why logs with bap_id as 'buyer-app-preprod-v2.ondc.org' submitted ?

on_search (full catalog)

• Why logs with bap_id as 'buyer-app-preprod-v2.ondc.org' submitted ?

search (inc catalog)

• context/bpp_id and context/bpp_uri should not be provided in search request
• is pull based incremental search supported?

Flow 2

select

• incremental on_search changes should get reflected, item (id: 106) was disabled in on_search (incremental), how its being selected
• additional properties tags and parent_item_id should not be provided at item level
• Buyer selects multiple items (> 1 qty for each item) for checkout as per the roll out plan https://docs.google.com/spreadsheets/d/1JZV6ZQzXcHUsOwegGtArX3DdIXYIy3gxkhQ00q7kICc/edit#gid=1367601795

on_select

• /fulfillments[1]/@ondc/org/TAT (O2D) in /on_select can't be equal to @ondc/org/time_to_ship (O2S) in /on_search (BNP should NACK)

on_init

• @ondc/org/TAT mismatch, BNP should NACK

confirm

• accept_bpp_terms, static_terms should not be provided as those are not enabled yet
• payment/uri should not be provided as placeholder

status, track

• transaction logs should be provided

on_status (out-for-delivery)

• pickup timestamp mismatch, BNP should NACK

Flow 3

• Buyer selects multiple items (> 1 qty for each item) for checkout as per the roll out plan https://docs.google.com/spreadsheets/d/1JZV6ZQzXcHUsOwegGtArX3DdIXYIy3gxkhQ00q7kICc/edit#gid=1367601795

Flow 4,5,6

• same as flow 2

Note

• Flow 1 should be submitted correctly
• Counterparty application should be different not from same NP
• Does variants supported ?

@nstoretech

[sahil-ondc]

The Buyer App should send ‘NACK’ for the following errors

Flow 1

search

• "status": "open” is not a valid key as per contract in search action call

search_inc

• Static terms are not required for now in seach_inc

Flow 2

on_init

• Only @ondc/org/buyer_app_finder_fee_type, @ondc/org/buyer_app_finder_fee_amount,@ondc/org/settlement_details are required in payment object as only buyer is collecting payment currently. Incase seller wants to collect the payment then you can send it the way you sent

on_status_picked

• Timestamp for pickup is not in range provided in ‘Delivery’ fulfillment for ‘start’ object

on_status_delivered

• Timestamp for delivery is not in range provided in ‘Delivery’ fulfillment for ‘end’ object

track

• Missing track payload

Above issues are processed in other flows as well

Flow 3

on_select_out_of_stock

• Domain-Error is missing in on_select_out_of_stock

flow 4

on_cancel

• The quote should be zero in this case as the order was cancelled pre-shipment

flow 5

confirm

• Incorrect payload is provided

flow 6

• @ondc/org/settlement_details are not captured properly in the update and on_update calls as same
• fulfillments ids are not captured properly in reverse_qc and liquidation
• Why the fulfillment id for ‘Return’ is same for reverse_qc and liquidation in on_update_interim_reverse_qc ?

@nstoretech

[sandeepshahi]

Flow 1

/search (inc)

• incremental stop request must be submitted for verification

Flow 2

/on_select

• TAT for self pickup (O2S) can't be more than TAT (O2D) for Delivery

/on_init

• delivery TAT should not change; must remain the same as in /on_select

/confirm

• delivery TAT should not change; must remain the same as in /on_select

/on_confirm

• end can't be earlier than start in /fulfillments/end/time/range

/on_status

• how can actual delivery timestamp be provided in the picked state?
• actual pickup timestamp is not captured correctly in picked state
• invoice must be provided once the order is picked

Flow 4

/on_cancel

• order/updated_at is not captured correctly

  Flow 6

/on_update (Interim)

• reason_desc should not change

Ques:

• is pull based incremental search supported ?
• while processing concurrent catalog updates, are the timestamps at provider / item level being used for correct versioning?
• is /select being called for every change in cart, with the same transaction_id?
• while processing unsolicited callbacks, are you ensuring that each response has a unique message_id for a specific transaction_id?
• is confirm retry enaled as mentioned in the contract?
• validation of cancellation reason codes when initiated by SNP?
• are hyperlocal and intercity fulfillment states being processed correctly as per routing.type of "P2P" or "P2H2P";
• provide a demo video with the entire order journey

@nstoretech

[nstoretech]

As requested, The UI changes has been made and we are sharing the "Cancel" and "Return" order video flow through this link separately.

https://nstoreassets.s3.amazonaws.com/Demo+videos/screen-recorder-mon-aug-12-2024-12-04-00.webm

https://nstoreassets.s3.amazonaws.com/Demo+videos/screen-recorder-mon-aug-12-2024-12-13-30.webm

[sandeepshahi]

@nstoretech, the reverse QC flow is invalid. How can return be successfully processed without a reverse QC flow? A return is only considered successful once it has been picked up.

As requested, The UI changes has been made and we are sharing the "Cancel" and "Return" order video flow through this link separately.

https://nstoreassets.s3.amazonaws.com/Demo+videos/screen-recorder-mon-aug-12-2024-12-04-00.webm

https://nstoreassets.s3.amazonaws.com/Demo+videos/screen-recorder-mon-aug-12-2024-12-13-30.webm