Share your ideas with us

We value your insights on AfterShip products and features. Let's innovate together!

Filter ideas

Tracking by Account Number

Chris Nichols
November 6, 2024 at 10:34 pm
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.
Submitted
0
0

Link to Return Status Page from Admin & Shareable link to return status page for Customer Service

Jason Ma
February 3, 2025 at 10:10 pm
Would be a great feature if there was a link to the returns status page within the returns dashboard.   And if this link can be easily copied so we can share to the end consumer if they call through the contact center/help, then our agents can quickly copy the link and then email/share to the end consumer
Submitted
0
0

Add Placeholder

Luis Mateo
June 20, 2026 at 3:11 am
it would be great to be able to manually add a placeholder delivery in order to keep track of my deliveries.
Submitted
0
0

Enhancement Request: Advanced Customization for AfterShip Returns

Thomas Peigné
May 11, 2026 at 12:24 pm
Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.
Submitted
0
0

Saving Clients

Scott Williams
August 20, 2026 at 6:51 pm
We use this to ship to clients it would be nice if we could save clients within the system to send notifications to. 
Submitted
0
0

Support "not-for-sale products" listing

Henry Baker
June 15, 2024 at 10:47 am
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.
Accepted
0
0

Need fast access for copying customer information (Look at Shopify as an example)

Andrew Trousdale
November 19, 2024 at 7:16 pm
If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image:
Submitted
0
0

Ability to refund shipping automatically in the returns portal

Jeremy Bobbitt
February 3, 2025 at 8:19 pm
Currently you can manually refund the shipping fee in the admin manually, but would like the ability for it to be automatic.
Submitted
0
0

Please add tracking for Shipglobal.in

Ugo Grandolini
July 15, 2026 at 11:40 am
Hi,   I recently started buying products from India and sometimes they ship using : https://shipglobal.in/tracking/   Unfortunately Aftership is not yet supporting shipglobal.in and I need to use another app (actually 17tracks works) to track these shipments.   Please consider adding shipglobal.in as a supported career.   thank you!
Submitted
0
0

Publish Webhook Outgoing IPs as a Machine-Readable Plain-Text Endpoint

Martinho Dias
June 3, 2026 at 7:47 pm
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.
Delivered
0
0