Share your ideas with us

I have had customers who have accidently unsubscribed themselves from receiving AfterShip emails. I can see them in the Unsubscribe list, but I cannot remove them. Please add a feature that would allow AfterShip administrators to remove emails from the Unsubscribe list. Currently this process has to be done by the AfterShip tech team. By making this a self-service feature, you will reduce the labor required by the AfterShip team and make the product more efficient.

It would be great if you could automate sending out the shipment tracking dashboard, and allow filters for that report, lijke the analysis report.  This enbales us to send the report to customers and others in our team as a live snapshot of their shipments. It consolidates all their shipments into one view so they don't have to track them individually each day. 

Would like to be able to display any discount received, from the orginal order, on the product selection page in the warranty portal. If possible, the discount code that was used as well. Important: Discount amount and discount code should show in the AfterShip admin portal.  

Most major carriers already provide an estimated delivery date/time as part of their tracking data, but this isn't currently surfaced in the app. Context: Customers tracking a shipment want to know when it will arrive, not just its current status. Right now they have to infer this themselves or check the carrier's own site separately. Issue to address: Add a field that displays the carrier's estimated delivery date (and time window, where the carrier provides one) on the tracking/order page. This would reduce "where is my order" support inquiries and improve the post-purchase experience. Suggestion: Pull the estimated delivery data from carriers that already expose it via their APIs, and display it prominently near the shipment status.

Goal: To make it easier for customers to accurately select the correct item for return when using the return portal. Preconditions: The customer has placed an order containing multiple items, some of which may have similar or identical titles, colors, or sizes. The SKU numbers for the items exist in the system but are not currently displayed in the return portal. Trigger: The customer initiates a return and accesses the return portal to select the item(s) they wish to return. Basic Flow: The customer logs into the return portal. The portal displays the items from their order, including details such as title, color, size, and now the SKU number for each item. The customer uses the SKU number to cross-reference their order confirmation or invoice, ensuring they select the correct item for return. The customer completes the return process with confidence that the correct item has been selected. Postconditions: The customer successfully returns the correct item without confusion. The support team receives fewer inquiries about mismatched returns. Benefits: For Customers: Improved user experience by reducing confusion when selecting items for return. Greater confidence in completing returns independently. For the Business: Reduced customer support requests related to returns. Increased efficiency in processing returns, minimizing errors caused by incorrect item selection. Priority: Medium – This enhancement has a high potential to improve customer satisfaction with a relatively low implementation effort. Technical Requirements: Modify the front-end display of the return portal to include SKU numbers as part of the product details. Ensure the SKU numbers are fetched and displayed consistently across all customer orders. This use case focuses on enhancing the clarity of the return process for customers while streamlining operational efficiency for the business.

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.

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. 

Like to set their own “Image not found” image for Products in the Returns Portal. That way, If a Product is not sent to AfterShip with an Image URL, they have an image that looks more branded.   Today, when an item does have an img url, the Return Portal defaults to the missing image icon.   Request - have a function within Return Portal where if any items on my return portal dont have an image URL, it can set to a image that I select instead of defaulting to the standard broken/no image icon.

I hope to insert a form in the email, allowing customers to fill out the form directly within the email.   For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.

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.