Share your ideas with us

Enhance Aftership’s functionality by integrating with Royal Mail, one of the leading postal services in the UK. This integration would allow users to track shipments directly through Aftership, providing seamless tracking updates, improved user experience, and broader carrier support. This feature would be particularly valuable for e-commerce businesses that frequently use Royal Mail for deliveries.

The vendor/supplier's email should be copied when sending any type of response to the customer regarding a return.  This includes the RMA confirmation of return, tracking label and when it is received, refunded and resolved.   We/supplier are getting chargebacks through Shopify from customers stating that their returns are not refunded in a timely manner and we have no way to get the email to show that it was processed in Aftership and to dispute a chargeback with shopify.   We have no copies sent to us.   Please fix this issue in Aftership/Shopify immediately.  Thank you. 

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,

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.

Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.

It would be very helpful if customers could select their preferred size during the exchange process, with real-time visibility of stock availability on the website. For example, when a customer initiates an exchange, the system should show whether the requested size is currently in stock. If the size is unavailable, it should display “Sold Out” instead of allowing the exchange to proceed. This feature would prevent unnecessary back-and-forth communication, improve customer experience, and reduce manual handling for merchants. Platforms like Revolve already offer this type of functionality, and it would be an excellent addition to AfterShip Returns.

Brand noted they’d like to be able to clearly communicate why certain Products are on the Blocklist - instead of the general text we have in place, without specifically making the customer review the Policy as a whole. Asking if we could define the error at the Blocklist Product Tag entry level. If the value is left blank, use default content.   Current state: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message that states "Does not comply with our return policy."   Desired State: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message from a configurable setting within RC where we can pass SKU or Product Category specific messages that state why an item is nt returnable like "Digital Goods are not returnable" or "Bundled Item cannot be returned" or "Last years models are not returnable but warranty available".   We'd like to be able to configure our own blocklist message for order item display when the end consumer logs into RC.

I am utilizing Smile to develop the Reward program for our business. This year, I aim to motivate members to increase their reviews by integrating Reviews into the reward system as bonus incentives. This will allow our members to accumulate extra points by sharing feedback for their purchases.

1. What is the context?  * We are currently a Premium plan subscriber operating a high-volume merchant shipping 68% of our Canadian orders via GLS Canada. We are looking to utilize the Enhanced MPS Visibility feature to improve our customer experience.   * Currently, your documentation lists carriers like FedEx, UPS, and DHL as supported for MPS, but GLS Canada is excluded. When we contacted support, we were told this is due to "carrier limitations.   2. What issue do you want to address? We believe the "carrier limitation" rationale may be outdated or incorrect because AfterShip is already successfully pulling data for GLS child packages. * Evidence: On GLS Canada tracking number P97186751, AfterShip retrieves events for both Package 1 (Delivered Nov 21) and Package 2 (Delivered Nov 19). * The Problem: Because GLS Canada is not on your "Supported Carriers" list for MPS logic, your system aggregates these distinct events into a single "scrambled" timeline instead of separating them into tabs. * The Gap: The data exists in your system; the parsing logic to separate "Master" vs. "Child" is simply missing for this specific carrier. 3. What outcome do you expect? * We request that the product team add GLS Canada to the Enhanced MPS Visibility supported carrier list * We need the system to recognize the child packages it is already detecting and display them in separate tabs (Piece 1, Piece 2), just as it does for FedEx or UPS.   4. Who will benefit from your idea? * Merchants: This allows Canadian merchants to use your Enterprise MPS features for their dominant carrier, reducing support tickets regarding "confusing" status updates. * AfterShip: It improves the value of your Enterprise plan for the Canadian market by supporting the region's major logistics provider.

Would love to see carrier support added for MyPost Business by Australia Post.  This is already an integration in ShipStation, Starshipit and Shopify - it would be a valuable addition to Aftership Shipping and Aftership Returns.