Build better products with our product team
Need a way to filter/report/export all shipments based on the actual shipping account used. Backend billing and financial reporting is based on the shiping account used and we need to be able to monitor shipments made on each account - whether 3rd party, shipstation or internal ups/fedex accounts.
Hello, I’m currently using Rate Shopper, but I’m finding the rules a bit limited. The basic options—choosing the cheapest rate or selecting a “Preferred” carrier within a certain amount or percentage—work fine, but they don’t fully meet my needs. Ideally, I’d like the option to choose the second cheapest rate instead of using the “Preferred” option when I don’t want the cheapest one. It would also be helpful to apply additional conditions, such as different rules for residential vs. commercial deliveries. Is there a way to configure something like this? Thanks.
Hello,For orders that are created through imports, we would like all associated information to be available when exporting from the shipment side of the process.For example, “custom Fields” are successfully generated and visible within the Orders section. However, when exporting shipment data, we are currently unable to include those same custom fields alongside the SKU information.Could you please advise if there is a way to include imported custom fields in shipment exports with SKUs, or if there are any recommended workarounds?
In the balance report in the list of transactions, it would be helpful to filter by type, and then for the adjustment details to be exported into .csv Current process is to look up this report, click into each individual adjustment ID, copy the tracking number into a spreadsheet, then look for that tracking in ShipStation to identify the order, and then record which customer to charge the adjustment to. It would also be helpful to know more details of the adjustment, to avoide adjustment fees in the future.
When you sort by tag in v2, your orders are secondarily sorted by order number. This make sense and is good function. When you sort by tags in v3, your orders are sorted by that specific tag however they are in a completely random order. Not by age, order number, etc. There is no rhyme or reason to the sort. v3 should be an upgrade over v2, this functionality should be easy to implement. There isn’t a use case where the current set up is beneficial in any way.
Currently, the <img> tag does not function outside of product images. Please add the ability to customize packing slips with more HTML elements including custom images.
The V1 Shipstation API passes the Payment Method from the ecommerce store, which is critical for correctly capturing how orders were paid in a connected ERP / business system.This same field is missing from the V2 API and should be added back in. I have had to resort to adding a custom tag or custom field via a ShipStation Automation rule so the the V2 API can pass the payment information to my ERP.
Hi ShipStation community, I'm Kevin, co-founder of Be Healthy, a French based brand in the health supplements space. I'm posting this feature request because Colissimo PUDO (Pickup/Drop-off) support is a critical missing piece for any merchant operating in France. The ProblemColissimo — operated by La Poste, France's national postal carrier — is the dominant shipping solution for French e-commerce. A large share of French consumers actively prefer home delivery alternatives: they choose a pickup point (post offices, local retail partners, lockers) at checkout rather than receiving parcels at their door.The issue is that ShipStation currently does not support Colissimo PUDO services. Attempting to create a label for a PUDO order in ShipStation returns the following error:> *"Le code ou l'adresse point de retrait n'a pas été transmis."*> (Translation: "The collection point code or address has not been transmitted.")This is a hard blocker — not a workaround-able edge case. Why This MattersFrance is one of the largest e-commerce markets in Europe. Colissimo PUDO is not a niche feature — it is a baseline expectation for any merchant selling to French consumers. Without it:- Orders where the customer selected a pickup point at checkout cannot be fulfilled through ShipStation- Merchants are forced to manage PUDO orders outside of ShipStation entirely, breaking automation workflows- It pushes French merchants to evaluate OMS alternatives that do support this natively (Shippingbo, SendCloud, Boxtal)I've personally spent significant time trying to find a technical workaround via the ShipEngine API (`ship_to_service_point_id` endpoint), Make automations, and Shopify metafields — without success. The limitation is at the carrier integration level, not something that can be patched client-side. What We're Asking ForNative support for Colissimo PUDO in ShipStation, specifically:1. Transmission of the pickup point ID (`locationId`) to Colissimo's API when generating a PUDO label2. Ability to read the selected pickup point from the Shopify order (already stored as a metafield or order attribute)3. Display of PUDO-eligible Colissimo services in the ShipStation UI without generating errorsThis is technically feasible — Colissimo's API fully supports PUDO label creation. The gap is on ShipStation's side in passing the required parameters. Community AskIf you're a French merchant or work with French carriers and have hit this same wall, please upvote and comment. The more visibility this gets, the better the chance of it making it onto the product roadmap.Thanks for reading — happy to provide more technical context if useful for the product team. KevinBe Healthy
Hello,I’m a seller using your platform, and I wanted to share a feature request that I believe would add significant value for users.It would be extremely helpful if ShipStation could track profitability per product, including how much sellers make on each item after shipping costs, fees, and other expenses. In addition, having built-in tracking for returns, refunds, and overall product performance would make the platform much more powerful for business insights.Right now, many sellers have to rely on external tools or manual tracking to understand their margins and return rates. If ShipStation offered these features directly, it would not only improve efficiency but also attract a large number of new customers looking for an all-in-one solution.Thank you for your time and consideration. I appreciate the work you’re doing and hope you’ll consider adding these capabilities in the future.
I’m a TikTok Shop seller and recently received a violation where I’ve been asked to provide an agreement with a carrier. I wanted to check if it’s possible to obtain such a document from your side.I have already shared shipping labels, invoices, and screenshots of my ShipStation account as proof, but they were not accepted—likely because these violations are handled by AI, which doesn’t fully understand explanations or context.When I contacted Shipstation support, they suggested I share this feedback so it can be considered by the internal team. Unfortunately, my verification was not successful, and I would like to help prevent this issue from happening to others.In my opinion, it would be very helpful if ShipStation could provide an official agreement or document confirming that our labels are authentic and that we are actively using ShipStation services.Please let me know if such a document is available or if you can guide me on how to proceed.Thank you.
Multiple inventory sync configurations are vital for international sellers.For example:Amazon.com FBA => US MarketplacesAmazon.co.uk FBA => UK MarketplacesAmazon.eu FBA => EU MareketplacesI wish Shipstation would implement this.
We'd like to show our customers that we're proactive when it comes to product traceability. To do this, we want to include inventory lot information on our packing slips.Currently, lot info is available on pick lists but not as a field on packing slip templates. The only workaround is manually importing lot data into an unrelated field (like Fill SKU), essentially repurposing it. And every time a lot changes or is added, we'd have to re-import that data.It would be much easier if lot information were simply available as a field on packing slip templates, the same way it is on the pick list.
When allocating inventory, there are sometimes errors because the chosen location doesn't have the enough qty or something similar. In this case an error message pops up calling out 3 skus at a time even if there are more. It would be great if the allocation process just skipped the lines with errors and allocated the restin the same process, if an allocation job is already under way, I shouldn't be allowed to click the “allocate” button until that job is complete. Right now when a job is in process, I am allowed to click the button again, which I have don't not knowing a job is in process, but I end up getting A “system Error” which doesn't go away even after I go into the order individually nad successfully allocate the inventory
When allocating inventory, there are sometimes errors because the chosen location doesn't have the enough qty or something similar. In this case an error message pops up calling out 3 skus at a time even if there are more. It would be great if the allocation process just skipped the lines with errors and allocated the restin the same process, if an allocation job is already under way, I shouldn't be allowed to click the “allocate” button until that job is complete. Right now when a job is in process, I am allowed to click the button again, which I have don't not knowing a job is in process, but I end up getting A “system Error” which doesn't go away even after I go into the order individually nad successfully allocate the inventory
Orders → awaiting shipmentI want to export package information at the Ship from location but the export doesn't have the option to add ship form location as a field. Just adding that one field will make analytics SO much easier
There is an Action Type to "Enable Saturday Delivery", but to use this action well, we need a criteria that basically says "If today is Friday and ______ premium shipping service was selected". I understand this may be difficult because you'd constantly need to check the date and reprocess the rule, so perhaps this is something that is triggered when doing the create and print label command? Or if that's impossible, perhaps the ability to say "if order date is between Thursday 3pm and Friday 3pm" or something of that nature to dial in on which orders will generally be shipped on a Friday, so we can selectively add the Saturday delivery option to orders that a customer has requested a shipping service where they expect it will be delivered on a Saturday.Since this option doesn't exist, we have to either pay the extra $15 Saturday delivery charge every order, or else manually enable it for certain orders when shipping out on a Friday. Usually this results in very angry customers because we forgot to check the box. My business sells parts that fix peoples' cars. They're not happy when they don't get their parts on Saturdays and have to miss work Monday because of a checkbox ><
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK