Retail

Stock you can sell, on the shelf.

Counts that match the shelf, deliveries that can be verified and exits that can be watched. The right technology is chosen for each step in the store and connected through DERAS to the POS and ERP already in use.

Retail store

The everyday gaps

Most lost sales start as a missing record.

An item the system shows but no one can find, a delivery no one checked, a loss no one saw. Different symptoms, one root cause: no reliable record of what moved, where, when and through which door.

65%of inventory records did not match physical stock in a field study of a leading retailer. California Management Review

1.6%of retail sales lost to shrink on average, with 27% of it traced to process and control errors. NRF National Retail Security Survey, 2023

Staff counting stock in a stockroom with a handheld readerPOS: 6 in stock · Shelf: 0
01

The system says it’s in stock. The shelf is empty.

Customers leave without buying, and the gap only shows up at the next count.

02

Counts that close the store

Full counts run overnight or after closing, so they happen a few times a year at best.

03

Deliveries no one really checked

Cartons are signed for and shelved, and differences from the ASN surface weeks later.

04

Stock stuck in the backroom

The item is in the building, just not on the floor where customers can find it.

05

Losses no one saw happen

Theft and process errors show up as a number at year end, without a record of when or where.

06

Online orders for stock that isn’t there

Orders are accepted from a store that cannot fill them, then cancelled.

07

Returns and transfers that fall through

Items moving between stores or coming back from customers drop out of the record on the way.

08

Data in too many places

POS, ERP, e-commerce, CCTV and door access don’t talk to each other, so every discrepancy is investigated by hand.

The workflow

From the delivery door to the checkout.

Pick a stage to see where the record is lost today, and what changes. One DERAS layer carries every event to the dashboard and the POS and ERP already in use.

BACKROOMASN 331812 of 12 casesDoor 1 · 09:42Delivery · verified

Stage 01

Receiving

Today

Cartons are opened and counted by hand, and differences from the ASN are found late.

With TUDI

Deliveries are verified against the ASN at the backroom door, with a time-stamped record.

Technology options

  • UHF RFID portal
  • Handheld reader
  • Barcode

DERAS · filter reads, add context, connect systems

+ camera and access events from across the store
Operational dashboard
Your existing POS / ERP

Example flow. Capture points, technology and integration are confirmed per project after assessment.

The software that connects it

Devices capture.
DERAS makes sense of it.

One garment near a reader can be read many times by several devices. The POS and ERP need one clean line: item received at Store 12, 09:42. DERAS sits in between, so technologies and brands can be mixed without rebuilding existing systems.

  1. Filter and deduplicate. Repeated and stray reads are removed, so each movement is recorded once.
  2. Add context. A read becomes a store event: which item, which store, when, and which step.
  3. Connect what is already running. One operational dashboard, with events passed to the POS and ERP. No rip-and-replace.
DERASILLUSTRATIVE WORKSPACE

Retail item events

CASE-3318RFID backroom doorMatched to ASN
SKU-2041Handheld count1 on floor · 5 in back
ITEM-7710POSSold
ITEM-7712Exit gate + cameraUnpaid · alert
01 / VISIBILITYOperational dashboard
02 / INTEGRATIONYour existing system ↗

Example interface and data. Workflow and integration are scoped to your project.

RFID reader, antenna and inlay tag

Realistic outcomes

What changes, and what needs process.

Technology makes good store process faster and easier to sustain. It does not replace it, so expectations are agreed before anything is installed.

No number is promised before the stores have been seen. The metrics are agreed, measured, and used to decide whether to roll out.

What improves

  • Counts that take less time and happen more often
  • Shelf gaps seen while stock is still in the backroom
  • Online availability that matches the shelf
  • Losses linked to a time, a door and a record

What still needs process

  • A tagging plan: at the source or in store, and for which categories
  • A clear response when the exit gate alerts
  • Training and ownership on the floor and in the backroom

How it is measured

A baseline is recorded first, then compared during the pilot:

  • Stock accuracy by SKU and store
  • Time per full-store count
  • Empty shelves while stock is in the backroom
  • Online orders cancelled for missing stock
  • Exit alerts and confirmed losses

One partner, end to end

From the first store walk to day-to-day support.

One team owns the whole project, so devices, software and existing systems work as one.

  1. 1

    Assess

    Walk a pilot store, map the flow from delivery to checkout, find where the record is lost, and check current systems and RF conditions.

  2. 2

    Design

    Choose the technology mix per step: barcode where it is enough, RFID, cameras or access control where they pay off.

  3. 3

    Supply & deploy

    Devices, tags and labels, exit gates, mounting and installation, tested on the real merchandise.

  4. 4

    Integrate

    Connect capture points through DERAS to the dashboard and the existing POS and ERP.

  5. 5

    Pilot & scale

    Start with one store or one category, measure against the baseline, then roll out.

  6. 6

    Support

    Training for store teams, tuning after go-live, and ongoing support.

Hardware in context

The devices behind each store step.

Example devices by capability. Final models, tags, accessories and quantities are confirmed during assessment.

Handheld RFID readerZebra TC22R

Explore specifications & applications

UHF RFID sledChainway R6

Explore specifications & applications

UHF RFID sledZebra RFD40

Explore specifications & applications

Barcode mobile computerZebra TC22

Explore specifications & applications

Fixed RFID readerZebra FX7500

Explore specifications & applications

Desktop RFID printerZebra ZD621R

Explore specifications & applications

Labels & tagsRFID labels & tags

Explore specifications & applications

AI-ready cameraHikvision DS-2CD1121-I

Explore specifications & applications

Questions

Before the first store walk.

Do we need to tag every item?

No. Most retailers start with the categories where counts, value or shrink matter most. Tags can be applied at the source or in store; the tagging plan is agreed during assessment.

Can this connect to our POS and ERP?

That is the starting point. DERAS passes clean events to the systems already in use. Integration scope is confirmed per project.

What happens to our current security gates?

Existing gates can stay in place. Whether RFID exit detection replaces or complements them is decided per store.

What about metal shelving and dense racks?

They affect RFID reads. Tags and reader positions are tested on the real merchandise and fixtures during assessment.

Can we start with one store?

Yes. Most projects begin with one store or one category, measured against the current baseline, before a wider rollout.

Do we have to buy everything from one brand?

No. Several hardware brands are supported, and DERAS keeps the data in one place whichever devices are used.

Start with one workflow

Find where
the stock goes missing.

Share the categories, the store process and the systems already in use. The first conversation sets a starting point and the metrics to measure.

Discuss your stores