Share your ideas with us

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

Filter ideas

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

ACI EXPRESS

Salil Gupte
March 22, 2026 at 12:50 pm
Please add the shipping company ACI EXPRESS, which is based in South Korea. They have partnerships with multiple overseas shipping companies, and a lot of merchandise is being shipped through ACI Express to the USA and the Middle East, especially after the implementation of tariffs in the USA.
Submitted
0
0

Provide an option for the customers to edit the post shipment review in the AfterShip tracking

Jason Ma
March 10, 2025 at 3:22 pm
Requesting to provide an option for the end consumers to edit the review on the AfterShip tracking page after the product is being delivered.    Currently, the customers are able to leave the review but unable to edit them. 
Planned
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

"Back Button" on RC Portal is not clear or prominent enough

Jason Ma
January 31, 2025 at 6:49 pm
The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page. 
Submitted
0
0

Shipments Header

Jana Churich
October 25, 2024 at 4:12 pm
Titles should update with count of items in the section so you know it's updating and should be clicked on. 
Submitted
0
0

Support "not-for-sale products" listing

Henry Baker
June 15, 2024 at 10:47 am
That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.
Accepted
0
0

Add SKU numbers in the return portal

Rowan Valentin
January 28, 2025 at 2:24 pm
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.
Submitted
0
0

Update indicator dot color

Visitor
August 3, 2026 at 11:52 am
Change the update indicator Dot from the light blue color to the orange color you already use in your iOS app. It is hard to pick out the dot if you have a long list of shipments. If it was the orange color you already use in the app it should be a simple change to make for an updated version. Also so carriers on the list of carriers to pick from are now asking for receiving zip, so those carriers never update now.  Thanks
Submitted
0
0

Missing pin feature

Nishant Dhiman
August 14, 2026 at 4:43 am
Image 1 — Shipment Selection & Pin Icon Behavior (pictures attached) When selecting shipments, the Pin icon should remain clean, clear, and fully visible when up to three shipments are selected. Once the user selects more than three shipments, the Pin icon should become visually disabled—either blurred, faded, or hidden—to clearly communicate that the action is unavailable. Please also indicate where the attached reference image should appear in relation to the Pin icon so that its placement and visual hierarchy are clear.   Image 2 — Pin Option Within the Shipment Menu (pictures attached) When the user opens any shipment and clicks the three-dot (⋮) menu, the following options should be displayed: 1:- Edit Shipment 2:- Mark as Delivered 3:- Pin at Top 4:- Delete The Pin at Top option should be presented as a polished, intuitive action within the existing menu, maintaining a premium and consistent user experience.   Thanks and Regards
Submitted
0
0