Question 1

Can ShipStation rate shop across carriers automatically?

Accepted Answer

Yes. Rate Shopper pulls live rates from your connected carriers and applies the winner, using a Cheapest, Fastest, or Best Value strategy — or a custom configuration, where the account's plan includes it. ShipStation documents three ways to apply it: from an automation rule using the Set Rate Shopper action, from the Service drop-down on a single order, or in bulk across a selection of orders. It's more thoughtful than people expect. Service Preferences let a preferred carrier win when it's within a cost threshold of the cheapest. Delivery time constraints restrict eligible services by carrier transit estimate, counted in business days from the day after ship date. Available for US, UK, Canada, Australia, and New Zealand accounts; plan-gated.

Question 2

Can ShipStation pick a service based on weight and zone?

Accepted Answer

Yes, and it's the most common rule people build. Total Weight, Country, State, City, USPS Zone, order value and residential-versus-commercial are all available as criteria, and none of them carry the single-line-item restriction that trips up SKU-based rules. The limitation is in the data. The only zone criterion is USPS's, so a rule using it to choose a UPS or FedEx service is substituting one carrier's distance model for another's, and the thresholds you set encode the rate card as it stood on the day you priced it. Worth asking what a large weight-and-zone matrix is actually for before building one. It exists to find the cheapest service that still arrives on time, which is what Rate Shopper does — using the real weight, the real dimensions and the real address rather than an approximation of each. Unless Rate Shopper is unavailable on your account or region, the better use of the effort is configuring it against what the customer was sold at checkout. Weight and destination criteria keep their place either way — routing an order to the right Rate Shopper configuration, and driving the actions that were never service selection: insurance thresholds, confirmation, tagging for customs.

Question 3

Can rules react to which products are in an order?

Accepted Answer

Yes, via tags — and this is the most underused capability in the product. Tag a product record and ShipStation applies that tag to any order containing it at import, before any automation runs. Same for customer tags. Rules keyed to tags work on orders of any size. Tags also chain: a rule can apply a tag that later rules use as criteria, which gives you a workable classification pass followed by an action pass. Combined with order-level criteria like total weight, this covers most of what people initially reach for SKU criteria to do.

Question 4

Can ShipStation split orders into separate shipments automatically?

Accepted Answer

Yes, when the rule is a property of the product. Auto-Split creates separate shipments based on settings you configure per product: Exclusive Bulk Shipping, Ships Individually, or Ship on Custom Quantity. Exactly right for an oversized item that always ships alone, or products that ship a fixed number to a box. Plan-gated (High Volume for US/Canada/ANZ, Enterprise for UK/EU, or an add-on) and doesn't apply to manual orders.

Question 5

Can ShipStation choose which warehouse fulfills an order?

Accepted Answer

Yes. Auto-Routing determines fulfillment based on which warehouses stock the items and which is closest to the recipient. Available for US and Canada accounts on the High Volume plan. You can also set Ship From Location per store with a basic rule, if your routing logic is simply 'Shopify orders ship from the main warehouse.'

Question 6

Can ShipStation hold orders and flag exceptions?

Accepted Answer

Yes. Hold Until moves an order out of the queue until a date you set — the standard pre-order pattern. In accounts I work in the action also takes a number of days rather than a date, and offers an indefinite hold, though neither is documented. The relative option matters inside a rule: a fixed date holds every matching order until the same day, and once that day passes it holds nothing, silently. Rules can also create alerts, add internal notes, set custom fields, assign users, add insurance, and flag dry ice with a declared weight. The tag-and-alert pattern is genuinely useful for anything the engine can't decide: identify the order, flag it, let a person handle it. That's a legitimate automation strategy, not a failure.

Question 7

Can ShipStation add insurance to orders automatically?

Accepted Answer

Yes. An automation rule can add ShipStation's insurance partner to any order that meets criteria you define — order value, contents, destination, ship-from location, or anything else the rules engine can read. The rule runs at import like every other rule. Insure the Package is a standard action in the criteria and actions reference, and ShipStation ships a rule template for it on the Automation Overview page. The amount is the one thing the rule does not choose: it always takes the order's Amount Paid, which you can adjust by hand before buying the label. So the decision to insure is automatable and the sum insured is a default you accept or override.

Question 8

Can a packing slip carry the information a picker actually needs?

Accepted Answer

Yes, and it goes further than most accounts use. Packing slips are edited through a template editor, so the SKU, the product name, a variant description, a product image and the warehouse location can all print on the slip the picker carries. What it depends on is the product records being complete — the warehouse location in particular has to be populated before it can print. If your team batch-picks rather than working order by order, Pick Lists are the companion feature.

Question 9

Can ShipStation fill in customs declarations automatically?

Accepted Answer

Yes. ShipStation builds a declaration for every international order from the order's items, and fills it from three layers: account-wide defaults and tax identifiers in International Settings, category-level values on a Preset Group, and per-product values on each product's Customs tab. The rules engine adds six customs actions on top, including content type, non-delivery instruction, tax identifiers and who is billed for duties. Set it up once and international orders arrive with the form already filled. Two defaults are worth checking rather than inheriting: country of origin defaults to your account's home country, which is wrong for anything you import and resell, and discounted items keep the price the channel sent, which ShipStation states you must change by hand.

Question 10

Can ShipStation check that the right items went in the box?

Accepted Answer

Yes. Scan to Verify has the packer scan a UPC or SKU barcode for each item, gives audio and visual feedback, and marks the order Verified once every item and quantity has been accounted for. Combined with Scan to Verify and Print it runs straight through to buying the label. Set the matching preference under Settings, Shipping, Workflow Settings, and populate UPCs or Fulfillment SKUs on your product records — the CSV import does this in bulk. One identifier per product: ShipStation states Scan to Verify does not support multiple UPC codes or Fulfillment SKUs on a single product, so check that one code covers each item before you roll it out.

Question 11

Can I change the service or address after a label has been printed?

Accepted Answer

Not by editing it — ShipStation states that once a label is created it cannot be changed, so the route is to void it and create a new one. Voiding preserves the shipment record, returns the order to Awaiting Shipment, and sends a refund request to whichever postage provider sold the label. Two things decide whether it costs you anything. Refunds follow the provider's own policy and window — UPS from ShipStation will not refund a label unused for 30 days, and a USPS label already scanned will not be refunded at all. And ShipStation does not update the marketplace when you void, so the channel keeps the old tracking number unless you change it there yourself.

Question 12

Is ShipStation's address validation good enough to rely on?

Accepted Answer

For US domestic parcels, yes. ShipStation runs validation on every order shipping to or within a supported country and auto-corrects domestic and international addresses for those countries, and as of September 2026 it documents eleven such countries. US addresses are checked against the USPS database and the other ten against the Melissa database. It also improves the address rather than only grading it — a postal code comes back enriched to ZIP+4, for instance. There is nothing to configure and no third-party tool worth adding alongside it. Validation grades an address against a postal database. It does not decide how a carrier will classify that address for billing, which is a separate question with a separate answer. It also does not act on what it finds: turning a grade into a hold, a tag or an alert is an automation rule job.

Question 13

Does ShipStation validate international addresses?

Accepted Answer

In the application, only for the countries its Address Verification feature supports — eleven as of September 2026, including Australia, Canada, France, Germany, Great Britain, Israel, Italy, Norway, Spain, Sweden and the United States. Ship somewhere else and ShipStation documents the outcome as address verification not completed, because the country is not supported. The ShipStation API is a wider surface: it validates those same eleven and, in its own words, over 160 others. On that wider API surface the depth varies by country and the status does not, which is the part worth knowing. ShipStation's API documentation publishes a validation level per country, and a verified address on a City/Municipality country means the city and postal code exist and correspond — the street, building number and apartment were never checked. Look up the level for the countries you actually ship to before deciding how much weight the flag carries.

Question 14

Does an address validation warning stop me printing a label?

Accepted Answer

No. ShipStation states that warnings do not stop you creating a shipping label — they exist to bring something to your attention that might influence your shipping decision — while an error blocks creation and requires a change before you can proceed. Address verification sits on the permissive side of that line: a verification warning or error still lets you attempt the label, though the postage provider may reject it afterwards. Through the ShipStation API it is a choice instead. The validate_address property defaults to no_validation, which runs no validation at all; set validate_only or validate_and_clean and an address that cannot be validated returns an error and the label is not created.

Question 15

How do I create an alert in ShipStation?

Accepted Answer

With an automation rule. Two actions produce a notice: Create an Alert, which puts a message in the numbered alert list next to the profile icon with text and an expiry you set, and Send an email, which emails a named address when the rule runs. A third, Add a Tag, produces something to filter on rather than something to read. Most alerts are worth building as a tag plus one of the other two, because they reach different people at different moments. Alert text takes four field replacements — Store Name, Recipient Name, Order Date and Order # — and an Order # replacement renders as a link to the order. Dismissing an alert dismisses it for that user only, so the same alert is still waiting for everyone else.

Question 16

Can ShipStation alert me about a bad delivery address?

Accepted Answer

Yes, and it is the alert most accounts should build first. ShipStation validates every order shipping to a supported country and exposes the result as the Address Verified criterion, but a verification warning or error does not prevent anyone creating a label — ShipStation states that directly for both. The platform tells you and does not act, so without a rule the order ships to the bad address. Build it as two rules, not one. ShipStation documents that Address Verified cannot take multiple values in a single criteria line, so Warning and Error each need their own rule. That is convenient anyway: they are different failures with different owners.

Question 17

Can ShipStation alert me when stock runs low?

Accepted Answer

Yes, but not through an automation rule. Stock level is not one of the rule criteria. It is a reorder threshold, set account-wide in Inventory Settings or per SKU on the product record, and ShipStation raises a Low Inventory Alert plus a warning icon in the Products Inventory grid — orange at or below the threshold, red at zero — with an Alerts filter to narrow the grid to them. Inventory Settings separately decides what happens at the label. For a product with no on-hand stock or an unknown level, ShipStation can allow the shipment, allow it with a warning, or block it, and blocking prevents label creation outright. That is the strongest interlock in the product and it is off unless somebody set it.

Question 18

What can't ShipStation alert me about?

Accepted Answer

Three things, and each for a different reason. Package dimensions, because the rules engine has a Set Package Dimensions action and no dimensions criterion — it can write them and cannot read them. A shipping service cleared by the Charge Shipping to My Account action, because the service on the order is not among the criteria either. And how long an order has been sitting, because the criteria express dates rather than elapsed time. That third one is worth separating from timing. Classic rules fire once at import, but on accounts with the redesigned Automation Rules screen a workflow can run on a schedule — I have seen it on a handful of accounts and none of it is documented. What a schedule does not change is that no criterion expresses age. All three conditions are still visible: the Orders grid has a documented Age column, a Service filter and saved views, so these are things you look at rather than things that find you.

Question 19

How do I make a folder of certain orders in ShipStation?

Accepted Answer

ShipStation does not use the word folder. What you want is a saved view: filter the Orders grid, then click Custom View - Click to Save and name it. It becomes a tab across the top of the grid carrying a live count of how many orders match, and it saves your column selection and column order along with the filters. The new layout allows an unlimited number; ShipStation Legacy caps them at five. Saved views are available to every user on the account, so this is a shared piece of workflow rather than a personal one. What each user sees inside a view can still differ, because a per-user restriction can limit someone to only the orders assigned to them.

Question 20

What is the difference between a saved view and a saved filter in ShipStation?

Accepted Answer

A saved view lives on the Orders grid and bundles filters with columns and column order, for looking at. A saved filter is built in Account Settings under Automation, Order Filters, and it is reusable logic — it appears in the Saved Filters menu on the Orders tab and it can also be used as automation rule criteria, via the Orders match an existing filter criterion. So a filter can drive an action; a view cannot. One documented catch when you use a filter as rule criteria. If the filter keys on Item SKU, Item Name or Warehouse Location, the rule will only apply to single-line-item orders — the same restriction those criteria carry on their own, inherited through the filter.

Question 21

Do automation rules re-run when an order changes?

Accepted Answer

Depends which your account has. Classic rules fire once, when an order first enters Awaiting Shipment or On Hold, and changes after that don't trigger them. Some accounts now have a redesigned Automation Rules screen where rules are grouped into named workflows, each with a trigger type — the default is Orders imported, and a workflow can also run off a tag being added, a tag being removed, or a schedule. This is rolling out gradually and is not documented — I see accounts with it and accounts without, so check Settings → Automation → Automation Rules in your own account. Either way, a trigger only decides when logic runs, which is a separate question from what that logic can evaluate once it does.

Question 22

Can I enforce a shipping cutoff in ShipStation?

Accepted Answer

Yes, through four mechanisms rather than one setting. A rule can hold an order until a date or for a number of days and set its Ship By Date; label creation takes a Scheduled Ship Date for the whole batch; shipment notifications can be delayed until a set hour, a number of hours after the label, or the first carrier scan; and End of Day manifests the day's shipments to the carrier. The piece you drive by hand is the import. ShipStation states that automatic imports cannot be scheduled or customized and that store auto-refresh cannot be set to run at intervals, recommending you press import when you need current orders. Since classic rules fire when an order first lands, a manual import at the cutoff minute is how you draw the boundary where you said it would be.

Question 23

What order does ShipStation automation run in?

Accepted Answer

Auto-Routing and Auto-Split, then SmartFill, then Preset Groups, then Product Defaults, then Service Mapping, then Automation Rules last. Within rules, ShipStation processes your list top to bottom, and later rules override earlier ones. SmartFill is the one most people do not know is in the chain: it is on by default and fills weight and dimensions from your own recent labels, and everything below it overwrites it. The sequence is also why rules have dependencies you manage yourself — service before insurance, dimensions before Rate Shopper, the packing rule before Rate Shopper, a tag before any rule keyed to that tag. That packing rule is the Recommend Package action, which computes a packing plan rather than writing a value you typed; it sits inside the rules layer and follows the same top-to-bottom precedence.

Question 24

What is the difference between a Preset Group and a Shipping Preset?

Accepted Answer

A Product Preset Group is a shared product default. Assign products to it and its shipping service, package, weight, dimensions and customs values apply automatically at import, unless an individual Product Default overrides them. A Shipping Preset is a manual shortcut applied at the shipment screen by hotkey or by scanning a barcode. Use a Preset Group when the answer is a property of the product, and a Shipping Preset when a person genuinely has to look at the parcel — presets carry hotkeys and print as scannable barcodes. If you want a rule to apply a saved combination, the mechanism is a Shipping Strategy rather than a preset: ShipStation states you cannot use automation to apply presets, but Set Shipping Strategy is a standard rule action.

Question 25

Can automation rules use OR logic?

Accepted Answer

Only inside a single criterion. Multiple values within one criterion are OR (semicolon-separated for typed values). Separate criteria lines are always AND. There's no OR across lines and no nesting. So (A AND B) OR (C AND D) becomes two rules, and you own the sequencing and override interactions between them. Fine at five rules. Harder to reason about at fifty.

Question 26

Where should the Charge Shipping to My Account rule sit in my rule list?

Accepted Answer

After whatever sets the service, when that is a static rule, a preset or service mapping. Both halves of that are documented: ShipStation processes automation rules from first to last in the list, and the Charge Shipping to My Account action clears the order's shipping service if the service already on the order is not offered by the account the rule selects. When Rate Shopper sets the service instead, the placement reverses — put the account rule above the Rate Shopper rule — but that pairing is my observation rather than documented behaviour, so test it before relying on it. What ShipStation documents for Rate Shopper is the general principle, in the dimensions-then-rate-shop example: rule sequence is crucial, and a rule the Rate Shopper rule depends on must run before it. The account rule is the same principle applied to a prerequisite ShipStation does not name. Placing it wrong is not a tidiness problem — an order whose service gets cleared imports successfully and reaches the packing bench with an empty service field.

Question 27

Why did all my automation rules stop working at once?

Accepted Answer

Most likely a rule with a blank criteria or blank action. ShipStation fails that rule and every rule below it in the list, with no warning.

Question 28

Where do ShipStation tags come from?

Accepted Answer

Three places, landing at different moments. Product tags and customer tags are applied to the order at import — ShipStation states they arrive before any other automation applies — so every rule that runs afterwards can read them. Rule-applied tags are added by an automation rule and are only visible to rules below it in the list. You can also apply tags by hand from the Orders grid or Order Details. The timing is the whole reason tags are useful. A product tag is on the order before Preset Groups, Product Defaults, Service Mapping or any rule has run, so it is available as criteria to all of them.

Question 29

Why do my SKU-based rules only work on some orders?

Accepted Answer

The Item Name, Item SKU, and Warehouse Location criteria only evaluate orders with a single line item. Multi-item orders are skipped. The same caveat applies to Saved Filter criteria keyed on those fields. ShipStation's criteria reference states the restriction directly, and adds a nuance worth knowing: the quantity of that single line item does not matter. That is a different rule from Product Defaults, which do require a quantity of one. The documented answer for multi-item orders is product tags, and it is a good one.

Question 30

What can't product tags do?

Accepted Answer

Tags give you set membership, not the bill of materials. A tag says FRAGILE is in the order. It can't say whether that's one wine glass or nine, or what each item's dimensions are. Which is exactly what every packing decision needs. You can't cartonize from a tag — fitting items in a box requires knowing which items, how many, and how big. The Recommend Package rule action is the native route: it reads the items directly rather than through tags.

Question 31

Why does an Item SKU filter find multi-item orders when a SKU automation rule does not?

Accepted Answer

Because ShipStation applies the restriction to rules and not to the grid, and it documents the difference directly: Item SKU as a filtering criterion applies both to orders containing just that SKU and to orders containing it alongside other line items, while Item SKU as an automation rule criterion only applies to orders with a single line item. Which is worth knowing before you conclude the platform cannot see inside a mixed basket. It can, on the grid. What it will not do is act on what it found there, because the acting happens in the rules engine where the restriction applies.

Question 32

Can automation rules do calculations?

Accepted Answer

Criteria can't. They compare a field to a value you typed, so the engine can't compute density or dimensional weight, compare two fields to each other, or sum across line items. One action is the exception: the Recommend Package rule action, a Labs beta, computes a packing plan from the items in the order and applies it.

Question 33

How do I filter for orders that do not have a tag in ShipStation?

Accepted Answer

Not from the tag filter on the Orders grid, which selects tags to include. The negative operator lives in the Order Filter builder under Account Settings, Automation, Order Filters — pick Order Tags as the criterion and the operator list offers Do not Include. Save that as a named filter and it becomes available in the Saved Filters menu on the Orders tab, and to automation rules through the Orders match an existing filter criterion. ShipStation documents that tags can be filtered by exclusion but not where the operator is, which is why this looks missing. The builder states that a filter matches orders meeting ALL of its criteria lines. For carries-none-of-these, give each tag its own line rather than multi-selecting them on one.

Question 34

How do I keep product tags up to date across a large catalogue?

Accepted Answer

Through the product CSV import, which carries Tags and Tag1 to Tag5 columns and can update weight, dimensions, tags and customs details in one file. Two documented constraints shape how you use it: order tags can be added but not removed by CSV, and a tag of 30 characters or more silently fails to apply, because the CSV tag field has a 29-character limit. Removing a tag from a product record has no effect on orders that already imported — it only stops future orders being tagged. So a tag correction is never retroactive, and an untagged new SKU falls through every rule keyed to that tag with no error.

Question 35

Why do the dimensions I set in Shopify not reach ShipStation?

Accepted Answer

Because Shopify has no native dimension fields on a variant. Shopify stores weight; length, width and height live in a metafield, an app, or a custom property, depending on which tool put them there. ShipStation reads the fields Shopify's standard order payload sends, so dimensions stored anywhere else never arrive, the ShipStation product record stays blank, and a packing rule that depends on item dimensions has nothing to read. The fix is to get the values into the ShipStation product record directly — CSV import or API — rather than expecting the store sync to carry them.

Question 36

Can automation rules use data from outside ShipStation?

Accepted Answer

No. Criteria read fields already on the order record. There's no action to fetch a forecast, query an ERP, or check anything external. This is the limit behind most cold-chain requirements: the right packaging depends on the forecasted temperature at the destination at ship time, which isn't on the order.

Question 37

Does ShipStation do cartonization?

Accepted Answer

Yes, through a rule action. Most automation rules apply assumptive logic you wrote in advance — 'if 3 products, use box X' — which works for a narrow catalog and degrades as SKUs and package types multiply. Packing Recommendations, a beta feature in ShipStation Labs, is different: it is applied by the Recommend Package rule action, and on the orders that rule matches it computes a packing plan at import from your product dimensions and available packages and applies it, multi-package configurations included, without anyone opening the order. Two things decide whether it helps you. ShipStation documents three requirements — enable it in Labs, add dimensions and weights to your products, and configure your custom packages with dimensions and a maximum weight — and the product dimensions are the one most catalogues do not have. Then add the rule, above any Set Rate Shopper rule, so the rate is priced against the plan. With that in place it works well for boxed goods. It works from rectangles, so a bag that gives or a bin with usable space inside it is where its answer needs checking. Being a Labs beta, its availability may change.

Question 38

Does the packing recommendation work for soft or compressible items?

Accepted Answer

Not reliably, because compressibility is not something a product record can express. ShipStation stores length, width and height, and the plan treats those as fixed. An item that gives — a bag of coffee, a sealed pouch, anything that settles into the space around it — takes up less room in practice than its measurements claim, and several of them together take up much less. What the plan picks will fit, so nothing fails. It reaches for a larger box than a packer would, and the gap widens as more soft items go into one order. How far off it runs depends on how much each item gives, which is the one property the record does not carry. At the far end — items that fold flat and ship in a mailer or a bag — the question stops being which box fits and becomes how much total volume is going into a soft container, which is a different calculation entirely.

Question 39

Where does ShipStation get an order's weight from?

Accepted Answer

From five places, which override each other in a fixed order: the weight the marketplace sent, SmartFill, Product Defaults or a Preset Group, an automation rule — including Recommend Package, which writes the item weight plus the chosen package's tare — and finally whatever a connected scale or a person types at the shipment screen. SmartFill runs after Auto-Split and before every other kind of automation, so anything below it wins. The one worth knowing about is SmartFill, because it is on by default and it is not a rule you wrote. It copies weight and dimensions from the two most recent labels for the exact same combination of items, and only when those two agree. Product Defaults are also unusual here: they normally require a single-item order, and weight is the documented exception that applies anyway.

Question 40

Can ShipStation apply the right package dimensions automatically?

Accepted Answer

For single-line-item, single-quantity orders with stable packaging, yes — via Product Defaults, and it works well. ShipStation applies Product Defaults only to orders containing one line item at a quantity of one, so a single SKU ordered three times does not qualify. Item-count rules approximate the rest, and accuracy falls as composition varies; where every product carries dimensions, the Recommend Package rule action computes the box for mixed orders instead. SmartFill sits underneath both and is on by default. It copies weight and dimensions from the two most recent labels for the exact same combination of items, and only when those two agree — which makes it a cache of decisions your packers already made rather than a calculation. It runs after Auto-Split and before every other kind of automation, so a Product Default or a rule overwrites it.

Question 41

Does the packing recommendation account for void fill and interior packaging?

Accepted Answer

No. A package record stores one set of dimensions, and ShipStation does not distinguish between the outside of the box and the space actually available inside it. If your 12×9×6 carries a corrugated insert, a layer of air pillows, or a liner, the usable interior is smaller than the record says and the plan will fit items into room that is not there. The answer is to enter interior dimensions on the package record, so the plan packs into the room that is actually there, and then bulk-update the orders to the box's true exterior dimensions before the labels are bought, because the carrier bills the outside of the box. That second step is manual.

Question 42

Does ShipStation account for the weight of the box?

Accepted Answer

Yes. A package record carries a tare weight, and it is added to the order's item weight when that package is selected. The constraint is that the tare is a fixed property of the record — one record, one tare. So anything that changes what is inside the box, like a liner, an insert, a coolant pack, or heavier void fill in winter than in summer, is not a weight you can vary on a package. It is a second package record, with its own dimensions and its own tare, and something has to decide which of the two an order gets.

Question 43

How do I handle a box that needs coolant only in warm months?

Accepted Answer

With two package records and a rule that chooses between them. The physical box is the same, but the version carrying a coolant pack has a smaller usable interior and a heavier tare, and both are properties of the record rather than of the order. So you create both, name them so a packer can tell them apart, and switch a rule between them by date. That works. It also means someone has to remember to switch it, remember again when the season turns, and that the switch date is a guess about weather rather than a fact about it. The decision actually depends on ship-to temperature and transit time, which are facts about the day.

Question 44

Should I use carrier packaging or my own boxes in ShipStation?

Accepted Answer

Default to your own, and use carrier packaging on the services that require it to give you their rate. Selecting a carrier's flat-rate package is a declaration, not a note about what you packed: it is how the carrier learns the box is theirs, and entering the same dimensions by hand does not do it. Only the second job changes how the parcel is rated. The carrier prices from the weight and dimensions it is sent, so a saved custom package rates exactly as the generic Package entry does — the value of a package list is accurate dimensions, and separately, box sizes small enough to keep parcels out of dimensional weight. Rate Shopper will not tell you which was cheaper: it compares the rates carriers return for different services, never different packages, so the box is the one input it never varies.

Question 45

Why can't I apply a custom package without setting a carrier?

Accepted Answer

The Set Carrier/Service/Package action sets all three together. The alternative, Set Package Dimensions, applies dimensions but leaves the package name off the order — which breaks anything downstream that reads it.

Question 46

Can ShipStation split an order across multiple boxes automatically?

Accepted Answer

Yes, by fit. Auto-Split handles splits that are a property of the product, configured per product in advance. For everything else, Packing Recommendations, a beta in ShipStation Labs, is now applied by the Recommend Package rule action: add the rule and it works out how to divide an order that doesn't fit in one box and builds the multi-package shipment at import, given dimensions on every product and a maximum weight on every package. Split Ship, Auto-Split, and multi-package shipments are three different features that get conflated constantly. Auto-Split runs automatically, and multi-package shipments now can too, through the Recommend Package rule action.

Question 47

Can I print the package name on a ShipStation label?

Accepted Answer

Not directly. ShipStation's Label Messages feature prints up to three messages of 26 characters each on a shipping label, and each can carry a dynamic field chosen from a documented list. The package name is not on that list. Dimensions are, so the box size can print today with no setup, and so are the three custom fields, so the package name can print if something writes it into one first. Label messages are account-wide. ShipStation states they cannot be customised per store or per carrier, and that not all carriers or services support them — some support none at all. Whatever you build here applies to every label in the account that accepts one.

Question 48

Can I save a multi-package configuration and reuse it?

Accepted Answer

Yes. A Package Set stores the number of component packages and the dimensions, weight and insured value for each one, and can be applied to a single shipment or to many at once with a bulk update. They are created under Settings, Shipping, Packages, on the Package Sets tab. Packing Recommendations, a beta in ShipStation Labs, goes further: it is applied by the Recommend Package rule action, and given product dimensions and configured packages it computes a packing plan at import and creates the multi-package configuration on every order the rule matches. Three things to know about sets themselves — a saved set cannot be edited, only deleted and rebuilt; one set applies per shipment, though you can add packages afterwards; and USPS does not support multi-package labels, so USPS volume uses split shipments instead.

Question 49

Where should the box name print for the packer?

Accepted Answer

On the packing slip, not the label. The packing slip template exposes a Package Type field replacement — documented as the package type selected for the order's shipment — so the box name prints without any workaround. The label is read by a carrier and a sorting machine; the packing slip is read by the person choosing the box. In the accounts I work in this is what I recommend, and it is almost always what the person asking for it on the label actually wanted. It also removes the 26-character limit and the carrier support question entirely.

Question 50

Can ShipStation compare flat-rate programs against standard rates?

Accepted Answer

No. Rate Shopper takes the package as an input — ShipStation's setup docs require the dimensions rule to run before the Rate Shopper rule. Since flat-rate programs require packing into the carrier's box, eligibility is decided upstream of rating, and a box you didn't pack into can't win on price. These misses are invisible. Rate Shopper reports a win every time, because it correctly found the cheapest service for the box you handed it. There's no report line for the box nobody considered. The stop-gap is to audit a sample, find the profile where flat rate wins most of the time, and set that service and package with an automation rule — blunt, since it can't check fit, and better than leaving the category unpriced.

Question 51

Is USPS Ground Advantage Cubic cheaper than standard Ground Advantage?

Accepted Answer

It depends on density, and the rule is simple enough to apply per parcel: cubic beats standard Ground Advantage Commercial once the weight in pounds exceeds the box volume in tenths of a cubic foot. A 0.3 cubic foot box wins on cubic above 3 lb, a 0.5 cubic foot box above 5 lb. The crossover holds in every zone, which is the whole point of cubic — it is priced on volume, so distance does not move it. Three things disqualify a parcel outright: over 20 lb, over one cubic foot, or a longest side over 22 inches. The comparison also changed sharply in 2026. Standard Ground Advantage rose 7.8% in January and took an 8% surcharge in April, and July collapsed the commercial ounce tiers so every sub-one-pound parcel bills at the old top rate. Cubic rose 8.0% across the same period and nothing more.

Question 52

Why didn't Rate Shopper pick the service I expected?

Accepted Answer

It only chooses from services you made eligible in the rule. An economy option that would have arrived in time can't win if it isn't in the set. Delivery time constraints help, but only within what you pre-selected — and a service the carrier returns no transit estimate for drops out entirely.

Question 53

Do I have to pay for Rate Shopper, and are the default strategies enough?

Accepted Answer

On plans sold since 8 July 2025 the default strategies are included at every tier, so turning Rate Shopper on costs nothing. The customisable version is what is gated — ShipStation's plan table marks Custom Rate Shopper unavailable on Starter and available on Standard and Premium. Whether the defaults are enough depends on what you ship with. ShipStation describes the three defaults — Cheapest, Fastest and Best Value — as containing the most-used services from ShipStation Carriers, enumerates exactly which services each one holds, and states you cannot edit or delete them. The defaults therefore price ShipStation's carrier accounts rather than yours. To compare a connected account of your own — or any mix of accounts and services — you build a new Rate Shopper rule rather than editing a default.

Question 54

Can automation rules pick the cheapest service without Rate Shopper?

Accepted Answer

Only by approximation, and it asks the rules engine to do a job it isn't built for. Rules classify an order well — heavy, residential, going to zone 8 — and cannot price one, so a rules-only setup encodes rates you looked up once and they go stale. Rate Shopper prices live. The better shape is a rule that classifies the order and applies a Rate Shopper strategy, leaving the pricing to the thing that can price. The static model is still right in two cases: accounts without Rate Shopper, which is plan-gated, and operations that need a predictable service on every order rather than the cheapest one. Re-price the model whenever carrier rates move.

Question 55

Why is my carrier bill higher than the rate I was quoted?

Accepted Answer

Fuel, residential delivery, oversize and overweight handling, address corrections, and delivery-area surcharges are applied after the fact and often aren't reflected in a base-rate comparison.

Question 56

Can I trust ShipStation's residential/commercial indicator?

Accepted Answer

Yes, and it is worth routing on. ShipStation validates every order shipping to a supported country, classifies US addresses as residential or commercial, and exposes that as a Residential / Commercial rule criterion alongside an Address Verified criterion. ShipStation documents the two rules that use it to avoid FedEx's Ground and Home Delivery surcharges in both directions. One thing to know about what the flag is. ShipStation states the marker comes from the Stamps.com or Melissa address database and "may not reflect the same determination made by UPS or FedEx", who bill from their own. Two datasets about what kind of building sits at an address will differ at the edges, so routing on it removes the large error rather than all of it.

Question 57

Can I see what the carrier actually billed me, not just what the label cost?

Accepted Answer

Yes, if you are on ShipStation carrier accounts. Settings → Shipping → Carriers leads through to the carrier's billing records, where adjustments and fees appear as their own transaction lines rather than folded into the label price, and the whole thing exports to CSV. This is the difference between what a label cost when you bought it and what the carrier charged once the parcel went through their facility. Summing label costs in a spreadsheet will not show it. On your own carrier accounts rather than ShipStation's, the same records live in each carrier's billing portal instead.

Question 58

Does ShipStation charge extra for insurance, address validation or returns?

Accepted Answer

One of the three. Address validation is included on every plan and runs automatically on orders to supported countries. Insurance is a per-shipment purchase, deducted from your ShipStation Balance when you buy it through ShipStation's partner. Return labels are priced like any other label, but the returns portal is not on every plan. The costs people miss are the indirect ones. Return labels, fulfillments and voided labels all count toward your plan's monthly shipment limit, so a high return rate consumes allowance you were budgeting for outbound. And ShipStation validating an address does not stop a carrier charging an address correction fee weeks later — UPS documents that it may update a validated address if it cannot be used to complete delivery, and bills the shipper for the correction.

Question 59

Should I use my own carrier account or ShipStation's rates?

Accepted Answer

It depends on parcel profile and volume, and it is worth testing rather than assuming. ShipStation's own discounted rates are hard to beat on lighter parcels and at moderate volume. A negotiated account of your own tends to win on heavier packages, on shipments using special services, and once volume is high enough to have earned deeper discounts than the platform's. Two things to price in before switching. Connecting your own carrier accounts carries a fee that varies by plan, and some plans add a per-shipment fee on labels bought against them — ShipStation publishes the current schedule. And the comparison is not one-directional: your negotiated rate can be better on one parcel profile and worse on another, which is an argument for comparing per order rather than picking a side.

Question 60

Is ShipStation Carriers worth using compared to my own carrier accounts?

Accepted Answer

Yes, and it is not an either/or. ShipStation Carriers needs no carrier account and no add-on to keep on the account, so the cost of having it available is nothing. Your own accounts sit alongside it and add their negotiated rates to the same comparison. The difference that shows up in operations is billing. ShipStation Carrier labels are bought from your ShipStation Balance at the moment you print them, and an unused label is only refunded if someone voids it — within 30 days for UPS from ShipStation and DHL Express from ShipStation, with funds taking up to 21 business days to return. Your own FedEx and UPS accounts are post-billed, so a label you never ship simply never appears on the invoice. Voided labels still count toward your plan's monthly shipment limit either way.

Question 61

Are ShipStation's FedEx rates good, or should I use my own FedEx account?

Accepted Answer

ShipStation's are good and require no FedEx account at all. FedEx from ShipStation is a ShipStation Carrier, so you enter billing details and start printing; ShipStation publishes the US discount as up to 90% off standard list rates, up to 53% off Ground Economy and up to 39% off One Rate. Your own contract tends to win once you have negotiated volume, and on the services and features ShipStation's version does not carry. Two documented differences decide it more often than the rate does. FedEx from ShipStation does not support pickups, and a pickup booked on your own account that collects those parcels is charged $4.00 per package. And FedEx Ground Economy on your own account requires FedEx to approve you for it, which is a conversation with a rep rather than a checkbox. As with UPS, you can connect both and let a rate comparison decide per order.

Question 62

Should I connect my own FedEx account to ShipStation, or use FedEx from ShipStation?

Accepted Answer

Connect your own if you need a capability ShipStation's FedEx account does not carry, or if you have negotiated a contract at all. ShipStation's FedEx rates are good, and a connected account does not have to beat them to be worth adding — Rate Shopper picks the cheaper of the two per order, so an account that wins occasionally still earns its place. You are adding a rate to the comparison, not replacing one. FedEx from ShipStation supports pickups in the UK only, and does not support third-party billing, collect on delivery, carrier insurance or multiple accounts. A connected FedEx account carries all of those for US and Canadian accounts, and FedEx invoices you monthly rather than drawing from a prepaid ShipStation Balance. The cost of connecting one depends on when you signed up: nothing if that was on or after 9 July 2025, a monthly add-on by tier on Legacy plans, a per-shipment fee on High Volume.

Question 63

Can I run two accounts with the same carrier in ShipStation, and how do orders get to the second one?

Accepted Answer

Yes, on carriers that support it. Connect both accounts and the first one becomes the primary — ShipStation states it always defaults to the primary account for a carrier when you select a carrier service. To send an order to the other account, change the Shipping Account in Other Shipping Options on the order, apply it to a selection in bulk, or set it at import with the Charge Shipping to My Account automation rule action. Three things always use the primary account regardless of what you configure: return labels, labels created directly in the Rate Calculator, and any service picked from a list sorted by carrier rather than by account. Not all carriers allow multiple accounts, and ShipStation recommends giving each one a unique nickname so they are distinguishable in the service menu.

Question 64

Can ShipStation use the shipping option the customer chose at checkout?

Accepted Answer

Yes. The checkout selection arrives as the Requested Service, and it is available to automation rules as criteria — both the raw marketplace value and the value after Service Mapping has run. So each option on your storefront can route to its own Rate Shopper configuration. That matters because the checkout selection is the only record of what you promised. A single rate shopper across all orders will happily win a cheap slow service on an order somebody paid a premium to have quickly. One configuration per shipping option you sell, routed on the requested service, keeps the price comparison while making sure every possible winner honours the promise.

The ShipStation Automation Guide: What It Does, and Where Custom Logic Starts

What it handles

Alerts and exceptions

How the engine behaves

Reading what's in an order

Packing

Rates

Business-specific logic

If one of these is your situation