Mahindra logistics - LSP - compliance check

[abhinavv245]

Flow 1

/search

• Use payment.type as "POST-FULFILLMENT" as this is what's enabled for now;

/on_search

• categories/0/time must have required property 'timestamp'
• items/0/time/timestamp must match date format
• all the supported categories including the child categories may be provided in the catalog

/on_init

• order/fulfillments/0 must have required property 'id'
• fulfillments/0/start and end must have required property 'contact'
• fulfillments/0/start and end/location/address must have required property 'name'

/confirm

• order/quote need not have additional properties (ttl)
• PCC (fulfillment.start.instructions.code & short_desc) are required when order ready_to_ship is "yes" (short_desc should not have more than 6 digits)
• @ondc/org/collection_amount is required only for payment/type 'ON-FULFILLMENT'
• @ondc/org/linked_order/order/weight/value Payload weight mismatches from /search
• Total order weight '0.800000011920929 does not match the total unit weight of items '00.00'

/on_confirm

• tracking should be enabled (true) for hyperlocal (Immediate Delivery)

/update

• linked order details may be sent only if there is a change in the weight / dim of the goods being shipped (from /confirm);

/on_update

• order/items/0/category_id must be equal to constant (Immediate Delivery)
• order/items/0 must have required property 'fulfillment_id'
• 'In-progress' is not a valid enum for fulfillments/0/state/descriptor/code
• linked_order must have required property 'order'
• linked_order/items/0 must have required property 'quantity', 'price'
• linked_order/provider/address must have required property 'name'
• fulfillments/0 must have required property 'tracking'

/on_status

• Pickup timestamp (fulfillments/start/time/timestamp) cannot change for fulfillment state - Out-for-delivery and Order-delivered

/track and /on_track

• live tracking should be enabled and logs should be provided for the same

RTO Flow

• similar issues

/on_confirm

• fulfillments/0 must have required property 'tags'

/on_status

• In case of RTO, fulfillment with type 'Delivery' needs to be 'Cancelled'
• fulfillments/1/state/descriptor/code is an enum (RTO-Initiated)

Note: Kindly use the log verification tool and rectify all the identified issues, also attach the generated report along with the logs

@jeevansanju

[abhinavv245]

Flow 1

/on_search

• do you not support standard delivery? (as searched by the BAP)
• items/descriptor for I1 is not correct (describes it as RTO)

/update

• why is end/instructions/code changing? (also, instructions/short_desc(DCC) cannot be same as PCC - \"884697\")

/on_update

• items/0/time/duration must be equal to constant (PT40M)
• @ondc/org/linked_order/items/quantity/measure/value has changed

/on_track

• tracking/location/time/timestamp cannot be future dated w.r.t tracking/location/updated_at

RTO Flow

• similar issues as above

/on_cancel

• rto_event tag is missing in /fulfillments/tags
• request to add precancel_state to the fulfillment in /fulfillments/tags

/on_status

• status update for RTO initiated need not be sent again as it was done already in /on_cancel (also, start/time/timestamp cannot change for RTO-Initiated w.r.t /on_cancel)
• start/time/timestamp for RTO Fulfillment (RTO-Delivered) should be same as /on_cancel
• may add tracking optimization params such as gps_enabled, url_enabled, url to fulfillment.tags.tracking in /on_status;

@jeevansanju

[abhinavv245]

/on_confirm

• @ondc/org/linked_order/items/quantity/measure/value mismatch from /confirm (in /on_update as well)
• start/time/duration (average time to pickup) is missing in fulfillments

/on_track

• tracking/location/updated_at cannot be future dated w.r.t context/timestamp

/on_cancel

• Is the RTO initiated after 1 retry? Is that the standard being followed?
• rto_id 'F1-RTO' in fulfillments/tags does not match with the one provided in on_search '2' in /fulfillments
• RTO id - '1-RTO' of fulfillment type 'RTO' does not match with the one provided in on_search '2' in /fulfillments (in on_status_rto_delivered as well)

@jeevansanju

[BLR-0118]

Flow 1

1. /on_track:
   • pls also add tracking.tags.order, tracking.tags.config;

@jeevansanju - clearing logs for v1.2.0; pls make sure the above issue is fixed