Ready to Ship status about ondc-protocol-specs

[BLR-0118]

Use tag "./ondc-order_ready_to_ship" to communicate if order is ready to ship (documented in Fulfillment)

[nirmay]

Thanks for adding the new field to facilitate this important use case.
2 quick questions,
Which API would Logistics Buyer use to send this tag /init or /confirm (the example above refers to create)
What are the enums for this tag? Ready / Not-Ready ?

[BLR-0118]

Since this status would typically be updated after confirmation of the order, you should use /update. This will have 2 values - no, yes as documented in the description for Fulfillment in the logistics spec

[nirmay]

So, if I understand this right, it will play out in 2 scenarios as per below,

if the category/product-type demands a separate step to be marked readiness of the order by the seller, then /init (and not /confirm) should include the tag ./ondc-order_ready_to_ship = no, later when it is indeed ready, Logistics Buyer to trigger /update with ./ondc-order_ready_to_ship = yes.

2. If the category/product-type does not demand a separate step to marked readiness of the order by the seller, then /init should include the tag ./ondc-order_ready_to_ship = yes.

pls confirm.

[BLR-0118]

I think making the order ready to ship will always be a separate step that includes packaging, tagging the PCC and probably other steps. As such, where do you see point 2 being required?