Writing · Use case
E-paper kanban labels: when they beat paper cards
E-paper kanban labels beat paper cards when cards get lost, card data changes often, or someone spends real time reprinting and walking cards between the line and the stores. They do not beat a stable two-bin loop that already works. The labels themselves are simple; the work is the integration and the update cadence.
Published 2026-11-11. We build color e-paper hardware and firmware on E Ink Spectra 6, including industrial e-labels, so we have a stake in this. Vendor capabilities below are described from that vendor’s own pages; battery figures for our stack come from our published power budget.
What an e-paper kanban label actually is
A small, battery-powered e-paper display that sits where the paper card used to: on the bin, the tote, or the rack position. It shows what the card showed (part number, description, quantity, supplier, location), but the content comes from software, not a printer. KanbanBOX, which sells electronic labels for kanban, describes the common extras: configurable buttons to signal that a container is empty or urgent, LED indicators, pairing by scanning the label’s barcode, and replaceable coin cells.
Why e-paper and not a small screen: E-paper holds its image with zero power and reads like printed paper under factory lighting. A label that changes a few times a shift spends almost all its life drawing nothing, which is why it can run on a coin cell or a small rechargeable battery instead of a cable.
Paper cards vs e-paper labels
| Paper card | Black-and-white e-label | Color e-label | |
|---|---|---|---|
| Changing the data | Reprint and swap by hand | Pushed from software | Pushed from software |
| Replenishment signal | Card travels or is scanned | Button or scan on the label | Button or scan, plus status color |
| Status at a distance | Card position or colored holder | Text, or an LED if fitted | The label is the status color |
| Lost or wrong card | Common failure mode | Label stays on the bin | Label stays on the bin |
| Power | None | Coin cell or small battery | Small rechargeable battery |
| Refresh time | n/a | Seconds | Roughly 20 to 30 s for Spectra 6 |
| Upfront cost | Lowest | Moderate | Highest |
Where e-labels pay for themselves
- Cards go missing. A lost card is a loop that silently stops replenishing. A label screwed to the bin cannot be lost in a pocket.
- Data changes often. Engineering changes, supplier swaps or quantity resizing mean reprinting cards. A label is updated from the system that already holds the change.
- Loops cross distance. Line to warehouse, building to building, or plant to supplier. A button press is faster than a card walk or a courier bag.
- Someone re-keys card data. If cards are scanned or typed into ERP today, an e-label closes that gap.
Where paper still wins
A short, stable, visible two-bin loop next to the line. If nobody loses cards and the data never changes, an e-label adds a battery to manage and a system to maintain. Start with the loops where digital adds the most and leave the rest on paper.
When color earns its cost
Lean visual management already uses color: green for running or full, yellow for attention, red for stop or hold. On a black-and-white label that status has to be text or a separate LED. On a six-color Spectra 6 label, the whole status field is the color, readable across an aisle with no LED to power. That matters for supermarket racks, quality holds and line-side status boards that people judge from a distance.
It matters much less when the label is only read up close at the moment of picking. There, a cheaper black-and-white or BWRY (black, white, red, yellow) panel with faster refresh is usually right, and our industrial page says the same: many industrial deployments are better served by BWRY panels when blue and green are not needed.
Battery life is an update-cadence question
Like every battery e-paper device, a kanban label’s runtime is set by how often it wakes its radio, not by the display. KanbanBOX quotes one year to several years on a coin cell, depending mainly on update frequency. On our ESP32-S3 + Wi-Fi stack, with a conservative budget of about 3.1 mAh per wake on a 3,000 mAh cell, a label that checks in once a day is limited by the cell’s own self-discharge, four times a day is roughly 7.8 months, and hourly is about 40 days. The full table and assumptions are in how long battery e-paper signs last.
The practical consequence: decide how fresh the label needs to be. A label that updates when stores refill the bin and otherwise sleeps lasts a long time. One that mirrors live MES counts every few minutes needs a bigger battery, a low-power radio, or mains power.
The integration question to ask every vendor
The chain is always label → gateway or Wi-Fi → kanban or warehouse software → ERP or MES. Ask which links the vendor owns, which you own, and what happens when one is down. Two answers matter most: the label must keep showing its last good content if the network drops, and a button press must be queued, not lost, until it gets through.
Pilot checklist
- Pick one loop where cards get lost or data changes often, not your best-run loop
- Count labels, sizes and mounting surfaces (totes, racks, gaylords, carts)
- Decide the update cadence, then size the battery from it
- Confirm the replenishment signal: button, scan, weight sensor, or system-driven
- Survey Wi-Fi or gateway coverage at the racks, including near metal and motors
- Define offline behavior: last content shown, button presses queued
- Agree on color meanings with the people who walk the floor, before artwork
- Check housing against wash-down, temperature and forklift traffic in that area
- Name who swaps or charges batteries, and how low-battery alerts reach them
- Measure the baseline you want to move (lost cards, stock-outs, reprint time) before go-live
Build or buy
For standard kanban on black-and-white labels, an off-the-shelf e-kanban system with its own labels and software is the fast, sensible route. A custom build makes sense when you need color status, a form factor nobody sells, or labels that talk to your systems without another vendor’s platform in between. Our dev-kit-to-product checklist covers what it takes to get ESP32 + Spectra 6 hardware to the field, and the industrial e-labels page has our pilot shape and pricing.
FAQ
What is an e-paper kanban label?
A small battery-powered e-paper display fixed to a bin, tote or rack position in place of a paper kanban card. It shows part number, quantity and status pulled from your kanban, MES, ERP or WMS software, and many models add a button that sends a replenishment signal from the label itself.
How long do e-paper kanban label batteries last?
It depends on how often the label updates. KanbanBOX, which sells e-labels for kanban, says a standard replaceable coin cell lasts from one year to several years depending mainly on update frequency. On our own ESP32 + Wi-Fi stack, a label that wakes once a day is limited by battery self-discharge rather than the electronics, while one that wakes every few minutes lasts days.
Do kanban e-labels need to be in color?
Not always. If the label only shows part data and the signal is a button press, black-and-white is cheaper and refreshes faster. Color earns its cost when status itself must be read from across an aisle: green for full, yellow for reorder triggered, red for stock-out or quality hold.
How do e-paper kanban labels connect to an ERP or MES?
The label talks to a gateway or Wi-Fi network, which talks to the kanban or warehouse software, which reads from or writes to the ERP or MES through its API. Labels are usually paired to a container or location by scanning a barcode on the label. Ask any vendor exactly which side of that chain they own.
When are paper kanban cards still the better choice?
When loops are short, stable and visible, when a lost card is rare, and when nobody re-keys card data into a system. E-labels pay where cards get lost, data changes often, loops cross buildings or suppliers, or someone spends real time reprinting and walking cards.