Commerce · Component · transactional-notifications
Localized transactional notifications
What it does
Render and deliver account, membership and booking notifications by email and SMS.
Core pattern
Business state to localized messages + delivery receipts
- Input
- Account or booking event
- Output
- Delivery result and localized message
Key parameters
| Name | Type | Default | Values |
|---|---|---|---|
| recipient | — | — | — |
| locale | — | — | — |
| template | — | — | — |
| template_variables | — | — | — |
Maturity and limits
Template, email and SMS tests with multilingual email assets. Static source inspection only; no runtime, provider, deployment or test-pass claim.
Provider credentials required; customer and booking data need tenant isolation. Manifest declares ISC; verify bundled assets and supplier terms.
Used in pipelines
Industry tags
- Travel & hotelsSource-supported industry
For work involving destinations, room rates and bookings, use business state to localized messages followed by delivery receipts.
- HealthcareTransferable use
For non-clinical resource booking and cancellation coordination, use business state to localized messages followed by delivery receipts.
- Lifestyle & consumer appsTransferable use
Support “Notify the user and retain history” with business state to localized messages followed by delivery receipts.
Skills pack
Contract scaffold and deterministic mock
Download · 10KBSHA-256 66ec4fd94f714cc3a4dfedecd75aabb7a06018f80d07904dc2e1b94ad4c3caa2
Related components
-
-
Subscription checkout, seats and workspace quotas
Plan payment linked to seats + atomic quota checks
Working 1 pipeline -
Opt-in subscriptions, digests and entity alerts
Double opt-in subscriptions + deduplicated digests and unsubscribe
Working 1 pipeline -
Cruise inquiries and request tracking
Preference-based inquiry records + numbered tracking and handling
Working 1 pipeline