Everything SerialTrack does.
The whole list, including the small things. If you are looking for something that is not here, ask us. Quite a lot of this list started as somebody's email.
Scanning
What happens at the packing station. Most people put a spare computer there and run the whole thing from the scanner.
- Scan the order, then each unit. Scan an order number, a SKU or a carrier tracking number to open it, then scan every unit going into the box
- Runs from the scanner. Any USB scanner in keyboard mode works. No driver, no SDK, nothing to install
- A barcode for “new order”. Tape it to the packing station and the whole workflow stays on the scanner. We give you the PDF
- Type it in when there is no barcode. EDI portals and emailed purchase orders often have nothing to scan
- Order-number patterns. We match your order numbers with a pattern, so several stores with different formats can be told apart
- Duplicate detection. A serial number already recorded is rejected rather than filed twice. Switch it off per account if you re-scan on purpose
- Several values in one scan. Semicolon-separated values in a single scan become separate records
- Delete with a reason. A mis-scan is removed with a note saying why, and the record is kept rather than erased
- Every scan is logged. The exact bytes, the barcode symbology and the outcome, whether it was accepted, rejected as a duplicate, or arrived with no order open
UDI and 2D barcodes
The 2D square on medical devices, prescription drugs and a lot of regulated stock holds several values at once. We take them apart. How that works in detail.
- GS1 DataMatrix. The 2D square on regulated stock. One scan captures every element in it
- Elements split out. GTIN, serial number, lot, expiry and the rest are each stored on their own, so you can search and report on any of them
- Around thirty application identifiers. Including SSCC, GTIN, lot, serial, production, packaging, best-before, sell-by and expiry dates, counts, customer part numbers and purchase order numbers
- GTIN check digit validated. A misread product code is caught at the scan, not months later
- Dates normalised. Stored as YYYY-MM-DD, so they sort and filter as dates rather than six ambiguous digits
- The separator browsers will not type. We capture the raw keystrokes so the invisible GS1 separator survives and your lot and serial do not run together
- Anything else is kept too. An identifier we do not have a column for is stored against its own code and stays reportable
- Non-UDI barcodes are untouched. The parser only engages on a valid GS1 code with a good GTIN. Everything else behaves exactly as it always did
Finding it again
The reason you scanned it in the first place.
- Search any value. Order number, tracking number, serial, lot, GTIN or expiry date. Whichever one the person asking you has
- Exact or partial. Full-value match by default, wildcard when you only have a fragment
- Siblings come with it. Find a serial number and its lot and expiry come back with it, because they were the same scan
- Scan history. Everything you have recorded, newest first, paged
- Order details on demand. Pages load from our own database, then fetch the customer and address from your fulfillment system when you ask for them
- Export everything. One CSV of every scan you have ever recorded, whenever you want it
Reports
Search answers a question about one unit. A report answers a question about every unit that matches, and gives you the customer list to work from. What a recall needs.
- Built in the background. You do not sit and wait. Large reports keep running while you work
- Filter on any element. Serial number, GTIN, lot, SSCC or count, plus any other identifier by giving its code and a value
- Date ranges. Scan date, expiry date or production date, as a from-and-to range
- Include deleted rows. For when you need the full picture rather than the current one
- Around thirty-five columns. Pick what you need: the scan elements, ship-to name and address, email and phone, bill-to details, order source, order date, order status, tracking number and internal notes
- Customer details filled in. Names and addresses are looked up from ShipStation or Shopify while the report runs
- Up to 50,000 rows. With the first 500 shown on screen and the whole thing as a CSV
- Kept for thirty days. Reports are cleaned up automatically, so old customer data does not sit around
Integrations
So the record is in the system your team already has open. Every integration.
- ShipStation. Paste an API key. We look orders up as you scan and write each serial number into the order's Internal Notes
- Shopify. Authorize it once. Connect as many stores as you run
- Veeqo. Same again: scan the order, scan the unit, and the value is added to the order's notes
- Choose the wording. A format string controls exactly how the note reads in your fulfillment system
- Webhooks. We POST to your URL on every scan, and again when something is deleted. Failures retry for 48 hours
- Zapier. Point the webhook at a catch hook and the data reaches everything Zapier connects to
- Packing slip barcodes. Step-by-step instructions for putting a scannable order number on your ShipStation and Shopify packing slips
Your account
- Thirty-day free trial. Nothing charged during it, and your records are still there at the end
- Three plans, from $19 a month. Priced on how many serial or batch numbers you record, not per seat and not per order
- Change plan any time. Up or down, from the settings page. Useful if your volume is seasonal
- Cancel yourself. From the same page, without talking to anyone
Two things we are asked for and do not do yet. We cannot stop an order shipping when the scan is missing, and we cannot expand a case or pallet code into the individual units inside it without a feed from whoever packed the case. Both are on the list. Tell us if you need either and it moves up.
Start recording on the next shipment.
Connect your store, scan one order, and look at the record. About five minutes to set up, and nothing to pay for thirty days.