Share your ideas with us

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. 

Support setting the total number of emails that can be sent by each contact within a certain period of time (frequency), including flows and newsletters.   I aim to reduce interruptions for my customers while still capturing important messages, which is why I am seeking more flexibility in the configurations.

Hi, The data when the shipment is created at the carrier is important for shipment analysis. Example:  Info received   Shipment information received DHL Express Mar 25, 2025 at 12:01 pm

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.

When I receive tracking from suppliers, I add manually to AfterShip.  Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.   When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.   Below example for tracking number 123456789 and 987654321  

Currently when searching anything in Aftership, you must start with the same exact string. It would be great for users to adapt it to simple match. Example: Currently: String 1ZW6522Y0299621269 is not found if you look by 2Y0299621269

I have built a website to publish articles about local business services. Can you tell me how I can rank my website? Is there any SEO expert who can help? The website is built on a custom Laravel framework.

Hi there,    We’re planning to fully transition to your warranty return platform and would like to see the following improvements: * Dynamic Reference Lines on Return Shipping Labels: We’d like the option to add customizable reference lines on shipping labels. While there are default placeholders available, we need a more flexible solution to include internal notes that will help us organize returns efficiently. * Delayed Replacement Order Processing: We’d prefer the ability to process a replacement order without sending it to Shopify until the carrier marks the warranty return as “en route.” * Regex Validation for Warranty Intake Form: Adding regex validation would help us ensure inputs follow specific formats, such as order numbers or serial numbers, for better accuracy.

I have loved your app from the start. And improvements made along the way have been spot on. But now you lost me in both content and execution.    First, you put in ads. One of things I loved was no ads. But, hey, that revenues hard to pass up forever, especially after you've built your user base.   Second, I could have dealt with the ads if you had placed in a footer bar. But when you place the ads as large blocks right in the middle of the data, you lost me.   I was a developer for over 30 years on several different platforms. I must say that decision alone makes my top 20 of bad UI choices.   So, I will be unloading your app in favor of one that has no ads and all the functionality I need. It is a shame, because you do beat them out in feature, although not too much.   If you would at least move them to the footer then I would most likely return

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.