Retire the grease pencil. SlabOS prints slab labels straight from your inventory — QR codes that open the slab's record on any phone camera, native Zebra printing, and a true-to-inch fallback for every other printer in the shop. From the office, or from a phone standing next to the slab.
The 4×6 slab tag — color, details, serial, and a QR that opens this slab's record on any phone.
Every stone shop knows the ritual. A serial scrawled in grease pencil on the back of the slab. A number that wore off in the rain. A rack of white quartz where three slabs look identical and only one of them is sold. The inventory system says one thing; the warehouse says another.
The fix isn't a bigger marker. It's a label that carries its own identity — printed from the same system that tracks the slab.
Handwritten, smudged, and gone after one wet forklift run.
Identical whites on the A-frame — which one belongs to which job?
Someone walks to the office, checks the system, walks back. Twice.
Is that a 1 or an I? An 0 or an O? At the saw, guessing is expensive.
SlabOS closes the gap between the rack and the record. Print the label from inventory, stick it on the slab, and from then on the slab identifies itself — to any phone camera in the building.
Four things, arranged to be read from a forklift: the color and material name, your configurable detail lines, the slab serial, and a QR code. Scan the QR with any phone camera — no app — and the slab's journey page opens in SlabOS.
You choose what prints. QR on or off, serial on or off, detail lines your way — field configuration is built into the label flow, not buried in a settings page.
Big and legible — the first thing anyone reads across the rack.
You pick what prints under the name — the fields your crew actually needs at the rack.
The slab's identity in SlabOS, printed in machine-friendly characters.
Deep-links to that slab's journey page in SlabOS. Any phone camera opens it — no scanner hardware, no app install.
Fig. 02 — Four parts, one identity. The QR is the shortcut; the serial is the fallback.
Labels get read by scanners — and sometimes by a guy with a pencil copying a serial onto a cut sheet. So SlabOS encodes labels with a Crockford base32 code: the ambiguous characters are simply not in the alphabet. No I to confuse with 1. No O to confuse with 0. No L, no U.
Built for scanners, legible as handwriting when the scanner isn't in your hand. Either way, the code resolves to exactly one slab.
Crockford base32: a machine-friendly encoding where every character survives a scanner, a phone camera, and a shop-floor pencil.
Fig. 03 — Characters that can be misread don't exist in the code.
Fig. 04 — Two print paths, one label. Zebra gets raw ZPL; everything else gets true-to-inch HTML.
Got a Zebra label printer? SlabOS talks to Zebra's Browser Print agent and sends raw ZPL straight to it — no driver dance, no print-preview roulette, no shrink-to-fit surprises.
Don't have one? You still print labels today. A true-to-inch HTML fallback pushes exact-size labels through the normal system print dialog on any printer in the shop. The Zebra makes it faster; it's never a requirement.
A truck shows up with a container's worth of slabs. You don't print one label, walk over, print another. Batch printing sends the whole delivery's labels as one ZPL job — the printer runs, you peel and stick down the line.
Sizes match the job: the 4×6″ slab tag for the rack, smaller formats for remnants and shelf edges, and custom sizes up to 8″ when your stock demands it.
Fig. 05 — The size lineup. Every one carries the same slab identity.
A label printer that only prints labels is a toy. This one is wired into the platform: the QR opens the slab's journey page, serials follow your locations, and remnants inherit their parent's identity.
The QR deep-links to that slab's journey page in SlabOS — its record, opened by any phone camera.
Labels print from the office — or from a phone in the warehouse. Crew inventory has the same button.
Serials support per-location sequences — each location numbers its own stock.
Cut a remnant and it carries a child serial off its parent — a -r1 style suffix that keeps the family tree intact.
This isn't a bolt-on label app. Labels print directly from SlabOS inventory — the same slab records your quotes draw on and your warehouse map organizes. Stick the label on, and the physical slab and the digital record stop drifting apart.
Slab labels are one piece of one platform — quoting, scheduling, slab inventory, the crew app, and the customer portal all live behind the same login. One login, one bill.
Book a demo — we'll print a real label from a real slab record, scan it with a phone, and land on the slab's journey page. Bring your Zebra if you've got one. Bring any printer if you don't.
One platform · one login, one bill · see pricing
No. Zebra printers are supported natively — SlabOS talks to Zebra's Browser Print agent and sends raw ZPL straight to the printer — but a true-to-inch HTML fallback prints exact-size labels through the normal system print dialog on any printer.
The QR deep-links to that slab's journey page in SlabOS. Scan it with any phone camera and the slab's record opens — no special scanner hardware and no app install required.
The color/material name, configurable detail lines, the slab serial, and the QR code. You choose which fields print — QR, serial, and details can each be toggled. Codes use Crockford base32, an alphabet with no ambiguous I/L/O/U characters, built for scanners and legible as handwriting.
Yes — batch printing sends the whole delivery's labels as one ZPL job. Sizes run from the 4×6″ slab tag down to 2×1″, with 4×3″ and 4×2″ in between, plus custom sizes up to 8″.
The remnant carries a child serial off its parent — a -r1 style suffix — so lineage stays intact. Serials also support per-location sequences, so each location numbers its own stock. Print the remnant its own label from the office or from a phone in the warehouse; crew inventory has the same printing built in.
