Share your ideas with us

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

Filter ideas

Add ability to be able to upload separate Desktop and Mobile images for the returns tracking page

Jeremy Bobbitt
February 3, 2025 at 7:28 pm
Add the ability to upload a separate images for desktop and mobile header logos. An example of the what the UI could like like is below. Returns > Customizations > Returns page    
Accepted
0
0

Automated Restock

Daniel Kinsella
October 1, 2024 at 4:49 pm
Can we get an option to automatically restock the item based on resolution, not just when received. We still need to process, and inspect the item before we issue the refund, and we can't have our inventory adjusted upon recept. Thanks!
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

Api endpoint to fetch the review data

Nayan Solanki
July 21, 2026 at 12:33 pm
I see that Aftership is already having public api end points available for tracking and returns. i would like to have similar one for reviews.
Submitted
0
0

Eliminate Additional Fees for Carrier Integration – Improve Aftership for All Users

Mario Labault
March 3, 2025 at 10:20 pm
As a loyal Aftership customer, I am extremely disappointed to learn that integrating a new carrier requires an additional fee—a neither transparent nor customer-friendly policy. Carrier expansion should be a standard improvement to Aftership’s platform, not an extra cost passed onto paying customers. Why This Needs to Change: Improving Aftership Should Be Your Priority, Not an Upsell Adding new carriers benefits all Aftership users. Expanding carrier integrations should be part of Aftership’s ongoing development efforts, not a hidden fee imposed on individual customers. Hidden Costs Undermine Customer Trust Nowhere in Aftership’s pricing model is it clearly stated that carrier integration comes with additional fees. This lack of transparency frustrates users and creates an unexpected financial burden. Loyal Customers Deserve Better Customers who have trusted Aftership for their business operations should not have to pay extra to access a fundamental feature like carrier support. Proposed Solution: Aftership should eliminate extra fees for new carrier integrations and invest in expanding its platform instead of charging individual users. This would be part of its commitment to improving service for all customers. Clear, upfront disclosure of costs should be required if Aftership maintains this fee structure. If Aftership truly values its customers, this change must ensure a fair, transparent, and customer-centric experience.
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 Walmart Seller MCF as a Feed Connection

Megan Bailey
March 20, 2026 at 3:17 pm
Hello,  We currently use AfterShip Feed to connect our Amazon Seller account to TikTok Shop. But it would be fantastic to be able to also connect with Walmart Seller's MCF. It would allow even greater reach of products on more sales channels.
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

Shipments Header

Jana Churich
October 25, 2024 at 4:12 pm
Titles should update with count of items in the section so you know it's updating and should be clicked on. 
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