Catalog modeling
Products, categories, variants, merchandising data and project-specific availability rules.
Capability explorer
Find the right
responsibility boundary.
This catalog describes architectural capabilities and implementation patterns. It does not claim that every Thonem deployment enables every capability.
Pricing & promotions
Pricing and promotion rules can be modeled around the project instead of spread across presentation code.
Checkout orchestration
Coordinates validation, delivery, payment intent and order creation behind a controlled boundary.
Order lifecycle
Explicit state transitions connect order capture with preparation, fulfillment and after-sales workflows.
Customer accounts
Account, address, order history and loyalty capabilities can be enabled when the implementation needs them.
Web storefront
Customer-facing web experiences can evolve independently from core commerce rules.
Mobile clients
APIs can support mobile apps while keeping domain rules centralized in the commerce core.
Payment adapters
Provider-specific request, callback, verification and idempotency logic stays at an adapter boundary.
Shipping adapters
Carrier requests, labels, tracking and status updates can be isolated from order domain logic.
ERP / CRM synchronization
Internal systems can exchange selected business data through explicit synchronization contracts.
Guarded releases
Public overlay releases can be verified, baselined, installed and rolled back separately from commerce code.
Public diagnostics
A non-sensitive endpoint reports only the health of files owned by the public website overlay.
No capabilities match that filter.
Deployment-specific configuration wins.
Use the capability explorer to understand the product model, then verify the exact modules, providers and contracts present in the target Thonem deployment.