Share your ideas with us

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.

Goal: To make it easier for customers to accurately select the correct item for return when using the return portal. Preconditions: The customer has placed an order containing multiple items, some of which may have similar or identical titles, colors, or sizes. The SKU numbers for the items exist in the system but are not currently displayed in the return portal. Trigger: The customer initiates a return and accesses the return portal to select the item(s) they wish to return. Basic Flow: The customer logs into the return portal. The portal displays the items from their order, including details such as title, color, size, and now the SKU number for each item. The customer uses the SKU number to cross-reference their order confirmation or invoice, ensuring they select the correct item for return. The customer completes the return process with confidence that the correct item has been selected. Postconditions: The customer successfully returns the correct item without confusion. The support team receives fewer inquiries about mismatched returns. Benefits: For Customers: Improved user experience by reducing confusion when selecting items for return. Greater confidence in completing returns independently. For the Business: Reduced customer support requests related to returns. Increased efficiency in processing returns, minimizing errors caused by incorrect item selection. Priority: Medium – This enhancement has a high potential to improve customer satisfaction with a relatively low implementation effort. Technical Requirements: Modify the front-end display of the return portal to include SKU numbers as part of the product details. Ensure the SKU numbers are fetched and displayed consistently across all customer orders. This use case focuses on enhancing the clarity of the return process for customers while streamlining operational efficiency for the business.

When exchanging a product, you have to pick from a list of products, sorted by the most recently created products. There's no search facility. This is particularly problematic when you have an old sku that comes in every season and it is buried deep in the list

Currently, I can only choose from 3 resolution options in Warranty admin: Repair item, Replace item & Other. At the end of the day, I need to manually export a list of Warranty claims and see how many store credit resolutions were recorded. (By using the “Other” option with a note.) This process is very time-consuming and inefficient.    It would be very helpful if a direct "issue store credit" feature were integrated, potentially automating the process across platforms like Shopify.

Please let me hide the ad carousel, I am happy to pay subscription or whatever to disable it. Thanks 

I am utilizing Smile to develop the Reward program for our business. This year, I aim to motivate members to increase their reviews by integrating Reviews into the reward system as bonus incentives. This will allow our members to accumulate extra points by sharing feedback for their purchases.

We are a worldwide dropshipping service catering to e-commerce entrepreneurs. Merchants can design and market personalized products through us, setting prices and choosing their sales platforms from our integrated e-commerce options.   Once merchants place orders, we will handle the manufacturing, fulfillment, and shipping logistics to consumers.   When I am using Aftership for tracking, I want to enable my premium customers (merchants) with the ability to customize white label branded tracking pages and possibly an API to create them (since they won't have access to Aftership admin, and it would be impossible for me to maintain all tracking pages for them).   So that I can add this ability as part of the product & service package for my main customers (merchants), which creates more value for my business.

Add the option to pay online ~ $2 at checkout for free returns and extended warranty later.    Add tags to people / allow different RMA flow for those who optin to this. 

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 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.