---
id: ADR-COM-ORD-010
title: Orders records carry no custom fields
product_area: commerce
module: orders
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Declare no custom-field capability on Orders records and retain purpose-built administration surfaces.
constrains:
  - DOM-COM-ORD-001
  - DOM-COM-ORD-002
  - DOM-COM-ORD-003
  - DOM-COM-ORD-004
  - DOM-COM-ORD-005
  - DOM-COM-ORD-006
  - SCR-COM-ORD-002
  - SCR-COM-ORD-003
origin: >-
  R2-ARCH-001 v1.0 (Andrew, 2026-10-19), copied into
  services-commerce:docs/milestones/plans/COMM-M2-plan.md#7a. Entity capabilities (R2-ARCH-001)
alternatives:
  - option: Opt orders into configurable entity fields
    why_not: Entity customization requires Andrew to revise the existing no-custom-fields decision.
consequences:
  - Order screens remain purpose-built without configurable custom-field layouts.
  - The order metadata object declares no entity capabilities.
supersedes: []
evidence:
  - >-
    services-commerce at c8b66a98: AGENTS.md (custom-field capability); aws/commerce.metadata.ts;
    modules/orders/metadata/orders.object.ts; docs/migrations/order-domain/README.md D10 (value table
    withdrawn).
---

# Orders records carry no custom fields

## Context

Custom fields require an explicit entity capability decision.

## Decision

Apply the recorded Commerce decision by declaring no custom fields on these records.

## Alternatives Considered

Opting orders into customizable fields would require Andrew to change the existing entity decision.

## Consequences

Order detail and composition remain purpose-built. Future configurable order data requires a new product decision.