OneScan AI

    Picking & verification for SAP EWM

    One scan per pick,and every one of them checked.

    OneScan AI reads one composite label, checks bin, material, serial and handling unit against the warehouse task, and stops a wrong pick before it posts to SAP EWM, with extra checks only where the risk is real.

    PostedMAT-1002
    The OneScan command-center conveyor, replaying sample scans
    fills and checks four fields
    1 scan
    fills and checks four fields
    of risk-adaptive verification
    3 levels
    of risk-adaptive verification
    posts while a check is pending
    0
    posts while a check is pending

    Today on the floor

    Every pick line costs seconds, and some cost customers

    Separate checks per pick

    Bin, material, serial number and handling unit are confirmed one by one, often on paper or in SAP GUI.

    Wrong picks reach customers

    A single mismatched serial or handling unit goes unnoticed until goods issue, packing or delivery.

    Supplier labels keyed by hand

    Labels in a supplier's own layout cannot be read, so they are typed in or wait for a ticket.

    No live view for supervisors

    Open, confirmed and failed tasks are hard to see without running SAP reports.

    Where it fits

    OneScan owns one step of the SAP order flow

    Everything before and after stays in standard SAP. OneScan makes the pick itself one scan and verified.

    SAP S/4HANA

    1. Order

    • Sales order
    • Outbound delivery
    • Replicated to EWM

    SAP EWM

    2. Task creation

    • Outbound delivery order
    • Wave release creates warehouse tasks
    • Bin, handling unit, material, quantity

    OneScan AI

    3. Scan and confirm

    • Fetch open warehouse tasks
    • One scan at the source bin
    • Validate and confirm

    SAP EWM and S/4HANA

    4. Goods issue

    • Warehouse task confirmed
    • Goods issue posted
    • Delivery updated

    The 1-scan engine

    Four fields, one label, checked against the task

    A composite barcode carries the bin, material, serial number and handling unit. OneScan splits it, compares every field with the open warehouse task on the server, and refuses confirmation until they all match.

    OneScan composite label2D · BIN|MAT|SER|HU

    BIN-A01|MAT-1001|SER-1001|HU-9001

    Bin
    BIN-A01
    Material
    MAT-1001
    Serial
    SER-1001
    Handling unit
    HU-9001

    Warehouse task WT1001

    Verifying
    • BinBIN-A01
    • MaterialMAT-1001
    • SerialSER-1001
    • Handling unitHU-9001

    Confirmed in SAP EWM

    And when it does not match

    A wrong bin, item, serial or handling unit stops the pick before posting and is recorded in the exception log, instead of being found at packing or by the customer.

    • Wrong bin
    • Wrong item
    • Wrong serial
    • Wrong handling unit
    • Unreadable label

    Risk-adaptive verification

    Checks sized to the risk of each pick

    Every task carries a transparent pick-risk score built from what happened before: rejected scans on the task, exceptions at the bin, a serial scanned for another task. The verification it requires is enforced, not suggested.

    A single mis-scan stays low risk; repeated problems escalate. A pick cannot be confirmed while a required check is still open. The risk bands are configurable.

    Pick risk · WT1007

    High

    LowMediumHigh

    Why this task is high risk

    • 2 rejected scans on this task
    • Exception logged at BIN-C07 this shift
    • Serial seen on another task
    1. Low risk

      One scan

      The composite label alone confirms the pick.

    2. Medium risk

      + Bin check

      The operator also confirms the bin before posting.

    3. High risk

      + Bin and item check

      Bin and item are both confirmed before posting.

    Label studio

    Supplier labels, read by governed rules

    A label that is not in the composite format can be read with an approved supplier rule: a delimiter and one field per segment. No ad-hoc parsing, no silent changes.

    1. 01

      Unreadable scan

      The label is captured and assigned to its supplier as a sample.

    2. 02

      Rule proposed

      OneScan proposes a layout from purchasing info records and master data.

    3. 03

      Tested on samples

      The rule is run against every saved label from that supplier.

    4. 04

      Supervisor approves

      A warehouse supervisor approves; the previous version is retired.

    5. Read on the floor

      Matching labels are now read by the rule, with rollback available.

    Capabilities

    Built around the pick, not the paperwork

    1-scan composite barcode

    BIN|MATERIAL|SERIAL|HU parsed and validated against the task.

    Risk-adaptive verification

    One scan, + bin check, or + bin and item check, always enforced.

    Label studio

    Teach OneScan a supplier's label layout; a supervisor approves the rule.

    Supplier scorecard

    Clean first scans, unreadable labels and mismatches per supplier, with evidence export.

    Serial trace

    Follow any serial or handling unit through every scan and decision.

    Audit evidence

    Raw barcode, rule, device, user, risk and every decision step kept per scan.

    Safe confirmation

    If SAP's answer is lost, the task is held, never posted twice.

    Exception log

    Wrong bin, item, serial, HU and unreadable labels, resolved on confirmation.

    Joule-ready assistant

    An in-app assistant panel prepared for SAP Joule.

    Live diagnostics

    Every layer checked, with round-trip time to the SAP system.

    Today vs OneScan

    What changes on the floor

    Confirming a pick line

    Scan or key bin, HU, material and serial one by one

    One composite label fills and checks all four fields against the task

    Verification policy

    The same for every pick: everyone double-scans or nobody does

    Sized to the pick risk of that task, enforced by the backend

    Wrong bin, item, serial or HU

    Often found at packing or by the customer

    Stopped before the EWM posting and written to the exception log

    Supplier label in another layout

    Keyed in by hand, or a ticket for a new parsing rule

    Rule proposed from master data, tested on saved labels, approved once by a supervisor

    Evidence for audits

    Task history in EWM; the raw barcode is usually not kept

    Raw barcode, rule, device, user, risk and every decision step kept per scan

    Supplier accountability

    Anecdotal complaints

    Label quality scored per supplier with exportable evidence

    Built on your SAP EWM

    Same warehouse tasks, same handhelds

    OneScan sits between the scanner and the EWM confirmation. It reads and confirms warehouse tasks through SAP's standard warehouse task interface, and runs on SAP BTP with an SAP Fiori interface.

    • SAP S/4HANA
    • SAP EWM
    • SAP BTP
    • SAP Fiori
    • SAP Cloud Connector

    SAP BTP

    Runs on SAP BTP and reaches S/4HANA or decentralised SAP EWM through SAP's own connectivity services.

    On-premise

    Connects to your SAP gateway over your own network when that is how your landscape is set up.

    Pilot sandbox

    Seeded warehouse tasks for training and evaluation, with no SAP system needed.

    How it works

    From the scan to the EWM confirmation

    What happens between the trigger pull on the handheld and the confirmed warehouse task, where OneScan says no, and how a pick stays safe when the network does not.

    The scan flow

    1. 01

      Scan

      The operator scans one composite label for the loaded task.

    2. 02

      Parse

      The label is split into bin, material, serial and handling unit, or read with an approved supplier rule.

    3. 03

      Validate

      Each field is compared with the open warehouse task, field by field.

    4. 04

      Verify by risk

      The task's pick risk decides whether a bin, or bin and item, check is required before posting.

    5. 05

      Confirm in EWM

      Only a fully matching, fully verified pick is confirmed in SAP EWM, and every step is written to the audit trail.

    What happens on every scan

    Picker scans the label
    Fields are split from the label
    Each field is compared with the task
    All four fields match?
    Yes

    Confirmed in SAP EWM and logged

    No

    Mismatch shown per field, picker rescans

    The flow is the same in every landscape. Only the connection to SAP changes.

    Every scan ends in one of four outcomes

    Posted

    Matched and confirmed in SAP EWM.

    Second check

    Matched; a bin or item check was required by the pick risk.

    Stopped

    A field did not match. The pick was refused and logged as an exception.

    Supplier rule

    A supplier label was read by an approved Label studio rule.

    Roles

    Picker

    Scans, verifies and confirms picks on the handheld.

    Warehouse supervisor

    Approves supplier label rules and resolves held confirmations.

    One task lifecycle

    Open
    scan passes
    Validated
    confirm OK
    Confirmed
    Failed

    Validation fails or SAP rejects the confirmation

    Cancelled

    The user stops before confirming

    On hold

    SAP's answer was lost; a supervisor resolves it

    Safe confirmation

    When SAP's answer is lost, nothing is guessed

    A confirmation that times out or loses its connection might or might not have posted. OneScan never assumes either way.

    1. 01

      Every attempt is recorded

      Each confirmation is written down before it is sent, so its state survives a crash or a dropped connection.

    2. 02

      Unclear outcome, task on hold

      If the answer is lost, the task is held. A new scan cannot lift the hold, so it cannot be confirmed twice.

    3. 03

      A supervisor resolves it

      The supervisor re-reads the task in SAP EWM. Only a definite result, confirmed or not confirmed, releases it.

    4. 04

      Nothing is re-sent on its own

      If the task was not confirmed, the operator scans and confirms again. OneScan never re-sends to SAP by itself.

    From pilot to rollout

    Start small, then scale

    1. 01

      Pilot

      One warehouse area, connected to your SAP EWM, measuring seconds per line and mis-picks stopped.

    2. 02

      Deploy on SAP BTP

      Production deployment in your SAP BTP landscape with your identity and roles.

    3. 03

      Scale out

      More handhelds and warehouses, with KPI reporting for supervisors.

    Business case

    What OneScan AI returns, on your numbers

    The same model as the business case page inside OneScan. Pick a preset, then replace every value with your own. In a pilot, OneScan measures seconds per line and label keying for you.

    Preset

    Volume

    lines
    days

    Speed

    s
    s
    $/h
    %

    Accuracy

    %
    %
    $

    Supplier labels

    /day
    min
    %

    Cost (placeholders)

    units
    $
    $

    What a pilot measures for you

    Seconds per pick line, before and after

    Measured from task opened to confirmed in EWM: median per line, one scan vs with check.

    Mis-picks stopped and their real cost

    Counted from the exception log; priced with your returns, re-ships and credits.

    Manual label keying

    Unreadable and rule-read labels per supplier, from the Suppliers page.

    Realization

    Did the freed hours cut overtime or temporary labour, or absorb volume growth?

    Where the preset assumptions come from

    • Labour: stockers and order fillers, mean wage $18.27/h, grossed up for benefits to about $26/h loaded. BLS OEWS
    • Cost per mis-pick: $30 to over $75 per incident; regulated goods run far higher. Voxware
    • Picking accuracy: industry median 99.5%; scanned RF operations usually do better, so the base case assumes 99.9%. WERC via Cisco-Eagle

    FAQ

    Questions warehouse teams ask us

    What is OneScan AI?

    A picking and verification application for SAP EWM. One scan of a composite label confirms bin, material, serial and handling unit against the warehouse task, with risk-adaptive extra checks and a full audit trail. Wrong picks are stopped before they post.

    Which SAP systems does it work with?

    SAP S/4HANA with embedded or decentralised SAP EWM, through SAP's standard warehouse task interface. It connects through SAP BTP or directly to an on-premise SAP gateway.

    Has the SAP connector been validated on a live landscape?

    The SAP EWM connector is built and covered by automated tests against a simulated SAP service. Validation against a live customer landscape is part of the pilot, and a step-by-step connection check is included to make that fast.

    Do we need new handhelds?

    No. OneScan runs on the handhelds and warehouse tasks you already use; it sits between the scanner and the EWM confirmation.

    What does 'risk-adaptive' mean?

    Each task gets a transparent risk score from rejected scans on the task, exceptions at the bin and serials seen on other tasks. Low risk needs one scan; medium risk adds a bin check; high risk adds a bin and item check. A pick cannot be confirmed until the required check is done.

    What if the network drops while a pick is being confirmed?

    The task is held instead of guessed. Every confirmation attempt is recorded before it is sent, so an unclear outcome is never lost. A warehouse supervisor re-reads the task in SAP EWM and only a definite result releases it. OneScan never re-sends a confirmation to SAP by itself.

    What about labels that are not in your composite format?

    Supplier labels can be read with rules taught in Label studio. A rule is proposed from master data, tested on saved labels and approved by a warehouse supervisor before it is used. Without an approved rule, a label stays unreadable rather than being guessed.

    What evidence is kept for audits?

    For every scan: the raw barcode, the rule used, device, user, risk level, verification level, outcome and a step-by-step trace, plus start and confirmation times. Any serial or handling unit can be traced through every decision.

    Who can approve supplier label rules?

    Only warehouse supervisors. Rules are versioned; rejecting and rolling back are supported.

    How do we start?

    With a pilot on a selected area of your warehouse. OneScan measures seconds per pick line, mis-picks stopped and supplier label keying, so the business case is built on your numbers. Pricing is on request.

    Have a question that is not here?

    Ask the OneScan team

    See a mis-pick stopped before it posts

    A 30-minute walkthrough: one-scan confirmation, a risk-driven second check, a supplier label taught in Label studio, and the full audit trail behind it.