Share your ideas with us

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

Filter ideas

Add Placeholder

Luis Mateo
June 20, 2026 at 3:11 am
it would be great to be able to manually add a placeholder delivery in order to keep track of my deliveries.
Submitted
0
0

Tags to alert merchants about combined orders.

Caleb Patel
July 19, 2024 at 10:48 am
In Shopify, merchants cannot identify which orders were combined in TTS. This will increase the risk of merchants repeatedly fulfil the same order items.   To address this issue proactively, I would recommend that we introduce a hint or tag within Shopify to alert merchants about combined orders, thus avoid this situation from happening.
Submitted
0
0

Hide ad carousel

Stephen Shepherd
September 22, 2026 at 1:30 am
Please let me hide the ad carousel, I am happy to pay subscription or whatever to disable it. Thanks 
Accepted
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

Highlight which module/box is selected during RMA Request Flow

Jason Ma
January 31, 2025 at 7:01 pm
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. 
Submitted
0
0

Eliminate Additional Fees for Carrier Integration – Improve Aftership for All Users

Mario Labault
March 3, 2025 at 10:20 pm
As a loyal Aftership customer, I am extremely disappointed to learn that integrating a new carrier requires an additional fee—a neither transparent nor customer-friendly policy. Carrier expansion should be a standard improvement to Aftership’s platform, not an extra cost passed onto paying customers. Why This Needs to Change: Improving Aftership Should Be Your Priority, Not an Upsell Adding new carriers benefits all Aftership users. Expanding carrier integrations should be part of Aftership’s ongoing development efforts, not a hidden fee imposed on individual customers. Hidden Costs Undermine Customer Trust Nowhere in Aftership’s pricing model is it clearly stated that carrier integration comes with additional fees. This lack of transparency frustrates users and creates an unexpected financial burden. Loyal Customers Deserve Better Customers who have trusted Aftership for their business operations should not have to pay extra to access a fundamental feature like carrier support. Proposed Solution: Aftership should eliminate extra fees for new carrier integrations and invest in expanding its platform instead of charging individual users. This would be part of its commitment to improving service for all customers. Clear, upfront disclosure of costs should be required if Aftership maintains this fee structure. If Aftership truly values its customers, this change must ensure a fair, transparent, and customer-centric experience.
Submitted
0
0

Searchable Idea Portal

Andrew Bird
August 15, 2025 at 12:43 pm
Seems like a basic thing, but when I have an enhancement I'd like to submit, I want to ensure I don't duplicate someone else's submission.  Obviously that's why there is an 'upvote' button.  The only way to determine if there is something worth upvoting is to scroll through the entire list from top to bottom.
Delivered
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

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

Export using screen layout

mlee
October 2, 2024 at 6:46 pm
When exporting, it would be handy if there was a third Data Format option.  In addition to Standard and Custom, something like “Same as current display” or something like that.  An option that would create the csv or xlsx file with the same columns in the same order that are displayed in the current view on the web page. I find myself adding or removing columns in the dashboard in order to see what I want to look at but, if I want to then export it, I need to either recreate the view again in the export wizard (which isn’t always even possible) or export it standard and move stuff around in excel. 
Submitted
0
0