Share your ideas with us

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.

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.

Currently OTD report, reports the complete journey so the avereage time can fluctuate based on how long it takes for customers to collect their order.  We need to report on the carrier performance and then the time it takes to collect.  It would be good to have  a PUDO report that breaks down : average transit time to collection point   Average time waiting for collection    If we expand our PUDO options in Europe it would be a good indication 

Scenarios 1. We give a customer a partial refund for a coupon code they forgot to enter. This partial refund is currently stopping the customer and us from being able to request a return in Aftership. Please allow an option to make RMA or override in this scenario. 2. (similar to #1) Customer orders multiple items, gets RMA for one item, returns it and is refunded. Now they want to return the other item, however, because there is a refund in Shopify we are not able to open a RMA for the other item because the order shows as returned. Please allow option to make RMA or override in this scenario.  Thank you

Please add the shipping company ACI EXPRESS, which is based in South Korea. They have partnerships with multiple overseas shipping companies, and a lot of merchandise is being shipped through ACI Express to the USA and the Middle East, especially after the implementation of tariffs in the USA.

We should be able to update the email address on the returns and warranty pages in case the cx is unable to access the default email.

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,

Goal: To make it easier for customers to accurately select the correct item for return when using the return portal. Preconditions: The customer has placed an order containing multiple items, some of which may have similar or identical titles, colors, or sizes. The SKU numbers for the items exist in the system but are not currently displayed in the return portal. Trigger: The customer initiates a return and accesses the return portal to select the item(s) they wish to return. Basic Flow: The customer logs into the return portal. The portal displays the items from their order, including details such as title, color, size, and now the SKU number for each item. The customer uses the SKU number to cross-reference their order confirmation or invoice, ensuring they select the correct item for return. The customer completes the return process with confidence that the correct item has been selected. Postconditions: The customer successfully returns the correct item without confusion. The support team receives fewer inquiries about mismatched returns. Benefits: For Customers: Improved user experience by reducing confusion when selecting items for return. Greater confidence in completing returns independently. For the Business: Reduced customer support requests related to returns. Increased efficiency in processing returns, minimizing errors caused by incorrect item selection. Priority: Medium – This enhancement has a high potential to improve customer satisfaction with a relatively low implementation effort. Technical Requirements: Modify the front-end display of the return portal to include SKU numbers as part of the product details. Ensure the SKU numbers are fetched and displayed consistently across all customer orders. This use case focuses on enhancing the clarity of the return process for customers while streamlining operational efficiency for the business.

Could you please make a slight programming change, could you please allow swipping back to the main list of packages once you looked at a package info    iOs

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.