Scan, sync and reconcile without losing the evidence.
The current pilot shape stages master data, opens a scoped count session, preserves raw scans through offline sync, and routes variance into review.
Keep the physical count and the reviewable evidence in the same workflow.
A private pilot for barcode-led physical inventory: scan, count, reconcile, review, approve, export and prove.
Availability is stated from the current source and test evidence. A private pilot is a review boundary, not a general-availability claim.
Open product proof →Where evidence enters, and where it stops.
The flow mirrors the current product boundary. It does not imply an unimplemented platform layer.
- 01
Master data
Stage a bounded Product Master import, validate rows and keep rejected or duplicate rows reviewable before applying any batch.
- 02
Count session
Define site and location scope, assign roles and open a count task with a baseline/as-of time and progress state.
- 03
Scanner and sync
Preserve the raw scan, resolve the configured lookup, queue work durably when offline and retry idempotently when connectivity returns.
- 04
Reconcile and prove
Compare expected and counted values, route exceptions and recounts, then export a reviewable result with audit evidence.
Capability truth stays close to the evidence.
States below are intentionally conservative. Partial source coverage remains Preview until the full product boundary is accepted.
| Capability | Status | Evidence boundary | Public proof |
|---|---|---|---|
| Product Master import Validation, duplicate detection and rejected-row reporting are part of the staged workflow. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Sanitized import preview |
| Locations and branch scope Customer-specific branch terminology remains in the working source and is not exposed in public proof. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Scope preview |
| Physical count sessions Session lifecycle, assignment, progress and close/reopen controls are present in the working app. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Session dashboard preview |
| Scanner and raw evidence Raw scan, normalization, alias/lookup and duplicate handling remain evidence-bearing steps. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Sanitized scanner preview |
| Offline queue and idempotent sync The accepted workflow keeps pending state, sync retry behavior and client request identity visible. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Offline queue preview |
| Reconciliation and variance Expected, counted, variance and review state stay tied to raw evidence. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Reconciliation table preview |
| Exceptions and recount Recount assignment and blind-count controls exist for variance review. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Exception review preview |
| Roles and audit trail Counter-like access is separated from administrative approval and configuration access. | Available | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Audit preview |
| Media evidence Media support exists in the working source but remains bounded and pilot-reviewed. | Preview | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Not used in public proof |
| ERP adapters and broader stock operations The pilot is not represented as a universal ERP/WMS replacement. | Preview | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Pilot-only integration preview |
| Serial, lot and recurring count plans These are P1 design items until they are implemented and independently accepted. | Planned | Source-backed capability and test evidence. Private operator boundary; no public credentials or production records. | Not shown as available |
Answers without the larger claim.
Does Inventory replace an ERP or WMS?
No. The pilot focuses on physical count evidence and reconciliation. Existing systems remain the source of truth unless a separate integration scope is approved.
Can it use existing barcodes?
The working scanner flow supports raw scan preservation, normalization and lookup rules. Pilot inputs are reviewed before access.
Does it work offline?
The accepted scanner workflow includes durable pending state, retry and idempotent sync evidence. The exact device and network matrix is validated in the pilot.
Can multiple locations be counted?
Location and branch scope are present in the working app. The pilot defines the hierarchy and access boundary rather than assuming every operating model is identical.
Can we run blind counts?
Blind count and recount controls are present in the working source, including a second-counter workflow for variance review.
Does it change stock automatically?
No automatic production adjustment is implied by the public page. Approval, export and any ERP posting are separate controlled steps.
This public page shows source-backed product shape and sanitized demonstration evidence for Inventory. It is not a customer report, production dashboard or general-availability promise.