Share your ideas with us

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.

Is it possible to increase the bulk search limit from 50? We often have to peform bulk search a number of times to retrieve the data that we're looking. 

Currently when searching anything in Aftership, you must start with the same exact string. It would be great for users to adapt it to simple match. Example: Currently: String 1ZW6522Y0299621269 is not found if you look by 2Y0299621269

Hello,  We currently use AfterShip Feed to connect our Amazon Seller account to TikTok Shop. But it would be fantastic to be able to also connect with Walmart Seller's MCF. It would allow even greater reach of products on more sales channels.

I want all orders over $30 to show a shipping fee of only $2, because this is subsidized by TikTok.

Expose an REST API for creating Warranty Claims.

I'd like to log an enhancement request for the Tracking page editor. Currently the section where we add social media connectors is limited in connection options. Specifically for Instagram (which is a really cool feature) the only way to connect is using our own credentials (user name/password login). This is an unacceptable option as it exposes us to being hacked and is a security concern obviously. The better way to do this is via Instagram's API connection: https://developers.facebook.com/docs/instagram-platform. Can you please log that as a high priority enhancement request? Should we decided to stay with AfterShip, this will be a critical branding requirement.

I have loved your app from the start. And improvements made along the way have been spot on. But now you lost me in both content and execution.    First, you put in ads. One of things I loved was no ads. But, hey, that revenues hard to pass up forever, especially after you've built your user base.   Second, I could have dealt with the ads if you had placed in a footer bar. But when you place the ads as large blocks right in the middle of the data, you lost me.   I was a developer for over 30 years on several different platforms. I must say that decision alone makes my top 20 of bad UI choices.   So, I will be unloading your app in favor of one that has no ads and all the functionality I need. It is a shame, because you do beat them out in feature, although not too much.   If you would at least move them to the footer then I would most likely return

Items + return reasons are not clearly highlighted/shown as selected, during the Return Request flow on the RC portal.    Request: During the return flow more clearly define that an item/return resolution is selected. i.e. have text say “Selected” or have the box change colour when an item/resolution is selected beyond just the black box. 

Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.