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.

在英语版本下，缺货订阅按钮会正常显示：https://eu.elegoo.com/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588 在法语及其他语言版本下，缺货订阅按钮未显示：https://eu.elegoo.com/fr/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588

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.

Background On the Return Summary page, the Return Status section is commonly used to display shipping instructions that guide customers on how to return their items. As part of these instructions, customers are often required to include both their RMA ID and Order ID with the return shipment so that the warehouse and processing teams can identify and process the return correctly. Currently, the RMA ID is only displayed at the top of the page, and the Order ID is not prominently visible within the Return Status section. Requested Enhancement Add configurable fields within the Return Status section of the Return Summary page to display: * Order ID * RMA ID These fields should be displayed alongside the shipping instructions and return status details, making them easily accessible to customers while preparing and packaging their return shipment. We are open to any placement within the Return Summary page that provides clear visibility and easy access to these details. Business Use Case Our client specifically requested this enhancement because their return instructions ask customers to include the RMA ID and Order ID with the return package. Having these details displayed directly within the Return Status section would: * Improve visibility of important return information. * Reduce customer confusion when preparing returns. * Eliminate the need for customers to search for these details elsewhere on the page. * Help ensure return shipments contain the correct identification information. * Improve operational efficiency and reduce return processing delays. Expected Outcome Customers can quickly locate the required Order ID and RMA ID in the same section where they view their shipping instructions, resulting in a smoother and more user-friendly return experience. Thank you for considering this enhancement. We believe it would benefit merchants who require customers to include reference identifiers with returned packages and would improve the overall returns experience.

Hi,   I recently started buying products from India and sometimes they ship using : https://shipglobal.in/tracking/   Unfortunately Aftership is not yet supporting shipglobal.in and I need to use another app (actually 17tracks works) to track these shipments.   Please consider adding shipglobal.in as a supported career.   thank you!

We are able to retrieve shipping rates for each carrier, but we would also like customs clearance fees and other charges available through each carrier’s API to be integrated via API as well. This is especially important for DDP shipments. Some information that can be retrieved through the carrier APIs cannot be retrieved through AfterShip, which means we would need to connect to each carrier’s API separately.

Background: * At the moment, a user with a specific domain can easily create a new organization when creating an account in AfterShip * We don’t indicate to this use that an existing organization is already linked to the same domain This can create confusion when member are trying to get access to an organization proactively (without being added by the current owner) * Hence we end up with support tickets from member not able to get access to their main org. Expectation: * Alert message during new inscription if we identify that the email domain is already used. * Eventually an option to send a request to the owner of the main org. * Possibility to delete the new account to avoid unnecessary org and member creations for our clients. * Could be active only for ENT client if we want to reduce the scope

What is the context  When using AfterShip Returns with the "Shop Now" / "exchange for anything" option that redirects customers to shop on the merchant's own store, customers can select any product available on the store as their exchange item. What issue do you want to address? There is currently no way to exclude specific products from being selectable as exchange items in this flow. The existing exclusion controls (the block list and excluding products from recommendations via product tags) only apply when AfterShip is recommending products or when "Exchange on AfterShip returns page" is selected. When customers shop directly on the merchant's own website via "Shop Now," these exclusions do not apply, so restricted products remain selectable. This allows customers to exchange low-value items for high-value products, resulting in margin loss and exchange abuse. The only current workaround, switching to "Exchange on AfterShip returns page," removes the on-store shopping experience the merchant wants to keep.   What outcome do you expect? The ability to exclude specific products from being eligible exchange items while still using the "Shop Now" flow where customers shop on the merchant's own website. Ideally the exclusion could be defined by SKU, in addition to collection or product tag, since some merchants do not have the relevant products grouped in a collection and may not have access to create collections in Shopify.   Who will benefit from your idea? Merchants using the "Shop Now" exchange flow who need to prevent certain products from being selected as exchange items, protecting their margins and preventing exchange abuse while preserving the branded on-site shopping experience during exchanges.

Allow me to still refund if I choose even if the return request has expired. Now I have to recreate the return request making more work for me.

Change the update indicator Dot from the light blue color to the orange color you already use in your iOS app. It is hard to pick out the dot if you have a long list of shipments. If it was the orange color you already use in the app it should be a simple change to make for an updated version. Also so carriers on the list of carriers to pick from are now asking for receiving zip, so those carriers never update now.  Thanks