Skip to main content

Filter by idea status

Filter by product

2468 Ideas

facosta
facostaEmployee

Feature Request: Add "Package Dimensions" as Automation Rule Criteria + Require Dimensions Before Label CreationNew

Hi ShipStation Product Team,I'm requesting two related features that would prevent costly UPS Dimensional Weight adjustments for ShipStation customers:1. Add "Package Dimensions" as a criteria option in Automation RulesCurrently, dimensions are only available as an Action Type ("Set Package Dimensions"). There is no way to create a rule that detects when dimensions are empty or set to 0x0x0. We need a criteria option such as "Package Dimensions Equal Zero" or "Package Dimensions Is Empty" so we can conditionally hold orders, add tags, or create alerts when dimensions are missing.2. Add an account-level setting to require dimensions before label creationShipStation currently allows labels to be created with no weight and no dimensions entered. There is no validation or warning. For any customer using UPS (or any carrier that uses Dimensional Weight billing), this is a serious problem. We need an admin toggle in Account Settings that blocks label creation unless dimensions are populated.Why this matters:We use UPS from ShipStation (One Balance). When a label is created without dimensions, UPS scans the package at their hub and applies a Dimensional Weight adjustment — often significantly higher than the original charge. Worse, when we tried to dispute these adjustments through ShipStation's automated claim portal, we were blocked because the original label had no dimensions on file (0x0x0). ShipStation's own dispute tool requires dimensions to exist on the original label.So the current situation is:- ShipStation allows labels without dimensions- UPS charges adjustments on those labels- ShipStation's dispute tool then blocks the dispute because dimensions are missingThe customer loses at every step. This needs to be fixed.We were advised by ShipStation Support to create an Automation Rule to hold orders when dimensions are empty. After reviewing every available criteria option, we confirmed with support that this criteria does not exist. Support then directed us here.We are a multi-location restaurant chain shipping across 100+ locations and this gap has directly cost us money that we cannot recover. I'm confident other ShipStation customers using UPS are experiencing the same issue.Thank you for considering this. Happy to provide additional details or screenshots if helpful.Frank Acosta

Kevin B
Kevin BEmployee

Colissimo PUDO - a must-have for French e-commerceNew

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