Barcode scanning for inventory & stocktakes (NZ)

Understand the decision

The single biggest driver of stock accuracy isn't a software feature list, it's whether your team scans. Manual counts and re-keying introduce error at every step; barcode and RF scanning capture each movement at the point it happens, so the system matches the shelf.

This guide covers how scanning works in practice for NZ operators, receiving, putaway, picking, dispatch and cycle counts, what hardware fits, and where scanning sits in the inventory-vs-WMS spectrum.

OpsUI's warehouse modules run scanner-driven workflows on standard devices; here's honestly when you need that depth and when a basic inventory tool is enough.

Local operating considerations

OpsUI runs barcode/RF scanning across its warehouse modules (Receiving, Picking, Cycle Counting, Shipping) on standard Android/iOS devices and dedicated scanners, see hardware for the device side. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. For where scanning sits between inventory and WMS, see wms vs inventory management and inventory management software nz.

Ask which carrier accounts, services and label formats are supported; how your accounting records move; and where production data, backups and logs are held. Record the answers for the exact deployment under consideration.

Compare the full operating cost.

Separate subscription cost from user allowances, integrations, devices, data preparation and onboarding. Ask who owns configuration, training, cutover and support, and which items are recurring.

A starting subscription price is not an implementation quote. Compare the same workflows, team size and transaction volumes across proposals. Keep the original currency, tax treatment and billing period visible.

OpsUI’s published package structure

Published monthly subscriptions in NZD. Existing annual pricing and package allowances apply. Additional seats are NZ$99 per month beyond the applicable allowance; integration connectors are separate add-ons.

A checklist you can use in a demonstration.

Bring representative records and ask each vendor to work through the same scenarios. Write down what was demonstrated, what needs configuration and what remains unverified.

1. Receive a discrepancy. Use an expected delivery with a missing line and damaged stock. Follow the difference through recording, review and the stock decision.
2. Allocate constrained stock. Use two orders competing for the same stock. Check reservations, priorities and what the service team sees.
3. Resolve a short pick. Start with an empty pick location. Show the exception, reassignment or backorder, and who can approve the next step.
4. Complete the dispatch handoff. Use your carrier, parcel mix and label format. Check tracking references, manifests and a rejected address.
5. Recover from an interrupted sync. Reject a record or interrupt delivery. Show visibility, retry behaviour, duplicate prevention and reconciliation.
6. Confirm access and reporting. Run the same scenario as an operator and supervisor. Check action permissions and the records available for investigation.

Fit and trade-offs

When you don't need scanning yet

If you sell a tiny single-location catalogue at low volume, a periodic manual stocktake may keep you accurate enough without any scanning workflow.

If you don't have bin locations or a real pick face, scanning adds little, the value comes from capturing movements you currently re-key.

If your need is purely accounting-inventory, Xero or MYOB's native tracking may suffice until volume or locations grow.

When scanner-driven accuracy pays off

Once you're multi-location, picking from bins, or moving real order volume, scanning eliminates the error and re-keying that periodic counts can't — receiving, putaway, picking, dispatch and cycle counts all captured at the point of action.

Flat per-module pricing lets you put scanners in front of every floor worker without a per-user tax, so accuracy isn't rationed by licence cost.

Every scan reconciles back to the stock record and the ledger (Xero, MYOB or NetSuite), with NZ data residency, so floor accuracy and the books stay in step.

Questions buyers ask.

Sources and evidence

Checked facts apply only to the scope described next to each source. Other vendor details in the editorial analysis remain unverified for a current purchase decision. Confirm them with the vendor and record the applicable plan, version and proposal date.

Current primary-source verification of this vendor’s detailed capabilities and prices is pending. An unknown is not a missing feature.

OpsUI integration delivery and scope · Security review information · Published OpsUI packages

Continue your evaluation.

• Inventory management for MYOB (NZ & AU)→
• Inventory software for small business in New Zealand→
• OpsUI vs Cin7 Core→
• OpsUI vs Unleashed→
• OpsUI vs Cin7 Core (formerly DEAR)→
• OpsUI vs Katana→