Skip to main content

Filter by idea status

Filter by product

2599 Ideas

Option to bulk update warehouse locationsNo Status

In the products tab of ShipStation, when you update a location on an individual SKU, there is a check box at the bottom that you can select to apply that new location to all orders that currently exist in ShipStation. If a location is updated and that check box is not selected, then the orders in “awaiting shipment” in SS will maintain the location that existed for that SKU when the order was first received in SS. If that check box is selected for that individual SKU, then all orders will reflect the new location.This is GREAT! However, we fail to see a way to do this on a mass scale. If we move an entire product line from aisle 10 to aisle 20 and need to update the location for all 56 SKUs, we use a file import to update all locations at the same time.Can ShipStation do one of the following? Either (1) have the product import routine  apply the new Warehouse Location value to any unshipped orders that already exist when the "Update product information if the products already exist" option is selected, (2) Add an import option that just has SKU and Warehouse Location and make updating the pick location for items on open orders a standard part of that "Location import" process, or (3) Rather than assigning the Warehouse Location to the SKUs in an order when the order arrives in ShipStation from the channel, have the lookup of the picking location occur as part of the pick list printing procedure.

Lily_h
Lily_hEmployee

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

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!

Add an opt-out for estimated duties & taxes on batch totals and column views (BYOA)New

For BYOA (bring your own account) sellers, ShipStation now displays an estimated duties and taxes line on any shipment where duties/taxes are billed to the payor. It appears in batch summaries and column views, it is enabled by default, and there is currently no way to hide or remove it. Support confirmed this is a known limitation with no opt-out.The request: add an account-level option to exclude estimated duties and taxes from batch summary totals and column views.Why it matters, specifically for the batch total. Many of us review the total shipping cost across a full batch before committing labels. That review is a cost-verification step, not a convenience. The estimated duties line inflates that total with a figure that is never actually billed (ShipStation has confirmed it does not calculate, collect, or settle these fees, and labels still purchase at the base carrier rate). Because the estimate varies per parcel, it cannot be cleanly subtracted to recover an accurate number. On large pre-order runs, where a batch can contain thousands of parcels, this removes our ability to sanity-check batch cost before purchase.For sellers whose goods are duty and tax exempt, the estimate adds an inaccurate value to every applicable line with no informational benefit at all.Keeping the feature on by default is fine for sellers who want it. The ask is simply a toggle for those of us it does not apply to, so the batch total reflects actual label cost.