Zeitgeist Retail - compliance check

[sandeepshahi]

Flow 1

/on_search

• @ondc/org/contact_details_consumer_care should be in the format "name,email,contactno" in /bpp/providers[0]/items
• bpp/providers/categories is invalid property
• bpp/providers/locations has many invalid attributes (refer API contract)
• serviceability constructs (defined in /locations/circle and /tags) are conflicting
• items/descriptor values can't be empty
• items/fulfillments_id is an invalid attribute (fulfillment_id is already present)
• use correct mapping as per the enhanced subcategory list

/on_select

• /fulfillments[0]/@ondc/org/TAT (O2D) in /on_select can't be equal to @ondc/org/time_ship (O2S) in /on_search
• packing,tax,discount,misc should not be present if 0 in quote/breakup. Also, why are they declared twice, even though there is only one fulfillment created?
• Delivery charge should only be declared once.
• context/key is invalid property (to be removed from all the APIs)

/on_init

• provider/descriptor is not required
• buyer app finder fee can't change in /payment
• /fulfillments/location/address/door is an invalid attribute

/on_confirm

• /fulfillments/0 must have required property '@ondc/org/provider_name'
• context/timestamp difference between /on_confirm and /confirm should be smaller than 5 sec
• order/updated_at timestamp should be updated as per the context.timestamp (can't be future dated)
• billing object mismatches in /confirm and /on_confirm
• payment object mismatches in /confirm & /on_confirm
• Incorrect time ranges for shipment and delivery of items in /start and /end

/on_status (Completed)

• all the previous unsolicited fulfillment states should be shared for validation
• Billing object mismatches in /confirm and /on_status
• order/created_at timestamp can't change (should remain same as in /confirm)
• delivery timestamp (/end/time/timestamp) can't be before pickup timestamp (start/time/timestamp)
• order/updated_at timestamp can't be future dated (should match context/timestamp)

/on_update

• must have required property 'created_at'
• must have required property 'updated_at'
• /quote must have required property 'ttl'
• /quote/breakup/ must have required property 'title'
• fulfillment timestamps can't change
• item with count=0 should not be present in /items

Flow 2

• How is location non-serviceable if serviceability is defined as PAN India

Flow 4

• Not as per the test case scenario. (quantity should be part fulfilled)

Check Flow 2,3 4,5 for similar issues raised in Flow 1

@Rajathkunder

[sandeepshahi]

Common Issues

/on_search

• Invalid radius value in /locations/circle/radius/value
• Use the category_id as defined in the enhanced subcategory list
• statutory reqs and "@ondc/org/mandatory_reqs_veggies_fruits" are optional for F&B categories
• Why time_to_ship is 7 days for F&B categories?

/on_select

• Why delivery TAT is of 8 days for Immediate Delivery?

/on_confirm

• Invalid pickup and drop time ranges in fulfillments/start and fulfillments/end

/on_status

• Invalid attributes "settlement_timestamp" and "settlement_reference", "settlement_status" in /@ondc/org/settlement_details

/on_update (Liquidated)

• Timestamps of /on_update (Initiated) API cannot be equal to /on_update (Liquidated) API

Flow 2

/on_search

• store enable/disable timestamp (/bpp/providers/time/timestamp) must match context.timestamp

/on_confirm

• store name /fulfillments[0]/start/location/descriptor/name can't change

/on_cancel

• cancellation_reason_id should be a valid seller initiated cancellation id

Flow 4

/on_select

• valid domain error should be provided when item quantity is not available

@Rajathkunder

[sandeepshahi]

Common Issues

/on_search

• HTML tags should not be used in short_desc, long_desc
• invalid format of item code in /bpp/providers/items/descriptor/code
• placeholder values should be avoided in "statutory_reqs_packaged_commodities"

/on_select

• invalid tax calculation; prices should be tax inclusive in quote/breakup

/on_init

• Why is there inconsistency in the tax breakup of items in /on_select and /on_init?

/on_confirm

• Invalid pickup and drop time ranges in fulfillments/start and fulfillments/end; should be realistic and feasible

/on_status

• placeholder values should not be used in instructions and Invoice
• values in fulfillments/end/location/address should not be modified
• How can context/timestamp be future dated for Order-delivered state?

/on_update (Initiated)

• Timestamp of /on_status (Delivered) cannot be greater than /on_update (Return_Initiated);Items can't be returned until delivered.

Flow 5

• invalid flow; complete out-of-stock scenario for one of the items should be tested

@SudarshanSirsi

[SudarshanSirsi]

Hello, I just wanted to understand some things regarding quote/breakup/price and tax.

1. In /on_select I just wanted to confirm that what you mean is quote.breakup.price.value = item_price +tax_value Where tax value is -> { "@ondc/org/item_id": "435", "title": "Tax", "@ondc/org/title_type": "tax", "price": { "currency": "INR", "value": "10" } }

AND

2. If suppose, for some products, if MRP includes all taxes also, then the below object for tax in quote/breakup is mandatory?

   { "@ondc/org/item_id": "435", "title": "Tax", "@ondc/org/title_type": "tax", "price": { "currency": "INR", "value": "10" } }

3. Regarding "invalid format of item code in /bpp/providers/items/descriptor/code" in /on_search , For /bpp/providers/items/descriptor/code, if we use the HSN code as mentioned in V.1.1.0 API contract is that acceptable? Because The HSN values would not be unique for every individual product, but they may be unique for a category. Please correct me wherever I am wrong @bluecypher Thank You.

[sandeepshahi]

Common Issues

/on_search

• net_quantity_or_measure_of_commodity_in_pkg should have the quantity and UOM

/on_confirm

• estimated pickup and delivery time ranges can't be the same and should not precede the context/timestamp

/on_update

• invalid return initiation; can't be reinitiated after receiving the FYI /update call for refund
• Reverse QC return flow should be provided for verification

Flow 3

/on_update

• why multiple objects for item 435 created in /items?

Flow 5

/on_select

• available and maximum count in quote/breakup/item/quantity should be in string format

@SudarshanSirsi