Skip to main content

Filter by idea status

Filter by product

2614 Ideas

eduardo123
eduardo123Employee

Add GoFo Express / YunExpress to carrier recognition — YT... tracking is sent to Etsy as "Other" and orders freeze at Pre-TransitUnder Review

What I'm asking forPrimary request: add GoFo Express and YunExpress to the carrier list ShipStation uses to recognize tracking numbers, so that YT... tracking resolves to a real carrier name instead of falling through to "Other."To be clear about scope, because I think this gets confused with a different request: I am not asking for a rate/label integration. I don't need to buy GoFo labels inside ShipStation. I only need ShipStation to recognize the tracking number format and pass a valid carrier name to the marketplace on fulfillments that were marked as shipped externally.Fallback request, which would help far more people: let merchants set a custom carrier name and a custom tracking URL on a Marked-as-Shipped fulfillment — via the UI, an automation rule, or the markasshipped API. That single field would fix this for every unlisted carrier, not just these two. What happens todayI run Etsy shops fulfilled through a partner that marks orders shipped in ShipStation via the markasshipped API. ShipStation then forwards the tracking to Etsy.ShipStation resolves the carrier by matching the tracking number's format. When the format matches something in its list, everything works — the Fulfillments grid renders a clickable tracking link, and the marketplace accepts the update.When the format matches nothing, the row renders as plain text with no link, the Service column is blank, the Carrier column shows a question-mark icon, and Cost is blank. ShipStation then sends the marketplace the carrier value "Other" — and Etsy cannot validate an unrecognized carrier, so the order sits at "Pre-Transit" forever. The buyer sees a tracking number that never moves, even after the package is delivered.YT... numbers (GoFo Express / YunExpress last mile) match nothing. The comparison that isolates the causeThis is the part I would ask the product team to look at, because it rules out the usual explanations.From a single page of my Fulfillments grid — 250 records, ship dates 08/28 to 09/02/2026:YT... (GoFo / YunExpress): 131 records, 100% destined to the United States. Do not resolve to any carrier. All stuck at Pre-Transit on Etsy. 92... (USPS) and LX... (PostNL): 49 records, also destined to the United States. Resolve correctly. All update normally on Etsy.Same account. Same destination country. Same Mark as Shipped workflow. Same marketplace. The only variable that differs is the tracking number prefix.Other formats in the same account that resolve correctly, for reference:SE... resolves to Intelcom LX... / UT... / ZK... resolve to PostNL 92... resolves to USPSThose all update on Etsy without any problem. Example of a failing record (tail masked for privacy — full order/tracking pairs are in my support ticket): order 41628999xx, tracking YT26402214371927xx, batch 100904, shipped 09/02/2026. Confirmed by ShipStation Support — ticket #10145586A support agent confirmed the following in writing, which is why I am bringing it here instead of continuing in the ticket:When a fulfillment is marked as shipped with a tracking number ShipStation cannot match to a known carrier, the carrier field sent to Etsy is the literal string "Other" — not an empty value, and the field is not omitted. The markasshipped endpoint does not support passing a custom or unrecognized carrierCode that would be forwarded verbatim to the marketplace. If the code is not in ShipStation's catalog, it still resolves as "Other." The recommended path to get a carrier added is a formal request here, where the product and carrier-integrations teams can see it and other merchants can upvote.So there is no workaround available to a merchant. The fix has to happen on ShipStation's side. What I already ruled outBefore posting, I checked every surface in my account:Mark as Shipped, Carrier dropdown. No GoFo entry (the list runs GoBolt, Gophr, Grupo ampm) and no YunExpress (the list ends at Yamato). Selecting "Other" exposes no free-text carrier field and no custom tracking URL field. Settings > Shipping Carriers > Add Carrier. Searching "gofo" and "yun" both return "No results found." Settings > Fulfillment Providers. Nothing applicable. Automation Rules. No available action can set a carrier name or a tracking URL on a Marked-as-Shipped fulfillment. The API. Closed by support, per point 2 above. Upgrading the plan. A higher plan grants carrier integrations for purchasing labels. GoFo and YunExpress are not on that list either, so upgrading does not solve it. Why this mattersEtsy requires tracking that shows delivery progress to keep Purchase Protection coverage and Star Seller status. An order frozen at Pre-Transit counts against both, and it generates "where is my order" messages on packages that have already been delivered. This is not cosmetic.For scale: roughly 900 fulfillments a month flow through my account, and that climbs sharply in Q4. In the sample above, 131 of 180 US-bound shipments — about 73% — were affected. If this affects you tooYunExpress and GoFo are widely used for cross-border last mile into the US, so I doubt I am the only one. If your YT... tracking is also landing as "Other," please upvote and add a comment with your marketplace — the more marketplaces this is shown to break, the easier it is to prioritize.And if you ship with any other carrier that is not in ShipStation's recognition list, the fallback request above (a custom carrier name and tracking URL field on Marked-as-Shipped fulfillments) would solve your case too. Worth upvoting on that basis alone.

mark35
mark35Employee

Export to csv format "Adjustment ID" detail in "Carriers"-Example: UPS thru ShipstationUnder Review

Settings>Shipping>Carriers>Carrier>USPS>Actions>View Report> Selecting Transactions and Balances. Then Export data. In the exported data under field “Type” shows on the word “Adjustment”. There is no way to link this data to orders in Shipstation. I was told by TechSupport that this is not available.We have a customer that we have to send chargebacks to for UPS adjustments. There are many. At this point now we have to manually click on each “Adjustment ID” on the screen readout, then a popup opens with data, then copy the tracking # then go back to shipstation from Stamps.com, then to Shipment>Seach>paste in tracking number. If there are a lot which we do have. We could create a spread sheet file (table) and place it into Libre Office and then export all order detail (item level) and then send the exported csv file to Libre Office then link the two files together, then do a view showing the order detail of the adjustment ID transaction. However, there will be no adjustment data with it. We have to go to stamps.com create the onscreen list and then click on each and every adjustment id and copy and paste all of the data in the adjustment into their respective fields in each record representing the adjustment ID in the spreadsheet created in Libre Office. The only other way to do this would be to call up each and every adjustment as a popup and try and find a very high performance OCR program (optical character recognition) hoping it will actually read the data in the adjustment popup and send the data to each individual field in the record representing each of the adjustments.Now when you have 70-100 adjustments that have to be copied pasted by hand it gets extremely time consuming. This should be a priority. I don’t understand why this is not an already available export.The only alternative to this copy/paste is asking Shipstation tech support to create the report each time which is fine but it really should be available on demand as an export feature.Thank you for reading this and I hope this happens soon.Mark  

Lily_h
Lily_hEmployee

Urgent Feature Request: Expand Customs Fields for UK-to-US Shipping Compliance (US Customs Regulations)Under Review

Hi everyone, I have been a long-time ShipStation user shipping from the UK to the US. I am writing to urgently request an upgrade to ShipStation’s customs data mapping and field limits. Following the stricter US Customs regulations, international shipments now require exhaustive product data to clear customs smoothly. Unfortunately, ShipStation’s current platform limitations are making compliance nearly impossible without manual workarounds that risk customs delays. I have actually had to move my business away from ShipStation due to these feature limitations, but I would be very happy to move back if you can improve the platform. I am asking the product team to address the following limitations: • Character Limit on Product Descriptions: The current 50-character restriction is far too short to provide the detailed descriptions now mandated by US Customs. We need this field expanded to allow as many characters as possible. I can send a carrier commercial invoice template created from another platform if that helps show what is required.• Net vs. Gross Weight Mapping: ShipStation only supports a single weight field. On carrier commercial invoices, this results in one weight showing accurately while the other defaults to zero. This discrepancy causes immediate confusion for customs officers. We need separate, clear fields for both Net and Gross product weights that map correctly to carrier invoices.• Packaging and Pack Sizes: There are currently no dedicated fields to input packaging details, pack sizes, packaging materials, or packaging weight information for customs declarations.• MID and Manufacturer Details: The Manufacturer Identification (MID) code field does not reliably transfer onto all carrier commercial invoices, and there is no structured space to provide full manufacturer names and addresses. While customer support suggested uploading supplemental PDF/PNG documents, doing so creates massive data contradictions. If a supplemental document lists both weights, but the ShipStation-generated commercial invoice shows a "0" for one of them, it flags the shipment for inspection. As international sellers, we need a basic, compliant data-mapping structure built into the platform—not temporary workarounds. Please lift the character limits and add proper net/gross weight and packaging fields so we can continue shipping to the US without friction. If anyone else is facing these customs hold-ups, please upvote and comment to get the product team's attention!