Share your ideas with us

I guess for shipping emails sent out to my customers, it would be nice to have dynamic info that updates as the package progresses through the network. I also want all my existing emails to stay current.   The reason is simply that I wanna give my customers a unified experience by delivering consistent messages to them. I believe this will help with my customer satisfaction.

I am using the API for Zoho Inventory integration with Aftership. I would like the items on the shipping order of Zoho Inventory displayed on the shipment items of the email notifications to my customers. The shipments are created within Zoho Inventory and tracked by Aftership.

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.

We are able to retrieve shipping rates for each carrier, but we would also like customs clearance fees and other charges available through each carrier’s API to be integrated via API as well. This is especially important for DDP shipments. Some information that can be retrieved through the carrier APIs cannot be retrieved through AfterShip, which means we would need to connect to each carrier’s API separately.

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.

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. 

Instead of directly integrating Aftership with Gmail, I would like to send my emails with package information to an aftership email address associated with my account, for aftership to parse and automatically show tracking information. 

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.

As online shopping continues to expand, cities and businesses are looking for ways to simplify last-mile delivery. In this shift, automated parcel lockers have become a practical solution, helping reduce missed deliveries and improving convenience for both couriers and customers. Their use is steadily shaping the future of contactless and efficient package management.

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.