---
id: TST-COM-ORD-032
title: The staff void of a placed order
kind: api-lifecycle
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/checkout/tests/e2e/order-void.e2e.spec.js
implements:
  - ATS-COM-ORD-008-01
  - ATS-COM-ORD-008-02
  - ATS-COM-ORD-008-03
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: The suite creates its own test workspace records and removes them using the fixture cleanup.
evidence:
  - provenance: test
    source: 'services-commerce:modules/checkout/tests/e2e/order-void.e2e.spec.js'
    test_cases:
      - 'refuses a reader without commerce.orders.void, 403 permission_missing, and a portal member the route'
      - 'refuses a void without a reason, 400 naming it'
      - answers 404 in the other tenant for this tenant’s order
      - 'answers 200 with the order voided, carrying the reason, its lines and the history'
      - 'released the participant’s claim, the ledger and the obligations'
      - 'refuses a second void, 409 order_not_voidable, and a read answers the order voided'
scenario_coverage:
  - scenario: ATS-COM-ORD-008-01
    test_cases:
      - 'refuses a reader without commerce.orders.void, 403 permission_missing, and a portal member the route'
      - 'refuses a void without a reason, 400 naming it'
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
  - scenario: ATS-COM-ORD-008-02
    test_cases:
      - 'refuses a second void, 409 order_not_voidable, and a read answers the order voided'
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
  - scenario: ATS-COM-ORD-008-03
    test_cases:
      - 'released the participant’s claim, the ledger and the obligations'
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
dependency_evidence:
  provenance: test
  source: 'services-commerce:modules/checkout/tests/e2e/order-void.e2e.spec.js'
  declared_by_test: >-
    the composed handler, the routes, the void, the reference participant's SQL functions, the persistence
    services and PostgreSQL. Doubled: the signing key pair, the other services' tables (local stand-ins) and
    the billing port (the fixture the running macroservice carries until P3-WP01).
---

# The staff void of a placed order

## Verification Boundary

The suite drives the composed local API dispatcher and its registered routes.

## What This Suite Proves

The registered cases check the staff void of a placed order with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised Commerce persistence or workflow code are real. Remote service records, clocks and transports follow the suite’s fixtures.

## Must Not Be Doubled

The database constraints, role restrictions, locks and transactions exercised by this suite must use PostgreSQL.