Share your ideas with us

As a business owner, having precise accounting records is essential for tax purposes. It's particularly important to account for returns correctly by adjusting for them and deducting the relevant taxes to prevent overpayment.   I've observed that Shopify currently only accommodates refunds, lacking store credit or exchange options for returns. Therefore, if aftership Return could support all three options and assist in reconciling taxes and producing accurate tax reports for returns, it would greatly benefit our operations.

Suggestion: Add Lazada Express (LEX MY / LEL) Support for Malaysia   Hi,   I would like to suggest adding Lazada Express (LEX MY / LEL) as a supported courier/carrier on your app and website.   Lazada Express is the official delivery courier used by Lazada in Malaysia, similar to how SPX Express / Shopee Express is the official courier for Shopee. Many Lazada shipments in Malaysia are handled by LEX, so having direct tracking support would be very useful for Malaysian users.   The official LEX Malaysia tracking website is: https://lex.com.my/   For testing purposes, you can use these example tracking numbers:   LXST191548638MY MYMPA257159996   I hope you can consider implementing Lazada Express (LEX MY / LEL) support soon. As Lazada is widely used in Malaysia, I believe many users would appreciate being able to add and track their LEX shipments directly through your app and website instead of having to visit the LEX website separately.   Thank you for considering this suggestion. I hope LEX MY support can be added in a future update!

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.

I would like to view the chart showing reasons for late shipments in the current on-time report that I am using.

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. 

We want to refer to the customer's username when packing the order. Right now, to do this, we need to download the tiktok orders, connect them to the shopify order number via the tiktok order in the notes field and then connect that to the order number in shipbob.   If we had the username in shopify, we could eliminate the step where we have to connect tiktok to shopify.

在英语版本下，缺货订阅按钮会正常显示：https://eu.elegoo.com/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588 在法语及其他语言版本下，缺货订阅按钮未显示：https://eu.elegoo.com/fr/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588

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.

Currently OTD report, reports the complete journey so the avereage time can fluctuate based on how long it takes for customers to collect their order.  We need to report on the carrier performance and then the time it takes to collect.  It would be good to have  a PUDO report that breaks down : average transit time to collection point   Average time waiting for collection    If we expand our PUDO options in Europe it would be a good indication 

Good morning, When viewing notification emails on a mobile device, the background colour only appears at the top as a small strip. As a result, the background colour on the sides and beneath the email is completely lost. I therefore propose hiding the background area entirely on mobile, displaying only what is within the content background, which is the main body of the email. Thank you.