---
id: ADR-COM-FUL-017
title: Use these records without custom-field extensions
product_area: commerce
module: fulfillment
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
decision: >-
  Retain these Commerce records without custom fields under the cited opt-in
  architecture ruling.
constrains:
  - DOM-COM-FUL-001
  - DOM-COM-FUL-002
  - DOM-COM-FUL-003
  - DOM-COM-FUL-004
  - DOM-COM-FUL-005
  - SCR-COM-FUL-001
  - RESP-COM
origin: >-
  R2-ARCH-001, Andrew 2026-10-19 (custom fields opt-in per entity; Commerce
  without): services-commerce:AGENTS.md#Custom Fields Are Opt-In Per Entity:
  R2-ARCH-001 (Andrew, 2026-10-19)
alternatives:
  - option: Add custom fields to warehouse or shipment registrations.
    why_not: >-
      The registration contains no approved declaration for shipment or
      warehouse custom fields.
consequences:
  - Additional fields need a deliberate schema or capability decision.
  - The examined screens have no configurable custom-field layout contract.
supersedes: []
evidence:
  - >-
    services-commerce at c8b66a98: AGENTS.md (R2-ARCH-001 section); module
    registrations declare no custom-field capability.
---

# Use these records without custom-field extensions

## Context

Custom fields require an explicit per-entity product declaration.

## Decision

Retain these Commerce records without custom fields under the cited opt-in architecture ruling.

## Alternatives Considered

Add custom fields to warehouse or shipment registrations. The registration contains no approved declaration for shipment or warehouse custom fields.

## Consequences

Additional schema or custom-field needs require a product decision. Existing screens use their built components and schemas.