ERPNext barcode scanning for receiving and picking: when teams need it
When receiving clerks, pickers and sales staff key item codes by hand, errors show up as wrong quantities on receipts, wrong lines on delivery notes and variances on stock counts that nobody can explain later. This page explains how ERPNext barcode scanning fits receiving, picking and sales, and what must be designed before scanning goes live. The short answer is that scanning helps most where volume is high, items look alike, or the same item is packed in more than one unit. Before any scanner is connected, the team should decide which codes identify each item, which unit of measure each code represents, and whether cases, inner packs and single units each need their own barcode. Those decisions shape every document that scanning touches, so they belong in the design phase, not the rollout.
Barcodes are a data design decision as much as a hardware decision. In ERPNext, an item can carry more than one barcode, and a barcode can be tied to a specific unit of measure, so a scan of a pallet label and a scan of a single bottle can resolve to different quantities. Pack barcodes, supplier barcodes and internal labels can collide if they are not planned, and a scan that matches the wrong record can post the wrong stock with no visible warning at the counter. Confirm in your own ERPNext version how the barcode and UOM fields behave on the item record, and test each label type against the documents it will feed. DeployOpen configures and documents this inside your own ERPNext deployment and does not recommend a scanner brand. Hardware should be chosen against the symbologies your labels use and the environment your staff work in.
Barcode options in ERPNext and when each one fits
This table compares the main barcode setup choices for ERPNext, from item-level and unit-of-measure barcodes to scanner input modes and label printing. Read each row against your operation: distributors, retailers and manufacturers tend to need different combinations. Confirm exact field names and scanning behavior against the ERPNext version you run before you commit to a design.
| Option | What it does | Best fit | What to confirm |
|---|---|---|---|
| Item-level barcode | Stores one barcode on the item master so scanning the product resolves to that item in receipts, deliveries and invoices. | Manufacturers and retailers with one sellable unit per SKU and simple, consistent packaging. | Where the barcode field sits in your version and whether duplicate barcodes are blocked across items. |
| Additional barcodes per unit of measure | Attaches a separate barcode to each UOM, such as an each barcode and a case barcode, so scanning a case converts to the correct quantity. | Distributors receiving cases and selling singles, where the same item moves in several pack sizes. | How conversion factors are maintained, and whether the scanned UOM flows correctly into stock entries and invoices. |
| Keyboard wedge scanner | A handheld scanner that types the code into the focused field, so no extra software is needed on the workstation. | Receiving docks and back-office desks where staff scan into one form at a time. | Scanner suffix settings (such as Enter after the code) and the focus behavior in your browser and ERPNext screens. |
| Camera scanning on a handheld or phone | Uses the device camera to read barcodes inside the browser, useful where a dedicated scanner is impractical. | Retail floor staff and field teams who scan occasionally and already carry a phone or rugged handheld. | Browser and device support, lighting and label quality tolerance, and whether scanning works on the screens you need. |
| Scanning in receipts and deliveries | Adds scanned items to purchase receipts, delivery notes or stock entries, with quantities updated per scan. | Distributors and manufacturers processing high volumes of inbound and outbound lines. | How quantities accumulate for repeated scans and how batch or serial items prompt for their numbers during the scan. |
| Scanning in invoices and point of sale | Lets sales staff scan items onto sales invoices or a point-of-sale screen to speed up checkout. | Retailers and counter sales where speed at the till matters most. | Whether your ERPNext version and POS setup support scanning on the screens you plan to use. |
| Label printing through print formats | Generates item or location labels with barcodes from print formats, usually for bins, pallets or shelf tags. | Manufacturers labeling work-in-progress and warehouses labeling bins or pallets. | Label printer language and size support, and which print format fields hold the barcode value. |
Where scanning changes receiving, picking, sales and counts
Scanning touches the same item lookup in several ERPNext documents, but each document updates the line in a different way. The differences that matter are whether a scan adds a row or increments a quantity, whether it sets a unit of measure, and what happens when the barcode matches nothing. Confirm each behavior in your own version before you write scanning rules for warehouse and sales staff.
Purchase receipt
Receiving is where scanned stock first enters the system. A scan of an item barcode on a purchase receipt should match the item and either add a new row or increase the quantity on an existing row, depending on your setup and how the barcode is recorded. A barcode that matches nothing should stop the line, so no item is created by accident. Check whether repeat scans increment the row, and test a supplier pack barcode against the unit of measure conversion before go-live.
Stock entry and transfers
Stock entries for material transfers, issues and manufacturing moves use the same item lookup on each row. A scan places the item into the row, and the team then confirms the quantity line by line, which suits warehouse moves between locations. Serial and batch items need a further scan or selection of their serial or batch numbers, so test that step with real labels from your suppliers. Confirm which source warehouse the scan reads from when the same item sits in several locations.
Pick list and delivery note
Picking works from a pick list created from sales orders, and the picker confirms each location by scanning the item. A correct scan confirms the line and the picked quantity, while a wrong item at the shelf should be flagged before it leaves the warehouse. The delivery note is generated from the pick list, so mismatches found during picking carry into shipping documents. Check how a batch barcode behaves when it differs from the batch the pick list suggested.
Sales invoice and point of sale
At billing and point of sale, a scan adds the item to the invoice or the POS cart. A barcode tied to a specific unit of measure can set the sale quantity in that unit, such as a case instead of a single piece. The rate depends on the price list and customer group, so the same scan can return a different price for a different customer. An unknown barcode should not add an unpriced line to a sales invoice. Confirm how the POS screen handles returns, discounts and connectivity loss.
Stock reconciliation for counts
Cycle counts and full physical counts use scanning to capture the counted quantity in a stock reconciliation. Each scan should add to the count for that item in the chosen warehouse, so a recount does not double a line that was already captured. Confirm whether repeated scans increment or overwrite the count in your version, and whether the difference against the system quantity is visible before submission. Treat an unknown barcode as a possible gap in the item master, not a stray scan.
How to set up barcode scanning in ERPNext step by step
This sequence takes barcode scanning from a agreed labeling standard through item data, scanner setup, document testing, labels and a validating count, so receiving, picking and sales all read the same codes.
Agree the barcode standard and code ownership
Decide which symbology your scanners and labels will use, whether you will reuse supplier barcodes or issue internal codes, and who is responsible for creating and retiring them. Confirm with your scanner vendor and label printer which formats they read reliably, and record the rules in a short internal document. This step is done when operations, purchasing and the item owner have signed off on one written standard and one named owner for new codes.
Clean item master data before adding codes
Review the item list for duplicate items, inconsistent item names, and units of measure that differ between purchasing and selling. Retire or merge duplicates, because a barcode that points to the wrong item will misstate stock in every document that scans it. Check that each stock item has the correct default unit and that the pack sizes you buy and sell are modeled as separate units. This step is complete when a sample export of active items shows one record per sellable or stockable product.
Add barcodes to items and units of measure
Open each item and add its barcode in the item's barcode table, and where a case or pack carries its own code, add that code against the matching UOM. Keep the item-level barcode for the base unit and use UOM-level barcodes only where a pack has its own label. Scan a test item into a draft Purchase Receipt and confirm that the item, unit and quantity fill in correctly. Repeat for one pack barcode to confirm the conversion factor applies.
Configure scanners in keyboard or camera mode
Most handheld and desk scanners in keyboard-wedge mode type the code into the focused field followed by Enter, so confirm the suffix setting matches what ERPNext expects. Camera scanning from a phone or tablet depends on the browser and the device, so test it on the hardware your staff will use and confirm the camera permission is granted. Ask your scanner supplier to document how to set the prefix, suffix and symbologies, and keep those settings in your configuration notes. This step is done when a test scan into a Stock Entry lands in the item field without manual correction.
Test each document type with sample items
Build a small sample set of items covering a serialized item, a batched item, an item with a pack UOM, and a plain item. Scan them through a draft Purchase Receipt, a Delivery Note, a Sales Invoice and a Stock Reconciliation, and record the quantity and unit that each document shows. Where a document does not accept scans in your version, note that gap and confirm the workaround with your implementation lead before go-live. The step is complete when each document type produces the expected quantity for every sample item.
Design label templates through print formats
Create the label layout as a print format on the item or stock document, with the barcode field, item code, item name and any batch or serial number you need to show. Test the printed output on the exact label stock and printer model used on the floor, because print scale and symbology quality change between printers. Confirm the scanned output of each printed label reads back to the item it was printed for. This step is done when a printed label from each template scans correctly on the receiving station.
Run a count to validate stock reconciliation
Choose a warehouse and a sample of items, count them by scanning the codes and the quantities, and enter the results in a Stock Reconciliation. Compare the system quantities with the physical count and investigate any variance before submitting the document. Confirm with your finance lead that valuation rates and accounts behave as intended before rolling the process out more widely. The step is done when the scanned count matches the physical count for the sample and the variances are explained and documented.
Barcode strategy for warehouses, shops and production floors
A distribution warehouse scans most heavily at receiving, putaway, picking and dispatch. The usual barcode layers are the item barcode on each sellable unit, a case or pallet barcode that carries the packed quantity, and a bin or location label that the team scans to confirm where stock sits. Handheld laser or imager scanners on mobile devices are typical, and the main risk is a receipt booked against the wrong unit of measure, because a scan of a carton that resolves to the each-level item posts the wrong quantity.
- UOM-specific barcodes: Assign a separate barcode to each unit of measure, such as the each, inner pack and case, so a scan posts the quantity the box actually holds.
- Location labels: Print warehouse and bin labels and scan them during putaway and transfers so stock lands where the process expects.
- Supplier barcodes: Decide whether supplier GS1 or manufacturer codes are mapped to items, and who maintains that mapping when a supplier changes a pack.
- Batch and serial scans: Where lots or serials are tracked, the scan must capture the batch or serial number as well as the item, so the Serial and Batch Bundle records what was received.
- Pick confirmation: Scan each pick against the pick list and block short or over picks in the workflow where your process allows it.
Confirm with your team which barcode belongs to which unit of measure and which items need batch or serial capture, then test receiving, putaway and picking together before go-live.
At a shop counter or point of sale, scanning speed matters most and the sale is often recorded through an invoice or a point-of-sale screen. The usual layers are the retail barcode printed by the manufacturer on each item, an internal code printed by the shop for unbranded or fresh goods, and sometimes a weight or price-embedded code for produce. Fixed counter scanners and card or receipt printers are common, and the main risk is a mismatch between the scanned barcode and the item price or tax setting, which shows up later as margin or tax errors.
- Retail barcodes on items: Map each manufacturer code to the correct ERPNext item and confirm that variants with different codes are not merged.
- Internal labels: Create shop codes for items without a manufacturer barcode, and keep them separate from supplier codes to avoid collisions.
- Serial scanning on sales: For serialized goods, scan the serial at invoice time so the sold serial is removed from stock and recorded against the customer.
- Returns: Scan the original invoice or serial on return so the credit reverses the right stock and value.
- Offline or outage handling: Decide how sales continue when the network or the ERPNext server is unavailable, and how those sales are reconciled afterward.
Confirm which sales path your shop uses, whether point of sale or invoice scanning, and test serialized returns and price lookups with real sample items before opening.
On a production floor, scans record material issue to a work order, transfers of components to the line, and finished goods entering stock. The usual layers are the item barcode on raw materials and components, a lot or batch label from the supplier or the shop, and a work order or job card code that ties a scan to a production step. Rugged mobile devices and fixed stations at each workstation are typical, and the main risk is issuing the wrong batch or serial into a production run, which breaks traceability for the finished product.
- Material issue scans: Scan components when they are issued to a work order so consumption matches the bill of materials and the batch used is recorded.
- Finished goods labels: Print labels with the item and batch or serial at completion so downstream scans can trace what was made.
- Work order codes: Use a scannable code for each job card or work order to link operator actions to the right production run.
- Quantity checks: Confirm that scanned quantities match the planned consumption and flag variances before the work order closes.
- Harsh environment hardware: Choose devices rated for dust, moisture and temperature, and plan for label durability on metal or cold storage.
Confirm with your production engineers which items must be traced by batch or serial through each step, then validate material issue, completion and traceability reports together before the first production run.
Loading barcodes in bulk with the Data Import tool
When barcodes already sit in a spreadsheet, the ERPNext Data Import tool is the usual way to load them in bulk instead of typing each item by hand. The tool imports and updates records from CSV or Excel files, and it works from downloadable templates for each doctype. It also supports child table rows, which matters for barcodes because an item can carry more than one barcode, and a unit-specific barcode for a case or pallet is stored as a row in the item's child table rather than as a single field. Build the file from the template the tool generates for your version, not from an older sheet you copied from another system, so the column headers match what the importer expects.
The documentation advises importing only a few thousand records at a time, so a large catalog should be split into batches, each with its own file and a clear record of what it contains. Run one batch on a test site first and check that the item codes, barcode values and UOM rows landed where you expected. After each batch, reconcile the counts: the number of items in the file against items created or updated in ERPNext, and a sample of barcodes scanned at a workstation. Plan for duplicates, since a barcode that already belongs to another item will cause a conflict that you need to resolve in the source file, not in the live catalog.
Before you commit to a bulk load, confirm on a test site that the barcode fields and unit barcode rows in the downloaded template match the ERPNext version you run, because the item and barcode structure has changed across releases. Ask your implementation partner or ERPNext administrator to record the template version, the batch sizes and the reconciliation results, so the load can be repeated or audited later. Treat the first production batch as a supervised run with someone ready to correct the source file and re-import.
Security and operational risks of scanning at the counter and dock
A barcode scan posts stock and money movements faster than a person can review them, so the risks sit in who can change item master data, who is logged in at the scanner, what labels reveal, and which errors go unseen. Each card names one risk, the ERPNext role or permission control that addresses it in general terms, and what to confirm in your own environment before go-live.
Who can edit barcodes and units
An item barcode or UOM conversion that points to the wrong item will quietly route receipts and deliveries to the wrong stock. Restrict edit rights on the Item doctype, including its barcode and UOM child tables, to a small master data group, and keep warehouse users read-only. Confirm which roles in your environment can change barcodes, whether those edits are logged, and who approves a new barcode before it reaches the dock.
Shared scanner and terminal logins
When several operators share one terminal login, the stock entry shows the account, not the person who scanned the pallet, so receiving discrepancies cannot be traced. Give each operator a named user with a role limited to the scan screens they need, and make session timeouts and two-factor authentication part of the design. Confirm how your site handles login policy and whether any dock device is still using a generic account.
Labels that reveal prices or supplier codes
Labels printed from item and supplier data can expose cost, selling price or a supplier's part number to anyone who picks one up from the floor or a bin. Review which fields each print format pulls in, and limit label printing to roles that need it. Confirm whether your print formats include rate or supplier fields, and who can change a print format in the system.
Scanned quantities that skip review
A scan that increments quantity without a second check can post a receipt or delivery that nobody reviewed, especially when a scanner is set to accept a default quantity. Decide which documents post directly and which go through a draft or approval step before they affect stock, and set roles so that the person who scans cannot also approve the same variance. Confirm which document types in your flow are submitted automatically and who reviews stock reconciliation differences.
Monitoring duplicate and unknown barcodes
Duplicate barcodes across items and unknown codes scanned at the counter are early signs of bad master data or tampering, but they fail quietly if no one reads the errors. Assign an owner to review failed scans and barcode conflicts on a set schedule, and keep the access logs and version history for item changes. Confirm where your team will see these errors, how long logs are kept, and who is alerted when a barcode is reassigned.
Questions buyers ask before adding barcode scanning to ERPNext
How much effort does barcode scanning setup take in ERPNext?
The effort depends mostly on how many items and unit barcodes you have, how many label formats you need, which scanning devices you use, and whether your items are batch or serial tracked. A catalog with one barcode per item and a single label size is a much smaller job than one with multiple units of measure per item, several packaging levels and tracked stock. Each device type also needs testing, because scanner keyboard modes and camera behavior differ. Ask any partner to break the estimate down by these drivers rather than giving one total.
Can our own team set up barcode scanning without a partner?
Yes, many teams configure item barcodes, UOM-specific barcodes and label printing in-house, provided someone understands the ERPNext stock modules and has time to test. The harder parts are usually the item master clean-up, agreeing barcode rules with suppliers and warehouse staff, and validating receipts, deliveries and reconciliations against real stock. If your team has no ERPNext stock experience, or cannot dedicate people to testing, an external partner can take on the configuration and test scripts while your staff keep ownership of the rules.
What does our team need to provide before scanning work starts?
Three things matter most. First, a clean item master, with duplicate items, inconsistent names and unit definitions resolved, because barcodes attach to items and UOMs. Second, a named owner for barcode rules, covering who issues new codes, which codes come from suppliers and which are generated internally. Third, sample stock and sample documents in a test environment, including batch or serial items if you track them, so that receipts, picks and invoices can be scanned and checked end to end. Without these inputs, the pilot tends to uncover data problems that should have been fixed first.
How long does a pilot in one warehouse usually take?
The pilot length depends on the number of items in scope, how many document types you test, and how quickly your warehouse can run test receipts, deliveries and counts alongside normal work. A focused pilot covering one warehouse, one set of label formats and the main scanning flows is faster than a site-wide rollout, which adds device deployment, staff training and cut-over planning. Ask for the pilot timeline in the written scope, with named acceptance tests and the sample data each test uses, so the duration is tied to deliverables rather than an open-ended estimate.
Does barcode scanning work on mobile devices with ERPNext?
ERPNext works in a mobile browser, and barcode input can be entered through a device that supports camera scanning or a connected hardware scanner acting as a keyboard. Whether a specific phone, tablet or rugged handheld scans reliably depends on the camera quality, the browser, lighting and the barcode symbology used. Confirm the exact device models, browsers and symbologies you plan to use, and run them against your real labels in the pilot. Also confirm how each device connects to the network inside your warehouse, because weak Wi-Fi often causes more problems than the scanner itself.
What should a barcode scanning quote include?
A useful quote lists the scope in writing: the item and UOM barcode set-up, the document types covered (receipts, deliveries, invoices and stock reconciliation), the label formats and printers, the devices to be tested, and the batch or serial handling in scope. It should also state what the client provides, the acceptance tests, the pilot warehouse and the training included. Separate one-time work, such as configuration, testing and training, from any recurring support. Ask how changes to scope are priced and who owns the final configuration. DeployOpen agrees scope, deliverables and timelines in writing before work starts, and the quote follows from that scope.
Limits to confirm in your ERPNext version and environment
Barcode scanning in ERPNext depends on the exact version, the item setup and the hosting model you run. The cards below are questions to answer with your own test data before you agree on scope, because each one changes how receiving, picking and sales documents behave.
Multiple barcodes per item and unit
Ask how ERPNext resolves an item that carries several barcodes, and whether a barcode can be tied to a specific unit of measure such as a single unit, an inner pack or a case. Confirm which document types (purchase receipt, delivery note, sales invoice, stock entry and stock reconciliation) pick up the unit-specific barcode and which fall back to the item default. Test a case where two items share a supplier barcode, since a wrong match at receiving posts the wrong stock.
Scanning batch and serial items
Ask whether scanning a barcode on a batch or serial item in your version fills the Serial and Batch Bundle correctly, or whether the team must enter the batch or serial numbers by hand. Confirm how the scanner behaves when a batch is expired, when a serial has already been delivered, and when a pick would drive a batch below zero. Run each case in a test site on the version you plan to use, since behavior differs between releases.
Label formats and printers
Ask which label sizes, symbologies (such as Code 128 or QR) and printer languages the standard print formats support, and which need a custom print format or a third-party label tool. Confirm whether the printer is driven from the browser, from a local print agent or from a network print server, and who maintains the template when a label design changes. Print a test sheet on the actual printer before the label design is signed off.
Scanner and camera compatibility
Ask whether the USB or Bluetooth scanners in use act as keyboard input and work in the browser or app your staff use, including the mobile and tablet clients on the warehouse floor. Confirm whether camera scanning works on the devices involved, and which browsers and operating system versions have been tested. Ask how a scanner that appends a newline or tab is handled, because the wrong suffix can submit a form before the quantity is entered.
Hosted environments that restrict scripts
Ask whether your hosting model allows the custom server scripts that a barcode workflow may need. Server Scripts are disabled by default from version 15 and must be enabled with the server_script_enabled setting, and public shared benches on Frappe Cloud do not allow them. If the logic needs a custom app, confirm the plan for hosting it, its upgrade path and who signs off changes to the scanning behavior.
Barcode import and export for other systems
Ask whether downstream systems such as a warehouse management tool, a shipping platform or an ecommerce channel need the barcode master data in a defined format. Confirm whether barcodes can be loaded and updated through the Data Import tool from CSV or Excel, including child table rows, and how large the batches should be. Agree which system owns the barcode master, so that a change made in one system does not silently overwrite the other.
How DeployOpen scopes and delivers barcode scanning for ERPNext
DeployOpen plans, implements, customizes, tests, documents and supports ERPNext inside your own infrastructure, so barcode scanning fits your receiving, picking and sales flows. We agree the scope in writing first, then build and verify each scanning path against your real item, UOM and warehouse setup before handover.
How we scope
- We list the scanning points you need: receipts, picks, deliveries, invoices and stock reconciliation.
- We map which items carry item-level barcodes and which need UOM-specific barcodes such as case or pallet codes.
- We agree in writing which label formats, printers and scanner hardware are in and out of scope.
- Engagements are fixed-scope, with deliverables and timelines confirmed before work starts.
How we build
- We configure item and UOM barcodes and check that scans resolve to the correct unit of measure.
- We set up scanning behavior in receipts, delivery notes, sales invoices and stock reconciliation to match your process.
- We design and test barcode label prints, then verify label output on the printers you will use.
- We test scanning with negative cases, such as unknown codes and duplicate barcodes, before go-live.
How we hand over
- We document the barcode scheme, item setup rules and the step-by-step scanning procedure for each role.
- We provide a test script that warehouse staff can run to confirm scanning works after each change.
- We walk your team through the configuration so you can maintain new items and labels yourselves.
- We confirm which steps depend on your scanner hardware settings, which you should verify with the device vendor.
How we support
- Ongoing support, upgrades and testing after go-live are available as a retainer.
- We review scanning changes when you add item families, new UOMs or new warehouses.
- We plan how barcode settings are checked when you upgrade ERPNext, with the upgrade scope agreed in writing.
