Rapidor | B2B | v2.0.2 | Compliance Check

[tanyamadaan]

Domestic flow 1:

{ "Message": { "search_0": { "RGC-end-Err": "Reverse Geocoding for end failed. Area Code 560001 not matching with 12.976594,77.599271 Lat-Long pair.", "CityCode-Err": "CityCode 0788 should match the city for the fulfillment end location 560001, 080" } } }

Domestic Flow 4:

{ "Schema": { "schemaErr0": "/confirm/0/message/order/quote/price/value must be equal to constant (42.83)", "schemaErr1": "/on_confirm/0/message/order/state must be equal to one of the allowed values (Created,Accepted,Cancelled)", "schemaErr2": "/on_confirm/0/message/order/quote/price/value must be equal to constant (42.83)" }, "Message": { "search_0": { "RGC-end-Err": "Reverse Geocoding for end failed. Area Code 560001 not matching with 12.976594,77.599271 Lat-Long pair.", "CityCode-Err": "CityCode 0788 should match the city for the fulfillment end location 560001, 080" } } }

Domestic Flow 5:

{ "Schema": { "schemaErr0": "/on_select/0/message/order/quote/breakup/0/item must have required property 'quantity'", "schemaErr1": "/on_select/1/context/message_id Message ID for on_action API should be same as action API: \"4731c6d6-e14e-43b8-ba69-2f5586503fbd\"", "schemaErr2": "/init/0/message/order/billing/name must NOT have fewer than 3 characters", "schemaErr3": "/confirm/0/message/order/quote/price/value must be equal to constant (9.06)", "schemaErr4": "/on_confirm/0/message/order/quote/price/value must be equal to constant (9.06)" }, "Context": { "on_select_0": { "tmpstmpErr": "Timestamp mismatch for /on_select " } }, "Message": { "search_0": { "RGC-end-Err": "Reverse Geocoding for end failed. Area Code 560001 not matching with 12.976594,77.599271 Lat-Long pair.", "CityCode-Err": "CityCode 0788 should match the city for the fulfillment end location 560001, 080" } } }

@rapidor @sanushilshad

[tanya-ondc]

Flow1

As discussed, kindly submit logs with a different NP.

/on_search:

• fulfillments.contact should be updated. Should not use example values.
• item.quantity.unitized.measure.unit should be KG as per the item.

/select:

• If chat link shared by seller app, should not be shared by buyer app. Buyer app should use seller apps chat if shared.

/on_init:

• Payments object does not include type, collected_by and settlement details.

/on_confirm:

• Payment object does not have all mandatory attributes.
• Order.state should not be created.

[abhinavv245]

Buyer App domestic

Flow 1

/on_search

• seller_id_no cannot be an empty string (Is BAP performing a validation for this?)

/on_select

• Include packing, tax, misc, discount charges in the quote breakdown unless their values are zero.

/init

• order/payments/0 must have required property 'collected_by'

/on_init

• order/payments/0 must have required property 'collected_by'
• payments/0 must have required property '@ondc/org/settlement_basis', '@ondc/org/settlement_window','@ondc/org/withholding_amount' (BAP should validate schema)

/confirm

• payments/0 must have required property '@ondc/org/settlement_basis', '@ondc/org/settlement_window','@ondc/org/withholding_amount', '@ondc/org/settlement_details',

/status

• is status API implemented?

Flow 3

/on_confirm

• Error object will be added along with context, message when the PO is rejected.

Flow 4

/on_select (Reject)

• @ondc/org/item_quantity will be updated to the available quantity, subsequently price will be updated (@ondc/org/item_quantity/count * item/price/value)

[sanushilshad]

@abhinavv245 @ondc/org/item_quantity will be updated to the available quantity, subsequently price will be updated (@ondc/org/item_quantity/count * item/price/value)

can u elaborate on this point?

[abhinavv245]

@sanushilshad The item quantity may either be 0, indicating it is completely out of stock, or a reduced quantity that is currently in stock (available). If the item quantity is 0, signifying it is completely out of stock, or if there is a reduced quantity available, the price will be adjusted accordingly based on the quantity.

[abhinavv245]

Seller App

Flow 1 (Seller Domestic)

/on_select

• Include packing, tax, misc, discount charges in the quote breakdown unless their values are zero.
• provider need not have additional properties (ttl)
• payments/0 must have required property 'collected_by'
• delivery charges to be provided when the fulfillment is serviceable

/init

• order/payments/0 must have required property 'collected_by'

/on_init

• order/payments/0 must have required property 'collected_by','type'
• payments/0 must have required property '@ondc/org/settlement_basis', '@ondc/org/settlement_window','@ondc/org/withholding_amount'

/on_status

• Are updates for other fulfillment states being sent? (Pending, Agent-assigned)

Flow 4

• similar issues as above

/on_select (Reject)

• @ondc/org/item_quantity and item/quantity will be updated to the available quantity in quote/breakup, subsequently price will be updated (@ondc/org/item_quantity/count * item/price/value)

Is BAP collecting prepaid payment flow implemented?

[sanushilshad]

@abhinavv245 Include packing, tax, misc, discount charges in the quote breakdown unless their values are zero. The above fields in the quotes in flow, can u send the exact field which is not there?

[abhinavv245]

@sanushilshad What I meant was include these charges only if their value is not zero. If the values is zero, that shall not be included except the delivery charge, that needs to be provided if the fulfillment is 'Serviceable'.

[sanushilshad]

@abhinavv245 is it mandatory to not include the values with zero?

[abhinavv245]

@sanushilshad It is a suggestion.

[sanushilshad]

@abhinavv245 noted

[sanushilshad]

Are updates for other fulfillment states being sent? (Pending, Agent-assigned) @abhinavv245 no, we are only using three status for now picked-up, Out-for-delivery, and delivered

[sanushilshad]

@abhinavv245 BAP payment for RFQ flow is not yet implemented yet.

[tanya-ondc]

RFQ Flow Seller App

All flows

/on_search

• country of origin should be 'IND' in /items/tags
• category should be 'RET10-*' in tags for serviceability

/select

• fulfillments/id does not match with any of the ids in /fulfillments in /on_search

/on_select

• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable'"
• item.quantity.selected.count should not be updated by BPP.

/on_init

• payments/0 must have required property 'type'

Flow 5

/on_select

• While rejecting the quote request due to unavailability of item quantity, item.quantity.selected.count cannot be changed by BPP. BPP may add item.quantity.available.count as new available count. Quote for available quantity looks okay.

Flow 6

• Kindly confirm what is the reason of rejection of quotation here.

@sanushilshad

[abhinavv245]

Non RFQ Flow - Buyer App

/search

• fulfillment/stops/0/location/gps Incorrect gps value (minimum of six decimal places are required)

/init

• payments/0 must have required property 'collected_by'
• fulfillments/id and items/fulfillment_ids does not match with /select (BPP should NACK)

/on_init

• fulfillments/id and items/fulfillment_ids does not match with /on_search (BPP should validate being the owner for these attributes)
• payments/0 must have required property 'type'

Flow 5

• similar issues as above

/on_select (Reject)

• @ondc/org/item_quantity for item with id MAIDA-01KG cannot be more than the available count (quantity/avaialble/count) in quote/breakup

@sanushilshad

[abhinavv245]

Non RFQ Domestic Buyer

Flow 1

/on_init

• fulfillments/0/@ondc/org/TAT cannot change from the one provided in /on_select (P2D) (How is buyer app handling this)

Flow 4

• similar issues

/on_select (Reject)

• Total price of the item with item id SUJI-500G is not in sync with the unit price and quantity
• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable'

Flow 5

• similar issues

/select

• no change in location of the buyer

/on_select (Reject)

• on what basis is the select request rejected? (as for the same location, it has been accepted later)

Note: Kindly test with another seller NP and resolve all the previously identified issues. Also, RFQ Buyer app logs needs resubmission.

@sanushilshad

[sanushilshad]

@abhinavv245 can you point out the reasons for RFQ Seller App log rejection?

[abhinavv245]

RFQ Domestic Seller

Flow 1

/on_select

• items/quantity/selected/count should be an integer

/on_init

• fulfillments/0/@ondc/org/TAT cannot change from the one provided in /on_select (P2D)

  Flow 5

• similar issues

/on_select (Reject)

• Total price of the item with item id BESAN-KP-30KG is not in sync with the unit price and quantity (Flow 6)
• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable'

[sanushilshad]

@abhinavv245

• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable' is this mandatory for reject case? as the delivery charge is manually entered by the seller when the RFQ is approved by the seller.

[abhinavv245]

@sanushilshad Yes, it is mandatory even if it is rejected. Only in case the location is non-serviceable, delivery charges will not be provided.

[sanushilshad]

@abhinavv245 -Total price of the item with item id BESAN-KP-30KG is not in sync with the unit price and quantity. "price": { "currency": "INR", "value": "245500.00" }, "@ondc/org/item_quantity": { "count": 100 }, "item": { "price": { "currency": "INR", "value": "2455.00" },

this is correct, right?

[abhinavv245]

@sanushilshad this is for flow 6 : { "title": "LAXMI BHOG KADI PAKODA BESAN 30 KG", "@ondc/org/item_id": "BESAN-KP-30KG", "@ondc/org/title_type": "item", "price": { "currency": "INR", "value": "2455000.00" }, "@ondc/org/item_quantity": { "count": 100 }, "item": { "price": { "currency": "INR", "value": "2455.00" }, "quantity": { "available": { "count": "100" }, "maximum": { "count": "100" } } } },

[sanushilshad]

@abhinavv245 https://github.com/ONDC-Official/verification-logs/issues/1347

• Buyer Finder Fee amount mismatches from /search (BAP should send NACK)

the above error in spicemoney issue board, can u specify in which status log is the issue happening?

[abhinavv245]

@sanushilshad The issue is in /on_init API. Have updated the board.

[abhinavv245]

@sanushilshad Catalog for construction and building looks fine.

[abhinavv245]

@sanushilshad Please include the below for all transactions:

/on_init

• order/tags (bpp_terms)

/confirm

• acceptance to bpp_terms should be provided in order/tags

[abhinavv245]

RFQ Seller App

Flow 1

/on_search

• how is BAP collecting the payment for 'ON-FULFILLMENT' and 'POST-FULFILLMENT'

/on_init

• order/tags (buyer_id, bpp_terms) are missing

Flow 5 & 6

• similar issues

/on_select (Reject)

• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable'

Note: Kindly resolve all previous issues before submitting the logs again

@sanushilshad

[tanya-ondc]

RFQ Seller App

Flow1

• Supported payment options in /on_search includes pre-fulfillment (collected by BPP). However, this is not developed by Rapidor yet. How will you handle the select request, if a buyer selects pre-fulfillment payment option.

/on_confirm:

• Duplicate bpp_terms tags.

/on_status:

"@ondc/org/settlement_basis", "@ondc/org/settlement_window", "@ondc/org/withholding_amount" missing in /on_status.

Flow4

• The buyer terms are same in /select and /confirm, as stated in rejection reason in /on_confirm. On what reasons have you implemented the auto-reject.

@sanushilshad

[sanushilshad]

Supported payment options in /on_search includes pre-fulfillment (collected by BPP). However, this is not developed by Rapidor yet. How will you handle the select request, if a buyer selects pre-fulfillment payment option.

@tanya-ondc this will be removed in this production at seller side, and at buyer side at UI level. as this field is being used for Non-RFQ flow

[tanya-ondc]

shud be removed in pre-production itself, if its not supported for now.

[tanya-ondc]

Seller App Logs

Rapidor B2B RFQ Seller App logs Approved. Rapidor B2B Non-RFQ Seller App logs yet to be Submitted. Note - Prepaid payment, Cancellation flows not yet implemented.

Buyer App Logs

Yet to be re-submitted.

@sanushilshad

[abhinavv245]

Non RFQ Flow Seller App

Flow 1

/on_search

• all mandatory attributes should be listed in items.tags.attribute (as per the taxonomy)
• Variant mapping is not correct, items/parent_item_id should map to the categories/id (both items/id and categories/id should not be same)
• In categories/tags, item.tags.attribute.colour is not defined in items.tags.attribute

/confirm

• In order/tags bpp_terms and its acceptance (bap_terms) are missing
• why is buyer app sending updating settlement basis, withholding amount in /payments (BPP should validate)

/on_status

• @ondc/org/settlement_basis indicates from when settlement window starts, enum - "delivery" (from delivery), "shipment" (from shipment)
• Proforma invoice is not required for Non- RFQ flow

Flow 3

• similar issues

/on_init

• For prepaid payment collected by BAP, Seller NP should be sending its settlement details for buyer app to settle the amount
• "@ondc/org/settlement_basis","@ondc/org/settlement_window","@ondc/org/withholding_amount" are not required and will be set by the buyer app

/confirm

• why is buyer app sending its settlement details in /payments when it is collecting the payment
• why is payments/params/transaction_id kept same as context/transaction_id (how will buyer NP handle in case of multiple payments)

Flow 4

• similar issues

Note: Flow 5 is missing

@sanushilshad

[sanushilshad]

@abhinavv245

• "@ondc/org/settlement_basis","@ondc/org/settlement_window","@ondc/org/withholding_amount" are not required and will be set by the buyer app

for the above issue, from which api will the buyer app set the settlement_window, withholding_amount and settlement_basis.

• @ondc/org/settlement_basis indicates from when settlement window starts, enum - "delivery" (from delivery), "shipment" (from shipment)

and for the above issue can you elaborate a little

[abhinavv245]

@sanushilshad

• in /confirm, BAP will send these details
• the enum should be 'delivery' (not 'Delivery')

[sanushilshad]

https://github.com/ONDC-Official/ONDC-RET-Specifications/blob/release-2.0.2/api/components/Examples/B2B_json/on_init/on_init_domestic_payment_BPP_Non_RFQ.json

@abhinavv245 then the above example needs to remove the settlement details, right?

[abhinavv245]

@sanushilshad in this example, the payment is collected by BPP, so it will set these details in on_init.

[abhinavv245]

Non RFQ Flow Buyer App

Flow 2

/confirm

• Transaction ID in payments/params cannot be provided when the payment status is 'NOT-PAID'

/on_status

• Proforma invoice (/documents) is not required for Non- RFQ flow
• payments/params/transaction_id will be generated by seller app when BPP is collecting the payment

Flow 3

• similar issues

/on_status

• payment/status changed to 'NOT-PAID' in on_status (Out-for-delivery, Order-picked-up)

Note: Flow 5 is missing

@sanushilshad

[abhinavv245]

All Flows (Non RFQ Buyer App)

/on_search

• providers/0/items/0/cancellation_terms/0 must have required property 'reason_required'
• providers/0/items/0/return_terms must have required property 'return_time'
• providers/0/items/0/return_terms/return_eligible must be boolean"

/on_select

• Delivery charges are not required in quote/breakup when fulfillment is 'Non-serviceable' (Flow 5)

/on_status

• /documents (Invoice) is not required before order is picked up

@sanushilshad

[sanushilshad]

@abhinavv245 Delivery charges are not required in quote/breakup when fulfillment is 'Non-serviceable' (Flow 5) this is optional right?

[abhinavv245]

@sanushilshad delivery charge to be included only if fulfillment state code is "Serviceable"

[sanushilshad]

@abhinavv245 but we can add the delivery break up with value as 0, right?

[tanyamadaan]

Electronics catalog:

• While verifying the logs with Spicemoney, I see that brand is created as a variant. How brand can be used as a variant in electronics.

@sanushilshad

[abhinavv245]

Non-RFQ Seller App (All Flows)

/on_search

• mapping of variant group (categories/id) to the items (parent_item_id) is incorrect, if categories/id is defined V1, then the item defined for varant group V1 will have items/parent_item_id as V1.
• serviceability is selected as hyperlocal (Type 10), however the value is 2440 km (what is the logic behind this, either you support PAN india or use geojson polygon)

@sanushilshad

[sanushilshad]

@abhinavv245 serviceability is selected as hyperlocal (Type 10), however the value is 2440 km (what is the logic behind this, either you support PAN india or use geojson polygon)

Can you elaborate on what is the issue?

[abhinavv245]

@sanushilshad many of the buyer apps cap their serviceability upto few kms for hyperlocal, so in case you are sending your serviceability as hyperlocal and providing value as 2440km, your provider wont be visible. So choose the appropriate serviceability.

[sanushilshad]

@abhinavv245 ok noted. what is the maximum value that can be used for hyperlocal?

[abhinavv245]

@sanushilshad Ideally should not be more than 50km.

[sanushilshad]

@abhinavv245 lets say I want the servicability to be entire rajasthan and gurjrat, then can't i set the the radius as 400km?

[abhinavv245]

@sanushilshad Please update attributes in /on_search as per the taxonomy, ram and item condition are mandatory attributes, refer to on_search example for smartphones

[sanushilshad]

@abhinavv245 are all the fields mentioned smartphones mandatory or is the ram and item condition is the only ones missing from the attributes for the submitted electronics log?

[abhinavv245]

Non RFQ Buyer App

/on_init

• why is seller app sending its settlement details

/confirm

• buyer app should not send settlement details when it is collecting the payment (Flow 3)

/on_confirm

• settlement details should be the one provided by buyer app in case BPP is collecting the payment (buyer app should validate)

@sanushilshad