Splynx ISP Framework

All-in-One ISP Billing and Management Management Software

https://splynx.com/

Grace Period with Auto-Deduction on Renewal

I would like to request a feature for a "Grace Period" for expired customers. The Problem: Customers often expire on weekends or holidays when they cannot easily pay. They need immediate, temporary internet access. Proposed Logic: 1. Activation: Add a button in the Customer Portal/Admin View to "Activate Grace Period" (available only if status is Blocked/Expired). 2. Constraint: This can be used only once per billing cycle. 3. Auto-Deduction (Crucial): if setup 3 days grace period as loan, not a gift. When the customer finally renews their package, the system should deduct the grace days used. β€’ Example: Package expires on 1st Jan. β€’ Customer activates Grace Period (gets internet till 4th Jan). β€’ Customer pays for 1 Month on 4th Jan. β€’ New Expiry Date: 1st Feb Value: This reduces support calls for "temporary access" while ensuring we don't lose revenue on grace days.

Ramesh Kafle 10 days ago

πŸ’‘ Feature Request

Feature Request : Starlink API Integration for Automated Provisioning & Management

As more ISPs become Starlink Authorized Resellers, there is a growing need to manage Starlink terminals and subscriptions directly from IS¨P Billing systems just like we manage MikroTik, Huawei OLT, or TR-069 devices today. I'm requesting a native Splynx module (or add-on) that integrates with the Starlink Enterprise API v2 to automate provisioning, deprovisioning, monitoring, and billing of Starlink services. Current Situation: Today, ISPs who resell Starlink services must manually: Log into the Starlink Enterprise portal to activate/deactivate service lines Copy terminal serial numbers and subscription IDs between Splynx and Starlink Monitor terminal health and telemetry through a separate dashboard Reconcile billing between Splynx invoices and Starlink wholesale charges Handle plan changes (upgrades/downgrades) through the Starlink portal independently of Splynx This creates double data entry, billing discrepancies, delayed provisioning, and poor customer experience exactly the problems Splynx solves for traditional ISP infrastructure. Proposed Solution: A Splynx add-on that connects to the Starlink Enterprise Management API (v2) with the following capabilities: 1. Automated Provisioning When a Starlink service is created in Splynx → automatically activate the service line via POST /service-lines on Starlink API Map Splynx tariff plans to Starlink subscription types (50GB, 500GB, 1TB, Unlimited, etc.) Store Starlink serviceLineNumber, terminalId, and accountNumber as custom fields in Splynx 2. Automated Deprovisioning When a Splynx service is cancelled or suspended → automatically deactivate via PATCH /service-lines/{id} or DELETE Support both temporary suspension and permanent termination Sync status back to Splynx (active, suspended, terminated) 3. Telemetry & Monitoring Pull terminal telemetry (uptime, latency, throughput, obstruction %) via the Starlink Telemetry API Display terminal health in the Splynx customer card or network monitoring dashboard Trigger alerts when terminals go offline or performance degrades 4. Billing Reconciliation Sync Starlink wholesale usage data with Splynx billing Support data overage tracking and automatic surcharge invoicing Match Starlink billing cycles with Splynx invoice periods 5. Terminal Inventory Management Track Starlink hardware (dishes, routers, mounts) in Splynx inventory Link terminal serial numbers to customer accounts Manage RMA and replacement workflows Why This Matters: Starlink now has 7,000+ satellites and operates in 100+ countries, with a rapidly growing Authorized Reseller program Many ISPs, especially in Africa, Latin America, and rural markets, are adding Starlink as a service offering alongside fiber/wireless Splynx already serves 1000+ ISPs worldwide — many of whom are likely reselling or considering reselling Starlink The Starlink Enterprise API v2 is mature and well-documented, with OAuth2 authentication and RESTful endpoints No ISP billing platform currently offers native Starlink integration — this would be a first-mover advantage for Splynx

yves.belebenie@arctelecom.sn 12 days ago

πŸ’‘ Feature Request

Feature Request: Purchase Orders + Bulk Hardware Import (MAC / Serial)

Summary Add native Purchase Order (PO) management to Splynx, including the ability to import distributor spreadsheets (Excel/CSV) with MAC addresses and serial numbers before items are deployed Problem Statement Currently, Splynx only supports adding hardware after purchase, at the invoice stage. This creates a workflow gap for ISPs/WISPs that need to: Generate Purchase Orders before ordering from distributors Track hardware that is ordered, backordered, or in transit Pre-stage inventory (MACs / serials) received from distributors before deployment Maintain internal approval and reconciliation workflows Requested Features 1. Native Purchase Orders (POs) Ability to: Create Purchase Orders without creating an invoice Assign PO numbers Attach distributor/vendor Email distributor from Splynx Track PO status: Draft Submitted Partially received Fully received Cancelled Convert PO β†’ Invoice when received 2. Bulk Import of Hardware from Distributors Ability to upload an Excel / CSV file from distributors containing optional fields: MAC Address Serial Number Manufacturer Model SKU PO reference Cost per unit This is critical because many distributors (e.g. wireless, networking, CPE vendors) already provide packing slips or order confirmations in spreadsheet form. Why This Matters (Operational Impact) Without PO + bulk import support: Inventory tracking becomes manual Accounting and ops are forced out of Splynx MAC/serial handling is error-prone Larger deployments become inefficient This feature would significantly improve Splynx’s usability for ISPs managing real hardware supply chains.

TRL About 1 month ago

πŸ’‘ Feature Request