Wits Adapter (SA: RET11) - compliance checks

[sandeepshahi]

Flow 1

/on_search

• different custom menus can't have the same display rank; check for categories/id: "hyt67G6g58GT" and "a1b2C3d4E5F6"
• default customization must be set for custom groups where config.min>0
• multi layer of customizations must be provided for verification
• max configuration for "K5lM6nO7pQ8r" is set as 2 while only single customization is provided in the catalog; check for similar issues in the payload
• lower/upper range and default_selection prices are not calculated correctly

Flow 2

/on_init

• np_type should also be provided in /tags/bpp_terms

/on_confirm

• address/locality in /start doesn't match with the store locality in /on_search
• how can estimated pickup/delivery time ranges be provided even before the order is Accepted?

/on_status

• Agent-assigned state is missing
• contact/email in /end is getting added and removed in /on_init, /on_confirm and /on_status; consistency must be maintained
• invoice must be accessible
• invoice link should be correctly

/track

• txn id can't change; SNP must respond with a NACK

Flow 3

• pls share the OOS scenario for customized item

Flow 5

/on_status

• invoice must be accessible

/on_cancel

• RTO should be initiated in /on_cancel and not disposed directly

@witslab-nikita

[witslab-nikita]

@sandeepshahi, we identified some issues before ONDC review while testing with NPs, and our latest logs are with Protean buyer application.

https://github.com/ONDC-Official/v1.2.0-logs/pull/2349