Share your ideas with us

Description: Aftership is a powerful tracking solution, but one major limitation is its inability to seamlessly track shipments handled by multiple carriers under a single tracking number. This creates gaps in tracking visibility, especially for cross-border shipments, multi-leg deliveries, or packages transferred between courier services. Why Aftership Needs ParcelApp Integration ParcelApp is a cutting-edge tracking solution that can consolidate multiple carrier updates into a single tracking number, ensuring a continuous, uninterrupted tracking experience—something Aftership currently lacks. Integrating ParcelApp into Aftership would provide several benefits: One Tracking Number, Full Visibility Many shipments pass through multiple carriers (e.g., a package starts with FedEx, then transfers to USPS). ParcelApp aggregates tracking data across different couriers, allowing customers to track their shipments without needing multiple tracking numbers or checking different carrier websites. Eliminate Tracking Gaps & Improve Accuracy Currently, when a package changes carriers, Aftership often loses visibility until the new carrier scans the shipment. With ParcelApp’s integration, tracking would remain consistent, even if the carrier changes mid-transit. Essential for Cross-Border and Dropshipping Businesses Global commerce relies on multi-carrier logistics. Many eCommerce sellers and dropshipping businesses depend on third-party logistics providers (3PLs) that transfer packages between multiple carriers before final delivery. ParcelApp ensures that customers don’t lose visibility just because a package has switched to a new courier. Enhanced Customer Experience & Reduced Support Inquiries When customers see tracking gaps, they flood support teams with "Where is my order?" questions. By integrating ParcelApp, Aftership can provide end-to-end tracking accuracy, reducing customer frustration and cutting down unnecessary support requests. Proposed Solution: Integrate ParcelApp (https://parcelsapp.com/) directly into Aftership’s tracking system to allow shipments with multiple carriers to be tracked under a single tracking number. Ensure that ParcelApp's multi-carrier tracking capabilities work seamlessly within Aftership’s dashboard, API, and branded tracking pages. Offer this as a standard feature for all Aftership users, as it enhances the core value of Aftership by improving tracking consistency, accuracy, and customer satisfaction. By adding this integration, Aftership would take a huge leap forward in solving a major pain point for businesses and customers alike, making it an even more indispensable tracking solution in the logistics and eCommerce space.

1. customer is NOT receiving any email from Aftership when a return has been received, refunded and resolved.  2. We are getting chargebacks from customers claiming they were not notified and advised a refund was on its way. 3. their bank (JPM) has sided with customers even though we have shown the ARP info from the return details.  4. An email advising of a received and pending refund would be quite helpful. 5. ALL other companies send these emails of pending refund, except Aftership/Shopify does not. 6. Its creating a lot of work and loss of revenue for our company. 

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 would like to view the chart showing reasons for late shipments in the current on-time report that I am using.

the only customization allowed is subject line and preview text for the reminder email, can't change the body copy of the reminder email.    benefit would be to add a secondary reminder of receiving loyalty points/an incentivization 

In our business we refund direcly in Shopify for our returns that are made from our online website. It would be nice if the status of Shopify shows refunded or partically refund that Aftership would show the return as resolved. Some of the tracking information has to be put in manaully and we have multiple people on our team and if they do not do it correctly our customers receive emails that their return was not send and is expiring when they have already been refunded. 

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.

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.

I hope to insert a form in the email, allowing customers to fill out the form directly within the email.   For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.

The background is that I sell my products on multiple marketplaces, and each has different return flows that the aftership Returns page cannot handle. It would be much easier if there is a Returns API that can meet my requirements below.   Need: - I need a Returns API to allow creating RMA/return requests without having to use the Returns Page to file it.  - I can call the API and pass the information regarding the Return Reason Resolution, etc in one go.  - Once I call this API, it will return creation in Pending or Auto-Approved Status.