Share your ideas with us

To enhance the shipping experience for customers purchasing hair extensions or hair care products, AfterShip could focus on providing real-time tracking updates that are both detailed and easy to understand. For the hair industry, ensuring timely delivery is critical, as customers expect to receive their products in a timely manner, especially for events like weddings, parties, or other special occasions. Additionally, offering automated notifications at each stage of the shipping process — from dispatch to in-transit updates and delivery confirmation — would allow customers to stay informed and reduce anxiety around the arrival of their products. A specific feature that would be beneficial in the hair industry is providing an estimated delivery window based on the type of hair products purchased, considering how delicate and time-sensitive hair products can be. Another improvement could be offering customized delivery options, like express shipping for urgent orders or delivery tracking tailored to customers’ needs based on their location, enhancing convenience and customer experience. By integrating these features, AfterShip could help ensure a seamless experience for customers in the hair industry, driving satisfaction and repeat business.

There should be an option to send at least all email notifications to one email address, such as a shared folder, each time a shipment has an action. Using a webhook should not be the only option. Many companies would like this option in conjuntion with an M365 automation to create MS teams messages etc for internal use.

In Shopify, merchants cannot identify which orders were combined in TTS. This will increase the risk of merchants repeatedly fulfil the same order items.   To address this issue proactively, I would recommend that we introduce a hint or tag within Shopify to alert merchants about combined orders, thus avoid this situation from happening.

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.

Allow me to still refund if I choose even if the return request has expired. Now I have to recreate the return request making more work for me.

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.

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.  

We'd like the ability to restrict which order-editing options are available on a per-country basis, rather than applying the same set of options globally.   Many merchants work with regional checkout or fulfillment partners (e.g. Global-E) that prohibit certain order changes after an order is placed in specific countries. For example, a merchant might need to limit editing to only "apply discount code" and "cancel order" for a subset of countries, while keeping the full set of editing options available everywhere else.   Being able to configure order-editing permissions by country/region would help merchants stay compliant with regional partner restrictions without giving up flexibility in other markets.

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.

As a merchant, I allow shoppers to exchange items for different variants during returns, which may have different prices. For example, a Small size costs $30 while a Large size costs $50.   Currently, Shopify allows me to adjust prices manually only after the Return Merchandise Authorization (RMA) is submitted. If aftership could facilitate charging or refunding price differences for variants during the return request process, it would greatly streamline our operations and enhancing the overall efficiency of RMA management.