CC-36943 vertex backoffice configuration page#3814
Merged
profuel merged 9 commits intoJul 24, 2026
Conversation
✅ Deploy Preview for spryker-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
|
|
||
| For projects that extend the module, the feature adds the following public API: | ||
|
|
||
| - **Facade method:** `VertexFacadeInterface::validateTaxProviderConfigurationPreSave(ConfigurationValueCollectionRequestTransfer $transfer): ConfigurationValueCollectionRequestTransfer`. |
Collaborator
There was a problem hiding this comment.
Is also not an extension point.
Maybe mention the interface from the extension module and why it might be required.
I'd personally drop this whole section. Public API and extension points
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
profuel
reviewed
Jul 22, 2026
…/cc-36943-vertex-backoffice-configuration-page
profuel
previously approved these changes
Jul 23, 2026
|
|
||
| This document describes how to manage Vertex settings from **Back Office** > **Configuration** and how to select the tax provider per scope `store`. | ||
|
|
||
| With this feature enabled, operators manage every Vertex setting from the Back Office, per **global** or **store** scope, instead of environment variables. A new **Taxes** > **Tax Provider** switch chooses between the built-in Spryker tax calculation and Vertex. Save-time validation prevents leaving the integration in a broken state. |
Collaborator
There was a problem hiding this comment.
Suggested change
| With this feature enabled, operators manage every Vertex setting from the Back Office, per **global** or **store** scope, instead of environment variables. A new **Taxes** > **Tax Provider** switch chooses between the built-in Spryker tax calculation and Vertex. Save-time validation prevents leaving the integration in a broken state. | |
| With this feature enabled, operators manage every Vertex setting from the Back Office, per **global** or **store** scope, instead of environment variables. A new **Configuration** > **Taxes** > **Tax Provider** switch chooses between the built-in Spryker tax calculation and Vertex. Save-time validation prevents leaving the integration in a broken state. |
…/cc-36943-vertex-backoffice-configuration-page
profuel
approved these changes
Jul 24, 2026
profuel
deleted the
feature/cc-36943-vertex-backoffice-configuration-page
branch
July 24, 2026 10:10
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.
PR Description
Updated spryker-eco/vertex documentation with new backoffice configuration feature
Tickets