Share your ideas with us

While using personalization, I want to understand the actual product results generated by these algorithms and the reason behind the chosen product displays for shoppers.   If I can preview the recommendation results in the admin, it would reduce uncertainty, ensure optimal outcomes, and improve my marketing strategies to boost conversions.

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

It would be very helpful to have an option to group orders by store/company name (e.g., all Amazon orders together, all eBay orders together, etc.). This way, I could collapse or expand groups and quickly view only the orders I want. Additionally, it would be great if users could create their own custom groups for even more flexibility.

Perhaps with Aftership Reviews, we could set a custom rule where if the transit time is exceeds X days, the platform won't initiate reviews.

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.

Can we have a way to export the report of the notifications? So for example, I would love to be able to export the list of people who had bounced emails for our shipping notifications or even to export the list of folks who did not open the message. 

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.

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.

I want to fully customize different free shipping thresholds for different currencies/regions.   This would better compensate for my shipping costs in different currencies and may also increase the order value.

I want to be able to show values and total value of anything that is currently in transit, out for delivery and delivered so i can manage my insurance process of total value out at a given time