Share your ideas with us

Honestly, this would help us to ease our shoppers through possible delays proactively.

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    

 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.

Instead of directly integrating Aftership with Gmail, I would like to send my emails with package information to an aftership email address associated with my account, for aftership to parse and automatically show tracking information. 

Hello, We would like to identify the parcels that were delivered by secured delivery methods, and which ones. For example, was the parcel delivered with a Pin Code? With a QR Code? With a signature? This would allow to better measure Exceptions per delivery method, and size the opportunity of such services, on which we are completely blind today.

Aftership agent is powerful and will be more in the future. In that future, MCP protocol connection is a must. It's a game changer! So customers (us) can connect their agents with Aftership.

We would love to be able to see the return comment information our customers provide when returning items within the return reports we download. Our customers are using the comment box to describe the return reason in depth but this information is lost when it comes to dowloading the return reports.

Title: Feature request: Claude MCP connector for AfterShip Returns AfterShip Returns should offer an official Claude MCP connector. Claude already connects to Shopify, Gmail, Slack, and Google Drive, so many merchants run their daily operations through it. Returns data is the missing piece. Without a connector, teams still have to open the portal, find the return, and copy details into customer replies or reports by hand. A connector would make it possible to ask questions like: “What’s the status of the return on order #1234?” “Which returns from last week haven’t been refunded yet?” “What are the top return reasons this month?” “Which SKUs have the highest return rate?” Why it should be added: Faster customer service. “Where’s my refund?” emails could be answered in seconds using live return data. Fewer errors. Order numbers, tracking, and refund amounts would come straight from AfterShip instead of being copied manually. More accessible reporting. Small teams without a dedicated analyst could get insight from return data in plain language. A connected workflow. Returns would link up with the order, email, and team tools merchants already use with Claude. Keeps AfterShip central. As more operations move through AI assistants, the platforms that connect to them become the ones merchants depend on. Read-only access would be a strong starting point: return lookups, statuses, reasons, and refund/exchange outcomes. Actions like approving or rejecting requests could follow later, with confirmation steps built in.

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

Enable merchants to customize the duration before an RMA is automatically canceled. Currently, the system only allows for auto-cancellation after 28 days of inactivity. To better suit our company's needs, we would like the option to extend this period.