Forum Replies Created

Viewing 15 posts - 1 through 15 (of 2,044 total)
  • Author
    Posts
  • Nishit Shan
    Participant
    Post count: 2050
    in reply to: Mobile View #16827

    Hello Andrey,

    I don’t think there are any pending tasks remaining from the corrections. However, I have requested testing feedback and am currently waiting for it from your side.

    Nishit Shan
    Participant
    Post count: 2050
    in reply to: Mobile View #16825

    Hello Andrey,

    I have shared my points on discussion forum.

    Nishit Shan
    Participant
    Post count: 2050

    Hello NanoM,

    Have you developed the API for these events? If so, could you please share the API details along with the required and optional request parameters?

    I would like to test the API in Postman and verify that it works correctly for all the specified events before proceeding with the integration on the EN side.

    Nishit Shan
    Participant
    Post count: 2050
    in reply to: Mobile View #16821

    Hello Andrey,

    For #16818:Yes, the “Hide Product Prices” option will also work for newly created customer groups, as I have added the show/hide checkbox to the new group creation form as well.

    For #16820:Yes, I will ask them to share the API details and required request parameters so that I can test the API in Postman and get a clear understanding of the integration process before proceeding with the implementation.

    Nishit Shan
    Participant
    Post count: 2050

    Hello NanoM,

    On the 5 areas you listed, could you tell me whether those are the places in EN’s existing order flows where the events need to be sent from, or new functionality EN would need built?
    =>These are the points where your API will be integrated on the EN side and triggered when the corresponding events occur.

    For number.canceled, the event should go whenever a sale is undone and the number goes back to being Nano’s: a full cancellation, or a refund of that number’s line.
    =>When a number is cancelled or refunded, the event will be triggered accordingly. Sometimes this may apply to all numbers associated with a particular order, while in other cases, only a single number from the order may be refunded.

    A blank supplier is fine wherever EN doesn’t record one. For the status labels, a list of the labels EN uses is all I need, since the portal keeps the label as EN sends it.
    =>Okay, the order supplier will be EN for all orders.

    The IN prefix was illustrative. Please send the order ID the way it appears in EN’s admin, so Nano can look an order up from the event.
    =>I will send the order ID exactly as it appears in EN’s admin panel.

    Could EN send “guest-” followed by the order ID for those, for example guest-30186? That keeps every event complete and makes it clear the buyer wasn’t registered.
    =>I can share the order ID prefixed with guest- for guest orders, for example, guest-30186.

    Nishit Shan
    Participant
    Post count: 2050
    in reply to: Mobile View #16816

    Hello Andrey,

    As discussed, i have added an option on the admin side to show or hide product prices for each customer group. This option is available when adding or editing a customer group.

    When the **Hide Product Prices** checkbox is enabled, all product prices will be hidden throughout the front end for customers belonging to that group. When the checkbox is unchecked, product prices will be visible again.

    Please check the video below for reference:
    [video src="https://excellentnumbers.com/temp_vid/Screencast%20from%202026-11-16%2011-53-53.mp4" /]

    Nishit Shan
    Participant
    Post count: 2050
    in reply to: Mobile View #16815

    Hello Andrey,

    I think the last message was intended for their internal team, not for us. They are still clarifying their points among themselves. Once everything is clear, we can proceed according to their requirements.
    For now, I don’t think we need to respond.

    Nishit Shan
    Participant
    Post count: 2050
    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 3 days, 4 hours ago by Nishit Shan.
    • This reply was modified 3 days, 4 hours ago by Nishit Shan.
    Nishit Shan
    Participant
    Post count: 2050

    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
    Participant
    Post count: 2050
    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
    Participant
    Post count: 2050

    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
    Participant
    Post count: 2050
    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
    Participant
    Post count: 2050

    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
    Participant
    Post count: 2050
    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
    Participant
    Post count: 2050
    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.

Viewing 15 posts - 1 through 15 (of 2,044 total)