Share your ideas with us

Suggestion: Add Lazada Express (LEX MY / LEL) Support for Malaysia   Hi,   I would like to suggest adding Lazada Express (LEX MY / LEL) as a supported courier/carrier on your app and website.   Lazada Express is the official delivery courier used by Lazada in Malaysia, similar to how SPX Express / Shopee Express is the official courier for Shopee. Many Lazada shipments in Malaysia are handled by LEX, so having direct tracking support would be very useful for Malaysian users.   The official LEX Malaysia tracking website is: https://lex.com.my/   For testing purposes, you can use these example tracking numbers:   LXST191548638MY MYMPA257159996   I hope you can consider implementing Lazada Express (LEX MY / LEL) support soon. As Lazada is widely used in Malaysia, I believe many users would appreciate being able to add and track their LEX shipments directly through your app and website instead of having to visit the LEX website separately.   Thank you for considering this suggestion. I hope LEX MY support can be added in a future update!

Currently OTD report, reports the complete journey so the avereage time can fluctuate based on how long it takes for customers to collect their order.  We need to report on the carrier performance and then the time it takes to collect.  It would be good to have  a PUDO report that breaks down : average transit time to collection point   Average time waiting for collection    If we expand our PUDO options in Europe it would be a good indication 

I hope to insert a form in the email, allowing customers to fill out the form directly within the email.   For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.

My package is currently reading that it is out for delivery in my area, but is still showing to be located in a totally different country so the tracking needs to be updated and fixed because this has been an ongoing issue that I've contacted them about for support and it's still reading the same way

Currently, AfterShip's webhook outgoing IP list is only available on an HTML documentation page (https://www.aftership.com/docs/tracking/webhook/webhook-outgoing-ips). This makes it impossible to automate IP allowlist management in infrastructure-as-code (IaC) workflows.   Problem: Teams that use IP-based firewalls to secure their webhook endpoints must manually monitor the documentation page for any IP changes and update their firewall rules accordingly. If a change is missed, it can cause webhook delivery failures and broken integrations.   Request: Please publish the webhook outgoing IP list as a dedicated plain-text endpoint — similar to how Cloudflare publishes theirs at https://www.cloudflare.com/ips-v4 — where each IP is returned on a separate line.   This would allow teams to: * Fetch the IP list programmatically as part of their CI/CD or IaC pipelines * Keep firewall allowlists automatically in sync without manual intervention * Avoid service disruptions caused by missed IP changes This is a standard practice among major API providers and would significantly improve the developer experience for customers who manage network security programmatically.

I am the owner of a fashion company preparing to expand my business operations in the US. I have been utilizing Aftership EDD for some time now and I'm interested in learning how to configure my EDDs to accommodate multiple locations.   Specifically, I have two separate locations in Australia and the US where identical SKUs are stocked. In cases where a particular SKU is out of stock at the US location, I would like orders to be fulfilled using available stock from the AU location as a fallback option. I am seeking guidance on integrating this specific logic into my EDD settings.

Would be a great feature if there was a link to the returns status page within the returns dashboard.   And if this link can be easily copied so we can share to the end consumer if they call through the contact center/help, then our agents can quickly copy the link and then email/share to the end consumer

Image 1 — Shipment Selection & Pin Icon Behavior (pictures attached) When selecting shipments, the Pin icon should remain clean, clear, and fully visible when up to three shipments are selected. Once the user selects more than three shipments, the Pin icon should become visually disabled—either blurred, faded, or hidden—to clearly communicate that the action is unavailable. Please also indicate where the attached reference image should appear in relation to the Pin icon so that its placement and visual hierarchy are clear.   Image 2 — Pin Option Within the Shipment Menu (pictures attached) When the user opens any shipment and clicks the three-dot (⋮) menu, the following options should be displayed: 1:- Edit Shipment 2:- Mark as Delivered 3:- Pin at Top 4:- Delete The Pin at Top option should be presented as a polished, intuitive action within the existing menu, maintaining a premium and consistent user experience.   Thanks and Regards

The vendor/supplier's email should be copied when sending any type of response to the customer regarding a return.  This includes the RMA confirmation of return, tracking label and when it is received, refunded and resolved.   We/supplier are getting chargebacks through Shopify from customers stating that their returns are not refunded in a timely manner and we have no way to get the email to show that it was processed in Aftership and to dispute a chargeback with shopify.   We have no copies sent to us.   Please fix this issue in Aftership/Shopify immediately.  Thank you. 

Currently it's possible to view returns analytics only per 1 store at a time. It would be great to be able to select multiple stores and have a consolidated view on returns.