Commerce Architecture · 2026-08-14
Why commerce architecture stops at the wrong boundary
The storefront is visible, but the expensive failures often happen after checkout.
A storefront is easy to draw on an architecture diagram because its boundary is visually obvious. Operational commerce is not.
The difficult questions often begin after a customer has already paid:
- Which system owns the order now?
- Which inventory state is authoritative?
- What happens when fulfilment can only be partially completed?
- Who can safely retry a failed integration?
- Which system is allowed to print the shipping artefact?
Architecture should follow responsibility
A useful architecture map does not merely show APIs. It shows who owns decisions and state.
That distinction is what turns a collection of integrations into an operable system.