feat: Add fulfillment-level tracking tracking support to /trackAPI#480
Open
rashap224 wants to merge 3 commits intobeckn:masterfrom
Open
feat: Add fulfillment-level tracking tracking support to /trackAPI#480rashap224 wants to merge 3 commits intobeckn:masterfrom
rashap224 wants to merge 3 commits intobeckn:masterfrom
Conversation
Open
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Reference : Resolves #313
This PR introduces support for tracking at the fulfillment level in the /track API. The following changes have been made:
API Schema Update:
Added an optional
fulfillment_idproperty to the /track API schema to enable tracking specific fulfillments within an order.Changelog Update:
Documented the changes in the CHANGELOG.md file.
Context:
The /track API previously supported tracking only at the order level. This enhancement addresses the need for item-based fulfillments where multiple fulfillments within a single order may involve different logistics providers, each with its own tracking URL.
Impact:
Enables more granular tracking for use cases involving multiple fulfillments.
Backward-compatible as the
fulfillment_idproperty is optional.