Walk into almost any distribution centre and you'll find the same artifact: a whiteboard near the dock doors with door assignments in dry-erase marker, half of it smudged, updated by whoever remembered. Beside it, a printed shift schedule from Monday. Digital signage for warehouses replaces both — not because whiteboards are old-fashioned, but because the information on them changes hourly and the person who knows is at a desk two hundred feet away.

What a warehouse screen is actually for

The mistake is treating it like a lobby screen with warehouse pictures on it. An operations screen has a job, and there are only four common ones.

• Door and dock assignment. Which carrier is at which door, what's next, what's running late. This is the board people look at while walking, from thirty feet, so it's big type and short rows or it's decoration.
• Shift and safety information. Days without a recordable incident, today's crew and supervisor, current safety focus, break times. Static enough to schedule, important enough to be visible.
• Throughput against the plan. Units picked, orders shipped, lines to go. Whether this motivates or annoys depends entirely on whether the number is trustworthy — a stale counter is worse than no counter, because people learn to ignore the screen.
• Instructions at the driver entrance. Where to check in, where to wait, PPE rules, site speed limit. This one earns its place fastest, because it's the same twenty questions asked at the door every day.

The data problem: nobody wants a second place to type

This is where warehouse signage projects usually die. Somebody builds beautiful screens, and then discovers that keeping them current means a supervisor typing dock assignments into a signage dashboard in addition to the spreadsheet where the assignments already live. That lasts about two weeks.

The fix is to treat the screen as a view of a source, never as a place where information is authored. If the dock schedule lives in a shared spreadsheet, the screen should read that spreadsheet. If it lives in your WMS and you can get a CSV out on a schedule, the screen should read the CSV. The rule that keeps these projects alive is simple: if updating the screen is a separate task, the screen will be wrong by Thursday.

A second, less obvious rule: a background job can never answer a question. If a column disappears from the source spreadsheet, something has to decide what the screen shows — and the safe answer is usually "keep the last good data and make the staleness visible," not "guess."

The environment problem

Warehouses are hostile to screens in ways offices aren't, and it's worth planning for before you buy hardware.

• Distance and glare. Mezzanine-mounted screens are read from far away, often against a skylight. Design for the worst seat in the house: fewer rows, larger type, high contrast, no thin fonts.
• Wi-Fi dead spots. Racking is metal and coverage maps lie. Assume the connection will drop and pick a player that keeps playing from local cache rather than showing a spinner or a black screen.
• Nobody is going to reboot it. A screen 20 feet up a wall needs to recover from a power cut on its own, without someone with a ladder and a keyboard.
• Dust and heat. Consumer TVs survive this better than people expect, but ventilation behind a wall mount matters more here than in a lobby.

Doing it with WeDisplay

The pieces that matter for this use case, from the digital signage side of the platform:

• Data tables fed from a link. Build a dataset from a spreadsheet or CSV, or point it at a published Google Sheet, and it re-reads the source on a schedule you set — so the dock board updates when the spreadsheet does, with nobody retyping anything. Datasets hold up to 2,000 rows and 200 columns, which is far more than a readable board should ever show.
• The rest of the operational widgets. A clock and date on the org's own timezone, a ticker for shift announcements, a countdown to the end of a wave or a cut-off, a message block for the safety focus, weather for the yard, and QR codes for the things drivers keep asking about.
• Zones, so one screen does several jobs. Split a display into a large table zone for the dock board, a strip for the ticker, and a corner for the clock — rather than cycling through slides people miss.
• Players that keep going. The WeDisplay player runs on any Android TV 7.0+ device, caches content locally, and recovers on its own after a restart or a dropped connection. Widgets keep showing the last data they received rather than going blank — with one deliberate exception: weather stops after a few hours, because a stale temperature isn't old information, it's wrong information.
• Screen groups. Push a change to every dock screen at once instead of walking the building.
• Scheduling by daypart. Day shift board, night shift board, weekend loading — set once, and the screens switch themselves on your organization's time zone.
• Proof that it's actually running. Every screen reports its online status and uptime plus a history of what played, which is how you find out a mezzanine screen has been dark for three days without walking under it.
• An emergency overlay. When something needs to be on every screen right now, it goes on every screen right now, over whatever was playing.

If your source data lives in a BI tool, the apps picker can also put a public Power BI or Tableau link on a screen — with the emphasis on public, since a report that requires a login can't be embedded on an unattended display.

The driver entrance is a different problem

The screen at the dock is signage. The desk where drivers and couriers check in is not — that's a reception problem, and in logistics it has a specific wrinkle: the people arriving often don't share a first language with the office.

WeDisplay's visitor kiosk runs the check-in tablet from the same account as the screens. Its seven visitor-facing languages — English, French, Spanish, Romanian, Punjabi, Hindi and Mandarin — exist precisely because trucking and logistics receptions asked for the last three. If your building is shared, one reception can also front for several companies, each with its own logo and host list, with the company picker appearing only when more than one is active.

For the office side of the same platform, meeting-room displays and workplace screens covers the front-of-house screens. And if you're picking hardware, the Android TV setup guide goes deeper on players.

FAQ

Can a warehouse screen pull data from our WMS? Directly, only if your WMS can publish a link the screen can read — a shared sheet or a CSV endpoint is the common bridge. Most sites already have a scheduled export somewhere; pointing a dataset at that is far easier than an integration project, and it fails in obvious ways rather than silent ones.

What happens when the Wi-Fi drops in the racking? The player keeps playing from its local cache, and widgets keep showing the last data they received. You lose freshness, not the screen. That's the specific reason to prefer a player with a real offline cache over a browser tab pointed at a dashboard.

How big should the type be on a dock board? Design for the furthest person who needs to read it, then cut the number of rows until it fits. The most common failure in this category is a beautiful twenty-row table that's unreadable at the distance it's actually viewed from.

Do we need a screen at every door? Usually not. One large board covering a bank of doors is easier to keep current and cheaper to run than a screen per door, and people are used to scanning a board for their row. Screens per door make more sense when each door has genuinely different content, like a carrier-specific instruction.