---
id: TST-COM-CAT-044
title: Merchandise Verification
kind: api-lifecycle
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/merchandise/tests/e2e/merchandise.e2e.spec.js
implements:
  - ATS-COM-CAT-007-01
  - ATS-COM-CAT-007-03
  - ATS-COM-CAT-007-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: 'Suite-owned workspace keys and database fixtures, removed by its cleanup hooks.'
binding_evidence:
  - scenario: ATS-COM-CAT-007-01
    source: >-
      services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#answers 400 to a
      product the tenant has not, a selection off the sets, a SKU in use and a second extension,
      naming the rule
  - scenario: ATS-COM-CAT-007-03
    source: >-
      services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#retires the product at
      its version, keeping the extension; a second retirement is 409
  - scenario: ATS-COM-CAT-007-08
    source: >-
      services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#lets a reader list and
      read, and refuses it every write 403 permission_missing, leaving the records as they were
  - scenario: ATS-COM-CAT-007-08
    source: >-
      services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#refuses custom fields
      (Commerce has none, R2-ARCH-001) and a product id that is not the merchandise’s 400 at the
      boundary
evidence:
  - 'services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js'
  - >-
    services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#Real: the composed
    handler, the routes, the mapper, the persistence services, the stand-in of Accounting's write
    path and PostgreSQL.
  - >-
    services-commerce:modules/merchandise/tests/e2e/merchandise.e2e.spec.js#Doubled: the signing key
    pair. The Accounting products the older cases hang on, and Accounting's configuration (the
    business unit, the tax classes, the type default), are planted as the owner.
execution_constraints:
  - No execution is performed in this documentation back-fill.
verification_boundary: >-
  Bindings identify the existing assertions contributing to each scenario; several suites can
  jointly cover a compound scenario.
---

# Merchandise Verification

## Verification Boundary

The composed API handler runs locally with signed caller contexts and the integration database. Its route, mapping, permission and persistence assertions establish the local API boundary.

## What This Suite Proves

The merchandise assertions contribute to the scenarios listed in the register. Each binding retains its exact source test anchor so a reviewer can distinguish an individual contribution from the complete scenario.

## What It Does Not Prove

The register records source inspection only. It establishes no run result, delivery qualification or Product approval.

## Real Dependencies and Test Doubles

PostgreSQL and the services called by the suite are real. External service ports, file storage and queues may use the fixtures declared by the suite and its support helpers.

## Must Not Be Doubled

Keep the asserted database constraints, transactions, service functions and execution contexts real. For API suites, preserve the dispatcher and permission enforcement.