Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sequel String (TSP) - LSP - compliance check #2638

Open
abhinavv245 opened this issue Oct 14, 2024 · 1 comment
Open

Sequel String (TSP) - LSP - compliance check #2638

abhinavv245 opened this issue Oct 14, 2024 · 1 comment

Comments

@abhinavv245
Copy link
Collaborator

Forward Flow

/on_search

  • Item timestamp '2024-10-13' is not as expected for item rto_std, should be relative to context/timestamp
  • Item timestamp '2024-10-13' is not as expected for item rto_exp, should be relative to context/timestamp

/on_init

  • cancellation_terms, bpp_terms are not enabled yet, need not be sent as they have implications

/confirm

  • Average Pickup Time (fulfillments/start/time/duration) mismatches from the one provided in /on_search",

/update

  • update/on_update calls are missing, deferred ready_to_ship flow needs to be provided

/on_status

  • are you sending on_status for Agent-assigned state as well?

/track

  • track/on_track calls are missing

RTO Flow

/on_cancel

  • cancellation/cancelled_by should have LSP's subscriber id
  • precancel_state/updated is not correctly recorded

/on_status

  • on_status for RTO-Initiated is not requried, as the information is already provided in on_cancel

Cancel Flow

/cancel

  • invalid cancellation reason id for LBNP (LSP to validate)

/on_cancel

  • quote price to be updated by LSP (is LSP charging complete delivery charges for cancellation before agent is assigned?)

@Nirdosh3312

This was referenced Oct 16, 2024
@abhinavv245
Copy link
Collaborator Author

/on_search

  • Item timestamp '2024-10-24' is not as expected for item rto_std, should be relative to context/timestamp (For e.g. If context date is 2024-10-21, and TAT is P1D, then item timestamp date should be 2024-10-22), please correct all category or item timestamps

/on_track

  • on_track/0/message/tracking/id must be equal to constant (a94ddc4d-6ac1-4097-81fa-22853cfed4f0)
  • order/tags should be provided

@Nirdosh3312

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant