Tech Logs for ONDC:SRV14 [Assaying Services]

[Nirdosh3312]

Description

Submitting tech logs for ONDC:SRV14 [Assaying Services]

Changes

1. Create a directory for organization
2. Added Logs for Happy Flow

[vishal-ondc]

@Nirdosh3312 Please find the below comment and get it fixed, let me know if have any queries

Note:

1. Location id and item id should be improved
2. Logs have exactly same as sample json, so hope you have made this dynamic based on your requirement

Search

1. You have sent the name in search instaed can send the catagory id

On Search

1. if we have the range then frequency and times no need to send under providers>time>schedule
2. category id in serviciability tag is incorrect
3. if we have the range then frequency and times no need to send under providers>items>time>schedule
4. I1C1 has price 150 and minimum 180 i.e. not possible

on select

1. No need to pass the name of the item, Please match with schema

Init

1. Item fulfilment id is incorrect, its not in on_search
2. Item category_ids is incorrect
3. billing tax id is inccorrect (hope you are using dummy)

On Init

1. No need to pass the name of the item, Please match with schema
2. In search request there is 0% but in on_init payment its asking 1% so its mismatched

confirm

1. Buyer_Finder_Fee_Amount is different in this call under payment

on confirm

1. same as on_select and on_init

on_status

if you fixed till on confirm, it will have the same schema

[Nirdosh3312]

Hey @vishal-ondc, I am resubmitting the Logs as per the observation and issues raised by you. Kindly have a look and do let us know if anything else is needed.

Regarding the below mentioned point, We are following the swagger and are currently using the commodity code passed in intent.tags to cater to our need. Kindly let us know if this is alright.

Search
You have sent the name in search instaed can send the catagory id

Looking forward to your response. Regards

[vishal-ondc]

@Nirdosh3312

Note: As you doesn't have buyer subscribed then transaction for search is doesn't perform through ONDC and it will not make sure Authetication is managing properly and also the cross NP compatibility so check with mock server its working properly or not but for now I have added the comment on logs so you can make sure your implementation payload fixes

---

Flow 1

search

• You have sent the name in search instaed can send the catagory id, as single item search may not match with different seller

on_search

• if don't have image for provider then no need to send the blank array key under message>providers>descriptor>images
• locations GPS can't be empty under message>providers>locations
• Range time should have the difference under message>providers>time>range
• if you are sending cred then URL can not be empty under message>providers>creds
• provider tags can not be empty and serviciability is mandatory under message>providers>tags
• ASSAYINGTEST_TYPE value can't be empty -- This indicate what kind of test is being offered, whether it's a physical or chemical test or both
• PICKUP_TAT is required (TAT for picking up the sample, only required if Seller-Fulfilled)
• COMPLETION_TAT value is missing but if you don't have initially then no need to send it
• Range time should have the difference under message>providers>items>time>range
• parameter is not valid value for items>quantity>unitized>measure>unit

select

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT

on_select

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• quote>breakup>title for some item is missing and its required (second and third item doesn't have)

init

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT

on_init

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• quote>breakup>title for some item is missing and its required (second and third item doesn't have)

confirm

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• quote>breakup>title for some item is missing and its required (second and third item doesn't have)

on_confirm

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• quote>breakup>title for some item is missing and its required (second and third item doesn't have)

on_status

• FARM_STATUS -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• ACRAGE -> if not have the real data for this then no need to send it under item tags for REPORT_REQUIREMENT
• quote>breakup>title for some item is missing and its required (second and third item doesn't have)

---

Flow 2

failure case flow is missing (We have already discussed when connected)

[Nirdosh3312]

Hey @vishal-ondc, I have updated the tech logs and have also added user and merchant cancellation flows as well. The logs have been generated using the provided mock server APIs.

With respect to the following point:

Range time should have the difference under message>providers>time>range

We are having values:

"range": {
     "start": "2025-10-25T00:00:00.000Z",
     "end": "2027-10-25T00:00:00.000Z"
  }

We have set the difference of two years. Please let me know if there is any concern. Thank you so much for your continued support and understanding. Looking forward to your response.

Regards

[vishal-ondc]

@Nirdosh3312

on_search

• gps under locations should have value like 28.497124,77.159740 instead of 28.497124, 77.159740 (It has the extra space just after comma)
• invalid category id SRV14-* under serviciability tags use instead SRV14-1004

Notes

• GPS issue found in many api calls, so once you will fix it and category id under tags then logs will be approved

[Nirdosh3312]

Sure @vishal-ondc, We will be resubmitting the logs. Thanks for the feedback. Regards

[Nirdosh3312]

Hi @vishal-ondc, Resubmitting the tech logs. Kindly have a look and let us know if anything else is needed. Looking forward to your response. Regards

[vishal-ondc]

@Nirdosh3312 I have identified below issues, Please fix and reshare

on_init

• fulfillments end location missing with address, city, country, area_code, state, contact, which is coming into init call

on_confirm

• Location id is invalid, this location id is not in on_search and while confirming the order you sent the wrong location id
• fulfillments end location missing with address, city, country, area_code, state, contact, which is coming into init call and start is also missing (but if its align with business then skip for start only but others are mandatory)

on_status (All)

• Location id is invalid, this location id is not in on_search and while confirming the order you sent the wrong location id
• Items has the tags here but it should be in on_conform as well

[Nirdosh3312]

Hi @vishal-ondc, Resubmitting the tech logs, Since we are encountering an error with incorrect location_id being sent in /confirm API, I am submitting an additional flow [Error Flow]. Kindly have a look and let us know if anything else is needed. Looking forward to your response. Regards