Share your ideas with us

Titles should update with count of items in the section so you know it's updating and should be clicked on. 

Background On the Return Summary page, the Return Status section is commonly used to display shipping instructions that guide customers on how to return their items. As part of these instructions, customers are often required to include both their RMA ID and Order ID with the return shipment so that the warehouse and processing teams can identify and process the return correctly. Currently, the RMA ID is only displayed at the top of the page, and the Order ID is not prominently visible within the Return Status section. Requested Enhancement Add configurable fields within the Return Status section of the Return Summary page to display: * Order ID * RMA ID These fields should be displayed alongside the shipping instructions and return status details, making them easily accessible to customers while preparing and packaging their return shipment. We are open to any placement within the Return Summary page that provides clear visibility and easy access to these details. Business Use Case Our client specifically requested this enhancement because their return instructions ask customers to include the RMA ID and Order ID with the return package. Having these details displayed directly within the Return Status section would: * Improve visibility of important return information. * Reduce customer confusion when preparing returns. * Eliminate the need for customers to search for these details elsewhere on the page. * Help ensure return shipments contain the correct identification information. * Improve operational efficiency and reduce return processing delays. Expected Outcome Customers can quickly locate the required Order ID and RMA ID in the same section where they view their shipping instructions, resulting in a smoother and more user-friendly return experience. Thank you for considering this enhancement. We believe it would benefit merchants who require customers to include reference identifiers with returned packages and would improve the overall returns experience.

The background is that I sell my products on multiple marketplaces, and each has different return flows that the aftership Returns page cannot handle. It would be much easier if there is a Returns API that can meet my requirements below.   Need: - I need a Returns API to allow creating RMA/return requests without having to use the Returns Page to file it.  - I can call the API and pass the information regarding the Return Reason Resolution, etc in one go.  - Once I call this API, it will return creation in Pending or Auto-Approved Status.

Hi AfterShip Community, Context: I run a small Shopify store (~50 orders/month) using AfterShip’s free plan to track shipments (USPS, UPS). While the free plan offers basic tracking (Web:10), there’s no way to analyze tracking page performance (e.g., visitor clicks, engagement) without upgrading to premium plans, which can be costly for small businesses (Web:18). Issue: Small merchants lack access to basic analytics on the free plan to understand how customers interact with tracking pages, limiting optimization efforts. Outcome: I propose a lightweight analytics dashboard in the free plan, showing metrics like tracking page visits and click-through rates (e.g., to return portals). This would help optimize post-purchase experiences without needing a paid plan. Beneficiaries: Small e-commerce businesses, startups, and solo entrepreneurs using the free plan would gain insights to improve customer engagement and retention. What do you think? Any similar needs or suggestions to refine this idea?

Some customers enter +1 before their phone number when requesting a return or exchange. This causes the shipping label to fail to generate and creates frustration for the customer and extra work for me. I would like the system to correct the phone number to allow successful label generation.

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

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 great if we could allow the discount to carry over to the new order if a customer is just exchanging a size, at the moment our customer is choosing to refund rather then exchange sizing because they have to pay the difference between the original discounted price and the price. 

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.

Can we get an option to automatically restock the item based on resolution, not just when received. We still need to process, and inspect the item before we issue the refund, and we can't have our inventory adjusted upon recept. Thanks!