search

ONDC-Official / verification-logs

ONDC Pre-production issue & discussion board
21 stars 248 forks source link

Blowhorn - compliance check #319

Open BLR-0118 opened 1 year ago

BLR-0118 commented 1 year ago
  1. /on_search - a. timestamp doesn't seem to be UTC (there's a 4 1/2 hr diff b/w search & on_search timestamps); b. timestamp isn't in RFC3339 format (where millisec has exactly 3 digits);
  2. /on_init - the payment block in /init can't be changed: "payment":{ "type":"POST-FULFILLMENT", "collected_by":"BPP", "@ondc/org/settlement_window":"PT2D", "@ondc/org/settlement_details":[ { "settlement_counterparty":"buyer-app", "settlement_phase":"sale-amount", "settlement_type":"neft", "settlement_bank_account_no":"1234512345", "settlement_ifsc_code":"15488ADEDD" } ] }, this means collection is by "BPP" (logistics provider) and the logistics buyer (i.e. DesignRight) is sending their settlement details. Why is this being changed in /on_init?
  3. /on_confirm - a. fulfillments.tracking has values true / false only; b. how's the start & end time range, agent, vehicle details assigned when ready_to_ship isn't triggered?
  4. /on_cancel - invalid RTO is triggered as unsolicited /on_cancel, not in response to /cancel; This is normal cancel initiated by the logistics buyer, in response to which the cancellation_reason_id should remain same;
  5. /on_status - fulfillment state code is invalid;
  6. No /update, /support APIs? a. /update is used to trigger ready_to_ship in response to which the AWB #, fulfillment start slot (may be end slot also), agent / vehicle details are assigned. Pls check the API contract for details; Not clear when the logistics order is being accepted?
BLR-0118 commented 1 year ago

@AdityaPin