Share your ideas with us

Most major carriers already provide an estimated delivery date/time as part of their tracking data, but this isn't currently surfaced in the app. Context: Customers tracking a shipment want to know when it will arrive, not just its current status. Right now they have to infer this themselves or check the carrier's own site separately. Issue to address: Add a field that displays the carrier's estimated delivery date (and time window, where the carrier provides one) on the tracking/order page. This would reduce "where is my order" support inquiries and improve the post-purchase experience. Suggestion: Pull the estimated delivery data from carriers that already expose it via their APIs, and display it prominently near the shipment status.

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.

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.

在英语版本下，缺货订阅按钮会正常显示：https://eu.elegoo.com/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588 在法语及其他语言版本下，缺货订阅按钮未显示：https://eu.elegoo.com/fr/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588

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

On the tracking dashboard customers/users need to be able to click to grab, then drag and drop the order we desire our packages to be in.

So, as a seller who often runs campaigns, I would love to have a cool discount setup that can be customized based on how customers behave.   For example, I could keep discounts hidden for shoppers with shopping carts over $1,000 but display them for those who have smaller carts, so that they would shop more to get a better discount.   This strategy can be effectively applied to our product recommendations, enhancing conversion rates and boosting average order values.

Good morning, I kindly ask you to enable the option to change the font, font size, colour, etc., for the “address” field within the footer of notification emails. Currently, this is the only field that cannot be customised, which creates a noticeable contrast between the main text in the body and this field, making the emails aesthetically unappealing. Thank you.

Currently, AfterShip's webhook outgoing IP list is only available on an HTML documentation page (https://www.aftership.com/docs/tracking/webhook/webhook-outgoing-ips). This makes it impossible to automate IP allowlist management in infrastructure-as-code (IaC) workflows.   Problem: Teams that use IP-based firewalls to secure their webhook endpoints must manually monitor the documentation page for any IP changes and update their firewall rules accordingly. If a change is missed, it can cause webhook delivery failures and broken integrations.   Request: Please publish the webhook outgoing IP list as a dedicated plain-text endpoint — similar to how Cloudflare publishes theirs at https://www.cloudflare.com/ips-v4 — where each IP is returned on a separate line.   This would allow teams to: * Fetch the IP list programmatically as part of their CI/CD or IaC pipelines * Keep firewall allowlists automatically in sync without manual intervention * Avoid service disruptions caused by missed IP changes This is a standard practice among major API providers and would significantly improve the developer experience for customers who manage network security programmatically.

I would like to include the RMA number barcode on the returns label. This way, upon receiving the returns label at my warehouse, I can simply scan the barcode to retrieve the RMA number. Subsequently, I can use this number to efficiently locate the corresponding RMA information within the returns system. This process will significantly enhance the operational efficiency of our RMA procedures.