Flow 1

/on_search (RET12)

Timestamp for /search api cannot be equal to /on_search api
For Dhotis, if there is no particular size then 'Free Size' to be used as per enums
Multiple descrepancies in the items/attribute - Please use the enums for Gender, Size
variant is defined in categories (V1) but not linked to any item (parent_item_id)
message/order/tags/bpp_terms np_type - is Esaras an ISN? do you have your own inventory? if not, the value should be MSN which means you are only selling inventory of other sellers as a marketplace.

/on_search (RET13 and 16)

Timestamp for /search api cannot be equal to /on_search api
Support for variants is mandatory, categories must be present in bpp/providers[0]
category in serviceability construct should be one of the category ids bpp/providers[0]/items/category_id

Flow 2

/on_search

similar issues as above
timing construct is mandatory in /bpp/providers[0]/tags

/on_init

provider_tax_number must be present for on_init
gps coordinates in fulfillments[0].end.location mismatch in /select & /on_init

/confirm

fulfillments[0].end.location gps is not matching with gps in /select Mismatch found for item with item_id 1490 while comparing quote object of on_select and confirm

/on_confirm

please remove null value attributes (payment/uri and /tl_method )
order.updated_at timestamp should be updated as per the context.timestamp (since default fulfillment state is added)
provider_tax_number must be present for on_confirm,
fulfillments[0].end.location gps is not matching with gps in /select",
payment object mismatches in /confirm & /on_confirm (in case settlement details are to be sent, should be sent in on_init onwards by seller app)

/on_status_pending

Order state should be accepted whenever Status is being sent 'Accepted'. Current state: Created",
Created At timestamp for /on_status_pending should be equal to context timestamp at confirm"

/on_status

status updates for fulfillment states - packed, ordered picked up, out for delivery, order delivered are mandatory

Flow 3

/on_select_out_of_stock

quote/price should be zero as "@ondc\org\item_quantity" is zero
/message/order/quote/breakup/0/item/quantity/ available and maximum count must be either 0 only
error object should be sent along context and message with appropriate error code for item out of stock

 "error":
  {
    "type":"DOMAIN-ERROR",
    "code":"40002",
    "message":"M1"
  }

error.message in the response should have the list of corresponding item ids referenced in stringified object notation, e.g. if items "I1", "I2", "I3'' are out of stock, error.message would be encoded as: "[{\"item_id\":\"I1\",\"error\":\"40002\"},{\"item_id\":\"I2\",\"error\":\"40002\"},{\"item_id\":\"I3\",\"error\":\"40002\"}]". This is in addition to the error.code (40002) which is being sent by seller NP;

/on_select

/message/order/quote/breakup/0/item/quantity/available/count available count must be either 99 or 0 only

/on_init

provider_tax_number' should have a valid PAN number format (Number of digits in provider tax number in message.order.tags[0].list should be 10)

/on_confirm

'TAT' must be provided in message/order/fulfillments
np_type is missing in message/order/tags/bpp_terms for ON_CONFIRM

on_status_pending

Order id in /confirm and /on_status_pending do not match
Order state should be accepted whenever Status is being sent 'Accepted'. Current state: Created,
Created At timestamp for /on_status_pending should be equal to context timestamp at confirm"
if authorization block is being used in fulfillments/start, then instructions/code should be '4' which indicates OTP
if authorization block is being used in fulfillments/end, then instructions/code should be '1' which indicates OTP
in fulfillments/tags - code for 'state' tag should be 'ready_to_ship' instead of 'Pending'
tracking tag in fulfillments/tags to be sent when the tracking is enabled (tracking attributes for fulfillment, may be provided, on or before fulfillment state of "Agent-assigned", if tracking = "true"), Also both gps_enabled, url_enabled cannot be no, one of them will be yes as per which type of tracking is enabled, in case url based tracking is active, then the url will also be present, else it will not be present
fulfillment delay tag in fulfillment/tags to sent in case there is a delay in the delivery
order/documents (invoice) to be sent from fulfillment.state = "Order-picked-up" and thereafter;

on_status_packed:

Order id in /confirm and /on_status_packed do not match",
Created At timestamp for /on_status_packed.message.order should be equal to context timestamp at confirm",
order/state should be \"In-progress\" for /on_status_packed

on_status_picked

payload should be provided

on_status_out_for_delivery:

Order id in /confirm and /on_status_out-for-delivery do not match,
Created At timestamp for /on_status_out-for-delivery should be equal to context timestamp at confirm",
order/state should be \"In-progress\" for /on_status_out-for-delivery,
fulfillments/state Should be out-for-delivery for /on_status_Out-for-delivery"
fulfillments/start/time/timestamp (pickup time) should be provided as the order is already picked up
fulfillments/end/time/timestamp (delivery time) should not be provided as the order is not delivered yet

on_status_delivered:

Order id in /confirm and /on_status_delivered do not match",
Created At timestamp for /on_status_delivered should be equal to context timestamp at confirm",
order/state should be \"Completed\" for /on_status_delivered",
fulfillments/state should be Order-delivered for /on_status_Order-delivered
fulfillments/start/time/timestamp (pickup time) should be provided as the order is already picked up

@bindukallupurackal

Additional issues

RET16 search

incorrect payload format, entire payload wont be inside string
please avoid escape characters like \ .

confirm

if BPP is collecting payment the the payment details will be provided in on_init and carried forward, and not in confirm. But as currently only BAP is collecting so collected by should be BAP and not BPP in Confirm and the rest will be same as you have provided now.

on_init

tags.bpp_terms: provider_tax_number is missing
tags.bpp_terms: only tax_number, provider_tax_number is required

on_confirm

provider_tax_number should be provided in bpp_terms and not in bap_terms
Why is on_confirm of flow 2 and 3 different at schema level

on_status

routing can't be p2p when when order is placed from different cities; it'll be p2h2p
While tracking is disabled then tracking object is not required
If tracking is enabled please provide track and on_track as well
fulfillment_delay object is only required when there is an delay in delivery, Its seem you've added it directly from contract; so please remove it
Note : all timestamps and time ranges are too much backdated (months) from context.timestamp

@bindukallupurackal

ESaras

RET12

Flow 1 - on_search

Escape characters are not allowed. For example: `\n\t\t\t\t\t\t\t\t\t\t\tHandicraft Bhawan”
Serviceability should be provided for each category_id.
Few item images/names do not fall under ret12. For example: bottle.
If month_year_of_manufacture_packing_import is unavailable, please provide “NA” and not an empty string.

RET13

Flow 1 - on_search

If attributes are not available for items, then you don't need to provide them. Example: item_id:1464, attribute:ingredient,conscious,preference,formulation.
Serviceability should be provided for each category_id.
Servicability not captured properly; category in serviceability construct should be one of the category ids bpp/providers[0]/items/category_id.
items.quantity.maximum should be a reasonable amount, i.e., 99 (if no limit on the number of items placed in order) or a reasonable number of items (not 90).

RET16

Flow 1 - on_search

Serviceability should be provided for each category_id.
Escape character \ is not allowed. Example: "https:\/\/uatesaras.digitalindiacorporation.in\/media\/catalog\/product\/p\/e\/pexels-pixabay-462235.jpg"

Flow 3

How is the timestamp of select and select_oos same and same for on_select.

on_select_oos

order.error message is missing. Please refer to contract for correct format of error message.
Items have not been reduced or updated.

select

Same items with same count selected in select when they should’ve been out of stock. Please refer to contract.
Why are there 2 different delivery charges in quote when there is only one fulfillment?

init

order.items.location_id is not required as per contract.

on_init

Tags.bpp_terms: Only tax_number, ’np_type' and provider_tax_number are required; others are not enabled yet.

on_status

Order.state not updated after on_confirm.
Routing can't be P2P when order is being placed from different states; it’ll be P2H2P.
While tracking is disabled then tracking object is not required but if tracking is enabled please provide track and on_track as well.
fulfillment_delay object is only required when there is a delay in delivery. It seems you've added it directly from contract; please remove it.
Invoice URL incorrect, please do proper formatting. Escape character \ is not allowed.
Invoice is required from fulfillment.state = "Order-picked-up" and thereafter, and not before it.

Flow 4

cancel

Incorrect reason_id. Please refer to the reason_code sheet.

on_cancel

"invldQuotePrices": "item quote breakup prices for on_cancel should be equal to the total price."
"Fulfillment_mismatch": "The count of cancellation fulfillments is not equal to the count of forward fulfillments or invalid fulfillment id."
precancelState.updatedAt: precancel_state.updated_at of on_cancel is not equal with the on_confirm order.updated_at.
Quote price should be 0 as order was cancelled pre-shipment.
Quote should’ve been updated as per quote trail.

Flow 5

on_search

Categories not captured properly.

on_cancel

Quote not captured properly. 2 items were selected but only 1 item provided in on_cancel.
order.items not updated properly.
Price should only be accurate up to 2 decimals and not have 4 decimals.
Quote trail not captured properly.
Are you not charging delivery fee? As the quote price is 0 and order has already left for delivery.

Note

Please provide curl for the payload as well.
Please provide the logs with proper formatting.
If you have any queries regarding the flow, feel free to ask.

@bindukallupurackal

Esaras

Unicode formatting ‘\’ and escape characters are not allowed in payload (repeated issue)

RET16

on_search

attribute.colour_name is now mandatory wherever colour is mandatory (flagged by utility).
Escape characters are not allowed in payload. For example: \n\t\t\t\t\t\t\t\t\t\t\t (repeated issue).
Circle.radius should be feasible; keep it up to 50 or 500 km even if its servicability is PAN India.
quantity.maximum.count should reasonably reflect the maximum amount of items allowed to be ordered. For example, if 100 units of dining table (repeated issue).
If month_year_of_manufacture_packing_import is not available, please provide "NA" and not an empty string (repeated issue).
Servicability should not be defined at item level, i.e., at items.tags.servicability.
Variants have not been implemented properly i.e variant has been declared but not used also, no attributes have been provided in the items on the path defined in the variant.
Servicability should be provided for each category_id (repeated issue).

Flow 2

confirm

If BPP is collecting payment, the payment details will be provided in on_init and carried forward, and not in confirm. But as currently only BAP is collecting, so collected by should be BAP in Confirm, and the rest will be the same as you have provided now (repeated issue).

on_status

Address mismatch with on_confirm in fulfillment and billing.
Why is there an additional settlement_details object?
Why did payment.collected_by change to BAP from BPP?
Why is the time.range for both start and end the same? Is it not calculated?
time.range can't change at each call.
Why is routing p2h2p when delivery is in the same city? Is this hardcoded? (repeated issue).
No need to provide tracking object when tracking is false (repeated issue).
fulfillment_delay object is only required when there is a delay in delivery. It seems you've added it directly from contract; please remove it (repeated issue).
fulfillment.tags.ready_to_ship is required only if fulfillment.type="Buyer-Delivery", indicating whether fulfillment is ready to ship; please remove it (repeated issue).

on_status_delivered

Payment status is still "NOT-PAID”.

Flow 3

on_select

How can you select the items which were not available as per on_select_oos?

Flow 4

on_cancel

precancel state not captured properly

on_status_RTO_delivered

Missing Payload

Flow 6

Incomplete Flow; no on_update call is provided for reverse qc.

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. @bindukallupurackal

Please check only the flows which are updated. Flow1 not yet updated after last comments received. Esaras not supporting partial cancel, RTO flow on flow5 also we are newly adding as these are handled by brown tape api on Esaras and they are not providing any api or status update.

On Thu, 4 Jul, 2024, 11:26 pm Jagannath Padhy, @.***> wrote:

Esaras

Unicode formatting ‘\’ and escape characters are not allowed in payload (repeated issue)

RET16 on_search

attribute.colour_name is now mandatory wherever colour is mandatory (flagged by utility).

Escape characters are not allowed in payload. For example: \n\t\t\t\t\t\t\t\t\t\t\t (repeated issue).

Circle.radius should be feasible; keep it up to 50 or 500 km even if its servicability is PAN India.

quantity.maximum.count should reasonably reflect the maximum amount of items allowed to be ordered. For example, if 100 units of dining table (repeated issue).

If month_year_of_manufacture_packing_import is not available, please provide "NA" and not an empty string (repeated issue).

Servicability should not be defined at item level, i.e., at items.tags.servicability.

Variants have not been implemented properly i.e variant has been declared but not used also, no attributes have been provided in the items on the path defined in the variant.

Servicability should be provided for each category_id (repeated issue).

Flow 2 confirm

If BPP is collecting payment, the payment details will be provided in on_init and carried forward, and not in confirm. But as currently only BAP is collecting, so collected by should be BAP in Confirm, and the rest will be the same as you have provided now (repeated issue).

on_status

Address mismatch with on_confirm in fulfillment and billing.

Why is there an additional settlement_details object?

Why did payment.collected_by change to BAP from BPP?

Why is the time.range for both start and end the same? Is it not calculated?

time.range can't change at each call.

Why is routing p2h2p when delivery is in the same city? Is this hardcoded? (repeated issue).

No need to provide tracking object when tracking is false (repeated issue).

fulfillment_delay object is only required when there is a delay in delivery. It seems you've added it directly from contract; please remove it (repeated issue).

fulfillment.tags.ready_to_ship is required only if fulfillment.type="Buyer-Delivery", indicating whether fulfillment is ready to ship; please remove it (repeated issue).

on_status_delivered

Payment status is still "NOT-PAID”.

Flow 3 on_select

How can you select the items which were not available as per on_select_oos?

Flow 4 on_cancel

precancel state not captured properly

on_status_RTO_delivered

Missing Payload

Flow 6

Incomplete Flow; no on_update call is provided for reverse qc.

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. @bindukallupurackal https://github.com/bindukallupurackal

— Reply to this email directly, view it on GitHub https://github.com/ONDC-Official/v1.2.0-logs/issues/1902#issuecomment-2209409365, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJKQNM66CVGPOAXSAHZ4UHLZKWEEDAVCNFSM6AAAAABJUOI2MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGQYDSMZWGU . You are receiving this because you were mentioned.Message ID: @.***>

Esaras

Flow 1

on_search

Serviceability for each category_id should be provided (repeated).
There should be at least 2 items with variant for it to be called variant. Please add another item with the same variant. (RET12)
"parent_item_id": “F11472” is used to link item with variant group. If no variant is applicable, please provide "parent_item_id": "”. (repeated issue)
Size chart URL is inaccessible. Eg: Size Chart.
Please don't provide attributes if their value is unavailable; only mandatory attributes are required. Eg: { "code": "ingredient", "value": "" } (RET13).

Flow 2

on_search

Escape characters are still present in address and context.bap_id, etc. Eg: "”"\n\t\t\t\t\t\t\t\t\t\t\t\”””, “”"https:\/\/buyer-app-preprod-v2.ondc.org\/protocol\/v1””(repeated issue)

on_status

fulfillment.end.time.range should be calculated based on the TAT (i.e., 7 days in your case), so the TAT and range should be calculated accordingly.

Flow 3

Escape characters are still present in context.bap_id. Eg: "”"https:\/\/buyer-app-preprod-v2.ondc.org\/protocol\/v1””.

select_out_of_stock

You have to select multiple items (> 1 qty for each item) for checkout and continue with the remaining items in Flow 3 as described in rollout plan. (repeated issue)

on_status_out_for_delivery

message_id 92128c64-c3d9-45a1-a1db-878a7428f6f3 should not be the same as provided in previous calls (i.e., confirm and on_confirm). (flagged by utility)

Flow 5

on_cancel

Quote trail mismatch (flagged by utility)
Invalid reason code used. Please refer to sheet as the reason code should be relevant and applicable for RTO.

on_status

If Tracking is false, no need to provide tracking object.

on_status_rto_delivered

Payload missing (repeated issue).

@bindukallupurackal

Flow 2

On_status

Delivery object was not captured properly after on_confirm. Quote.breakup provided duplicate delivery charges, and its ID should be fulfillment id as provided in on_confirm.
Timestamp issues are similar to those in Flow 5.

Flow 5

Timestamp 2024-07-11T08:47:46.361Z used as a placeholder in multiple locations. For example:
- on_status_pending: fulfillment.time.range should be calculated properly, i.e., the start range should not be less than context.timestamp, but 2024-07-11T08:47:46.361Z is used.
- on_status_picked: fulfillment.start.time.timestamp is again 2024-07-11T08:47:46.361Z. How can it be picked at the same time as the init call? order.updated_at should be updated whenever there is a change in the order object, so in no scenario can the updated_at timestamp be less than created_at.
- on_cancel_rto: fulfillment.start.time.timestamp is again 2024-07-11T08:47:46.361Z.
Please ensure that timestamps are captured in real-time.
on_status.order.updated is 2024-07-11T08:47:46.361Z for all calls (order.updated_at should be updated whenever there is a change in the order object, so in no scenario can the updated_at timestamp be less than created_at).

On_status_rto_delivered

orders.items object not carried forward from on_cancel.
Fulfillments object should also be carried forward from on_cancel_rto, and the end.time.timestamp of RTO_fulfillment should be updated.
Delivery fulfillment not carried forward.
Quote price not carried forward from on_cancel.

Flow 6

on_update

order.created_at should remain the same as confirm.
@ondc/org/settlement_details trail should be maintained. How are you getting settlement details for a refund before the order is picked for return? Please do not provide mock details.

on_update_approval

Quote price changed from 99 to 100.

on_update_picked

order.items not mapped with new fulfillment.
igm_request is required in reference to the issue related to return request raised in IGM. This will be added here only after issue resolution and returned in all post-order APIs like /on_status, /on_update, /on_cancel. If that's not the case, please do not provide this.
settlement_amount should be in string.

@bindukallupurackal

Flow 2

On_status

@ondc/org/settlement_details missing.

Flow 5

On_status

@ondc/org/settlement_details missing.

Flow 6

On_update_interim_reverse_qc

delivery_fulfillment.start and end.timestamp updated after on_status; trail must be maintained.

on_update_picked

items object not updated

@bindukallupurackal

Esaras

Flow 2

On_select

quote.ttl is 300s in on_select and in on_init its 30s

on_status

fulfillment.start and end contact and person not carried forward from on_confirm
In 'Delivery' fulfillments/tags - 'state' tag to removed (it is used in case of Buyer app procuring logistics), also, list/code should be 'ready_to_ship' indicating whether the order has been marked ready to ship (it would not be updated to fulfillment state every time)

Flow 5

On_status_rto_delivered

delivery_fulfillment start.time.timestamp missing
Fulfillment of type 'Delivery' should be 'Cancelled' (state/descriptor/code)

Flow 6

on_update

fulfillment.start and end contact and person not carried forward.

on_update(delivered)

why quote_trail/type is 'tax'? tax is not a part of breakup, also in on_update_picked, type is 'item'

@bindukallupurackal

Flow 1

on_search

@ondc/org/return_window:”” ; should not be an empty string and must contain a value, as it also serves as the IGM window.
categories.descriptor.name should be meaningful and not a code.

on_search_inc

Only delta changes should be provided in on_search_inc, and bpp_provider.tags updates cannot be provided in on_search_inc. For example, if there is an update in the items array, then only the provider id and items array should be provided.

Flow 6: Part-Cancel

Does Esaras provide part-cancellation functionality before accepting the order?

@bindukallupurackal

ONDC-Official / v1.2.0-logs

Esaras - SA - compliance check #1902

Flow 1

Flow 2

Flow 3

Additional issues

RET16 search

confirm

on_init

on_confirm

on_status

ESaras

RET12

Flow 1 - on_search

RET13

Flow 1 - on_search

RET16

Flow 1 - on_search

Flow 3

on_select_oos

select

init

on_init

on_status

Flow 4

cancel

on_cancel

Flow 5

on_search

on_cancel

Note

Esaras

RET16

on_search

Flow 2

confirm

on_status

on_status_delivered

Flow 3

on_select

Flow 4

on_cancel

on_status_RTO_delivered

Flow 6

Note

Esaras

Flow 1

on_search

Flow 2

on_search

on_status

Flow 3

select_out_of_stock

on_status_out_for_delivery

Flow 5

on_cancel

on_status

on_status_rto_delivered

Flow 2

On_status

Flow 5

On_status_rto_delivered

Flow 6

on_update

on_update_approval

on_update_picked

Flow 2

On_status

Flow 5

On_status

Flow 6

On_update_interim_reverse_qc

on_update_picked

Flow 2

On_select

on_status

Flow 5

On_status_rto_delivered

Flow 6

on_update