How Scan to Verify Works in ShipStation

ShipStation ships a barcode workflow that confirms the right items are in the box before the label prints. It is called Scan to Verify, it lives in the Scan tab, and it does the job well — audio and visual feedback on every scan, quantity tracking per line, and a straight run into label purchase if you want it.

This is a setup guide. The feature is sound; what decides whether it works for you is product data, and that is worth checking before you roll it out rather than after.

Three workflows, not one

The Scan tab holds three separate options and they solve different problems.

Scan to Print takes a packing slip barcode, opens the order, pulls the weight from a connected scale, and prints the label. No item checking. This is for operations where picking accuracy is already handled elsewhere and the bottleneck is the label.

Scan to Verify checks the items and stops. It marks the order Verified and moves to the next one. There is no print step. This suits a pack line where verification and label printing are separate stations.

Scan to Verify and Print does both: verify every item, then land in the shipment screen with the weight already applied, then print.

For most operations under one roof, the third is the one to build.

What it needs before it works

Four things, and the second is the one that stops people.

A barcode scanner with the carriage return function enabled. This is worth doing properly. If the scanner does not send an Enter signal after each scan, ShipStation waits for someone to click Verify, and you have built a workflow that is slower than the thing it replaced. ShipStation names two models it has tested — the Zebra Symbol LS2208 and the Motorola LI4278 — and notes most general-purpose USB or Bluetooth scanners work.

UPCs or Fulfillment SKUs on your product records. This is the project. Verification compares a scanned barcode against product data, and if that data does not exist there is nothing to compare against. ShipStation recommends the CSV import method to populate them in bulk, which is the right approach — doing it product by product is how this initiative dies.

Packing slips with a barcode. Either a Scan to View barcode or an order number barcode, so the packer can open the order by scanning rather than typing. If your slips do not carry one, that is a packing slip template change and it is a small one.

A preference set. Under Settings → Shipping → Workflow Settings → Scan To Verify Items By, you choose whether verification matches on UPC, Item SKU, Fulfillment SKU, or a combination. Set this deliberately. It determines which of your product identifiers has to be correct.

For the print half you also need ShipStation Connect running, and either preconfigured weights or a connected scale. If you use ShipStation Carriers, auto-funding must be enabled — the workflow buys labels in sequence and a balance prompt stops the line.

Check this before you roll it out

One identifier per product. From ShipStation’s documentation:

Scan to Verify does not support using multiple UPC codes or Fulfillment SKUs on a single product.

— ShipStation, Verify & Print Shipments with Barcode Scan

That is fine for most catalogues and worth a ten-minute check on yours. The products that break it are the ones carrying more than one barcode in the racking — a supplier changed packaging, the same item sells under two GTINs, a bundle carries both its own code and its components’. Only one code verifies; the others scan as unrecognised.

Take the twenty products most likely to have that problem, look at what is physically printed on the boxes, and confirm one identifier covers each. If it does, you are ready. If it does not, that is a relabelling job worth doing first, and better found now than at the bench.

How the verification actually runs

The packer scans the packing slip barcode to open the order, then works through the items. There are three ways to clear a line, and ShipStation notes each is tracked and reported differently:

• Scan the barcode for each item
• Click Verify to clear a line by hand
• Click Verify All to clear the whole order at once

That last option exists for good reasons and is also the hole in the floor. An order cleared with Verify All has been marked verified without anything being checked. Because the three methods are tracked separately, you can see how often it is used, and it is worth looking. A high Verify All rate means the workflow is being performed rather than done.

Quantities are handled properly: scanning increments the count for a product until the full ordered quantity is reached, at which point the line is Verified. A three-unit line needs three scans.

There is audio and visual feedback on each scan, which is what makes this work at speed — a packer does not have to look at the screen to know a scan was wrong.

Once everything is verified, Mark as Verified moves on. There is a Workflow Setting that removes even that click and advances automatically after the last item, which is worth enabling once the team is comfortable.

One useful detail: if you scan an item that is in the order but scrolled out of view, ShipStation tells you it counted an off-screen item rather than silently accepting it. That is the right behaviour and it prevents a specific confusing failure.

The scale, and why it belongs here

If a scale is connected, the shipment weight is applied automatically when you reach the print step.

ShipStation makes a point about this that is easy to skim past and is the best argument for the workflow. Because the scale is live while packing, the packer can put the box on it as they fill it, and the weight captured is the weight of the finished parcel — bubble wrap, void fill, the bonus sample, everything. A product-level weight never includes any of that.

That is the difference between a weight that is derived and a weight that is measured, and on most catalogues it is the difference that shows up on the invoice.

Removing the last clicks

Two optional pieces take the mouse out of the loop entirely.

Scan to Print barcode. Click Print Barcode Sheet inside the workflow and keep the sheet at the workstation. Scanning it purchases and prints the label, replacing the button and the P hotkey.

Preset barcodes. Shipping Presets can be printed as barcodes too, so a packer can apply a saved service, package and confirmation combination with a scan. Where a shipment genuinely needs a human decision, this is how you make that decision cost one motion.

The order has to have a ship-from location, a shipping service and a package type before a label can be created. If your automation is already setting those at import, that requirement is invisible. If it is not, the packer hits it on every order, and the fix is upstream in automation rules rather than at the bench.

Scope worth knowing

Three things it is deliberately not, so you put them somewhere else rather than expecting this to cover them.

Stock checking happens earlier. ShipStation states the verify workflows are not for inventory management and do not add products to an order with a scan. That is the right split — you want to know an item is unavailable before a picker walks to the shelf, not after. For a partially available order ShipStation’s recommendation is to split it into separate shipments for the in-stock and out-of-stock items, which is a different mechanism.

It requires the current layout. Both Scan to Verify and Scan to Verify and Print are new-layout only, not available in ShipStation Legacy.

It verifies contents, not packing. Confirming the right items are present is a different question from whether they should have gone in one carton or two, which is cartonization.

What to do

Start by counting. Pull your returns or replacements for the last quarter and separate the ones caused by a wrong or missing item from everything else. That number, times the cost of a replacement plus two labels plus the labour, is what the workflow is worth per year.

Then check the data. Run an export of your products and count how many have a UPC or Fulfillment SKU populated. If the coverage is under about ninety per cent by order volume, populating it is the project and the workflow is the easy part afterwards.

Then run it on one station for a week and look at how the orders were verified — scanned, individually cleared, or cleared in bulk. That tells you whether you have a control or a ritual.

Where it stops paying

Verification catches errors at the last possible moment, which is the cheapest place to catch them and not the cheapest place to prevent them. If a particular pair of SKUs is being confused repeatedly, the answer is where they sit in the racking, not another scan.

It also adds a step. On a single-item order that a packer could not plausibly get wrong, that step is pure cost. Most operations should apply it to multi-item orders and skip it on the trivial ones, and the filter for that already exists in the orders grid.