Share your ideas with us

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

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.

When utilizing an HTML email editor, I aim to display and personalize shipment or order items within my tracking notifications.   This feature would allow shoppers to conveniently view their purchases directly in the email, thereby improving customer satisfaction.

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.

it would be great to be able to manually add a placeholder delivery in order to keep track of my deliveries.

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.

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.

I would find it very useful if I could pull the SMS communication metadata using an API. Currently it is only available as a download from the portal which makes automation impossible.

Seems like a basic thing, but when I have an enhancement I'd like to submit, I want to ensure I don't duplicate someone else's submission.  Obviously that's why there is an 'upvote' button.  The only way to determine if there is something worth upvoting is to scroll through the entire list from top to bottom.

Would like to be able to display any discount received, from the orginal order, on the product selection page in the warranty portal. If possible, the discount code that was used as well. Important: Discount amount and discount code should show in the AfterShip admin portal.