-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ops - Track MAC address, quality and Serial Number of certain devices we stock locally #260
Comments
@danry25 can you provide a copy of this spreadsheet? |
To recap @uncheckederror and my conversation, each product item should have a TeleDynamics order ID and a tracking # field. |
These fields are now live. |
Everything on this issue is complete except what is listed below, closing this issue now. Additionally, when a TeleDynamics order ships they provide us the Serial Number and MAC address of the device along with a tracking number. It would be great to track this data and use it in issue #281 and inform the customer of the shipping status. |
How will this improve revenue or reduce our costs? Please provide a complete explanation!
This will enable easier loading of devices into gdms.cloud, dm.yealink.com and enable tighter inventory management and higher inventory churn.
Is your feature request related to a problem? Please describe.
We have all these phones in stock and we need to use their serial number and MAC to properly manage them in both FusionPBX and the vendor's device management system. When reselling imperfect devices, tracking the quality of the device would also be useful.
Additionally, when a TeleDynamics order ships they provide us the Serial Number and MAC address of the device along with a tracking number. It would be great to track this data.
Describe the solution you'd like
Add this data to our inventory page
Describe alternatives you've considered
Tracking on an out of band spreadsheet is what is currently done, though it gets out of sync and requires manual loading into Yealink and Grandstream's device management systems
The text was updated successfully, but these errors were encountered: