Splynx ISP Framework

All-in-One ISP Billing and Management Management Software

https://splynx.com/

Inventory UX Issues

When returning item to Stock Location, Splynx doesn't automatically change the stock location from “Customer Premises” OR give you an option to choose a stock location. This also happens when unlinking an item from Network Site. Scenario: 1) Customer radio was upgraded from Ubiquiti PowerBeam 5AC to Tarana CBRS RN 2) Employee assigns Tarana CBRS RN to customer account via Inventory → Actions → Assign to customer/lead 3) Employee returns used Ubiquiti PowerBeam 5AC to inventory via Inventory → Actions → Return → Return 4) Equipment now shows Status: In Stock but also has kept Stock location: Customer Premises. Employee now has to manually change stock location via Inventory → Actions → Change Stock Location → Stock Location → Save Relevant to above: When using Action→ “Return” or Action → “Unlink from network site” to return an item to inventory stock, default state is "new" when returning, even if the item was previously marked “Used” at the existing deployed location (e.g. Customer Premises, Network Site Premises, etc). If an item is marked “Used”, it should be assumed, and default, to be “Used” upon return (it could still be manually marked otherwise if desired) "Please Insert Barcode" red text error on inventory MAC address is not always needed. Not every inventory-worthy item has a MAC address. When creating the product it should be a checkbox to enable or disable MAC address field, setting the default state of this toggle in the Config → Networking → Device Types section, just like “Create hardware with this item” appears in this section, but can still manually enable or disable the toggle when manually adding items. “Please Insert Barcode” error should only appear if MAC field is toggled on in the first place. When assigning a New item to a Network Site, Splynx does not automatically change the item from “New” to “Used”. Once equipment has been deployed into service, it should no longer be considered New and should automatically be marked Used (with the option to keep “New” if desired from the dropdown. Currently, the item remains marked New after deployment. Additionally, the New/Used mark cannot be edited while the item is deployed, so correcting it requires unlinking/returning the item to stock, changing the mark, and then deploying it again. Inventory table does not preserve the current page after an action or refresh. When working in Inventory → Items, with enough items to span multiple pages, Splynx always returns the user to page 1 after performing an action on an item. For example: if the user is on page 3 and edits, assigns, returns, or otherwise modifies an item, the table reloads on page 1 instead of returning to page 3. The same occurs when using the Splynx table's built-in Refresh button. This makes working through large inventories unnecessarily cumbersome. The current page, filters, sorting, and other table state should be preserved when refreshing the table or completing an item action.

TRL 1 day ago

1

👌UX improvements

Inventory Items: External / Third-Party Sale, Disposal, and Archive Status

It would be useful to have a way to mark inventory items as sold or otherwise disposed of without requiring them to be sold to a Splynx customer. Currently the Sell action requires selecting a customer and is clearly designed for subscriber sales. A common alternative lifecycle is: Purchased → In stock → Customer / Network site → Returned to stock → Sold externally For example, we may upgrade customers from older item such as PowerBeam 5AC, return those units to stock, and later sell excess used equipment through eBay or another third party. We still want to retain the item record, serial/MAC, purchase history, and movement history; but the equipment is no longer owned by us and should not remain In stock. The current workaround is to move it to a stock location such as Sold Externally / Disposed, but the status still remains In stock, and those items continue to affect dashboard statistics and inventory totals. It would be useful to have: - A native Sold externally / Disposed status that does not require a customer Or - Configurable terminal inventory statuses -An archive function for equipment that has permanently left company ownership - Archived/disposed items should remain searchable with full history, but be excluded by default from active inventory counts, dashboard statistics, and inventory totals unless an Include archived or similar filter is selected. - Optional disposition fields such as date, notes, sale channel, reference/order number, and sale amount would also be useful. The main goal is to retain historical records without creating fake customers, deleting equipment history, or having disposed equipment continue to appear as active inventory.

TRL 1 day ago

1

💡 Feature Request

Change ONU speed profile in Huawei Addon

Hi, It would be nice to have a button to change the speed profile in the Huawei addon section, instead of eliminating the ONU and reprovision it with another speed profile. For now, for each profile you can only assign 1 tariff. Let’s say you have 3 different tariffs with different prices for 300Mbps. We can only assign one tariff to this, so when we change this tariff to another tariff with another speed profile, Splynx will change this is in the OLT. However if we have another tariff of 300Mbps, i need to remove the ONU and provision it again, losing time with these actions. Best thing to do it assign various tariffs for just 1 speed profile, so when i change a tariff, the speed profile in Huawei will be adjusted also. The only problem i see if a customer has various services, how does splynx know which ONU to change? Regards. Paul

Paul Gerhardt 6 days ago

💡 Feature Request

Bulk invoice via whatsapp

Hi, Would it be possible to add a WhatsApp bulk messaging option under the Finance section in Splynx? Currently, we can send invoices and financial notifications to clients via email, SMS, and the client portal, but adding WhatsApp as an option would greatly improve customer communication and response rates. From an ISP perspective, many clients are far more responsive to WhatsApp messages compared to emails or SMS. This feature would allow us to: Send invoices to clients in bulk via WhatsApp. Send payment reminders and overdue invoice notifications more effectively. Send bulk suspension warnings before service termination. Improve collections by reaching clients through a communication channel they actively use. WhatsApp has become the primary communication platform for many customers, and having bulk WhatsApp messaging integrated into the Finance workflow would help ISPs recover outstanding payments faster and reduce manual follow-ups. This would be a valuable addition to the billing and customer communication tools already available in Splynx.

Jaco Potgieter 20 days ago

💡 Feature Request