Share your ideas with us

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.

Hello to Aftership team, I am from Fabricdekho.com. I am here to write a request for providing a return request  button along with seller approval so that return could be the easy process. As return is a difficult process as of now. Customer need to request again n agian to seller. We should work on this so we can ease the process of return.   Thanks.

I am utilizing Smile to develop the Reward program for our business. This year, I aim to motivate members to increase their reviews by integrating Reviews into the reward system as bonus incentives. This will allow our members to accumulate extra points by sharing feedback for their purchases.

I want all orders over $30 to show a shipping fee of only $2, because this is subsidized by TikTok.

As a user, I'd like the ability to pull in tracking numbers to my dashboard by parcel account number so that I can view all shipments assigned to a specific or multiple parcel accounts.   For example I have 10 parcel accounts (4 with DHL and 6 with FedEx). I'd like the ability to utilize the parcel account number(s) instead of the API to pull in tracking associated with my parcel accounts.

When exchanging a product, you have to pick from a list of products, sorted by the most recently created products. There's no search facility. This is particularly problematic when you have an old sku that comes in every season and it is buried deep in the list

1. What is the context?  * We are currently a Premium plan subscriber operating a high-volume merchant shipping 68% of our Canadian orders via GLS Canada. We are looking to utilize the Enhanced MPS Visibility feature to improve our customer experience.   * Currently, your documentation lists carriers like FedEx, UPS, and DHL as supported for MPS, but GLS Canada is excluded. When we contacted support, we were told this is due to "carrier limitations.   2. What issue do you want to address? We believe the "carrier limitation" rationale may be outdated or incorrect because AfterShip is already successfully pulling data for GLS child packages. * Evidence: On GLS Canada tracking number P97186751, AfterShip retrieves events for both Package 1 (Delivered Nov 21) and Package 2 (Delivered Nov 19). * The Problem: Because GLS Canada is not on your "Supported Carriers" list for MPS logic, your system aggregates these distinct events into a single "scrambled" timeline instead of separating them into tabs. * The Gap: The data exists in your system; the parsing logic to separate "Master" vs. "Child" is simply missing for this specific carrier. 3. What outcome do you expect? * We request that the product team add GLS Canada to the Enhanced MPS Visibility supported carrier list * We need the system to recognize the child packages it is already detecting and display them in separate tabs (Piece 1, Piece 2), just as it does for FedEx or UPS.   4. Who will benefit from your idea? * Merchants: This allows Canadian merchants to use your Enterprise MPS features for their dominant carrier, reducing support tickets regarding "confusing" status updates. * AfterShip: It improves the value of your Enterprise plan for the Canadian market by supporting the region's major logistics provider.

I'd like to log an enhancement request for the Tracking page editor. Currently the section where we add social media connectors is limited in connection options. Specifically for Instagram (which is a really cool feature) the only way to connect is using our own credentials (user name/password login). This is an unacceptable option as it exposes us to being hacked and is a security concern obviously. The better way to do this is via Instagram's API connection: https://developers.facebook.com/docs/instagram-platform. Can you please log that as a high priority enhancement request? Should we decided to stay with AfterShip, this will be a critical branding requirement.

Title: Feature request: Claude MCP connector for AfterShip Returns AfterShip Returns should offer an official Claude MCP connector. Claude already connects to Shopify, Gmail, Slack, and Google Drive, so many merchants run their daily operations through it. Returns data is the missing piece. Without a connector, teams still have to open the portal, find the return, and copy details into customer replies or reports by hand. A connector would make it possible to ask questions like: “What’s the status of the return on order #1234?” “Which returns from last week haven’t been refunded yet?” “What are the top return reasons this month?” “Which SKUs have the highest return rate?” Why it should be added: Faster customer service. “Where’s my refund?” emails could be answered in seconds using live return data. Fewer errors. Order numbers, tracking, and refund amounts would come straight from AfterShip instead of being copied manually. More accessible reporting. Small teams without a dedicated analyst could get insight from return data in plain language. A connected workflow. Returns would link up with the order, email, and team tools merchants already use with Claude. Keeps AfterShip central. As more operations move through AI assistants, the platforms that connect to them become the ones merchants depend on. Read-only access would be a strong starting point: return lookups, statuses, reasons, and refund/exchange outcomes. Actions like approving or rejecting requests could follow later, with confirmation steps built in.

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.