How to Use OCR to Add Products to Lightspeed R Series From an Invoice

If you run a boutique on Lightspeed and you have gone looking for a faster way to load new inventory, you have probably run into OCR. It's the technology behind every "scan your paperwork and never type again" app, and it's not hype. It just does less than the marketing suggests, and Lightspeed asks for more than most systems, so the gap between "OCR read my invoice" and "my products are stocked" is wider than you would expect.

Here is what OCR handles, what it leaves to you, and how to get from a scanned invoice to live inventory without spending the evening on it.

What OCR Does (and What It Doesn't)

OCR stands for optical character recognition. It looks at an image of a document, a scan, a photo, a flat PDF, and works out which letters and numbers are in the picture. To a computer, a scanned invoice starts as a photograph; OCR turns that photo back into text you can select, copy, and edit.

That is useful for plain paperwork. If a vendor sends a paper invoice or a PDF you can't highlight, OCR lets you copy the numbers instead of retyping them. Where it stops is when the destination isn't a document but a structured system like Lightspeed, which wants your data split, formatted, and matched in a very particular way.

Why Lightspeed Needs Two Files, Not One

This is the part that trips people up, and it has nothing to do with OCR. Lightspeed R Series splits product loading into two separate imports:

• The Item Import creates the items in your catalog: descriptions, SKUs, categories, retail prices, and the size-and-color matrix.
• The Purchase Order import records what you ordered: wholesale unit costs and quantities, tied back to the items you just created.

You need both. Step one puts sellable products in the catalog with retail prices; step two records your cost of goods and, once you receive the shipment, your on-hand stock. Our full Lightspeed R Series import guide covers every column and screen.

Now picture a plain OCR transcript in hand. Here is what still has to happen before Lightspeed will take it:

What OCR gives you	What the two Lightspeed files need
Sizes listed across a row	A matrix item with each size and color as a variant
Wholesale cost	Retail price in the Item Import, wholesale cost in the PO
A vendor style code	Custom SKU and Manufacturer SKU, kept consistent
A flat list of line items	Every PO line matched to its catalog item by System ID or SKU

That last row is the slow part. Fan the invoice out into two spreadsheets, then keep every purchase-order line pointing at the right catalog item. One mismatch and Lightspeed rejects the row or attaches a cost to the wrong product.

From Scanned Invoice to Lightspeed, by Hand

If you would rather keep your current process, OCR can still save some typing. Here is a reasonable path:

1. Get a clean scan. A flat, straight-on scan or photo reads far more accurately than a wrinkled receipt at an angle. If your vendor can send a PDF instead of paper, take it.
2. Run it through OCR. Most PDF and phone scanner apps have OCR built in. Aim for editable text or a spreadsheet.
3. Build the Item Import first. Create each item with its description, SKUs, category, retail price, and the matrix values for size and color. This lands products in your catalog.
4. Then build the Purchase Order file. Add order quantities and unit costs, and make sure each line ties back to the matching item from step three. Keep your SKUs consistent so the two files line up.
5. Price with a formula. Use a column formula off the wholesale cost, then copy it down, instead of calculating retail line by line.
6. Import, then receive. Load the Item Import, then the Purchase Order, then run Lightspeed's receiving workflow to move the stock into inventory. Check a few items under Inventory > Item Search before you sell.

It works. It's just slow, and you repeat the whole thing every time a shipment lands. For twenty or thirty styles across sizes and colors, that is comfortably over an hour, before you fix any OCR misreads.

Or Let Ohavah Build Both Files

Skipping the tedious middle is why Ohavah exists. You upload the supplier invoice as a PDF and get back both finished CSVs instead of a raw transcript.

Here is how it works:

1. Upload your supplier invoice or purchase order as a PDF.
2. Configure your vendor settings once: markup multiplier, rounding, SKU format, and size preferences.
3. Download the Item Import CSV and the Purchase Order CSV, already matched and formatted for Lightspeed R Series.

Ohavah reads the invoice, expands every size and color into the matrix, applies your pricing rules, generates the SKUs, and matches every PO line to its catalog item. The hour of reading, retyping, and cross-checking two spreadsheets turns into about two minutes of reviewing and uploading. Because the files are built to match, you're not hunting for the one line that landed on the wrong item.

A Few Tips Either Way

Match on SKU or System ID deliberately. Pick one and use it across both files so the PO links to the right items every time.

Receive before you count on stock. The imports set up items and costs, but inventory isn't live until you run the receiving workflow.

Handle images separately. OCR won't find product photos. Photo Finder pulls images for the styles you ordered.

Running Shopify Too?

Plenty of boutiques use Lightspeed in the shop and Shopify online. The reading is identical; only the output changes. We cover the Shopify side in using OCR to add products to Shopify, which handles the single-CSV format Shopify's importer expects.

Either way, the point holds: OCR is a fine first step, but it hands you words, not a stocked catalog. The hours live in everything after the reading, and on Lightspeed that means two matched files worth handing off.