Ecom Express - LSP - compliance check

[abhinavv245]

Flow 1

/on_search

• categories/time/timestamp and items/time/timestamp should be referring to date (w.r.t Context.timestamp) for which this TAT (P5D) is provided (same day for Immediate Delivery / SDD, next day for NDD, appropriate date for other categories)
• parent_item_id for the item with fulfillment_id :1 (i.e parent item) should be "" (as it does not have a parent)
• parent_item_id for the item with fulfillment_id :2 (i.e RTO item) should be the id of the parent item (i.e '1').

Flow 2

• similar issues as above

/init

• payment need not have additional properties (collected_by)

/on_init

• order/quote must have required property 'ttl'

/confirm

• order/id should be unique (cannot be equal to transaction_id) (LSP should send NACK)

/on_update

• context/timestamp difference between on_update and update should be within 1 seconds

/on_status

• Kindly submit unsolicited on_status call for fulfillment state - 'Agent-assigned'
• fulfillments/tags (ready_to_ship) not required
• how is payment status 'PAID' for payment type 'POST-FULFILLMENT'
• pickup timestamp (fulfillments/start/time/timestamp) for fulfillment state 'Order-picked-up' is not recorded correctly, cannot be before RTS (ready to ship) was triggered in /update
• delivery timestamp (fulfillments/end/time/timestamp) for fulfillment state 'Order-delivered' is not recorded correctly

Flow 3

• similar issues as above

/on_cancel

• appropriate cancellation/reason/id should be used
• fulfillment of type 'Delivery' should be 'Cancelled' and another fulfillment of type 'RTO' will be added initiating the RTO (RTO-Initiated) with its start/time/timstamp

/on_status

• all fulfillment states (Agent-assigned, Order-picked-up,Out-for-delivery) should be provided until RTO is delivered
• same as on_cancel (RTO-Delivered)

@AryanSinghEcom Kindly test with another logistics buyer in Pre Production and resubmit the logs

[AryanSinghEcom]

/on_search Sure, will correct it as mentioned

/on_init order/quote must have required property 'ttl' This is an error in the log verification utility. When I was testing using the utility, it informed that ttl is an extra field. Thats why I removed this. Can you please confirm?

/confirm I do not understand the error here, in the logs submitted, order id is CQ9CP72042 and the transaciton ID is:b7ada47b-fb73-4907-9a5b-734701342c5e

/on_update _context/timestamp difference between onupdate and update should be within 1 seconds Since in the backend for requests, these are apis of the testing environment, This can take a little more than a second. But rest assured this is unlikely to happen in the production

/on_status _Kindly submit unsolicited onstatus call for fulfillment state - 'Agent-assigned' This is not in our use case, these are more likely to occur for orders that are Immediate Delivery

_fulfillments/tags (ready_toship) not required Sure, will update my logic to remove this from on_status

pickup timestamp (fulfillments/start/time/timestamp) for fulfillment state 'Order-picked-up' is not recorded correctly, cannot be before RTS (ready to ship) was triggered in /update

delivery timestamp (fulfillments/end/time/timestamp) for fulfillment state 'Order-delivered' is not recorded correctly Sure, will update

how is payment status 'PAID' for payment type 'POST-FULFILLMENT' Ideally we will not accept anything other than prepaid orders (ON-ORDER). But since the seller we integrated with was sending POST-FULFILLMENT, I accomodated the requests for the same temporarily. Will correct this.

FLOW-3 Will do the required changes and update.

fulfillment of type 'Delivery' should be 'Cancelled' and another fulfillment of type 'RTO' will be added initiating the RTO (RTO-Initiated) with its start/time/timstamp can you please elaborate this a little further?

[abhinavv245]

Clarifications

/on_init

• ttl is a required property in quote (please check contract)

on_status (Agent-assigned)

• it is a requirement as the seller would get to know when the agent has been assigned (please check contract for all the fulfillment states required for inter city)

/confirm - you can ignore this one

/on_update

• Pre prod environment should be replica of the Prod environment apart from money flow

Flow 3

• when RTO is triggered, the previous fulfillment is cancelled, however its trail is maintained. A new fulfillment is added of type RTO. Please check on_cancel (RTO-flow) documentation and example in the contract

@AryanSinghEcom

[abhinavv245]

@AryanSinghEcom Please resolve all previous issues identified above and the issues identified by the utility and resubmit the logs.

[abhinavv245]

Flow 2 and 3

/on_init

• fulfillment charges will have separate quote line item for taxes (in quote/breakup)
• context/timestamp difference between on_init and init should be within 1 seconds (Flow 2)

@AryanSinghEcom

[AryanSinghEcom]

• fulfillment charges will have separate quote line item for taxes (in quote/breakup) Taxes were not a part of v1.2.0 Phase-1 contract for ONDC. Please confirm.

• context/timestamp difference between on_init and init should be within 1 seconds (Flow 2) We have a very scaled down infrastructure on the preprod environment. With proper resources allocated, this unlikely to happen on Production environment.