Define the money path
Map product discovery → cart → checkout → payment → order → fulfillment. Identify which existing systems own each state today.
- Choose one market and one customer journey first.
- Record external contracts that cannot change during the first release.
- Separate must-have transaction work from optional analytics or marketing hooks.
Create explicit integration boundaries
Gateways, carriers, ERP, CRM and mobile clients should depend on stable internal contracts rather than leaking provider details throughout the commerce core.
commerce → adapter → provider
provider callback → adapter → verified domain eventShip with rollback evidence
Capture protected-route baselines, validate the overlay or service locally, deploy atomically, then compare the revenue-critical routes after the switch.
Project-specific contracts win.
These pages describe Thonem implementation patterns. Exact endpoints, payloads, credentials, retry rules and provider capabilities must be taken from the deployed project and its provider documentation.