Kudisms Notification Laravel Package

Product Decisions This Supports

• Buy vs. build: SMS delivery is a commodity integration. This package is a thin Laravel notification channel for KudiSMS — adopting it saves roughly 1–3 days of driver code plus ongoing upkeep as Laravel's notification contracts evolve. Building in-house only makes sense if we need behavior the package doesn't expose.
• Channel strategy: Enables SMS as a first-class channel alongside mail, database, and push for OTP/2FA, transaction alerts, delivery updates, and onboarding nudges — particularly relevant for Nigerian users where email engagement is weak and SMS is the default trust channel.
• Platform upgrade sequencing: 2.0.0 hard-requires Laravel 12/13 and PHP 8.3+. This becomes a concrete input to our framework upgrade roadmap: if we're on Laravel 10/11, SMS via this package is blocked until we upgrade (or we pin 1.1.1 and accept it as frozen).
• Maintenance planning: The vendor and namespace rename is a mechanical but breaking migration — one coordinated PR touching composer.json, every import, and the published config. Budget it as a maintenance ticket, not feature work.
• Vendor risk review: A package changing vendor identity (toneflix-code → toneflix) with a major bump is a natural trigger to confirm provenance, ownership continuity, and whether 1.x will still receive security patches.
• Use cases to validate first: OTP/2FA, payment confirmations, order/delivery status, and re-engagement campaigns in low-email-engagement segments.

When to Consider This Package

Adopt when:

• You're on Laravel 12 or 13 and PHP 8.3/8.4 — this is a hard requirement in 2.0.0, not a soft preference.
• KudiSMS is your chosen provider, or you want a low-effort way to validate SMS as a channel before committing contractually.
• You want Laravel-native Notification class integration rather than hand-rolled HTTP calls scattered through the codebase.
• Blast radius is small: SMS is a secondary channel and swapping the wrapper later is cheap.

Look elsewhere when:

• You're on Laravel 10/11 or PHP < 8.3 — either upgrade first or pin 1.1.1 and treat it as unmaintained going forward.
• You need multi-provider failover, per-country routing, or provider-agnostic abstraction — this locks you to one gateway.
• You need delivery receipts, cost analytics, sender-ID management, or templated campaigns at scale — evaluate the KudiSMS API directly.
• Procurement or compliance requires an SLA and contractual support; this is a community package with no stated support commitment.
• The vendor rename can't be cleared by a security/provenance review — verify the repository and namespace ownership before merging.

How to Pitch It (Stakeholders)

To executives: This is a small, low-cost adapter that lets us send SMS — OTP codes and transaction alerts — through KudiSMS using Laravel's standard notification system. Version 2.0 is housekeeping, not a feature release: the maintainer renamed the package and it now targets Laravel 12/13 and PHP 8.3+. The cost is a short, mechanical upgrade pull request whenever we're on the supported stack. The real decision this informs is buy-vs-build for messaging and which SMS provider we standardize on — not our architecture.

To engineering: 2.0.0 is breaking. Package renamed toneflix-code/kudisms-notification → toneflix/kudisms-notification; namespace ToneflixCode\KudiSmsNotification → Toneflix\KudiSmsNotification; requires PHP ^8.3|^8.4 and Illuminate ^12|^13. Migration is composer remove / composer require plus import and published-config updates. Before we adopt: confirm the new vendor namespace is the same maintainer, check whether 1.x is now EOL, and verify queueing, retry, and error-handling behavior against our requirements. Keep provider-specific calls behind our own notification class so a future provider swap stays a one-file change.