Chipped
Finding a chipped slab on install day is the most expensive way to find out. Flag it where you find it: scratched, sun damaged, chipped, cracked. Up to 6 photos, notes attached, and tell the office on the spot. slabos.com
Open video ↗Your warehouse isn't a spreadsheet — it's a building. SlabOS lets you draw the real thing: walls, bays, racks. Assign every slab to a physical bay, and the whole shop knows where everything lives — from the office, from a phone in the yard, from a printout on the wall.
Your floor plan, your bay names, your slab counts — live from inventory.
Past a hundred slabs, memory stops working. Somebody walks the racks. The saw waits. The truck waits. The one person who knows where the Calacatta went is on a job site. Every shop with a real yard knows this hunt — and runs it more than once a day.
Someone physically walks the racks reading slab labels.
One guy holds the whole yard in his head. He takes a vacation, the yard goes dark.
Inventory says you own the slab. It doesn't say which rack in which building.
A hand-drawn grid that was accurate the day somebody drew it.
Sketch your actual building outline — the same drawing-first DNA as the SlabOS quoting engine, pointed at your warehouse.
Split the floor into bays, racks, and A-frames — named the way your crew already talks about them.
Put each slab in its physical bay. From then on, every slab record in SlabOS carries its address.
Most slab inventory software gives you rows in a table. SlabOS gives you a floor plan. Draw your warehouse the way it actually stands — walls, bays, racks — so the map on screen matches the ground under your boots. Got more than one building? Draw them all.
No scanners, no hardware, no RFID gates. Your team places slabs in bays the same way they place them on racks — deliberately. SlabOS just never forgets where they put them.
Once a slab has a bay, that bay shows up everywhere the slab appears — the inventory list, the quote it's allocated to, the purchase order it arrived on. No second system to check. No "let me look that up."
Click "Show on map" on any slab — the map opens focused on its bay.
A rack has a limit long before it has a problem. Give every bay a capacity, and the map flags the ones running over — visually, right on the floor plan — before a delivery truck shows up with nowhere to unload.
Overstuffed bays are where slabs get chipped, buried, and forgotten. Capacity on the map turns "we'll find room" into a decision you make on purpose.
The crew doesn't hunt from a desk. The mobile warehouse map is a full-screen floor plan on any phone — search a slab by name and the map jumps straight to its bay. More than one building? It jumps across buildings too.
The forklift driver, the new hire, the installer picking up material — everyone finds slabs the same way, without asking the one guy who knows.
Search on a phone → the map jumps to the right bay, in the right building.
Some shops still run on paper by the loading dock — fine. One click prints the whole floor with a bay-by-bay manifest, so the wall copy and the software finally agree.
The warehouse map isn't a bolt-on tracker with its own database. It reads the same slab inventory the rest of SlabOS runs on — so quotes, nesting, and purchase orders all agree on what you have and where it sits.
Slabs allocated to jobs are the same slabs on the map — with their bay attached.
Nest counters onto the real slabs you own — then look up exactly where those slabs live.
POs reference the same inventory, so arriving material joins the map instead of a side list.
That's the SlabOS pattern across 150+ capabilities — quoting, scheduling, the crew app, inventory, the warehouse map — one platform, one login, one bill. The map is just the piece that answers "where is that slab" without anyone leaving their chair.
Book a demo — we'll sketch your warehouse live, drop slabs into bays, and show the crew search jump straight to a rack.
One platform · one login · one bill · see pricing
No. There's no hardware. Your team assigns slabs to bays in SlabOS — when a slab moves, you move it on the map. SlabOS keeps that location on the slab record everywhere it appears.
Yes. Draw each building, carve its bays, and search finds a slab wherever it sits — the mobile map jumps across buildings to the right bay.
No — that's the point. The map reads the same slab inventory as the rest of SlabOS. Slabs allocated to jobs, nested onto layouts, or arriving on purchase orders all reference the same records, so the bay shows up everywhere the slab does.
Yes — there's a full-screen mobile map made for a phone in one hand. Type a slab name, the map jumps to its bay. And for the paper crowd, one click prints the floor plan with a bay manifest for the wall.
SLABOS IN MOTION 06 FILMS
A closer look at the decisions, details and handoffs that make the work happen.
Finding a chipped slab on install day is the most expensive way to find out. Flag it where you find it: scratched, sun damaged, chipped, cracked. Up to 6 photos, notes attached, and tell the office on the spot. slabos.com
Open video ↗Follow a received slab into a kitchen, its remnant into a vanity and the next remnant into a bar top. Each remnant keeps its parent relationship and can crop its photo from the original slab.
Open video ↗See SlabOS lock an inventory slab during selection so one job wins the simultaneous pick. The other receives a clear message to choose again, without adding the slab.
Open video ↗Compare an attached supplier invoice with the purchase order line by line. Differences over one dollar are flagged for reconciliation before receiving the slabs.
Open video ↗Pick the slab you actually have in inventory and SlabOS nests the job on its real, locked size: this kitchen: a 120 x 60 slab takes 4 slabs, a 126 x 63 slab takes 3.
SlabOS — Nest on the slab you actually own (all on-screen information, plain text)
Same kitchen. Which slab? One kitchen, 72.32 square feet: an L-shaped sink run (CT1), a range run (CT2) and an island (CT3).
Slabs you own: inventory slab SL-1188, 120 by 60 inches, and inventory slab SL-2047, 126 by 63 inches. Both are Taj Mahal White quartzite, 3 cm.
SL-1188 is picked. The slab size is locked to the real slab.
Nesting on SL-1188, 120 by 60. Auto Nest. Optimizing.
Result: 4 slabs. Slab 1 holds CT1.1, Slab 2 holds CT1.2, Slab 3 holds CT2, Slab 4 holds CT3, each with its own splash strips.
Mode: Veined material, keep strips with parents.
On 60-inch-tall slabs the L splits across 2 slabs.
Nesting on SL-2047, 126 by 63. Auto Nest. Optimizing.
Result: 3 slabs. Slab 1 holds CT1.1 and CT1.2, Slab 2 holds CT2, Slab 3 holds CT3.
Same job, same mode, same scale.
On 63-inch-tall slabs the whole L and its splashes share Slab 1.
Side by side: SL-1188, 120 by 60, needs 4 slabs. SL-2047, 126 by 63, needs 3 slabs. One fewer slab.
Same kitchen, real slab sizes. A 130 by 65 jumbo slab still needs 3 slabs.
SlabOS. Nest on the slab you actually own. slabos.com. Book a demo.
Layouts: this job is nested by the real SlabOS Auto Nest engine (default mode, standard 0.25 in blade kerf and 0.5 in slab border).
Walk a rack with an RFID reader and SlabOS takes inventory. Rack A-3 should hold 12 slabs. A Take inventory count with RFID reads 12 tags, but one slab (SL-2047) is booked to B-1 and one expected slab (SL-2112) was not seen. Review every change, confirm 12 pieces, and the one misplaced slab's location updates. Unseen stock stays in inventory.
SlabOS: Walk the rack. Count the yard.
The video has no voiceover. Everything below appears on screen, over an original instrumental score.
12 slabs on paper. Which 12 are on the rack? Rack A-3.
Walk the rack. In SlabOS scanning, choose Take inventory, the RFID scan method and rack A-3, then Start count. Use the Crew app with an RFID sled, or a paired reader.
The reader walks the aisle and the tags are read one by one, from 00 of 12 to 12 of 12. No aiming, no line of sight. Each tag is counted once, and reads are saved on the device.
Same count, different slabs. SL-2047 is on the rack, but its record says B-1: it is unexpected on this rack. SL-2112 is expected on A-3, but it was not seen.
Review every change. Also place the selected pieces on this rack. I reviewed the unseen pieces; keep them in inventory. Confirm 12 pieces.
12 confirmed. SL-2047 moves from B-1 to A-3, and its location is updated. SL-2112 was not seen, and it stays in inventory.
SlabOS. Walk the rack. Count the yard. QR, barcode, RFID. slabos.com. Book a demo.
Notes: RFID needs a compatible reader (the Crew native app with an RFID sled, or a paired reader that sends EPCs as keyboard input), and labels are encoded and verified on an RFID-capable printer before they are activated.
Choose a film to play Explore the collection →