BuyNxt (SA : RET14) - Compliance check

[Jagannath-wits]

BuyNxt RET14

Flow 1

on_search_full_catalog_refresh

• variants should be implemented and categories should not be empty
• tmpstmp: context/timestamp difference between /on_search and /search should be less than 5 sec
• InvldValueforItem[0][0] : weight: Invalid item value: [172g]. It must be one of the allowed values or match the regex pattern [^[0-9]+(.[0-9]{1,2})?$], shouldn't provide unit as it's already defined in the sheet https://docs.google.com/spreadsheets/d/1APAvavF_BNbTA89benAlGtv0GuFvpn2b6XXi4lSdTTw/edit#gid=244000021.
• bpp/providers[0]/items[0]/descriptor/code: code should have 3:GTIN as a value in /message/catalog/bpp/providers[0]/items[0]/descriptor/code
• bpp/descriptor/accept_bap_terms: accept_bap_terms is not required in bpp/descriptor/tags for now
• bpp/descriptor/collect_payment: collect_payment is not required in bpp/descriptor/tags for now
• prvdr0categories: Support for variants is mandatory, categories must be present in bpp/providers[0]
• desc: short_desc and long_desc can't be same

Flow 2

select

• tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /select api

on_select

• brkupitemstitles5: If the tax price is 0, there is no need to add tax in the breakup

on_confirm

• tags_bap_terms: Tags should have same and valid gst_number as passed in /confirm

on_status_packed

• on_status_packed: Missing Payload

on_status_picked

• invoice: Invoice should be publicly accessible
• if tracking is false no need to provide this :   { "code": "tracking", "list": [ { "code": "gps_enabled", "value": "yes" }, { "code": "url_enabled", "value": "no" } ] }

Flow 3

select_out_of_stock

• tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /select api

Flow 4

on_cancel

• invldQuoteTrailPrices: quote_trail price and item quote price sum for on_cancel should be equal to the price as in on_confirm

Flow 5

on_cancel

• schemaErr0: /message/order/fulfillments/1/@ondc~1org~1provider_name must be string
• schemaErr1: /message/order/fulfillments/1/end/location/address/name must be string
• schemaErr2: /message/order/fulfillments/1/end/location/address/building must be string
• schemaErr3: /message/order/fulfillments/1/end/location/address/country must be string
• schemaErr4: /message/order/quote/breakup/1/@ondc~1org~1item_quantity must be object
• schemaErr5: /message/order/quote/breakup/1/item must be object
• schemaErr6: /message/order/quote/ttl must be string
• schemaErr7: Many of the value are provided null, kindly provide a valid value
• rtoFFObj/end/time: fulfillment type rto end/time should not be present in /on_cancel when state/desc/code is RTO-Initiated

on_status_rto

• on_status_rto: on_status_rto_delivered/on_status_rto_disposed must be provided after on_cancel

Flow 6

on_update_part_cancel

• schemaErr0: /message/order/created_at must match format "rfc3339-date-time"

on_status_packed

• on_status_packed: Missing Payload

on_status_picked

• message/order.fulfillments/0: Missing fulfillment type 'Cancel' in on_status_picked

on_status_out_for_delivery

• message/order.fulfillments/0: Missing fulfillment type 'Cancel' in on_status_out_for_delivery

on_status_delivered

• message/order.fulfillments/0: Missing fulfillment type 'Cancel' in on_status_delivered
• message/order.fulfillments/1/start/location: Mismatch occurred while comparing 'Delivery' fulfillment object with on_status_pending on key 'start/location/locality'

on_update_interim_reverse_qc

• schemaErr0: /message/order/created_at must match format "rfc3339-date-time"
• message/order.payment/@ondc/org/settlement_details/0: Missing payment/@ondc/org/settlement_details as compared to update_settlement_part_cancel i.e. {"settlement_counterparty":"buyer","settlement_phase":"refund","settlement_type":"netbanking","settlement_amount":"62990","settlement_timestamp":"2024-06-09T22:16:39.873Z"}
• message/order.fulfillments/Cancel: Fulfillments/Cancel is missing in on_update_interim_reverse_qc

on_update_approval

• schemaErr0: /message/order/fulfillments/3/end/time must be object
• schemaErr1: /message/order/fulfillments/3/end/person must be string
• schemaErr2: /message/order/created_at must match format "rfc3339-date-time"
• on_update_approval_msgId: Message id should not be same with previous calls
• message/order.payment/@ondc/org/settlement_details/0: Missing payment/@ondc/org/settlement_details as compared to update_settlement_part_cancel i.e. {"settlement_counterparty":"buyer","settlement_phase":"refund","settlement_type":"netbanking","settlement_amount":"62990","settlement_timestamp":"2024-06-09T22:16:39.873Z"}
• message/order.fulfillments/Cancel: Fulfillments/Cancel is missing in on_update_approval

on_update_picked

• Similar as above

update_settlement_reverse_qc

• update: Missing Payload

on_update_delivered

• schemaErr0: /message/order/fulfillments/3/end/person must be a string
• schemaErr1: /message/order/created_at must match format "rfc3339-date-time"
• on_update_delivered_msgId: Message id should not be same with previous calls
• message/order.payment/@ondc/org/settlement_details/0: Missing payment/@ondc/org/settlement_details as compared to update_settlement_part_cancel i.e. {"settlement_counterparty":"buyer","settlement_phase":"refund","settlement_type":"netbanking","settlement_amount":"62990","settlement_timestamp":"2024-06-09T22:16:39.873Z"}
• message/order.fulfillments/Cancel: Fulfillments/Cancel is missing in on_update_delivered

on_update_interim_liquidated

• schemaErr0: /message/order/created_at must match format "rfc3339-date-time"
• message/order.payment/@ondc/org/settlement_details/0: Missing payment/@ondc/org/settlement_details as compared to update_settlement_part_cancel i.e. {"settlement_counterparty":"buyer","settlement_phase":"refund","settlement_type":"netbanking","settlement_amount":"62990","settlement_timestamp":"2024-06-09T22:16:39.873Z"}
• message/order.fulfillments/Cancel: Fulfillments/Cancel is missing in on_update_interim_liquidated

on_update_liquidated

• schemaErr0: /message/order/created_at must match format "rfc3339-date-time"
• on_update_liquidated_msgId: Message id should not be same with previous calls
• message/order.payment/@ondc/org/settlement_details/0: Missing payment/@ondc/org/settlement_details as compared to update_settlement_part_cancel i.e. {"settlement_counterparty":"buyer","settlement_phase":"refund","

update_settlement_liquidate

• update: Missing Payload

@pranav-buynxt Please provide the utility payload you are using from next iteration onwards and the reports as well as most of these errors could've been flagged by utility

• Please run utility before submission so iterations can be reduced
• Also don't provide placeholder or mock values in payload
• urls and invoices should not be placeholders and should be publically accessible

[Jagannath-wits]

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 but then it wont change in confirm call; right now payment is only accepted by buyer on network so the payment object in confirm is correct

confirm

timestamp should be in rfc3339 format i.e YYYY-MM-DDTHH:MN:SS.MSSZ.

on_status_picked

• invoice should be accurate as per quote for all flows (repeated issue)

Flow 4

• is the id for cancellation fulfillment id 24932_C1 static ? how will you handle if there are multiple cancellations eg: part-cancel, cancel_rto, etc?

Flow 5

On_status_rto_delivered

• RTO fulfillment type will be RTO and not cancel.
• RTO fulfillment start.time.range is not required as per contract.
• RTO fulfillment end.timestamp missing.
• RTO fulfillment person, contact is not required as per contract.

Flow 6

on_update_interim_reverse_qc

• forward fulfillment present twice in fulfillments (24932_F1)

update_settlement_reverse qc

• Missing payload

update_settlement_liquidated

• Missing payload

Settlement details missing hence not carried forward

Note: Please try to follow the flow i.e part-cancel, reverse qc, Liquidation to avoid false errors from utility.

@@pranav-buynxt

[Jagannath-wits]

Flow 1: on_search

• Please provide @ondc/org/return_window as this also works as the IGM window. Please provide some duration as well.
• /message/catalog/bpp-providers/0/items/tags/ Country must be in ISO 3166-1 format (three-letter country code).
• bpp/providers[0]/items[1]/descriptor/code: Code should have "3:GTIN" as a value in /message/catalog/bpp/providers/items/descriptor/code.
• Either one of fixed (range) or split (frequency and times) timings should be provided in /bpp/providers[0]/locations[0]/time.

Flow 2: on_init

• If BPP is collecting payment, then the payment details will be provided in on_init and carried forward. If only BAP is collecting, then "collected by" should be BAP in Confirm, and the rest will be the same as currently provided.

Flow 2: on_status

• Start and end timestamps cannot be the same and should be practical.

Flow 3: on_status

• fulfillment.tags.state.ready_to_ship is only required if fulfillment.type="Buyer-Delivery", indicating whether fulfillment is ready to ship.

Flow 5:

on_status_rto_delivered

• Won’t you charge for delivery fee as the order was already out for delivery?

on_cancel_rto

• on_cancel_rto missing payload

Flow 6: on_update_delivered onwards

• Invoice not carried forward.
• Settlement details not carried forward.

Flow 6: on_update_liquidated

• Same as above.

@pranav-buynxt

[pranav-buynxt]

1 - Flow 1,2,3 and 6 issues are resolved. 2 - For Flow 4, we submitted the on_cancel_rto payload. Could you please clarify why it was marked as missing in your comments?

Additionally, could we arrange a quick call to discuss and clarify a few points?

[Jagannath-wits]

1 - Flow 1,2,3 and 6 issues are resolved. 2 - For Flow 4, we submitted the on_cancel_rto payload. Could you please clarify why it was marked as missing in your comments?

Additionally, could we arrange a quick call to discuss and clarify a few points?

Hi Pranav the comment is for flow 5 where on_cancel_rto is missing @pranav-buynxt

[Jagannath-wits]

Flow 1

on_search

• @ondc/org/statutory_reqs_packaged_commodities: Value is required and cannot be NA for RET14.
• colour_name: Should be in lowercase as specified in enums. For example: midnight blue.
• Why is categories.id of variant 24932_2740440 same as item.id 24932_2740436?

Flow 2

on_status_pending

• routing.type should be sent when order is accepted

Flow 3

on_select

• item.id 24932_2740436 is the same as categories.id of the variant.

Flow 5

on_status_rto_delivered

• delivery fulfillment start.time.timestamp: Missing.
• quote.rto_delivery : rto_delivery object missing in quote.
• Quote trail not captured correctly please refer to contract. eg: rto_fulfillment.tags.cancel_request should be provided in delivery fulfillment. Please refer to contract
• Trail must be maintained as the details provided in on_cancel must be carried forward.

Flow 6

on_update_part_cancel

• How is on_update_part_cancel sent before order is accepted?

update_settlement_part_cancel

• How were settlement details provided in on_status_pending when update_settlement_part_cancel was received after on_status_pending?
• Were the logs manipulated or created manually?

update_settlement_reverseqc

• 24932_2740433 price is 72990 but the settlement details have price as 82990?
• Incorrect settlement details also carried forward.

@pranav-buynxt

Note

• Please try to follow the flow i.e. part-cancel, reverse qc, Liquidation to avoid false errors from utility.
• Please provide the utility payload and response to make verification quicker and easier.
• Please format the on_action calls before submitting.

[pranav-buynxt]

for flow 2 -- In our payload, "tracking" is set to "false." Do we still need to provide the routing object??

in Api contract it is optional -- optional, may be provided, on or before fulfillment state of "Agent-assigned", if tracking = "true"; if tracking="true" & this is not provided, default routing.type will be "P2P"

[pranav-buynxt]

??

[Jagannath-wits]

optional, may be provided, on or before fulfillment state of "Agent-assigned", if tracking = "true"; if tracking="true" & this is not provided, default routing.type will be "P2P"

- Yes, routing object is mandatory now

[pranav-buynxt]

okay, but please update these points in the API contract also.

[pranav-buynxt]

For Flow 5 -- on_status_rto_delivered:-- I have cross-checked, and we are passing the start object with the necessary details. Please verify it on your side.

I didn't fully understand your other point od flow 5 We have also cross-verified our logs with the verifier logs of other Seller NPs and found no reference to this in the API contract as well. Could you please provide a document or clarify these points in more detail?

[Jagannath-wits]

For Flow 5 -- on_status_rto_delivered:-- I have cross-checked, and we are passing the start object with the necessary details. Please verify it on your side.

I didn't fully understand your other point od flow 5 We have also cross-verified our logs with the verifier logs of other Seller NPs and found no reference to this in the API contract as well. Could you please provide a document or clarify these points in more detail?

on_status_rto_delivered

• delivery fulfillment start.time.timestamp: Missing.
• quote.rto_delivery : rto_delivery object missing in quote.
• Quote trail not captured correctly please refer to contract. eg: rto_fulfillment.tags.cancel_request should be provided in delivery fulfillment. Please refer to contract
• Trail must be maintained as the details provided in on_cancel must be carried forward.

@pranav-buynxt updated

[Jagannath-wits]

Flow 5

on_cancel

• RTO_fulfillment.start.time should just have just timestamp and not time range

On_status_rto_delivered

• items object is provided as an empty array
• RTO_fulfillment.start.time.timestamp is future dated than on_cancel_rto, it should be same as whats provided in on_cancel only RTO_fulfillment.end.time.timestamp will be updated here

@pranav-buynxt

[pranav-buynxt]

For Eletroinics(RET:14) We only have some minor fixes for Flow 5 only. Could we resubmit only the logs for flow 5 for your review?

[pranav-buynxt]

For Flow 5:-- on_cancel(RTO_fulfillment.start.time should just have just timestamp and not time range): --

If I understand correctly, you mentioned that the RTO.fulfillment.start should only have a timestamp key and not a range object. I have checked our last submitted logs, and we are indeed only passing the timestamp and not the range object. Please cross-verify this at your end. I have also attached a screenshot for your reference.

[sandeepshahi]

Flow 1

/on_search

• entire address need not be provided in /locations/address/street

Flow 2

/on_confirm

• how can estimated pickup and delivery time ranges be provided even before the order is accepted
• for above point, considering that the 'time_to_ship' provided in /on_search is 3 hours, how can the estimated pickup time range be only 1 hour?

/on_status (picked)

• how can actual pickup timestamp be earlier than timestamp in "Packed" state
• invoice URL should be carefully drafted, as multiple buyer apps can create the same order ID

Flow 4

/on_cancel

• updated_at timestamp is not captured correctly

Flow 5

/on_cancel

• actual pickup timestamp is missing from cancelled forward shipment
• "005" is not a valid RTO reason id
• quote_trail should only include line items with delta changes; delivery with value = 0 should not be provided in quote_trail
• no need to add RTO delivery charges in quote/breakup if value = 0

/on_status (RTO)

• similar issues as above
• why has the RTO fulfillment id changed?
• tags/cancel_request need not be provided in RTO fulfillment

Flow 6

/on_update (part cancel)

• Why are the cancellation fulfillment IDs the same for both partial and full cancellations? What happens if a full cancellation is initiated by BNP after a partial cancellation is received from SNP
• Why is a line item with quantity = 0 created for the partially cancelled item '24932_2740433' in quote/breakup? There should only be one object with the remaining quantity

/on_update (picked)

• Return pickup timestamp is not captured correctly; can't be future dated

/on_update (delivered)

• return pickup timestamp should not change

/on_update (liquidated)

• similar issues

@pranav-buynxt, please fix the above issues and resubmit the logs for Flow 5 and 6

[pranav-buynxt]

Subject: Updated Payloads for Review: Flow 2 /on_confirm and /on_status

Hi Sandeep, As per our discussion today, we have addressed the two points you raised:

1 - How can estimated pickup and delivery time ranges be provided even before the order is accepted? 2 - Considering that the 'time_to_ship' provided in /on_search is 3 hours, how can the estimated pickup time range be only 1 hour?

We have fixed these issues and attached the updated payloads for your review: on_confirm and on_status (order-accepted).

In the updated flow:

• The pickup and delivery times are not sent until the order is accepted.

• As we are sending a ready-to-ship range of 3 hours and a total delivery range of 4 hours in on_search, the new pickup range is 3 hours and the delivery range is 1 hour.

We appreciate your time and understanding.

on_confirm.json on_status(order-accepted).json

@sandeepshahi

[sandeepshahi]

Flow 5

/on_cancel

• quote_trail should only include line items with delta changes; delivery with value = 0 should not be provided in quote_trail

Flow 6

/on_update

• invoice must be accessible
• label should be "Invoice" instead of "invoice"; letter casing of enums must be followed

@pranav-buynxt