Share your ideas with us

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

Filter ideas

Claude integration

Janis Tello
October 9, 2026 at 10:06 pm
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.
Delivered
0
0

Api endpoint to fetch the review data

Nayan Solanki
July 21, 2026 at 12:33 pm
I see that Aftership is already having public api end points available for tracking and returns. i would like to have similar one for reviews.
Submitted
0
0

Saving Clients

Scott Williams
August 20, 2026 at 6:51 pm
We use this to ship to clients it would be nice if we could save clients within the system to send notifications to. 
Submitted
0
0

Need fast access for copying customer information (Look at Shopify as an example)

Andrew Trousdale
November 19, 2024 at 7:16 pm
If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image:
Submitted
0
0

SMS opt in at customer level

Isabella Davis
February 13, 2024 at 5:34 pm
As a retailer, it would be great if customer preferences can be collected and determine whether to send an SMS notification based on the subscription status synchronized via API.   Moreover, a customer-facing page that allows users to manage their preferences would be even better. We would love to communicate more with our shoppers, which will efficiently improve our customer satisfaction and brand reputation.
Submitted
0
0

Email address update button

Juan Lopez
December 3, 2024 at 2:49 pm
We should be able to update the email address on the returns and warranty pages in case the cx is unable to access the default email.
Submitted
0
0

need readable email notice for refund pending resolved return

Ash Ash.Com
April 29, 2026 at 10:22 pm
The vendor/supplier's email should be copied when sending any type of response to the customer regarding a return.  This includes the RMA confirmation of return, tracking label and when it is received, refunded and resolved.   We/supplier are getting chargebacks through Shopify from customers stating that their returns are not refunded in a timely manner and we have no way to get the email to show that it was processed in Aftership and to dispute a chargeback with shopify.   We have no copies sent to us.   Please fix this issue in Aftership/Shopify immediately.  Thank you. 
Planned
0
0

Required custom fields on the returns page (e.g. serial number)

Jamie Wright
October 7, 2026 at 2:28 pm
The problem: We can't process a return without the item's serial number, and many merchants selling electronics, equipment or warranty-backed products are in the same position. The only option today is to make comments required on every return reason. Customers can type anything to get past it, so our team still has to chase missing or wrong serial numbers by hand, which slows down refunds for everyone. The request: Let merchants add custom fields for each item on the returns page, with: The option to make a field required before the return can be submitted Why it matters: Correct information at the point of submission means fewer bad returns, less admin, quicker refunds and happier customers. It also makes AfterShip Returns a better fit for any brand that tracks returns by serial number, IMEI or batch code.
Submitted
0
0

access to Orders in the AfterShip MCP connector (Claude)

Audrey Tomba
November 3, 2026 at 12:59 pm
Hello AfterShip team, We use the AfterShip Post-Purchase connector in Claude to automate our daily delivery follow-up, and it works very well for shipments. However, the connector currently only exposes shipments (trackings) and returns. Orders without a tracking number are not accessible, although they are visible in the AfterShip admin under Tracking > Orders. Our use case: every morning we want to detect orders that are still "Unfulfilled" (or "Partially fulfilled") more than 2 business days after the order date, and that have no tracking yet, so we can follow up with our suppliers. Could you add the following to the MCP connector? 1. A list_orders tool with filters on fulfillment status (unfulfilled, partially fulfilled), order status (open / canceled), order date (placed_at) and order number. 2. For each order: fulfillments with their trackings (to know whether a tracking exists), line items, customer, tags and order notes. 3. Access to the internal comments added on an order (the "Comments" section of the order page), so we can exclude orders already handled by our team. 4. If possible, order-level custom fields (e.g. our "isBackorder" flag, which today only exists on shipments). Is this on your roadmap? In the meantime, is there another supported way (API endpoint, scheduled export or webhook) to get this list of unfulfilled orders automatically? Thank you for your help.
Accepted
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