Elogic Commerce · Research data

Commerce Integration Failure Atlas Codebook

Version 1.1.0 · Generated 2026-08-01 · 40 synthetic test records.

All launch records are Evidence Class D reproducible synthetic fixtures. The atlas does not claim that a named vendor caused an incident or that any failure pattern has a measured frequency.

Record schema

Field	Type / rule	Example
`id`	Immutable string	CIF-001
`slug`	Stable URL-safe string	duplicate-order-after-webhook-retry
`title`	Plain text	Duplicate order after webhook retry
`category`	Controlled enum	orders_and_fulfillment
`severity`	Controlled enum	critical; high; medium; low
`evidence_class`	A–E	D
`systems`	Array	[commerce, oms, erp]
`symptom`	Plain text	Visible business or operational result.
`root_cause`	Plain text	Failure mechanism, not blame.
`detection`	Array or text	Signals, reconciliation, and alert.
`control`	Array or text	Preventive and recovery controls.
`given`	Plain text	Starting state and data.
`when`	Plain text	Failure injection or event.
`then`	Plain text	Expected technical and business result.
`sources`	URL array	Control-principle sources where relevant.
`version`	Semantic version	1.1.0
`last_reviewed`	ISO date	2026-08-01
`control_sources`	URL array	Official documentation that supports the control behavior, not the incident.
`evidence_scope`	Controlled string	synthetic_fixture; documented_behavior; public_incident; vendor_advisory
`telemetry_fields`	Array	Minimum fields required to detect and trace the failure.
`limitations`	Plain text	What the fixture and source do not prove.

Category enum

Label	Enum	Records
Orders and fulfillment	`orders_and_fulfillment`	CIF-001 to CIF-006
Pricing and promotions	`pricing_and_promotions`	CIF-007 to CIF-011
Inventory and availability	`inventory_and_availability`	CIF-012 to CIF-016
Customer and B2B accounts	`customer_and_b2b_accounts`	CIF-017 to CIF-020
Catalog and product data	`catalog_and_product_data`	CIF-021 to CIF-025
Payments, tax, and fraud	`payments_tax_and_fraud`	CIF-026 to CIF-029
Returns and refunds	`returns_and_refunds`	CIF-030 to CIF-032
Observability and recovery	`observability_and_recovery`	CIF-033 to CIF-036
Security and access	`security_and_access`	CIF-037 to CIF-040

High-level control tags used by the interactive filter

These tags group the visible preventive-control text into the ten control themes published on the canonical page. The full preventive control remains the authoritative record field.

Control	Filter key	Plain-English rule
1. System of record	`system-of-record`	Name the system allowed to decide each business fact.
2. Idempotency	`idempotency`	The same request can be repeated without creating a second business action.
3. Event identity	`event-identity`	Every event has a unique ID and source.
4. Ordering and version	`ordering-and-version`	New state cannot be replaced by an older event.
5. Bounded retries	`bounded-retries`	Temporary failures are retried with delay, limits, and jitter.
6. Dead-letter handling	`dead-letter-handling`	Failed messages remain visible and recoverable.
7. Reconciliation	`reconciliation`	Systems are compared even when no error is visible.
8. Correlation ID	`correlation-id`	One business flow can be traced across every system.
9. Least privilege	`least-privilege`	An integration can access only the data and actions it needs.
10. Replay safety	`replay-safety`	A recovery action cannot repeat an unsafe side effect.

Evidence classes

Class	Meaning	Publication rule
A	Official vendor advisory, defect note, or documented behavior.	Link the exact official source and version.
B	Public incident report or technical postmortem.	Preserve context and do not generalize beyond the report.
C	Anonymized operational incident with explicit publication rights.	Legal and client approval required. Remove re-identification risk.
D	Reproducible synthetic fixture based on a defined failure mechanic.	Label as synthetic. Publish inputs, expected result, and limitation.
E	Unverified community report or anecdote.	Use only as a research lead. Do not publish as a confirmed failure record.

Change policy

IDs and stable anchors are immutable. Corrections, severity changes, test changes, and additions should be appended to the changelog. Historical data releases should remain available.

License and attribution

Recommended license: Creative Commons Attribution 4.0, subject to Elogic Commerce legal approval. Required attribution: “Commerce Integration Failure Atlas by Elogic Commerce” with a link to https://elogic.co/commerce-integration-failure-atlas/