Share your ideas with us

Hi, The data when the shipment is created at the carrier is important for shipment analysis. Example:  Info received   Shipment information received DHL Express Mar 25, 2025 at 12:01 pm

A notification to give the customer the opportunity to change their requested ship date. This allows wineries to change the date without re-directing.  Using the RSD and sending a notification 3 days or so before. 

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.

Like to set their own “Image not found” image for Products in the Returns Portal. That way, If a Product is not sent to AfterShip with an Image URL, they have an image that looks more branded.   Today, when an item does have an img url, the Return Portal defaults to the missing image icon.   Request - have a function within Return Portal where if any items on my return portal dont have an image URL, it can set to a image that I select instead of defaulting to the standard broken/no image icon.

Brand noted they’d like to be able to clearly communicate why certain Products are on the Blocklist - instead of the general text we have in place, without specifically making the customer review the Policy as a whole. Asking if we could define the error at the Blocklist Product Tag entry level. If the value is left blank, use default content.   Current state: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message that states "Does not comply with our return policy."   Desired State: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message from a configurable setting within RC where we can pass SKU or Product Category specific messages that state why an item is nt returnable like "Digital Goods are not returnable" or "Bundled Item cannot be returned" or "Last years models are not returnable but warranty available".   We'd like to be able to configure our own blocklist message for order item display when the end consumer logs into RC.

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.

It would be really useful to see how often the Gift Tracking Page is actually being used, separately from the regular tracking page. At the moment, it’s hard to tell uptake or performance unless the page has a unique URL or rely on Google Analytics. Having native reporting in AfterShip would make this much easier. Ideally this would show: - Views and unique visitors for the gift tracking page - How it compares to the standard tracking page - Basic engagement (e.g. CTA clicks) This would help merchants understand adoption and value of the gifting feature much more clearly.

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.

Some customers enter +1 before their phone number when requesting a return or exchange. This causes the shipping label to fail to generate and creates frustration for the customer and extra work for me. I would like the system to correct the phone number to allow successful label generation.

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.