Share your ideas with us

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.

I work in the furniture industry with thousands of products and continuous new product listings.   Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests.   Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.

As a merchant, I would like to charge the cost of return when the shopper chooses to replace the returned item.  aftership Returns provides Stripe checkout only for this scenario, but I don't have a Stripe account, I would like to use my Shopify checkout to charge the exchange upsell and cost of return. So that I don't have to open a Stripe checkout and manage two accounts (Shopify and Stripe checkout) at the same time.

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

When using the mobile App, currently shipments remain visible in the tracking list even after they have been delivered. Over time, this can make the main tracking screen feel cluttered, especially for users who receive a large number of packages. It would be very helpful to have an option to: - Archive delivered shipments manually, or - Automatically move delivered shipments to an archive after a certain period of time. This would allow users to keep their active tracking list clean and focused on packages that are still in transit, while still retaining access to past deliveries when needed.   Thank you,

Show all packages to a us zip code

As a merchant, I allow shoppers to exchange items for different variants during returns, which may have different prices. For example, a Small size costs $30 while a Large size costs $50.   Currently, Shopify allows me to adjust prices manually only after the Return Merchandise Authorization (RMA) is submitted. If aftership could facilitate charging or refunding price differences for variants during the return request process, it would greatly streamline our operations and enhancing the overall efficiency of RMA management.

What is the context  When using AfterShip Returns with the "Shop Now" / "exchange for anything" option that redirects customers to shop on the merchant's own store, customers can select any product available on the store as their exchange item. What issue do you want to address? There is currently no way to exclude specific products from being selectable as exchange items in this flow. The existing exclusion controls (the block list and excluding products from recommendations via product tags) only apply when AfterShip is recommending products or when "Exchange on AfterShip returns page" is selected. When customers shop directly on the merchant's own website via "Shop Now," these exclusions do not apply, so restricted products remain selectable. This allows customers to exchange low-value items for high-value products, resulting in margin loss and exchange abuse. The only current workaround, switching to "Exchange on AfterShip returns page," removes the on-store shopping experience the merchant wants to keep.   What outcome do you expect? The ability to exclude specific products from being eligible exchange items while still using the "Shop Now" flow where customers shop on the merchant's own website. Ideally the exclusion could be defined by SKU, in addition to collection or product tag, since some merchants do not have the relevant products grouped in a collection and may not have access to create collections in Shopify.   Who will benefit from your idea? Merchants using the "Shop Now" exchange flow who need to prevent certain products from being selected as exchange items, protecting their margins and preventing exchange abuse while preserving the branded on-site shopping experience during exchanges.

For instance, customers can quickly locate reviews based on size, incorporate images and videos, consider age, product characteristics, and the reviewer's recommendation status.

Allow me to still refund if I choose even if the return request has expired. Now I have to recreate the return request making more work for me.