Add PostNL V4 migration planning docs#313
Open
sal4sup wants to merge 4 commits into
Open
Conversation
…e PostNL V4 migration. - Introduce phased implementation plan, technical rationale, and routing model for SDK-backed services. - Outline per-flow service interface pattern (Legacy and V4 implementations). - Document folder structure, class hierarchy, request sequence via diagrams. - Include open questions for PostNL, product mapping details, and test strategy. - Highlight backward compatibility and staged rollout/rollback options to ensure risk-managed deployment.
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
2 participants
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.
Summary
This is a documentation-only draft PR for reviewing the PostNL V4 SDK/API migration plan.
It includes:
Notes
No production code changes are included in this PR.
The proposed implementation approach is hybrid:
The main remaining blocker for label migration is the product/options to V4
shipmentType/servicesmapping.Smart Returns and activatereturn are documented as blocked until PostNL confirms the correct V4 behavior.
Files added
docs/postnl-v4-migration/postnl-v4-sdk-api-reference.mddocs/postnl-v4-migration/postnl-v4-migration-implementation-plan.mddocs/postnl-v4-migration/sources/PostNL-Future-Proof-V4-API.postman_collection.jsondocs/postnl-v4-migration/sources/sdk-docs/Review focus
Please review: