Attribute required to inform the logistics provider that COD collection will be required by the Logistics Agent during search request. about ondc-protocol-specs

[nirmay]

Including CoD preference of Retail Buyer in the search request to Logistics network, will avoid negotiation between Logistics Buyer and Seller later in the flow.

A suggestion would be to include, order.Payment.type = ON_FULFILLMENT in the Search Intent. This need not be required parameter.

[VidyaGF]

But then it would tell about the logistics payment type, rather than the CoD preference of Retail Buyer ? Little confused here.

[BLR-0118]

I think we should delink when the payment is collected vs payment collection preference. One way to do this would be through a new attribute in the search intent. What do you think?

[VidyaGF]

I too think a new attribute in search intent will be better

[nirmay]

I did not realise that order.payment.type would represent the settlement between Logistics buyer and seller, for any instructions from Retail Seller, it would have to be a separate attribute.

[VidyaGF]

@BLR-0118 - Any idea by when we can get this spec attribute?

[BLR-0118]

Will add Payment.collection_preference will have a single enum "CoD" for now. Retailer can use Intent.Payment.collection_preference to set this value

[VidyaGF]

ok , so Logistics Seller App can set values , CoD , prepaid and CoD , or prepaid only , to let the Logistics Buyer know , that only such Retail orders it will accept for delivery?

[BLR-0118]

For now, there is 1 value - "CoD". This would normally be set as part of the search intent by the retailer, which is why this issue was filed.

[BLR-0118]

renamed payment.collection_preference to payment."./ondc-collection_preference"