---
id: TST-COM-FUL-033
title: Fulfillment policies
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - >-
    modules/fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js
implements:
  - ATS-COM-FUL-001-01
  - ATS-COM-FUL-001-02
  - ATS-COM-FUL-001-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js
    test_titles:
      - >-
        answers each as written: a UUIDv7 id, the policy with the contract’s defaults filled in, the
        scope, active unless stated, its system properties
      - >-
        stores a paid-amount threshold given as the wire’s number or as the boundary’s decoded
        bigint, and reads it back as a JSON number
      - 'refuses a second tenant default and a second policy of one scope, 400 naming the replacement'
      - >-
        refuses a tenant default naming a scope, a scoped policy naming none, a policy the contract
        refuses, and a blank name
      - >-
        replaces a policy at the version read, refuses a stale version 409, and refuses a locked
        record
      - 'deletes a policy and answers 404 to a read, an update or a delete of it afterwards'
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js#refuses
        a tenant default naming a scope, a scoped policy naming none, a policy the contract refuses,
        and a blank name
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js#refuses
        a second tenant default and a second policy of one scope, 400 naming the replacement
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js#replaces
        a policy at the version read, refuses a stale version 409, and refuses a locked record
---

# Fulfillment policies

## Verification Boundary

This suite checks fulfillment policies against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.