Build better products with our product team
Would like an additional option in the “Confirmation” drop down for both UPS and Fedex packages to have “adult signature with valid ID” option that matches the name on the shipping label. What I mean is if John Smith is the name on the shipping label as the receiver, only John Smith can sign for the package with a valid id. Both the valid id and name on the label needs to match. We’ve had a number of fraudulent orders that we chose “adult signature” and the carrier just had anyone over 18 sign for the package. This has caused many headaches. Would like for this option to be implemented if at all possible. Thank you.
FedEx has just come out with a 2 day one rate extra small box. Could this be integrated into ShipStation?
Have Shopify's "Additional Details" and "Notes" sections import to different ShipStation fields! They are currently importing to 1 field in Shipstation, "Customer Order Notes". Currently, if an order in Shopify has any information stored in the "Additional Details" column of an order, that information is imported into Shipstation in the "customer Order Notes" Field. This is the same field that the Shopify "Notes" section imports to. Shopify businesses commonly use the Shopify "Notes" section for gift messages. So, when all this info is imported, you get a gift message + any data from the "Additional Details" column funneling all together in the same Shipstation field. This causes a huge headache for fulfillment and shipping teams that have to then manually separate a gift message from any other data that the import is capturing. Check out my images to see a live example.
Please allow users to map which fields in ShipStation the Shopify Notes and “Additional Details” fields map to. Currently both of these fields automatically map to ShipStation “Note from Buyer”. You should let users map to their desired fields! For example, let us map Shopify “Notes” to ShipStation “Gift Note” - that’s the whole purpose of this field. Furthermore, you have mandated a 2:1 mapping where both the “Notes” and “Additional Details” fields are mapped to the same 1 field in ShipStation (“Note from Buyer”) without allowing us to change that. I don’t want Additional Details to also map to this field. I was able to set up a Custom Field Mapping to allow Shopify “Additional Details” to map to ShipStation Custom Field 2 but it still repeats/duplicates/concatenates the data into “Note from Buyer”. These are basic functionality to run our business on Shopify and ShipStation and improving mapping capabilities should be a high priority for ShipStation. Thank you for considering.
With USPS now requiring all package dimensions to be recorded in the manifest, there should be a column so we can see if we have entered the dimensions. Without the column, I have to go through each order to check. This is very time consuming when I have a lot of orders.
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.
Hi- We often times have back orders but can ship partial shipments. Would love the ability for Shipstation to automatically split orders for us based on rules.
Please consider updating Settings to allow Admins to Turn Custom Field 1 and Custom Field 3 to be required.
Create an EMAIL alert when the re-order quantity goes below the set threshold
As instructed by Shipstation support, creating this topic to recommend adding the following feature: automatic syncing of recipient CPF/CNPJ from Shopify into ShipStation's Brazil label fields during order sync. This feature currently exists for Mexico, it would be great for it to be added for Brazil shipments as well, as Brazil customs will automatically refuse a parcel without this information. It’s a huge bottleneck in our workflow at the moment having to manually copy this info over from the order page on our online store each time and adding it in. Would also recommend seeing what other countries require this and if it can be automated for them too. cheers
I would like to suggest adding export functionality that would allow us to pull both order and shipment level data in one report. As it stands right now, we need to create two separate exports and merge the data in Excel to get the full data set needed.Order Data NeededCustom - Field 2Custom - Field 1Custom - Field 3Shipment Data NeededShip DateOrder NumberCompanyNameStreet 1Street 2CityStatePostal CodeCountry CodeTracking NumberSKUDescriptionQuantityCarrier FeeWeight OzStore NameRMA NumberService CodeLengthWidthHeightInternal Transaction ID
When we provide a discount to an order we don’t see the full break down with the discount only the total paid cost but not the new price for the product cost. It will helpful to have this implemented to have the breakdown so we are insuring the product with the new product price with the discount.
As of right now there is a carrier-level limitation within the UPS API that causes custom fields 2 and 3 to be merged when the data is sent. This creates a problem for invoice reconciliation because when our system scrapes the UPS invoices for our references, it's not able to find a match. The only workaround currently is to use only reference fields 1 and 2. This limits or ability to add special packing instructions on the labels for our warehouse team. It would be wonderful if all three reference lines could be passed to UPS individually.
the default Rate Browser pop-up window is fixed in size and cannot be expanded horizontally. Additionally, the carrier display settings within this view are defaulted by the system design to show the full carrier details rather than just the nickname. these options are not currently customizable,expanding the window or displaying only nicknames would improve visibility and streamline workflow.
We need ShipStation to support converting an existing standalone product SKU into a Store Alias of a specific nested Variant without restructuring the entire Parent group.Current case:- Target Variant: TSD2358-GREYCAMO- Existing standalone SKU to convert: 709257409214- Sibling Variant: Khaki CamoRequired behavior:1. Keep the Parent and both existing Variants active and unchanged.2. Deactivate the standalone 709257409214 product record.3. Add 709257409214 as an alias of TSD2358-GREYCAMO.4. Preserve historical order activity, open orders, inventory quantities, locations, allocations, warehouse associations, and product defaults.5. Provide a record-level preview before applying the change.Today, manually adding the alias is blocked because the alias value already exists as a product SKU. Combine Products also cannot safely target only the nested Variant because selecting the Variant pulls in the entire Parent group and risks the sibling Variant.This limitation affects inventory accuracy for merchants whose retailer order imports use UPCs or retailer-specific item numbers as SKUs. A supported Variant-only merge/alias operation, or a scoped pre-import normalization layer, would prevent duplicate product records and incorrect inventory deduction.ShipStation Support confirmed that no safe supported workflow currently exists and suggested submitting this as a product idea.
Very Frustrating! When someone orders with an automatic discount applied, it won’t change the declaration. I have to manually adjust EVERY SINGLE sale item for international orders. It is time consuming and if I miss one, I have to pay lot of extra money in duties! Please help!!
This enhancement would make it easier for warehouse and fulfillment teams to separate orders that have already completed the item verification process from those that still require verification. By adding a dedicated "Items Verified" filter, users could streamline fullfillment.
Thanks for launching LTL! Can you please provide support for LTL Carriers such as: XPO, ABF Freight, Estes, Roadrunner, and so on. This would help us to only use ShipStation for shipments.
I need the option to be able to turn off import Amazon package weight on the store setting just like we can turn off the package dimension. CC @CaraAdmin
It would be absolutely fantastic to expand the “Scan to Verify” feature so that it can verify a products lot code, not just SKU or UPC. ShipStation allows you to allocate lots to your orders, and even run a report and see all orders that were connected to a lot. Both of these features are fantastic, but it doesn’t mean much if the person picking the product cannot scan to verify the lot code of the product they are picking, as it then relies on the picker to get everything correct, which almost defeats the purpose of lot tracking if you’re not able to guarantee this is correct.I imagine the update to this feature would not need to be that expansive, as you are already able to scan to verify a UPC and SKU, which is just matching digits to what is already in ShipStations system. Expanding this functionality of scanning to verify lot codes would allow users to not have to seek 3rd party integrations and further expand their evergrowing techstack.Would really love to see this feature implemented.
We’d like to see the pickup location selected by the user when a pickup order is placed. At the moment the order page shows the billing address and ship to address, but we’d like to also see a pickup address chosen by the user when placing the order.This has been tested on Shopify.
We currently create customs declarations from order items in Ship Station, but we have a lot of items which have the same HS code.It would be useful if there was an option to automatically group items with the same HS code into a single line on the customs declaration. For instance, change:1 x birthday card1 x birthday card1 x christmas card1 x wrapping paper to:3 x greetings cards1 x wrapping paper Many thanks.
When changing the address for an order inside the UI, it locks the address so future marketplace syncs will not change it back to the marketplace value. But, when changing the address via the API, there is no way to lock it. So, changes will be overwritten on the next marketplace sync. Very frustrating and makes exposing address fields via the API almost like a red herring.This seems like a major oversight as I imagine many using ShipStation have at least an Amazon marketplace they sync with, if not multiple marketplaces. And often little things need to be fixed or standardized from what a customer entered (such as changing country from PR to US, moving data from street2 into street1, standardizing a phone number, etc).
It would be very helpful if the checkout rates provided through the store connection had support for conditions. In our case, we always insure any orders that exceed a certain value but the added cost of insurance cannot be provided through the store connection checkout rates. This means that for any high value orders we receive, we are footing the bill for insurance. If we could have a conditional for our checkout rates that basically says "If the order exceeds x value, add a flat fee of y dollars" or something similar that would suffice. If it actually calculated the added cost of insurance that would be even better.I believe this would improve the open-endedness of Shipstation and would benefit other businesses selling a diverse product lineup including products of lower and higher values.
When displaying your checkout rates in Shopify, the rates only display the lowest option not all the options. So for instance, USPS Priority Mail and UPS Ground are basically the same and yet it only displays USPS Ground because it is cheaper. But our customers have stated that they have no confidence in the USPS and would prefer UPS. Also, UPS provides insurance and more of a guarantee on their packages. We really need a way to display all the options not just the lowest priced option. So unfortunately this feature is useless to us. and we must use Shopify and have discrepancies.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
