Share your ideas with us

As a business owner, having precise accounting records is essential for tax purposes. It's particularly important to account for returns correctly by adjusting for them and deducting the relevant taxes to prevent overpayment.   I've observed that Shopify currently only accommodates refunds, lacking store credit or exchange options for returns. Therefore, if aftership Return could support all three options and assist in reconciling taxes and producing accurate tax reports for returns, it would greatly benefit our operations.

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.

the only customization allowed is subject line and preview text for the reminder email, can't change the body copy of the reminder email.    benefit would be to add a secondary reminder of receiving loyalty points/an incentivization 

It would be useful to have a Sku column amognst the list when editing the returns dashboard. The image of the item is useful but often the item is enclosed in a boxed which is marked with the sku. Therefore at first glance, the sku is seen before the physical item.

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.

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

As a user, I'd like the ability to pull in tracking numbers to my dashboard by parcel account number so that I can view all shipments assigned to a specific or multiple parcel accounts.   For example I have 10 parcel accounts (4 with DHL and 6 with FedEx). I'd like the ability to utilize the parcel account number(s) instead of the API to pull in tracking associated with my parcel accounts.

Good morning, When viewing notification emails on a mobile device, the background colour only appears at the top as a small strip. As a result, the background colour on the sides and beneath the email is completely lost. I therefore propose hiding the background area entirely on mobile, displaying only what is within the content background, which is the main body of the email. Thank you.

As online shopping continues to expand, cities and businesses are looking for ways to simplify last-mile delivery. In this shift, automated parcel lockers have become a practical solution, helping reduce missed deliveries and improving convenience for both couriers and customers. Their use is steadily shaping the future of contactless and efficient package management.

Would like to be able to filter the shipping exceptions so I only receive ones for damages. Especially after a club run, we can receive many notices for delivery exceptions which can include delays, intercepts, etc. However, the ones we would primarily like to receive are for damages. we would like to catch these before the customer reaches out to let us know or from the return report.