---
id: ADR-COM-ORD-011
title: No Orders operation is published to Submissions
product_area: commerce
module: orders
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Record the current absence of Submissions publication for every operation and leave a purchase-stage
  integration contract as a product question.
constrains:
  - SVC-COM-ORD-checkout
  - SVC-COM-ORD-orders
  - SVC-COM-ORD-participants
  - SVC-COM-ORD-entitlements
  - SVC-COM-ORD-purchasing
  - RESP-COM
origin: 'R2-ARCH-002 (publish or say why not), as applied by other corpus modules; OQ-COM-ORD-006'
alternatives:
  - option: Publish submission purchase and payment contracts immediately
    why_not: The purchase-stage integration has no agreed contract to publish yet.
consequences:
  - >-
    Existing benefits can be consumed through the database function without a submission-operation
    publication.
  - A submitting purchase stage needs the outstanding contract decision.
supersedes: []
evidence:
  - >-
    services-commerce at c8b66a98: route declarations of modules/{checkout,orders,entitlements,purchasing} (no
    Submissions binding); docs/forge-handoff/commerce.md F9 (Submissions asks).
---

# No Orders operation is published to Submissions

## Context

Operation contracts must make publication status visible.

## Decision

The current contracts state why each operation has no Submissions publication. A future purchase-stage interface remains open.

## Alternatives Considered

Publishing payment and placement now would commit an integration shape before its submitting workflow is designed.

## Consequences

The database consumption contract can support existing rights, but it is not itself a published submission-stage operation. The future purchase contract needs an explicit ownership decision.