A proximity sensor can make a transparent LCD showcase react before a shopper touches the screen. The display may leave an idle loop, reveal product information, start an animation, or highlight merchandise when someone enters the intended engagement area.
The difficult part is making that interaction repeatable in the finished transparent display case, where glass, shelves, merchandise, lighting, neighboring traffic, multiple shoppers, cleaning, and media-player restarts can all change the result.
The same control logic can also be integrated with products from a broader transparent LCD screen range, but sensor performance belongs to the complete installation rather than to the LCD panel alone.
A useful design separates four layers:
physical shopper position → sensor observation → confirmed interaction state → player behavior
If raw sensor output is allowed to control content directly, common results include repeated video restarts, passersby activating content, missed engagement, or a player that appears faulty even though the sensing device itself is operating.
There is no universal detection distance, dwell time, cooldown period, or retrigger rule. Those values depend on sensor technology, cabinet geometry, shopper path, content behavior, surrounding traffic, and the actual application.

Start With the Shopper Interaction You Actually Need
"Detect a customer" is too broad to serve as an engineering requirement.
Define the physical behavior that should change the content. For example:
- a shopper approaches the showcase from the aisle;
- a person stops directly in front of a featured product;
- someone remains in an engagement area long enough to indicate interest;
- a shopper leaves and later returns;
- another shopper enters while an interaction is already active.
These are different sensing problems. A motion detector behaves differently from a ranging sensor or a system that maintains occupancy information.
Before selecting hardware, define at least three spatial regions:
- Target zone: where a shopper should be able to activate the experience.
- Exclusion zone: nearby traffic that should not activate it.
- Transition area: where a shopper is approaching or leaving but has not yet satisfied the interaction rule.
This distinction is especially important in retail storefront transparent-display applications, where aisle traffic can pass close to the intended engagement position.
A sensor can have excellent maximum range and still create a poor retail experience if its exclusion zone is not controlled.
Choose the Sensor Technology Around the Finished Showcase
"Proximity sensor" describes a category, not one sensing mechanism.
| Sensor approach | What it primarily observes | Useful characteristic | Important transparent-showcase boundary |
|---|---|---|---|
| PIR | Changes in thermal infrared from a moving target | Simple human-motion sensing | Ordinary glass or acrylic may block the infrared wavelengths required by specific PIR sensor families |
| Time-of-Flight | Optical distance to a target | Can support defined distance or multizone logic | Cover glass, air gap, reflections, contamination, and crosstalk can change ranging behavior |
| mmWave radar | Radio-frequency reflections, position, and motion information | Can support zone occupancy and, depending on the implementation, detection of relatively stationary people | Detection volume, clutter, neighboring radar, and zone configuration still require commissioning |
This is not a universal ranking. The selected device, firmware, mounting geometry, and final enclosure determine actual performance.
PIR: motion detection is not the same as occupancy
Passive infrared sensing responds to changes in infrared energy across its detection pattern.
Panasonic states in its PaPIRs PIR sensor FAQ that this sensor family cannot detect a person through ordinary glass or acrylic. Panasonic also notes that sensitivity can deteriorate when the temperature difference between a human body and the background becomes small.
That creates two practical boundaries for a transparent showcase.
First, the sensor's optical path must be verified before the industrial design hides the component behind glazing. Second, a motion-oriented sensor may behave differently after a shopper enters the area and stands relatively still.
A cabinet-based product such as a transparent-screen merchandise cabinet therefore needs the sensor aperture and viewing geometry designed together with the enclosure rather than added after the cabinet is complete.
Time-of-Flight: the cover window becomes part of the ranging system
A Time-of-Flight sensor emits light and estimates distance from the returned signal. This can support a more explicit distance or zone boundary than general motion detection.
However, a transparent cover is not optically neutral to the sensor.
STMicroelectronics documents in its VL53L5CX cover-glass guidance that cover-glass geometry and air gap contribute to crosstalk, and that dirt or scratches can change the crosstalk level during product life.
For a transparent LCD assembly, the production test should therefore include the actual:
- cover glass or optical window;
- air gap;
- sensor orientation;
- gasket or light blocker where used;
- cabinet framing;
- merchandise position;
- clean and contaminated window conditions relevant to service.
A sensor working correctly on an exposed development board does not prove the same ranging behavior after it is recessed behind the final transparent assembly.
This is relevant to compact integrations such as a 27-inch transparent touch-screen assembly, where the industrial design may provide limited freedom for sensor position, optical aperture, and air gap.
mmWave radar: occupancy zones can be more useful than raw motion
Radar-based sensing can use target position and movement information to maintain defined occupancy regions.
Texas Instruments demonstrates zone occupancy detection with mmWave sensing, illustrating why radar can be useful when the application needs to separate an area of interest from surrounding space.
That does not eliminate site tuning. Nearby metalwork, shelves, product displays, neighboring traffic, sensor angle, and the signal-processing configuration all influence the useful detection volume.
In a more open physical arrangement such as a floor-standing transparent touch display, controlling cross-traffic and side approaches can matter as much as the nominal forward range.

Do Not Treat Transparent Material as Sensor-Transparent
Transparent-display industrial design often encourages teams to hide sensing hardware behind glass or decorative material. Whether that works depends on the sensor technology.
For the production configuration, record:
- sensor position and orientation;
- cover or aperture material;
- glass thickness where relevant;
- sensor-to-cover spacing;
- gaskets or optical blockers;
- merchandise and shelf position;
- nearby reflective or metallic structures;
- cleaning access.
If a dedicated aperture, RF-transparent section, optical gasket, or other integration detail is needed, it becomes part of the controlled product configuration.
That detail should remain documented when developing a custom transparent display assembly. A later cabinet or cosmetic change can alter sensing performance even when the sensor part number does not change.
Map the Real Detection Zone in Front of the Finished Display
A datasheet field-of-view diagram is not a finished retail detection map.
Install the production-equivalent sensor, display, glass, merchandise, shelving, lighting, cabinet, and player. Then map the physical area in which the system actually changes interaction state.
A practical test can use marked floor positions or a measured grid.
At each position, record:
- distance from the showcase;
- lateral position;
- approach direction;
- expected sensor condition;
- actual interpreted sensor condition;
- confirmed interaction state;
- actual player response.
Test more than the centerline. Include:
- direct approach;
- walking across the front;
- diagonal approach;
- passing close to one edge;
- standing just outside the intended zone;
- nearby circulation that should remain excluded.
This type of zone validation should be part of the wider engineering work for transparent LCD retail display solutions, because the effective shopper experience depends on the finished cabinet and store geometry rather than the panel specification alone.
Check Adjacent Sensors and Overlapping Detection Zones
One showcase may work correctly in isolation and behave differently when several sensor-equipped displays are installed beside each other.
Two different issues should be considered.
Logical zone overlap
Even when sensors do not physically interfere, their configured detection areas can overlap.
A shopper standing between two cabinets may then satisfy both engagement rules. Decide whether:
- both displays may activate;
- only the nearest zone should own the interaction;
- zones need physical separation;
- a higher-level application resolves competing events.
Sensor-to-sensor interference
Some active sensing technologies can also interfere physically with neighboring devices.
For FMCW radar, Texas Instruments' AWR/IWR interference guidance describes radar-to-radar interference as a potential cause of higher noise, missed detections, blind regions, and in some cases ghost targets.
Optical ranging systems can also require model-specific review when several emitters operate in overlapping optical fields.
The correct commissioning rule is therefore to validate the production installation with all nearby sensors operating, rather than assuming that a successful one-unit bench test scales automatically to a multi-display rollout.
Define Dwell, Hold, Cooldown, and Retrigger Separately
These four concepts solve different interaction problems.
Dwell
Dwell determines how long the qualifying presence condition must remain true before a shopper becomes engaged.
A shorter dwell feels responsive but may admit cross-traffic. A longer dwell can reject incidental movement but may make the display feel late.
The value should come from actual shopper approach behavior and content intent rather than a copied default.
Hold
Hold prevents a brief loss of sensor observation from immediately ending the interaction.
Without it, a person standing near a zone boundary can produce:
engaged → idle → engaged → idle
even though the shopper has not intentionally left.
Cooldown
Cooldown prevents an interaction that has just finished from immediately starting again under the same continuing or returning condition.
This can be useful when a longer animation should not replay continuously for one shopper.
Retrigger
Retrigger defines what the application does when qualified presence occurs while content is already active.
Options can include:
- ignore the additional event;
- extend the active state;
- restart the content;
- queue a new interaction;
- switch to another experience.
The correct rule belongs to the interaction design, not to the sensor hardware alone.
Separate Sensor Sampling, Interaction Evaluation, and Player Events
A proximity system can operate at several different rates.
Sensor sampling rate describes how often raw measurements or detections are produced.
Interaction-state evaluation rate describes how often the application evaluates dwell, hold, zone membership, and other state conditions.
Player event rate describes how often a content transition is actually commanded.
These do not need to be identical.
A sensor may update many times while one shopper remains in the same state. Sending a player START command at the same rate would continuously restart the content.
A robust pipeline is closer to:
sensor samples → filtering / zone logic → state transition → one player event
This distinction is particularly important when combining proximity with an interactive product such as a transparent touch-screen display, because touch input and proximity observation may both update much faster than the media narrative should change.
Use a Presence State Machine Instead of Raw Sensor Updates
| State | Meaning | Typical player behavior |
|---|---|---|
| Idle | No qualified shopper presence | Idle or attract content |
| Candidate | A possible shopper is present but dwell is incomplete | Keep the current idle state |
| Engaged | Presence meets the engagement rule | Start or reveal active content |
| Hold | Observation briefly drops but the interaction remains valid | Preserve the active experience |
| Exit | Shopper absence is confirmed | Complete or leave the active experience |
| Cooldown | Interaction has finished but an immediate repeat is blocked | Controlled return toward idle |
| Sensor Fault | Presence information is unavailable or implausible | Use a defined fallback |
This is an illustrative model rather than a mandatory architecture.
What matters is that a raw measurement does not become a content command until the required interaction condition has been confirmed.

Trigger Playback on State Transitions
A player normally needs to know when the interaction changes from:
not engaged → engaged
It does not normally need a new START instruction for every sensor report while a shopper remains present.
Separate:
- level state: a qualified shopper is currently present;
- transition event: a qualified shopper has just entered or exited a defined interaction state.
The media-player interface may carry:
- ENTER;
- EXIT;
- current occupancy state;
- zone identifier;
- timestamp or sequence information;
- sensor health.
Use only what the application needs.
The broader content strategy for see-through LCD retail experiences should therefore define how long-form animations, product callouts, and shopper-triggered states behave rather than leaving restart logic implicit.
Make Lost, Duplicate, and Restarted Events Recoverable
The event path may be:
sensor → local controller → application → media player
or another project-specific architecture.
A healthy sensor does not prove the complete event path is healthy.
Possible failures include:
- the sensor changes state but the application never receives it;
- the application receives the same ENTER event twice;
- the EXIT event is lost;
- the media player restarts while the shopper remains present;
- communications recover while the zone is already occupied.
Useful controls can include:
- timestamps or event sequence information;
- deduplication;
- periodic state reconciliation;
- player acknowledgement where needed;
- timeouts;
- sensor-health state;
- deterministic fallback content.
A large transparent display installation may have a more distributed player and controller architecture than a compact cabinet, so the recovery strategy should reflect the actual system topology.
Decide How Multiple People Affect One Interaction
A proximity experience built around one shopper can behave unexpectedly when a group arrives.
Define:
- whether one qualified person is enough to hold the active state;
- whether a second person entering restarts content;
- whether the nearest person matters;
- whether separate zones operate independently;
- when the system returns to idle after a group leaves.
For a simple single-zone interaction, a useful model is:
trigger ENTER once when the zone changes from confirmed unoccupied to confirmed occupied; remain active while at least one qualified shopper remains; trigger EXIT when the zone becomes confirmed unoccupied.
This prevents every person joining an existing group from restarting the same content.
Define Priority Between Proximity, Touch, Door, and Service States
Transparent LCD systems may combine:
- proximity sensing;
- touch interaction;
- door-open input;
- service mode;
- scheduled content.
Their priority should be explicit.
An illustrative hierarchy might be:
Service / Door Open → Active Touch Session → Proximity Engagement → Idle
This is not a universal rule. The point is preventing contradictory commands.
For example, proximity should not automatically restore customer content while an employee has opened the showcase for replenishment. Likewise, a touch interaction already underway may need protection from a new proximity ENTER event.
Lighting, Products, and Store Conditions Can Change Detection
The environmental effect depends on sensing technology.
For optical sensors, relevant changes can include:
- direct illumination;
- sunlight;
- glass reflections;
- window contamination;
- highly reflective merchandise or packaging.
For PIR, thermal contrast and fast environmental temperature changes can affect behavior.
This is why the proximity feature should be evaluated as part of the complete retail display rather than as an isolated PCB function. The same principle applies when planning transparent LCD specifications for retail: the panel datasheet does not define shopper-sensing performance.
Make Sensor and Player Faults Visible
Store staff should be able to distinguish:
no shopper is present
from
the interaction feature is unavailable.
Relevant failure conditions can include:
- sensor disconnected;
- invalid ranging output;
- persistent implausible target;
- sensor-to-controller communication failure;
- controller-to-player event failure;
- player unavailable.
A fallback mode can keep the display useful. For example, when proximity sensing becomes unavailable, the player may return to a normal attract loop rather than remain permanently waiting for an ENTER event that cannot arrive.
Test False Triggers in the Finished Showcase
Acceptance testing should include people and objects that are expected not to activate the interaction.
| Test condition | What it checks |
|---|---|
| Walk directly into the target zone | Intended engagement path |
| Walk across the front without approaching | Passerby rejection |
| Stop just outside the target zone | Boundary stability |
| Enter slowly | Dwell and candidate-state behavior |
| Enter quickly | Fast-approach handling |
| Stand relatively still in the zone | Presence retention for the selected sensing technology |
| Leave and return | Exit, cooldown, and retrigger |
| Two or more people enter | Group behavior |
| Move merchandise or cabinet elements | False physical targets and reflection changes |
| Change relevant lighting | Environmental sensitivity |
| Operate neighboring sensors | Zone overlap or sensor-to-sensor interference |
| Disconnect the sensor | Fault fallback |
| Break the event path | Integration diagnosis |
| Restart the player while a shopper remains present | State reconciliation |
Testing should use the production-equivalent hardware rather than only a sensor evaluation board. An integrated product such as a transparent display installed into a cabinet introduces glass, framing, product, and mounting variables that are absent from an open bench test.

Record Both Detection Quality and Player Response
A useful acceptance record should make the test reproducible.
| Record field | Example information to capture |
|---|---|
| Scenario | Direct approach, cross-traffic, stationary shopper, group entry, neighboring sensor active |
| Expected result | Trigger, remain idle, hold, exit, or fault fallback |
| Test position | Distance, lateral position, and approach direction |
| Sensor configuration | Model, firmware/configuration, mounting position, zone definition |
| Environment | Glass/window condition, merchandise, lighting, neighboring sensors |
| Observed sensor result | Detection / occupancy / range result as applicable |
| Confirmed interaction state | Idle, Candidate, Engaged, Hold, Exit, Cooldown, Fault |
| Player result | Expected content transition completed or not |
| False trigger | Yes / No |
| Missed trigger | Yes / No |
| Disposition | Pass / Fail / Investigate |
This table deliberately does not prescribe a universal number of repetitions or maximum acceptable false-trigger rate. Those acceptance limits belong to the specific project requirement.
Troubleshoot Proximity Trigger Problems by Symptom
| Symptom | First condition to investigate |
|---|---|
| Passersby repeatedly start content | Detection-zone geometry, approach direction, dwell |
| Video continuously restarts while one shopper remains present | Raw sample or occupancy level is being treated as repeated ENTER events |
| Shopper reaches the display before content starts | Detection zone begins too late or dwell is too long for the interaction |
| Sensor works before final assembly but not behind glass | Sensor/material compatibility, cover geometry, or optical crosstalk |
| Detection changes after cleaning | Window contamination, optical path, or sensor movement |
| Merchandise becomes a persistent target | Product position, reflections, clutter, or zone configuration |
| One shopper leaving ends content while another remains | Multi-person occupancy logic |
| Sensor indicates presence but content does not change | Controller/application/player event path |
| Content remains active after the area becomes empty | EXIT confirmation, hold logic, lost event, or stale state |
| Behavior changes when another nearby display is powered | Zone overlap or sensor-to-sensor interference |
| Different sites need unexplained threshold changes | Installation geometry, environmental differences, or inconsistent commissioning baseline |
A symptom identifies the first investigation area; it does not prove one root cause.
Retest After Changes That Can Affect Detection or Interaction Logic
Relevant changes can include:
- sensor model or firmware;
- sensor mounting angle or bracket;
- glass or optical window;
- gasket or cover-window geometry;
- cabinet or shelf layout;
- merchandise position;
- lighting;
- adjacent sensor installation;
- dwell, hold, cooldown, or retrigger logic;
- state-machine processing;
- media player;
- event protocol;
- door/service priority;
- touch-interaction logic.
A text-only content update that preserves the same interaction states normally does not require remapping the physical detection zone.
The useful decision rule is:
Can this change alter what the sensor observes, how observations become an interaction state, or how the player responds to that state?
If yes, repeat the affected tests.
This level of integration review should also be considered when selecting a transparent display supplier, because a proximity-triggered project depends on enclosure, sensing, software, and content integration rather than the panel alone.
Transparent LCD Proximity-Sensor Integration Checklist
- Define the shopper behavior that should trigger content.
- Select a sensing technology that matches motion, distance, or occupancy requirements.
- Validate the sensor with the final glass, aperture, enclosure, and merchandise.
- Map both the intended target zone and exclusion zone.
- Test realistic approach directions and cross-traffic.
- Define dwell, hold, cooldown, and retrigger independently.
- Separate sensor sampling from interaction-state evaluation and player-event generation.
- Trigger content from confirmed state transitions rather than repeated raw updates.
- Define multi-person behavior.
- Define priority between proximity, touch, door, service, and scheduled states.
- Check neighboring sensors and overlapping zones where multiple displays operate together.
- Provide a defined fallback for sensor or player faults.
- Test duplicate, lost, and interrupted event recovery where relevant.
- Record false triggers and missed triggers under defined scenarios.
- Repeat targeted testing after geometry, sensing, or interaction-logic changes.
The goal is not to make a transparent display react whenever something moves nearby. It is to create a repeatable shopper engagement zone in which the intended person causes one intentional content transition, surrounding traffic does not, and the system can recover predictably when the sensor, environment, or software state changes.
For projects that need proximity-triggered interaction, sensor integration should be defined together with the wider transparent LCD retail specification, rather than added after the display enclosure and content have already been frozen.
If you are evaluating a new interactive configuration, review the available transparent display architecture and project requirements before finalizing the sensor, cabinet, and player. You can then request a project-specific quotation with the intended sensing method, detection-zone requirements, enclosure geometry, content behavior, and installation environment.
