It Looked Perfectly Flat
In my first year handling orders for a high-end renovation firm (2017), I landed a project for a master bathroom. The client had chosen a gorgeous Cosentino Silestone shower tray—a dark, charcoal veined quartz. The existing floor looked good. Hardly any lippage on the tiles. I was confident.
I said, "The subfloor is ready." The installation team heard, "Just needs a skim coat." Result: A $3,200 tray that cracked under the weight of a porcelain toilet within six months. That's when I learned the hard way that smooth doesn't mean ready.
Why We All Fall for the Smooth Stone Trap
The problem isn't the Cosentino material—it's our definition of "smooth." For a standard tile floor, a little variation is fine. Thinset absorbs it. But a prefabricated stone tray (like the ones from Cosentino) is engineered to be perfectly flat. It doesn't flex. It doesn't give.
I only believed the prep advice from the manufacturer after ignoring it and eating an $800 mistake (including the replacement material, labor, and one very unhappy client). The subfloor looked smooth to my eye, but a simple 5-foot level revealed a 1/8-inch dip in one corner. That dip, multiplied by the rigid weight of the Silestone, created a stress point.
The numbers said to spend an extra $80 on self-leveling underlayment. My gut, wanting to save money and time, said to skip it. I went with my gut. Turns out that my gut was wrong.
The Hidden Cost of a 'Cheap' Surface
This brings me to a crucial point about value. In my experience managing over 50 stone slab and tray projects, the lowest quote on subfloor prep has cost us more in 60% of cases. That $80 self-leveling job I skipped turned into a $1,500 problem when we had to rip out and replace the tray.
Let's do the math (as of early 2025):
- Cost of doing it right: Self-leveling compound (approx $40) + time ($40 labor) = $80
- Cost of doing it wrong: Cracked tray ($800) + removal and disposal ($200) + new tray ($800) + re-installation labor ($300) + client compensation (embarrassment) = $2,100+
The ‘savings’ of $80 created a disaster. The cheapest path was not, in fact, the most economical. (Note to self: I really should have documented that first failure with photos—a painful lesson for the blog.)
The Deep Root Cause: Underestimating Substrate
The surface problem was a dip. The deep problem? I assumed the existing tile floor was a suitable base. Most shower tray instructions specify that the substrate must be perfectly flat, structurally sound, and free of deflection. A tile floor is usually none of these things.
We were using the same words—'smooth' and 'flat'—but meaning different things. I meant 'looks level.' The installation team meant 'within 1/16-inch over 6 feet.' Discovered this when the level showed the true story.
Another factor: soundproofing. The client had requested soundproofing panels under the bathroom (above a home theater). These panels compress slightly over time. If I had installed the tray directly on top of that flexible assembly without a proper, rigid decoupling layer (like a piece of 3/4-inch plywood), the tray would have failed anyway.
How to Actually Make Smooth Stone
Okay, here is the short version of the solution. If you are installing a Cosentino shower tray (or any large format stone piece), the only way to make a smooth stone is to start from a perfectly flat subfloor.
- Remove the old floor. Do not install over existing tile. Tear it out.
- Check the plywood. Ensure it's 3/4-inch T&G, secured every 4 inches.
- Use self-leveling compound. Don't just skim it. Pour it to create a monolithic, level plane. Let it cure for 24 hours.
- Use a high-flex, uncoupling mat. This prevents minor structural movement from transferring to the stone. It's cheap insurance.
- Dry-fit the tray. Before applying any adhesive, place the tray. Check with a level in every direction.
It's a few extra steps and a couple hundred bucks. But it's nothing compared to the cost of a cracked tray.
Prices and methods as of early 2025. Always consult the specific Cosentino installation guide for your model. I've been meaning to write up a full checklist on this.
