Share your ideas with us

As a business owner, I am seeking a system that can facilitate risk level scoring for each RMA (Return Merchandise Authorization) and enable my staff to input risk assessment findings based on actual RMA inspections. This system will enable us to assess risk levels effectively and respond accordingly. Moreover, the system will allow for the reporting of any detected fraud instances.   Implementing this system is crucial for mitigating fraud occurrences, as well as proactively preventing future fraudulent activities. Such measures are instrumental in safeguarding my business's profitability in the long term.

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.

Title: Feature request: Claude MCP connector for AfterShip Returns AfterShip Returns should offer an official Claude MCP connector. Claude already connects to Shopify, Gmail, Slack, and Google Drive, so many merchants run their daily operations through it. Returns data is the missing piece. Without a connector, teams still have to open the portal, find the return, and copy details into customer replies or reports by hand. A connector would make it possible to ask questions like: “What’s the status of the return on order #1234?” “Which returns from last week haven’t been refunded yet?” “What are the top return reasons this month?” “Which SKUs have the highest return rate?” Why it should be added: Faster customer service. “Where’s my refund?” emails could be answered in seconds using live return data. Fewer errors. Order numbers, tracking, and refund amounts would come straight from AfterShip instead of being copied manually. More accessible reporting. Small teams without a dedicated analyst could get insight from return data in plain language. A connected workflow. Returns would link up with the order, email, and team tools merchants already use with Claude. Keeps AfterShip central. As more operations move through AI assistants, the platforms that connect to them become the ones merchants depend on. Read-only access would be a strong starting point: return lookups, statuses, reasons, and refund/exchange outcomes. Actions like approving or rejecting requests could follow later, with confirmation steps built in.

I want to be able to show values and total value of anything that is currently in transit, out for delivery and delivered so i can manage my insurance process of total value out at a given time 

We use this to ship to clients it would be nice if we could save clients within the system to send notifications to. 

Enable merchants to customize the duration before an RMA is automatically canceled. Currently, the system only allows for auto-cancellation after 28 days of inactivity. To better suit our company's needs, we would like the option to extend this period.

The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page. 

Would love to see carrier support added for MyPost Business by Australia Post.  This is already an integration in ShipStation, Starshipit and Shopify - it would be a valuable addition to Aftership Shipping and Aftership Returns.

Like to set their own “Image not found” image for Products in the Returns Portal. That way, If a Product is not sent to AfterShip with an Image URL, they have an image that looks more branded.   Today, when an item does have an img url, the Return Portal defaults to the missing image icon.   Request - have a function within Return Portal where if any items on my return portal dont have an image URL, it can set to a image that I select instead of defaulting to the standard broken/no image icon.

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.