Published
ShipStation has five separate mechanisms for getting a weight onto an order, four of which run before anyone touches the parcel. Between product records, a feature that learns from your own shipping history, two rule actions and a direct scale integration, most operations can have accurate weights without typing any.
They stack in a fixed order and later ones overwrite earlier ones, so the useful question is not whether weight is being set but which layer is setting it.
ShipStation can populate a weight from five places. They apply in a fixed sequence and later ones overwrite earlier ones.
Set the Total Order Weight defines the weight outright, while Adjust the Order Weight adds a fixed amount to whatever is already there — the one to use for packaging weight you know gets added to every parcel. ShipStation notes that Adjust applies to an order only once and will not re-apply when rules are reprocessed.Knowing the order matters because the answer to “why is this order 2 lb” is different depending on which layer won, and four of the five happen before anyone looks at the parcel.
SmartFill is the one most people have never heard of, and it is enabled by default.
ShipStation documents it as follows: as orders import, it compares the new order’s items to the two most recent shipments for the exact same combination of items. If those two shipments have identical weight and dimensions, it copies them onto the new order. If they disagree, it does nothing, which is how it avoids locking in a value you have since changed.
Two consequences.
It overwrites the marketplace weight by default. There is a Marketplace Override toggle, on by default, which means the weight your channel sent is discarded in favour of what you actually shipped last time. That is usually the better number. It is worth knowing it is happening if you have been treating the marketplace figure as the source of truth.
It sits at a specific point in the order of operations. ShipStation states it “applies after Auto-Split and before all other types of automation,” and that this is deliberate so it does not overwrite rules and defaults you set up. Practically: SmartFill fills the gap, and anything you configure beats it. If you have a rule that adjusts order weight, that rule applies to the weight SmartFill just wrote — ShipStation flags this directly as a way to end up with weights inconsistent with the labels you have already printed.
It only handles ShipStation Default and Custom package types, not carrier-specific packaging, and it will not copy dimensions when the two prior shipments were both recorded as 0×0×0. Where it acts, it leaves an entry in the shipment’s activity log saying what it changed, which is the only way to tell after the fact.
The layer order here is the same one that governs the rest of ShipStation’s automation, and SmartFill is a genuinely useful addition to it: it does the work of a product default without anyone maintaining a product record.
Product Defaults normally apply only when an order contains that product and nothing else. On top of that, ShipStation’s Products overview says the carrier, service, confirmation and dimension defaults only apply when the item’s quantity is 1.
Weight is the exception, stated in the same place:
This means that if other products are present on the order, the defaults will not apply (the Weight default is the notable exception to this rule).
So a product-level weight contributes to multi-item orders where a product-level box size does not. That asymmetry is the single most useful thing to know about product data in ShipStation, because it means populating weights on your catalogue pays off across your whole order mix, while populating dimensions only pays off on single-item orders.
Which is also why dimensions need a different mechanism entirely and weight does not.
Here is the diagnostic worth running.
Export a few months of shipments and calculate what share of your weights are exact whole pounds. If a meaningful majority are, those weights were typed by a person or defaulted, not weighed. Real parcels do not come out at exactly 1, 2 or 3 lb at that rate.
In one operation I assessed, 79.9% of the orders carrying a weight were an exact whole pound. That is a single account and not a benchmark — I have no basis for saying what is typical, and anyone quoting a figure for the industry does not either. It is offered as an illustration of what the pattern looks like when it is there.
What the pattern means is worth more than the number. A high whole-pound share is somebody rounding up, which is the safe direction to round and also the expensive one, because you pay for weight you are not shipping on every parcel. Rounding down is rarer and worse: it comes back as an adjustment with a correction fee attached rather than as a slightly higher rate.
Run it on your own export. The result tells you whether the rest of this article is a project or a formality, and your number is the only one that matters.
A USB scale is the direct answer. ShipStation supports most HID-compliant USB scales connected directly to the workstation, via ShipStation Connect. The constraints are worth reading before you buy: serial and COM scales are not supported, scales connected through hubs or extenders are not supported, and two named brands — Accupost and Brecknell — are listed as incompatible. Australian and New Zealand merchants should look for a model that is trade approved as well as HID compliant.
If your readings come back wrong by a factor of ten or a hundred, that is a known condition with a documented fix: disable the scale in ShipStation Connect, disconnect it, power it down for two minutes, reconnect, then reset to defaults and configure for high capacity mode.
A scale inside Scan to Verify is better than a scale at the shipment screen, because it removes the step where somebody has to remember. In the Scan to Verify and Print workflow the packed box goes on the scale and the weight lands on the shipment automatically, right before the label is bought. ShipStation makes a nice point about this in passing: because the scale is live while you pack, it captures the bubble wrap, the packing material and anything else that went in the box, which a product-level weight never does.
A dimensioner solves the other half. ShipStation supports Cubiscan devices for capturing dimensions the same way a scale captures weight. That is a capital purchase and it earns out only at a certain volume, but if you are already measuring by hand it is worth pricing.
Two changes in 2026 sharpened this.
USPS moved its dimensional weight divisor from 166 to 139 above one cubic foot in July 2026, which makes the same box bill as a heavier parcel. And dimensions now round up to the nearest whole inch on all three sides, so a 10.1 inch side bills as 11. Both are in the July restructure.
Carriers bill on the greater of actual weight and dimensional weight. When the divisor tightens, more of your parcels cross over to being billed on size rather than contents, and at that point an accurate actual weight stops changing the price at all — the box is setting it.
That does not make weight accuracy pointless. It makes it the cheaper of the two problems to fix. A scale costs a few hundred dollars and fixes weight this week. Fixing the box is a packaging project.
There is one more reason to care, which is that an inaccurate weight breaks rate comparison in a way that is invisible. Rate Shopper compares live rates for the shipment as described. If the shipment is described as 3 lb and is actually 2.1 lb, the comparison is correct and the answer is wrong, and nothing about the label tells you so.
Run the whole-pound calculation first. It takes ten minutes and it decides whether you have a problem.
If you do, the order of work is: put weights on the product records for your top SKUs by volume, since that is the layer that applies to multi-item orders; confirm SmartFill is on and doing what you expect by checking a few shipment activity logs; and put a scale at the pack bench inside a scan workflow so the final number is measured rather than inherited.
Then re-run the same calculation a month later. If the whole-pound share has not moved, the scale is not being used, and that is a process problem rather than a configuration one.
An accurate weight does not tell you whether the box was the right box, and on most catalogues the box is the larger number. It also does not recover anything you have already overpaid — carriers correct in their own favour when the manifest understates, and do not refund when it overstates.
Weight accuracy is worth having because it stops the bleeding and because everything downstream depends on it. It is not, on its own, a saving.
Knowing how a carrier prices a package is useful. The harder problem is making the right packing and rate decision on every order, when the correct answer changes with the contents, the destination and the rate card.
String builds and maintains that logic inside existing ShipStation accounts, for operations shipping roughly 6,000 orders a month or more. Below that, ShipStation's native automation and accurate product dimensions will get you most of the way there.
Eight patterns that show up when an operation needs custom shipping logic