Share your ideas with us

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.

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.

Please let me hide the ad carousel, I am happy to pay subscription or whatever to disable it. Thanks 

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.

Hi there,    We’re planning to fully transition to your warranty return platform and would like to see the following improvements: * Dynamic Reference Lines on Return Shipping Labels: We’d like the option to add customizable reference lines on shipping labels. While there are default placeholders available, we need a more flexible solution to include internal notes that will help us organize returns efficiently. * Delayed Replacement Order Processing: We’d prefer the ability to process a replacement order without sending it to Shopify until the carrier marks the warranty return as “en route.” * Regex Validation for Warranty Intake Form: Adding regex validation would help us ensure inputs follow specific formats, such as order numbers or serial numbers, for better accuracy.

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

What is the context  When using AfterShip Returns with the "Shop Now" / "exchange for anything" option that redirects customers to shop on the merchant's own store, customers can select any product available on the store as their exchange item. What issue do you want to address? There is currently no way to exclude specific products from being selectable as exchange items in this flow. The existing exclusion controls (the block list and excluding products from recommendations via product tags) only apply when AfterShip is recommending products or when "Exchange on AfterShip returns page" is selected. When customers shop directly on the merchant's own website via "Shop Now," these exclusions do not apply, so restricted products remain selectable. This allows customers to exchange low-value items for high-value products, resulting in margin loss and exchange abuse. The only current workaround, switching to "Exchange on AfterShip returns page," removes the on-store shopping experience the merchant wants to keep.   What outcome do you expect? The ability to exclude specific products from being eligible exchange items while still using the "Shop Now" flow where customers shop on the merchant's own website. Ideally the exclusion could be defined by SKU, in addition to collection or product tag, since some merchants do not have the relevant products grouped in a collection and may not have access to create collections in Shopify.   Who will benefit from your idea? Merchants using the "Shop Now" exchange flow who need to prevent certain products from being selected as exchange items, protecting their margins and preventing exchange abuse while preserving the branded on-site shopping experience during exchanges.

It would be really useful to see how often the Gift Tracking Page is actually being used, separately from the regular tracking page. At the moment, it’s hard to tell uptake or performance unless the page has a unique URL or rely on Google Analytics. Having native reporting in AfterShip would make this much easier. Ideally this would show: - Views and unique visitors for the gift tracking page - How it compares to the standard tracking page - Basic engagement (e.g. CTA clicks) This would help merchants understand adoption and value of the gifting feature much more clearly.

I work in the furniture industry with thousands of products and continuous new product listings.   Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests.   Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.

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.