Share your ideas with us

Hello to Aftership team, I am from Fabricdekho.com. I am here to write a request for providing a return request  button along with seller approval so that return could be the easy process. As return is a difficult process as of now. Customer need to request again n agian to seller. We should work on this so we can ease the process of return.   Thanks.

The same videos are displayed to shoppers on my collection page or recommendation widgets. I want greater exposure to alternative products and videos, but selecting which ones to display and updating them regularly feels overwhelming.   Furthermore, testing to determine which video garners the most traffic is even more challenging. I have no idea if my efforts will result in sales. If only there is a tool could help!

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

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.

For the tracking page I am currently using, it would be great to have the Delivery Instructions feature, so that my customers can provide specific instructions to carriers, and ensure successful deliveries.   This feature will also be valuable for drivers who can have all the necessary information at their fingertips, even for dispatchers who can manage delivery more effectively with all that info.   A seamless last-mile delivery experience can create a sense of reliability and convenience that fosters long-term customer relationships and encourages repeat purchases for my brand.

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.

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.

The background is that I sell my products on multiple marketplaces, and each has different return flows that the aftership Returns page cannot handle. It would be much easier if there is a Returns API that can meet my requirements below.   Need: - I need a Returns API to allow creating RMA/return requests without having to use the Returns Page to file it.  - I can call the API and pass the information regarding the Return Reason Resolution, etc in one go.  - Once I call this API, it will return creation in Pending or Auto-Approved Status.

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.

We would love to be able to see the return comment information our customers provide when returning items within the return reports we download. Our customers are using the comment box to describe the return reason in depth but this information is lost when it comes to dowloading the return reports.