Share your ideas with us

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.

Hello AfterShip team, We use the AfterShip Post-Purchase connector in Claude to automate our daily delivery follow-up, and it works very well for shipments. However, the connector currently only exposes shipments (trackings) and returns. Orders without a tracking number are not accessible, although they are visible in the AfterShip admin under Tracking > Orders. Our use case: every morning we want to detect orders that are still "Unfulfilled" (or "Partially fulfilled") more than 2 business days after the order date, and that have no tracking yet, so we can follow up with our suppliers. Could you add the following to the MCP connector? 1. A list_orders tool with filters on fulfillment status (unfulfilled, partially fulfilled), order status (open / canceled), order date (placed_at) and order number. 2. For each order: fulfillments with their trackings (to know whether a tracking exists), line items, customer, tags and order notes. 3. Access to the internal comments added on an order (the "Comments" section of the order page), so we can exclude orders already handled by our team. 4. If possible, order-level custom fields (e.g. our "isBackorder" flag, which today only exists on shipments). Is this on your roadmap? In the meantime, is there another supported way (API endpoint, scheduled export or webhook) to get this list of unfulfilled orders automatically? Thank you for your help.

Currently the aftership is one way communication making it diffucult for business to see integrated full status at one place again when customer login to their shopify page they see status of item still on the way as shopify stops at fullfilled stge. Though the track order option by Aftership is good it is still a bad customer experience.

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.

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 

Currently you can manually refund the shipping fee in the admin manually, but would like the ability for it to be automatic.

It would be great if we could allow the discount to carry over to the new order if a customer is just exchanging a size, at the moment our customer is choosing to refund rather then exchange sizing because they have to pay the difference between the original discounted price and the price. 

Would be a great feature if there was a link to the returns status page within the returns dashboard.   And if this link can be easily copied so we can share to the end consumer if they call through the contact center/help, then our agents can quickly copy the link and then email/share to the end consumer

Integration of Sharetown to schedule pickups of items being returned. The process involves Sharetown picking up items directly from the customer's doorstep without the need for packaging. Once the items are picked up, Sharetown will resell the items through their channels and provide business with an agreed-upon gain-share payback based on the resale price.   Key Requirements: No label generation is needed as Sharetown will handle the pickup. A system integration will be needed to push the return data to Sharetown as a pickup request in their system. Sharetown will manage the logistics and resale of the items.

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