Quickbooky

Accounting News

Inventory & Items

Users Struggle to Get Barcode Scanning Working in QuickBooks Desktop

QuickBooks Desktop users report scanners that will not register; two hardware rules and a built-in wizard resolve most cases.

COMMUNITY ISSUESQUICKBOOKY

A familiar bottleneck keeps surfacing among QuickBooks Desktop shops that adopt barcoding. The scanner arrives, gets plugged in, and then refuses to cooperate with the software. The resolution, drawn from Intuit’s accepted guidance for its Desktop line, has two halves. First comes a hardware check with two firm rules. Then a setup wizard has to run before the first scan.

The symptom pattern behind the reports

Users describe the same arc. A business adds Advanced Inventory, the stock module tied to the Enterprise edition of Desktop, hoping barcodes will speed up buying, selling, and stock counts. A scanner gets ordered and plugged in. It works everywhere else, yet QuickBooks ignores every code, or the item never lands on the form. The team falls back to typing item numbers by hand.

The confusion is understandable. Most USB scanners behave like a second keyboard, so they type into any text field without complaint. That behavior hides the two rules below, and it leads buyers to assume the hardware itself is fine. Usually the hardware is fine; the setup is what is missing.

Can any scanner work with QuickBooks Desktop?

No, and the boundary is firm. The device must read EAN-13 and Code 128 formats. EAN-13 is the international article number printed on most retail packaging; Code 128 is a common choice for internal labels. The device must also send exactly one carriage return, in plain terms a single Enter keystroke, at the end of each code. A scanner that misses either rule produces reads the software treats as noise.

One exclusion catches owners of older gear: serial port scanners are not supported at all, and no setting changes that. A USB model is the practical answer. Scope matters too. The mobile warehouse app and the purchase order processing worksheet call for a different class of scanner again, so a desktop unit that handles invoices will not necessarily cover those jobs.

Run the barcode wizard before the first scan

The second half of the fix is configuration, and skipping it explains many dead ends. The wizard lives inside the Preferences dialog and walks you through the setup end to end.

  1. Open the Edit menu and choose Preferences.
  2. Select Items and Inventory, then open the Company Preferences tab.
  3. Choose Advanced Inventory Settings, then the Barcodes tab.
  4. Turn on barcodes and launch the barcode wizard.
  5. Pick the item field that will carry the code, and choose one that is unique for every item. The item name or the part number is a safe choice.
  6. Select the item types that should get generated codes, then finish.

Items must carry a barcode before a scan will recognize them, whether you are buying or selling. The wizard generates those codes as part of setup. Users who never find the wizard often assume their edition lacks the feature; in most reports, the toggle was simply waiting two dialogs deep, unvisited.

Transactions that accept a scan

Once the wizard finishes and items carry codes, daily use is direct. Open any supported transaction and scan an item; it appears as a new line on the form. The reach spans the whole sales and purchasing cycle: estimates, sales orders, invoices, sales receipts, refunds and credits, purchase orders, item receipts, bills, checks, and inventory transfers. Scanning also supports adjusting the quantity of items in stock, so counts can be worked through with the reader instead of the keyboard.

Importing barcodes you already use

The guidance also covers catalogs that come with codes in place, such as items that already print barcodes on supplier labels. In those situations the codes can be imported rather than entered one at a time. That spares larger product lists the manual typing that often discourages adoption before it starts.

Our read on the pattern

We see the same two causes each time this question comes up: hardware that was never compatible, or hardware that is fine but was never configured. Both produce silence at the moment of the first scan, and both look identical from the desk. Prevention is cheap. Confirm the two rules before buying the device: support for EAN-13 and Code 128, and a single carriage return after each code. Then finish the wizard, and make sure every item carries a code. Shops that clear both hurdles get the payoff the feature promises: quicker and simpler data entry across sales, purchasing, and stock counts.

← Back to Community Issues