Share your ideas with us

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:

When a warranty is approved, you can choose to include an label. In the “Warranty claim approved” email, there is no ability to account for this decision. We would need to add an ability to have wording around a label being included as well as a label not being included. Below is an example email we have now.   Two ways this could be addressed: 1. Split this notification into 2 notifications: “Warranty claim approved - with label” and “Warranty claim approved - no label”. 2. Add Flows to Warranties with Split functionality for generated labels.

We use this to ship to clients it would be nice if we could save clients within the system to send notifications to. 

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.

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.

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.

Enhance Aftership’s functionality by integrating with Royal Mail, one of the leading postal services in the UK. This integration would allow users to track shipments directly through Aftership, providing seamless tracking updates, improved user experience, and broader carrier support. This feature would be particularly valuable for e-commerce businesses that frequently use Royal Mail for deliveries.

I am using the API for Zoho Inventory integration with Aftership. I would like the items on the shipping order of Zoho Inventory displayed on the shipment items of the email notifications to my customers. The shipments are created within Zoho Inventory and tracked by Aftership.

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

Hi there, We ship wine, which means orders are often held by our fulfilment center when temperatures along the route are above or below certian threshold we have set. I would like to create a flow that automatically notifies the customer that their order has been flagged for a weather hold and ensures them it is still on the way. Is this possible? Thanks