Frequently asked questions

Because a clipboard can't tell you who counted, when, or which exact item. In a spreadsheet someone types SKUs by hand, and every typo becomes a variance that takes weeks to chase. In OpticCount every line starts as a scan: the item resolves from the catalog with a name, a photo and a price, each scan is logged with the counter's name and a timestamp, and a duplicate raises an alert the second it happens instead of in a report at the end.

An external crew shows up for a day, counts, and leaves you with a file. The knowledge and the control leave with them, and counting again means booking them again. With OpticCount your own people count, in your store's own language, and the same count can be repeated whenever you want: fifteen minutes on one category mid-month, with nobody to schedule.

A handheld is another device to buy or rent, charge, hand out and collect, and six counters means six devices. Here the worker's own phone is the scanner, and our scan engine is fast enough that most businesses never need to buy hardware at all. If you still want a Bluetooth gun you can connect one, but it's a choice, not a requirement.

We don't replace the ERP and don't pretend to. An ERP count screen was built for a desk, not for someone standing at a shelf with one hand free. OpticCount is the floor layer: scan from the phone, ten people at once, and the ERP gets a file back in the format it already knows.

You keep counting. Scans are stored on the device and upload the moment the network returns, with a sync indicator on screen. It's one of the reasons a warehouse count in OpticCount doesn't stall halfway through.

Yes, and on the floor it matters more than it sounds. The interface ships in Hebrew, English, Arabic and Russian, and each worker picks their own language on their own device. Same count, same catalog, everyone reading in the language they're fastest in, so fewer mistakes come from misreading an item name.

Any business that counts stock: a single store with two employees, a twenty-branch chain, a distribution warehouse, a garage, a pharmacy or a factory. Same system, different scale. A small business loads few credits and works with one user; a chain adds stores, users and permissions without moving to a different product.

The one step that needs preparation is the catalog: upload an XLSX or CSV, map the columns on a mapping screen (name, barcode, price, location and more, matched by header name), and from there you open a count and scan. There's nothing to install on servers and no IT project.

The screen a counter sees does one thing: scan and add. There are no menus to learn, and the item pops up with a photo and a name so it's obvious the right thing was scanned. In practice a worker starts after a short demo at the shelf, and it's the count manager who touches the settings.

No. The smartphone camera is a full scanner, and the app runs in the browser as a PWA with no app store install (add to home screen in one tap). Bluetooth scanners are an optional one-time purchase with a one-year warranty, and every sixth scanner is free.

No technical ceiling. The system is built for tens of thousands of items and hundreds of thousands of scans, and stores and users are added from the screen. What drives price is how many users work in parallel and how many credits you loaded, not how many stores you opened.

One credit = one item scanned, regardless of the quantity you entered on it. Every process (counting, receiving, picking and more) draws from the same shared credit bank, and the more you load at once, the lower the price per credit. You pick processes, volume and users and get one final number up front, with no asterisks and no commitment.

The count doesn't stop. Load more in one click at any moment, including mid-count, and it applies immediately. On the annual plan, up to 25% of leftover credits carry over to your next renewal if you renew within a month of the period ending.

Yes. There's a single-month license for a one-off count alongside the annual plan. Counting once a year shouldn't mean paying for a whole year, and counting every month gets you a full year for close to the price of a single month.

The scanning interface, several counters working in parallel, scanning with the smartphone camera, controls that prevent mistakes, unlimited export of count data, a variance report and stock reports for the ERP, management of stores, users, locations and permissions, unlimited cloud storage, and version updates at no cost. Phone and WhatsApp support sit in there too.

Yes. Common in variations (color/size). Enable autocomplete to choose by name/description. The reverse (different SKUs sharing one barcode) is supported but not recommended due to ambiguity.

Yes. Search by name or SKU (partial match). Enable autocomplete for fast selection.

Scanner is preferable for hundreds/thousands of consecutive scans, harsh lighting, or worn labels. The phone camera is sufficient for most use cases, our scan engine is fast and nearly identical to a dedicated scanner, and saves hardware costs. In practice, the phone camera is enough for most operations.

Currently no. We come in once you have a file and stay through the export of the summary.

Yes. XLSX and CSV are supported. There's a smart column mapping screen, item name, barcode, price, color, size, model, balance, location, and more. Order doesn't matter, mapping is by header name.

Yes. The catalog is shared across stores, but if you upload columns like 'location per ERP' or 'quantity per ERP', you'll be asked to pick a store to attach the location/balance data correctly.

Stopping inventory movement is recommended, but rolling counts work too, count a zone, mark complete, continue. If your ERP supports a date-window file load, in-flight movements are handled.

Yes. Enable autocomplete, after 2 seconds, a match list appears.

Yes. Open the recent scans list → pick an item → delete or edit quantity. With 'Cancel auto-add after alert' enabled, every scan requires confirmation, reducing mistakes.

No hard cap; the system is built for tens of thousands of items and hundreds of thousands of scans. Workers can count in parallel, enable duplicate alerts for safety; everything merges in real time.

Yes. Count by location, category, or a defined item list. The export lets you choose: only counted items, only negatives, or a consolidation by fields.

Yes. In user management, define a list of authorized stores per user.

Yes. You can download at any stage, it doesn't disrupt the count.

Yes. The Excel export lets you choose which columns to include and pick consolidations. Complex needs, reach out and we'll guide you.

Currently no public open API. We have official integrations, Shopify, Wix, WhatsApp, and more, and customizable file exports. Need a dedicated connection? Contact support.

Yes, through the integrations page. Support for Shopify, Wix, WhatsApp, and more. Other systems, usually via custom export or a dedicated integration.

Yes. In user management, add users and grant permissions. Licensing is based on active users and scan volume (per your plan).

Yes. Scanners are input devices (like keyboards), add as many as you want. Licensing isn't per hardware unit but per user and scans.

Both are supported: Bluetooth/USB HID scanners (very fast) and the smartphone camera.

Yes. In advanced settings: duplicate alerts, item-not-in-catalog warnings, negative/positive controls (per customer needs), and the option to manually approve every addition after an alert.

Yes. Fields like size, color, and model are supported in the catalog and exports. We recommend a unique barcode per variation.

Yes. Count each entity separately, then download and consolidate (including a 'view-all' screen with 'consolidate all stores').

Yes. In license management, you can extend the plan or add capacity. Activation is immediate.

Yes. WhatsApp and email support are available; depending on your plan, phone support when needed.

Yes. 300 scans for the first month + an active user, free trial. Start working and feel the system without commitment.

Only essential data is kept locally for fast operation (cache, recent scans). The counts themselves live in the cloud and sync. No dependency on a specific device.

Servers in Israel only, logical separation between customer data, continuous backups. End-to-end encryption (TLS 1.3). Full audit log for every action. Development team with cybersecurity background.