Share your ideas with us

Currently the aftership is one way communication making it diffucult for business to see integrated full status at one place again when customer login to their shopify page they see status of item still on the way as shopify stops at fullfilled stge. Though the track order option by Aftership is good it is still a bad customer experience.

I don't want to sync my email, so it would be great to be able to add a record for items that I've ordered but haven't shipped yet. I can then edit/update the shipment when the tracking number is available. 

There is a massive discrepancy between the notificaiton customization capabilities within the Tracking module and the Returns module.  In the Returns module, all you can do is update the messaging. There is no ability to alter colours, add logos, images, or otherwise truly 'brand' the notifications.  All of this exists in the Tracking module.  Recommendation is that you port over the same functionality into the Returns module ASAP.  Those notification emails are currently a horrific customer experience.

Hi,   I recently started buying products from India and sometimes they ship using : https://shipglobal.in/tracking/   Unfortunately Aftership is not yet supporting shipglobal.in and I need to use another app (actually 17tracks works) to track these shipments.   Please consider adding shipglobal.in as a supported career.   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.

As a retailer, it would be great if customer preferences can be collected and determine whether to send an SMS notification based on the subscription status synchronized via API.   Moreover, a customer-facing page that allows users to manage their preferences would be even better. We would love to communicate more with our shoppers, which will efficiently improve our customer satisfaction and brand reputation.

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

Background On the Return Summary page, the Return Status section is commonly used to display shipping instructions that guide customers on how to return their items. As part of these instructions, customers are often required to include both their RMA ID and Order ID with the return shipment so that the warehouse and processing teams can identify and process the return correctly. Currently, the RMA ID is only displayed at the top of the page, and the Order ID is not prominently visible within the Return Status section. Requested Enhancement Add configurable fields within the Return Status section of the Return Summary page to display: * Order ID * RMA ID These fields should be displayed alongside the shipping instructions and return status details, making them easily accessible to customers while preparing and packaging their return shipment. We are open to any placement within the Return Summary page that provides clear visibility and easy access to these details. Business Use Case Our client specifically requested this enhancement because their return instructions ask customers to include the RMA ID and Order ID with the return package. Having these details displayed directly within the Return Status section would: * Improve visibility of important return information. * Reduce customer confusion when preparing returns. * Eliminate the need for customers to search for these details elsewhere on the page. * Help ensure return shipments contain the correct identification information. * Improve operational efficiency and reduce return processing delays. Expected Outcome Customers can quickly locate the required Order ID and RMA ID in the same section where they view their shipping instructions, resulting in a smoother and more user-friendly return experience. Thank you for considering this enhancement. We believe it would benefit merchants who require customers to include reference identifiers with returned packages and would improve the overall returns experience.

The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page. 

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.