Share your ideas with us

Please add the shipping company ACI EXPRESS, which is based in South Korea. They have partnerships with multiple overseas shipping companies, and a lot of merchandise is being shipped through ACI Express to the USA and the Middle East, especially after the implementation of tariffs in the USA.

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.

The same videos are displayed to shoppers on my collection page or recommendation widgets. I want greater exposure to alternative products and videos, but selecting which ones to display and updating them regularly feels overwhelming.   Furthermore, testing to determine which video garners the most traffic is even more challenging. I have no idea if my efforts will result in sales. If only there is a tool could help!

Expose an REST API for creating Warranty Claims.

While using personalization, I want to understand the actual product results generated by these algorithms and the reason behind the chosen product displays for shoppers.   If I can preview the recommendation results in the admin, it would reduce uncertainty, ensure optimal outcomes, and improve my marketing strategies to boost conversions.

Image 1 — Shipment Selection & Pin Icon Behavior (pictures attached) When selecting shipments, the Pin icon should remain clean, clear, and fully visible when up to three shipments are selected. Once the user selects more than three shipments, the Pin icon should become visually disabled—either blurred, faded, or hidden—to clearly communicate that the action is unavailable. Please also indicate where the attached reference image should appear in relation to the Pin icon so that its placement and visual hierarchy are clear.   Image 2 — Pin Option Within the Shipment Menu (pictures attached) When the user opens any shipment and clicks the three-dot (⋮) menu, the following options should be displayed: 1:- Edit Shipment 2:- Mark as Delivered 3:- Pin at Top 4:- Delete The Pin at Top option should be presented as a polished, intuitive action within the existing menu, maintaining a premium and consistent user experience.   Thanks and Regards

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.

Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.

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.

GM is there a way to close an exception order rather than a total delete?