Share your ideas with us

It would be very helpful if customers could select their preferred size during the exchange process, with real-time visibility of stock availability on the website. For example, when a customer initiates an exchange, the system should show whether the requested size is currently in stock. If the size is unavailable, it should display “Sold Out” instead of allowing the exchange to proceed. This feature would prevent unnecessary back-and-forth communication, improve customer experience, and reduce manual handling for merchants. Platforms like Revolve already offer this type of functionality, and it would be an excellent addition to AfterShip Returns.

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.

Hello,  We currently use AfterShip Feed to connect our Amazon Seller account to TikTok Shop. But it would be fantastic to be able to also connect with Walmart Seller's MCF. It would allow even greater reach of products on more sales channels.

Show all packages to a us zip code

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.

If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image:

After RMA is created, admin needs the ability to edit details of the return. Including: 1. 1. editing products on return 2. editing customer email/address details 3. add remove return fees prior to receipt of return Often customers will call and need a return label sent to a new email address or want to add or remove items on their return. Also, if items are returned that are not included the return must be canceled and reopened, which is a messy process that sends a ton of unneccessary emails to the customer.

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.

So, as a seller who often runs campaigns, I would love to have a cool discount setup that can be customized based on how customers behave.   For example, I could keep discounts hidden for shoppers with shopping carts over $1,000 but display them for those who have smaller carts, so that they would shop more to get a better discount.   This strategy can be effectively applied to our product recommendations, enhancing conversion rates and boosting average order values.

Hello, Could you add Vinted Go shipping to the shipping list in the next update, please? It's a very very good app to follow shipping. Thanks's in advance Best regards