SMS provider

Transactional SMS (order confirmations, OTPs, shipping updates) runs through a shared, versioned package. The call site — send_sms(...) — is provider-agnostic; each adapter maps its vendor onto the same canonical contract.

What’s available

Setting value	Provider
twilio	Twilio
a BD local gateway	a local SMS gateway adapter

The settings

Setting	Purpose	Default	Where
sms_provider	The SMS provider for this store	blank → the deployment default	Tenant config → Providers
SMS_DEFAULT_PROVIDER	Deployment-wide default SMS provider	twilio	.env
provider credentials	API keys / tokens	—	Integrations (encrypted)

The active provider resolves in order: TenantConfig.sms_provider → SMS_DEFAULT_PROVIDER (.env, defaults to twilio) → the first provider that has credentials.

Wiring a provider

1. Add the provider’s credentials as an App integration — encrypted at rest automatically.
2. Set sms_provider in the tenant config (or SMS_DEFAULT_PROVIDER in .env for a deployment-wide default).

Credentials are handled securely — and never echoed

SMS API keys and tokens live only in the encrypted Integrations store, never in the tenant config or .env, and are never returned by the public config endpoint. The config only names which provider is active.

On the lite profile, SMS sends inline

In the lite profile, SMS is sent synchronously with a strict 2-second timeout; a failed send is logged and retried from the outbox (every 10 minutes), never breaking the request. On the full profile it runs on a Celery worker with patient timeouts. See Architecture overview.

Related: Payment providers · Courier providers.