Share your ideas with us

So, as a seller who often runs campaigns, I would love to have a cool discount setup that can be customized based on how customers behave.   For example, I could keep discounts hidden for shoppers with shopping carts over $1,000 but display them for those who have smaller carts, so that they would shop more to get a better discount.   This strategy can be effectively applied to our product recommendations, enhancing conversion rates and boosting average order values.

Add the ability to upload a separate images for desktop and mobile header logos. An example of the what the UI could like like is below. Returns > Customizations > Returns page    

For the tracking page I am currently using, it would be great to have the Delivery Instructions feature, so that my customers can provide specific instructions to carriers, and ensure successful deliveries.   This feature will also be valuable for drivers who can have all the necessary information at their fingertips, even for dispatchers who can manage delivery more effectively with all that info.   A seamless last-mile delivery experience can create a sense of reliability and convenience that fosters long-term customer relationships and encourages repeat purchases for my brand.

In Shopify, merchants cannot identify which orders were combined in TTS. This will increase the risk of merchants repeatedly fulfil the same order items.   To address this issue proactively, I would recommend that we introduce a hint or tag within Shopify to alert merchants about combined orders, thus avoid this situation from happening.

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!

It would be very helpful if customers could select their preferred size during the exchange process, with real-time visibility of stock availability on the website. For example, when a customer initiates an exchange, the system should show whether the requested size is currently in stock. If the size is unavailable, it should display “Sold Out” instead of allowing the exchange to proceed. This feature would prevent unnecessary back-and-forth communication, improve customer experience, and reduce manual handling for merchants. Platforms like Revolve already offer this type of functionality, and it would be an excellent addition to AfterShip Returns.

 I just started using the app today and overall I do like it, but I have a few minor suggestions. 1. A compact mode: right now the list of tracking numbers/packages is very spread out. Consolidating it would make it look cleaner, IMO. 2. Allow me to put tags on them, custom or otherwise. For example I have a few incoming packages and a few outgoing ones. It would be nice to add tags to differentiate them and also filter by them if needed. Hopefully that made sense. Thank you.

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

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.

When a warranty is approved, you can choose to include an label. In the “Warranty claim approved” email, there is no ability to account for this decision. We would need to add an ability to have wording around a label being included as well as a label not being included. Below is an example email we have now.   Two ways this could be addressed: 1. Split this notification into 2 notifications: “Warranty claim approved - with label” and “Warranty claim approved - no label”. 2. Add Flows to Warranties with Split functionality for generated labels.