[Nishit Shan]

in reply to: Mobile View #16807

Hello Andrey,

I have shared my observations on the discussion forum.

Based on my initial review, the integration will take at least 8–10 days to complete.
To achieve what the NanoTelecom team is requesting, I will need to work on the following areas:

1. Order Creation Flow (Frontend): Implementing the order creation process on the frontend.
2. Admin Orders: Handling and managing orders from the admin panel.
3. Custom Telecom Orders (API): Integrating the custom telecom order functionality through the API.
4. Port-Out Statuses: Handling and synchronizing different port-out statuses.
5. Refunds: Implementing refund handling. A return should be able to mark an individual order line as refunded without changing the overall order status. The full-order cancellation/refund process will be handled separately.

I am still reviewing the integration requirements to identify the complete scope. However, based on my current findings, these are the major areas that need to be addressed.

• This reply was modified 13 hours, 44 minutes ago by Nishit Shan.
• This reply was modified 13 hours, 43 minutes ago by Nishit Shan.

[Nishit Shan]

in reply to: NanoTelecom Imrpovment Ideas #16806

Hello NanoM

Thanks for the detailed specification. We’ve reviewed EN’s storefront, admin, API-related telecom order flows, number status handling, customer and service records, and cancellation/refund paths. The integration is feasible, and the receiving side can remain as you described.

EN has a stable internal customer ID for registered buyers. Guest orders may have no registered customer ID, so we’ll need to agree on the customer_id value for those events. EN stores numeric order IDs; please confirm whether the IN prefix in your example is required or illustrative.

Supplier information is available in some telecom inventory/provider flows, though we’re confirming whether it is recorded for every sold number. Where EN has no supplier value, we can send it blank as specified. We’ll also confirm the exact number-status labels and which refund/cancellation cases should produce number.canceled.

[Nishit Shan]

in reply to: Mobile View #16803

Hello Andrey,

The price visibility settings on the EN admin side will be a new task and will require additional development work. I can start working on it if you approve, but I would expect an additional budget allocation for this task.

Meanwhile, I am reviewing the EN website to understand the requirements and identify the appropriate integration point for the webhook API URL.

[Nishit Shan]

in reply to: NanoTelecom Imrpovment Ideas #16802

Hello Andrey,

Please give me a little time to review the project for this scope of integration. Once I have completed my review, I will provide a clear and concrete response to NanoM.

[Nishit Shan]

in reply to: Mobile View #16799

Hello Andrey,

The prices on Excellent Numbers should be visable for the following groups:
New Customers – Do NOT allow to see the prices.
Approved Customers – allowed
Resellers – Allowed
Banned Group – NOT allowed
Wholesale customers – Allowed

Regarding your requirement for price visibility on ExcellentNumbers:
There is currently no specific rule in the code to control price visibility based on customer groups. Also, I don’t think this can be handled reliably through frontend changes alone.
All these customer groups are created and managed by the admin, and they can also be deleted or recreated. If I manually use the group IDs to control price visibility, those IDs may change in the future when the admin modifies the groups. This would make the implementation unreliable.
However, we can implement this properly by adding an option in the admin panel to allow or restrict price visibility for each customer group. The selected settings will then be applied automatically on the frontend.
Currently, no such group-based price visibility rules are configured. Only some manual restrictions are in place for the Banned Group, preventing its members from purchasing products.
So, I recommend implementing this as an admin-controlled setting rather than hardcoding group IDs or applying manual frontend conditions.

Regarding post #16785:
Point 3:Could you please share a reference image to help me understand the expected design?
All the other tasks mentioned in #16785 have been completed from my side. I have also completed all the tasks related to the mobile view.
Please review and test the changes and share your feedback so I can address any remaining issues within the agreed scope and then move on to the next task.

[Nishit Shan]

in reply to: NanoTelecom Imrpovment Ideas #16796

Hello NanoM

Could you please explain your request in detail, specifically what you actually want from ExcellentNumbers (EN)?
We can create a webhook API on the NanoTelecom side and integrate it with EN so that whenever a new entry is created in EN, the same entry is automatically synced to NanoTelecom.

Please clarify the expected workflow and the type of data you want to sync so we can implement it accordingly.

[Nishit Shan]

in reply to: Mobile View #16794

Hello Andrey,

I am unable to post messages in the discussion forum. I keep seeing the same error message even after logging in.
Please check the issue and fix it.
Reference: https://ibb.co/RJKt0d0

[Nishit Shan]

in reply to: Mobile View #16788

Hello Andrey,

India will be observing Diwali holidays on Monday and Tuesday, so I will be unavailable on both days.

I am trying to complete the maximum remaining points you mentioned and will share an update by the end of today so that you can test during these holidays.

[Nishit Shan]

in reply to: Mobile View #16786

Hello Andrey,

I have noted your points and will check them.
Please also check the Promotion section on the Advanced Search page.

[Nishit Shan]

in reply to: Mobile View #16773

Hello Andrey,

Can you please explain the “Pin Numbes Increase” task , I am confuse about it .

[Nishit Shan]

in reply to: Customer api management console #16772

for reference , see i am getting this screen even after login: https://ibb.co/Ljtdzkn

[Nishit Shan]

in reply to: Customer api management console #16771

Hello Andrey,

Please check the following video for reference:
[video src="https://excellentnumbers.com/temp_vid/Screencast%20from%202026-11-04%2012-27-36.mp4" /]

I have changed the setting from **”Designed for Business Use”** to **”Personal or Business Use.”**

Regarding the reCAPTCHA API key, if you remember, you previously shared the SEO ExcellentNumbers email account details with me. I noticed that the account was still logged in, so I used the same account to create the reCAPTCHA API key.

Most Important: I am unable to access the Topic Forum in the mobile view. The page keeps asking me to log in, even though I am already logged in. When I try logging in again from that page, it still redirects me to the same login prompt.Could you please check and fix this issue?

[Nishit Shan]

in reply to: Mobile View #16767

Hello Andrey,

Thank you for the deposit!
I have integrated Google reCAPTCHA into the registration and Contact Us forms to prevent spam submissions.
I have also made the “My Numbers” page responsive, and you can now test it.
I am still working on the remaining points and have yet to test the Contact Us page. I will update you once everything is ready for testing.

[Nishit Shan]

in reply to: Mobile View #16752

Please find #post-16751

[Nishit Shan]

in reply to: Mobile View #16749

Hello Andrey,

Thank you for adding the new task.

I have reviewed the task, but the budget you assigned is not sufficient to cover the required work. My accounts team has suggested a budget of NZD 350 for this task.
I also recommend adding CAPTCHA to the Contact Us page to protect it against spam submissions.

Please let me know , so i can proceed for the task .

[Author]

Posts