Share your ideas with us

1. What is the context?  * We are currently a Premium plan subscriber operating a high-volume merchant shipping 68% of our Canadian orders via GLS Canada. We are looking to utilize the Enhanced MPS Visibility feature to improve our customer experience.   * Currently, your documentation lists carriers like FedEx, UPS, and DHL as supported for MPS, but GLS Canada is excluded. When we contacted support, we were told this is due to "carrier limitations.   2. What issue do you want to address? We believe the "carrier limitation" rationale may be outdated or incorrect because AfterShip is already successfully pulling data for GLS child packages. * Evidence: On GLS Canada tracking number P97186751, AfterShip retrieves events for both Package 1 (Delivered Nov 21) and Package 2 (Delivered Nov 19). * The Problem: Because GLS Canada is not on your "Supported Carriers" list for MPS logic, your system aggregates these distinct events into a single "scrambled" timeline instead of separating them into tabs. * The Gap: The data exists in your system; the parsing logic to separate "Master" vs. "Child" is simply missing for this specific carrier. 3. What outcome do you expect? * We request that the product team add GLS Canada to the Enhanced MPS Visibility supported carrier list * We need the system to recognize the child packages it is already detecting and display them in separate tabs (Piece 1, Piece 2), just as it does for FedEx or UPS.   4. Who will benefit from your idea? * Merchants: This allows Canadian merchants to use your Enterprise MPS features for their dominant carrier, reducing support tickets regarding "confusing" status updates. * AfterShip: It improves the value of your Enterprise plan for the Canadian market by supporting the region's major logistics provider.

Hi, The data when the shipment is created at the carrier is important for shipment analysis. Example:  Info received   Shipment information received DHL Express Mar 25, 2025 at 12:01 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!

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. 

To enhance the shipping experience for customers purchasing hair extensions or hair care products, AfterShip could focus on providing real-time tracking updates that are both detailed and easy to understand. For the hair industry, ensuring timely delivery is critical, as customers expect to receive their products in a timely manner, especially for events like weddings, parties, or other special occasions. Additionally, offering automated notifications at each stage of the shipping process — from dispatch to in-transit updates and delivery confirmation — would allow customers to stay informed and reduce anxiety around the arrival of their products. A specific feature that would be beneficial in the hair industry is providing an estimated delivery window based on the type of hair products purchased, considering how delicate and time-sensitive hair products can be. Another improvement could be offering customized delivery options, like express shipping for urgent orders or delivery tracking tailored to customers’ needs based on their location, enhancing convenience and customer experience. By integrating these features, AfterShip could help ensure a seamless experience for customers in the hair industry, driving satisfaction and repeat business.

Consider leveraging Estimated Delivery Dates for Return Shipments as a column on the Returns Dashboard

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.

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.

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.

Honestly, this would help us to ease our shoppers through possible delays proactively.