Skip to content

docs: add tax-inclusive (VAT) totals example - #681

Open
YanisMtcr wants to merge 1 commit into
Universal-Commerce-Protocol:mainfrom
YanisMtcr:docs/vat-tax-inclusive-example
Open

docs: add tax-inclusive (VAT) totals example#681
YanisMtcr wants to merge 1 commit into
Universal-Commerce-Protocol:mainfrom
YanisMtcr:docs/vat-tax-inclusive-example

Conversation

@YanisMtcr

@YanisMtcr YanisMtcr commented Aug 3, 2026

Copy link
Copy Markdown

Description

The totals examples only cover the US model, where tax is a line added on top of subtotal. There's no example for tax-inclusive (VAT) pricing, where subtotal is net, each rate is its own tax entry, and total is the tax-inclusive gross.

Add one example under the totals #### Examples section: a cart mixing a standard and a reduced rate (20% and 5.5%). Uses the existing repeating-tax rule; no schema change. 6000 + 800 + 110 = 6910.

Category (Required)

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Related Issues

None.

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

@damaz91 damaz91 added status:needs-triage Signal that the PR is ready for human triage documentation Improvements or additions to documentation status:under-review and removed status:needs-triage Signal that the PR is ready for human triage labels Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:payments documentation Improvements or additions to documentation status:under-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants