Share your ideas with us

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.

Perhaps with Aftership Reviews, we could set a custom rule where if the transit time is exceeds X days, the platform won't initiate reviews.

A notification to give the customer the opportunity to change their requested ship date. This allows wineries to change the date without re-directing.  Using the RSD and sending a notification 3 days or so before. 

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

Would like to be able to filter the shipping exceptions so I only receive ones for damages. Especially after a club run, we can receive many notices for delivery exceptions which can include delays, intercepts, etc. However, the ones we would primarily like to receive are for damages. we would like to catch these before the customer reaches out to let us know or from the return report.

Can we have a way to export the report of the notifications? So for example, I would love to be able to export the list of people who had bounced emails for our shipping notifications or even to export the list of folks who did not open the message. 

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.

Hello AfterShip Team, We run an e-commerce platform that sells digital licenses and premium accounts (our store is https://accountlicense.ir/). We are looking to use AfterShip to manage our post-purchase experience and customer tracking, but we've run into a limitation because our products are purely digital. Currently, AfterShip is heavily tailored toward physical goods with carrier tracking numbers. Since we deliver license keys and credentials digitally (via email/SMS), we would love to see a dedicated "Digital Delivery Flow" in AfterShip. Specifically, it would be amazing to have: 1. A tracking page layout optimized for digital goods that displays license activation instructions or download links instead of shipping carrier maps. 2. Webhook and API triggers that update the order status to "Delivered" when the digital product is sent to the customer's portal or inbox. 3. Custom post-purchase emails specifically designed to track when a customer reveals or views their digital key. This feature would be incredibly helpful for digital merchants like us. Currently, adapting standard physical tracking for a site like https://accountlicense.ir/ requires confusing workarounds. Are there any plans to support customized tracking portals for digital-only products in your roadmap? Thank you!

The current OpenGraph meta preview generated by AfterShip's referral link system is unacceptable. We run a professional e-commerce business in South Africa selling premium seat covers, yet the influencer link preview looks like a child’s sticker book. Confetti, a USD coupon graphic, and a generic "Get special offers" line? Completely irrelevant, off-brand, and frankly embarrassing when shared by influencers. This isn’t just a design problem. It reflects poorly on our business when our partners share this link on Facebook and social platforms. It gives the impression of an unprofessional or scammy brand — damaging our credibility and costing us leads. We don’t even use USD as our currency. Why are you pushing American coupon-style banners to international stores?

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.