Share your ideas with us

We value your insights on AfterShip products and features. Let's innovate together!

Filter ideas

Enhance exchange process for tax reporting reconciliation purpose

Alexander Cook
April 3, 2024 at 10:25 pm
As a business owner, having precise accounting records is essential for tax purposes. It's particularly important to account for returns correctly by adjusting for them and deducting the relevant taxes to prevent overpayment.   I've observed that Shopify currently only accommodates refunds, lacking store credit or exchange options for returns. Therefore, if aftership Return could support all three options and assist in reconciling taxes and producing accurate tax reports for returns, it would greatly benefit our operations.
Delivered
0
0

Multiple Tracking Numbers - Comma Separated

Oliver Mortimer
October 25, 2024 at 12:22 pm
When I receive tracking from suppliers, I add manually to AfterShip.  Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.   When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.   Below example for tracking number 123456789 and 987654321  
Submitted
0
0

Eliminate Additional Fees for Carrier Integration – Improve Aftership for All Users

Mario Labault
March 3, 2025 at 10:20 pm
As a loyal Aftership customer, I am extremely disappointed to learn that integrating a new carrier requires an additional fee—a neither transparent nor customer-friendly policy. Carrier expansion should be a standard improvement to Aftership’s platform, not an extra cost passed onto paying customers. Why This Needs to Change: Improving Aftership Should Be Your Priority, Not an Upsell Adding new carriers benefits all Aftership users. Expanding carrier integrations should be part of Aftership’s ongoing development efforts, not a hidden fee imposed on individual customers. Hidden Costs Undermine Customer Trust Nowhere in Aftership’s pricing model is it clearly stated that carrier integration comes with additional fees. This lack of transparency frustrates users and creates an unexpected financial burden. Loyal Customers Deserve Better Customers who have trusted Aftership for their business operations should not have to pay extra to access a fundamental feature like carrier support. Proposed Solution: Aftership should eliminate extra fees for new carrier integrations and invest in expanding its platform instead of charging individual users. This would be part of its commitment to improving service for all customers. Clear, upfront disclosure of costs should be required if Aftership maintains this fee structure. If Aftership truly values its customers, this change must ensure a fair, transparent, and customer-centric experience.
Submitted
0
0

Perhaps AI can help me select videos to showcase?

Ella Green
July 1, 2024 at 9:30 pm
The same videos are displayed to shoppers on my collection page or recommendation widgets. I want greater exposure to alternative products and videos, but selecting which ones to display and updating them regularly feels overwhelming.   Furthermore, testing to determine which video garners the most traffic is even more challenging. I have no idea if my efforts will result in sales. If only there is a tool could help!
Submitted
0
0

Please alliw swipe back

Robert T. Edmiston
August 3, 2026 at 2:09 pm
Could you please make a slight programming change, could you please allow swipping back to the main list of packages once you looked at a package info    iOs
Submitted
0
0

Add ability to block a return and direct customer to warranties

Jeremy Bobbitt
February 3, 2025 at 8:18 pm
Add the ability to block a return and direct the customer to the warranty portal. Bonus if you could log the customer in and auto fill information.   Potential Mockup Potential User Experience
Submitted
0
0

API for SMS

Zoltan Rab
September 15, 2026 at 4:10 pm
I would find it very useful if I could pull the SMS communication metadata using an API. Currently it is only available as a download from the portal which makes automation impossible.
Submitted
0
0

Suggestion: Add Lazada Express (LEX MY / LEL) Support for Malaysia.

Julia Blame
August 8, 2026 at 9:21 am
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!
Submitted
0
0

Enable Hazmat label selecting when creating return label

Little V
March 21, 2025 at 5:50 am
we provide return shipping label after approving the return request. Our product contains hazarious material, which should be shipped with hazmat label. Aftership doesn't grant the api access of selecting the Hazmat label when auto-generating return shipping label Please fix it
Delivered
0
0

Publish Webhook Outgoing IPs as a Machine-Readable Plain-Text Endpoint

Martinho Dias
June 3, 2026 at 7:47 pm
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.
Delivered
0
0