IndiaPost - compliance check

[sandeepshahi]

Indiapost/Viranc

1. /on_search

   • context/timestamp can't be the same as in /search
   • fulfillment type of RTO should be provided along with the quote in /items
   • invalid time object in /catalog/bpp/providers/locations
   • address is missing in /locations (/locations is required only when shipment is to be dropped at LSP location )
   • Delivery TAT for Standard Delivery should be reduced (/categories/time/duration)

2. /on_init

   • context/timestamp can't be the same as in /init
   • invalid attributes rating, rateable,related, recommended in /items
   • /quote/price/value should be in string format
   • /quote/breakup/price/value should be in string format
   • many invalid attributes in quote/price and quote/price/breakup/price (estimated_value,computed_value,listed_value,offered-value,minimum_value, maximum_value)

3. /on_confirm

   • context/timestamp can't be the same as in /confirm
   • many invalid attributes in /items and /fulfillments (refer API Contract v1.1.0)
   • category_id can't change in /order/items (should be the same as in /on_search)
   • RTO charges should not be present in /quote/breakup (quote.price should be equal to sum of(quote.breakup.price))
   • payment object is not required in /on_confirm
   • /order/updated_at is missing
   • /start/location and /end/location is not required in /on_confirm

• unsolicited /on_status covering complete order delivery should be provided
• ready to ship thru /update and corresponding pickup & delivery time in /on_update needs to be supported

@Nibin7818

[abhinavv245]

IndiaPost/Viranc

• unsolicited /on_status calls covering complete order delivery should be provided
• ready to ship through /update and corresponding pickup & delivery time in /on_update needs to be supported

@Nibin7818

[abhinavv245]

Flow 1

• context/timestamp of all /on_action APIs should be in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format

/on_search

• fulfillment type of RTO should be provided along with the quote in /items
• Delivery TAT for Standard Delivery should be reduced (/categories/time/duration)

/on_init

• provider_location to be provided in case returned in /on_search

/on_confirm

• /on_confirm/message/order/billing/tax_number mismatches in /billing in /confirm and /on_confirm
• /on_confirm/message/order/billing/created_at mismatches in /billing in /confirm and /on_confirm
• /on_confirm/message/order/billing/updated_at mismatches in /billing in /confirm and /on_confirm
• /on_confirm/message/order/created_at mismatches in /confirm and /on_confirm
• /on_confirm/message/order/updated_at does not match context/timestamp

/on_status

• /on_status/message/order/provider/id mismatches between /init and /on_status
• /on_status/message/order/items must have required property 'category_id'
• /on_status/message/order/items must have required property 'descriptor'
• /on_status/message/order/items/id mismatches in /confirm and /on_status
• /on_status/message/order/payment must have required property 'type'
• /on_status/message/order/payment must have required property 'collected_by'
• /on_status/message/order/billing must have required property 'address'
• /on_status/message/order/billing/tax_number mismatches in /billing in /confirm and /on_status
• /on_status/message/order/billing/created_at mismatches in /billing in /confirm and /on_status
• /on_status/message/order/billing/updated_at mismatches in /billing in /confirm and /on_status
• RTO charges to be added in quote/breakup once RTO is initiated
• eway bill details should only be provided for orders with amount>50k
• fulfillments/state/updated_at is an invalid attribute
• fulfillments/id,rating,provider_id are not required
• how is order picked up as the fulfillment is not marked ready_to_ship in fulfillments/tags in /confirm or /update
• Pickup timestamp (fulfillments/start/time/timestamp) is required for fulfillment state - Order-picked-up
• Pickup timestamp (fulfillments/start/time/timestamp) is missing for fulfillment state - Out-for-delivery
• Pickup timestamp (fulfillments/start/time/timestamp) is missing for fulfillment state - Order-delivered
• Delivery timestamp (fulfillments/end/time/timestamp) is required for fulfillment state - Order-delivered
• fulfillments/start and end are missing

Flow 2

• similar issues as above
• cancellation flow triggering RTO needs to be implemented

@SrujanMungara

[abhinavv245]

Flow 1 and 2

/on_search

• item/time/timestamp should be of the date 3 days after context/timestamp as TAT is P3D (RTO item)

/on_init

• provider_location to be provided if returned in on_search, to be used where shipment is to be dropped at provider location by the logistics buyer

/on_confirm

• provider/locations is not required (id mismatch with on_init as well)

/on_update

• fulfillments/end/time/range should be provided as per TAT (P3D)

/on_status

• RTO charges to be added in quote breakup only when RTO is initiated

@SrujanMungara

[abhinavv245]

Flow 1 and 2

/on_search

• items/id for RTO item should not be same as the item id of the parent i.e Standard Delivery
• items/parent_item_id should be mapped with the item id of the parent item i.e Standard Delivery
• fulfillment_id for RTO item should be mapped with the correct id for RTO in bpp/fulfillments i.e '3'

/on_init

• provider_location to be provided if locations object is provided in on_search (used where shipment is to be dropped at provider location by the logistics buyer)

/on_confirm

• eway bill details is required for inter-state orders with amount>50k

/on_status

• fulfillments/state/updated_at is not required
• fulfillments/start and end should be provided for fulfillment type - 'Prepaid' (RTO-Initiated and RTO-Delivered)
• items/quantity is an invalid attribute
• provider/locations is not required
• fulfillments/start and end time range timestamps should be in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ)
• Precision for all prices in quote can be maximum of 2 decimal digits

/on_cancel

• 'AWB no' is required for P2H2P shipments in /tags

/on_update

• /on_update/0/message/order/items/0/id must be equal to constant (Standard Delivery)
• fulfillments/start and end time range timestamps should be in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format

@SrujanMungara

[sandeepshahi]

/on_search

• mapping of parent_item_id for RTO should be correct; should be the item_id of the parent category;

/update

• order/state can't change from "Accepted" to "Created" by BNP; should be NACK'd

/on_update

• order/updated_at should be updated as per the context/timestamp; can't be before /update timestamp

/on_status (RTO)

• RTO initiated timestamp is not captured correctly; can't be same as Order-picked-up timestamp

@SrujanMungara, All the previously identified issues should be rectified before resubmitting the logs

[abhinavv245]

Flow 1

/on_search

• parent_item_id for the item with id 'Standard Delivery' will be "" as it is the parent itself.

/on_update

• fulfillments/delivery/time/range should be within the TAT duration provided in on_search (P3D)

/on_status

• quote price does not match the total breakup price
• in /fulfillments, 'start/time/range' and 'end/time/range' are missing fulfillment state - 'Agent-assigned',

Flow 2

• Incorrect Flow as per context/timestamps - (on_cancel,on_status,search,on_search,init,on_init,confirm,on_confirm,update,on_update)

/on_status(RTO-Initiated/Delivered) and /on_cancel

• Transaction ID should be same across the transaction: "805fc922-4060-4f67-87cf-16e433318d4f_6528ed3727b73d292cff697a"
• order id mismatches from /confirm API

@SrujanMungara : All the previously identified issues should be rectified before resubmitting the logs

[abhinavv245]

Flow 1 and 2

/update

• order/state can't change from "Accepted" to "Created" by BNP; should be NACK'd

/on_status (Agent-assigned)

• Order state should be 'In-progress' once the fulfillment state changes from 'Pending'

/on_status(RTO-Initiated/Delivered)

• For fulfillment with type 'RTO', start/time/timestamp is missing

@SrujanMungara

[sandeepshahi]

/init

• gps and area_code mismatch in /fulfillments/end/location; How is SNP checking the serviceability
• building is mandatory; SNP should NACK the request

/on_update

• pickup time range should be realistic and feasible; should not overlap with context/timestamp

/on_status (RTO-Initiated)

• context/timestamp can't be earlier than /on_cancel timestamp
• AWB no is missing in /tags
• invalid item id of RTO quote in quote/breakup; should be "Standard Delivery-RTO"
• tracking is enabled for RTO shipment. Is this intented?

@SrujanMungara