Get more out of your ShipStation account: spot the quick wins and automate the small stuff. Free, and it stays free.
Operations I build and maintain automation for
Every product used in the last 30 days with no weight or no dimensions in ShipStation, ranked by how many shipments it touched. Missing weight does not stop a label printing. It means the label goes out carrying whatever the rest of the order weighed.
Every box you actually shipped in, grouped by dimensions rather than by package record, so 10 × 8 × 2 and 2 × 8 × 10 count as one box. It shows how often each was selected from a saved package versus typed in by hand, which is usually the first time anyone finds out their team is retyping boxes the account already has.
Which shipments were priced on the size of the box rather than the weight, which is where dimensional weight quietly costs money. It also flags shipments where the contents measure larger than the box they went in — a contradiction that means either the product data or the package record is wrong.
Which box sizes your shipments actually need. It tests the packages in your account against ULINE’s catalogue, works out which to keep, which to drop and which to add, and shows the point past which stocking more sizes stops paying for itself.
The oldest shipments that have not reported delivery, with every carrier event inline. ShipStation shows you a status. This shows you how long ago that status happened, which is the difference between a package in transit and a package that stopped moving nine days ago.
Everything in this group writes to ShipStation. Each one stays off until you turn it on, and each shows you what it would do before it does it.
Every 30 minutes, pending shipments that aren't already in a batch get grouped into one — by the day the order came in, by a "BATCH:" tag you put on the order, or by whether the order is one SKU or several. A batch that's still open is added to rather than duplicated, and anything already in a batch is left where it is. Test it first and it shows you exactly what it would do without touching ShipStation.
Date, tag and SKU count are the three things it can group on. If your batches turn on something else — pick path, carrier cutoffs, which station packs what — that's past what a tool can work out without knowing your floor.
Shopify and most other channels hand ShipStation everything in one block of text — gift message, delivery instructions, PO number, whatever the storefront collected — and it usually lands in Notes from Buyer. This pulls a value out of that block and writes it into the field you actually want it in.
Pick a preset for your channel rather than writing a pattern, load any recent order to see exactly what it would extract, and it only ever writes to the one field you nominate. Gift messages are where most people hit this first, but anything consistently formatted in that block can be mapped the same way.
Start here
Paste a ShipStation API key and the reports build in about five minutes. Nothing writes to ShipStation until you switch it on.
