Share your ideas with us

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

Filter ideas

Enhance the process of uneven exchanges for “Replace with the same item”

Sebastian Jenkins
March 18, 2024 at 2:36 am
As a merchant, I allow shoppers to exchange items for different variants during returns, which may have different prices. For example, a Small size costs $30 while a Large size costs $50.   Currently, Shopify allows me to adjust prices manually only after the Return Merchandise Authorization (RMA) is submitted. If aftership could facilitate charging or refunding price differences for variants during the return request process, it would greatly streamline our operations and enhancing the overall efficiency of RMA management.
Delivered
0
0

How Fast Delivery Impacts Customer Satisfaction for Heavy Equipment

Alex Liam
October 28, 2025 at 1:53 pm
Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.
Submitted
0
0

Shopify checkout for Returns

Victoria Ward
March 19, 2024 at 11:29 pm
As a merchant, I would like to charge the cost of return when the shopper chooses to replace the returned item.  aftership Returns provides Stripe checkout only for this scenario, but I don't have a Stripe account, I would like to use my Shopify checkout to charge the exchange upsell and cost of return. So that I don't have to open a Stripe checkout and manage two accounts (Shopify and Stripe checkout) at the same time.
Delivered
0
0

Returns Order Item Display - Customize Blocklist Error Message Based on Order Items

Jason Ma
February 13, 2025 at 9:45 pm
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.
Submitted
0
0

Pick up & BOPIS Tracking Enhancement

Jason Ma
February 3, 2025 at 5:40 pm
Related to BOPIS Track - set a Pickup deadline date and use it as a Merge Tag on Notifications.   Ideally, set a date and time expiration date so the end consumer know when they need to pick up their order. If the end consumer doesn't pick up their package before the expiration date, then cancel the order, notify the client and possibly refund the end consumer.
Accepted
0
0

UI in Greek language

Raúl Morales
June 15, 2026 at 1:32 pm
Hello,   We'd need User Interface in Greek language because we are selling in Cyprus and maybe in some months we'll start selling in Greece, so for us it's very important.   Thanks a lot.
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

Provide Cost of tracking as data in analytics

Ethan White
May 23, 2024 at 1:17 pm
The ability to see how much it cost per tracking label for the carrier, alongside all the other analytics would be beneficial to business operations.   Having “cost” as a piece of data collect and display in analytics will help us make larger business decisions when it comes to choice of carrier preferences to know which carrier is best to work with in the long run. I believe this feature will be great value add to Aftership as well!
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

Highlight which module/box is selected during RMA Request Flow

Jason Ma
January 31, 2025 at 7:01 pm
Items + return reasons are not clearly highlighted/shown as selected, during the Return Request flow on the RC portal.    Request: During the return flow more clearly define that an item/return resolution is selected. i.e. have text say “Selected” or have the box change colour when an item/resolution is selected beyond just the black box. 
Submitted
0
0