{"id":441,"date":"2026-09-30T12:11:16","date_gmt":"2026-09-30T12:11:16","guid":{"rendered":"https:\/\/www.tilesitsolutions.com\/blog\/?p=441"},"modified":"2026-09-30T12:11:16","modified_gmt":"2026-09-30T12:11:16","slug":"salesforce-integration-mistakes-tile-brands","status":"publish","type":"post","link":"https:\/\/www.tilesitsolutions.com\/blog\/salesforce-integration-mistakes-tile-brands\/","title":{"rendered":"7 Salesforce Integration Mistakes Tile Brands Make (and How to Avoid Them)"},"content":{"rendered":"

Most Salesforce integration mistakes don’t show up on launch day. They show up three weeks later, when a rep quotes 1,800 square feet of a porcelain that’s split across two shade lots, or a dealer’s negotiated price gets overwritten by a list price nobody meant to push. Tile data is stubborn. Boxes, pallets, lots, and caliber don’t fit neatly into a default Salesforce product record. <\/span><\/p>\n

Below are the seven mistakes that come up most in tile projects, and what a properly scoped <\/span>ERP and CRM integration solution<\/strong><\/span><\/a> does differently.<\/span><\/p>\n

Why Tile Is Harder to Integrate Than Most Industries<\/b><\/h2>\n

Salesforce is built around accounts, opportunities, and products with a price. Simple enough.<\/span><\/p>\n

A tile distributor, though, quotes by the square foot, ships by the box or pallet, reserves stock by shade lot, and invoices out of an ERP like SAP or NetSuite. Each of those handoffs is a translation. And every translation is a spot where numbers drift.<\/span><\/p>\n

Generic integration advice covers the basics well: clean your data, map your fields, test before launch. Good advice. It just stops short of the product reality that makes tile different, which is exactly where most of these projects go wrong.<\/span><\/p>\n

7 Salesforce Integration Mistakes Tile Brands Keep Making<\/b><\/h2>\n

Some of these are technical. Most are planning gaps that only turn into technical problems once real orders start flowing.<\/span><\/p>\n

1. Treating Tile SKUs Like Generic Products<\/b><\/h3>\n

Picture this. A rep builds a quote in Salesforce for 2,400 square feet. The ERP sells that item in boxes of 15.5 square feet. Salesforce rounds one way, the ERP rounds another, and the order that reaches the warehouse no longer matches what the customer signed.<\/span><\/p>\n

Small gap. Expensive argument.<\/span><\/p>\n

The fix is to model dual UoM on purpose. Store the conversion factors (square feet per box, boxes per pallet) on the product record, and let exactly one system do the rounding. Then bring over the attributes reps actually quote on, like size, finish, PEI rating, and caliber. If those only live in the ERP, reps will quote from memory. They’ll get it wrong sometimes.<\/span><\/p>\n

2. Letting Two Systems Fight Over the Same Data<\/b><\/h3>\n

Syncing everything both ways sounds ideal. In practice, it’s where silent overwrites come from.<\/span><\/p>\n

Pick a system of record for each data type, and write it down before anyone builds a connector. A typical tile setup looks something like this:<\/span><\/p>\n\n\n\n\n\n\n\n\n
Data<\/b><\/td>\nSystem of Record<\/b><\/td>\nSync Direction<\/b><\/td>\n<\/tr>\n
Credit terms and payment status<\/span><\/td>\nERP<\/span><\/td>\nERP to Salesforce<\/span><\/td>\n<\/tr>\n
Dealer pricing tiers<\/span><\/td>\nERP or pricing engine<\/span><\/td>\nERP to Salesforce, read only<\/span><\/td>\n<\/tr>\n
Opportunities and quotes<\/span><\/td>\nSalesforce<\/span><\/td>\nSalesforce to ERP when won<\/span><\/td>\n<\/tr>\n
Stock and lot availability<\/span><\/td>\nERP or warehouse system<\/span><\/td>\nERP to Salesforce, read only<\/span><\/td>\n<\/tr>\n
Contacts and activity history<\/span><\/td>\nSalesforce<\/span><\/td>\nStays in Salesforce<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Your split might look different. That’s fine. What isn’t fine is nobody knowing which record wins when two of them disagree.<\/span><\/p>\n

3. Syncing Stock Totals Instead of Lot Availability<\/b><\/h3>\n

This one hurts tile brands more than almost anyone else.<\/span><\/p>\n

Watch for this: Salesforce shows 3,000 square feet on hand. Sounds great. But it’s really 1,200 in one lot, 1,100 in another, and 700 in a third. A customer tiling a single open floor needs one shade lot, so that 3,000 is really 1,200.<\/p><\/blockquote>\n

Reps who only see totals will overpromise. Every time.<\/span><\/p>\n

Push availability into Salesforce by lot, or at minimum show the largest single lot for each SKU. Better still, let reps place a soft hold on a specific lot when a quote goes out. An <\/span>inventory management solution with lot tracking<\/a><\/strong> does the heavy work here, tracking lot numbers for color and shade matching so Salesforce only has to display what’s currently sellable.<\/span><\/p>\n

Frankly, you don’t need every stock movement inside the CRM. Reps need to know what they can sell today, by lot. The full audit trail can stay in the warehouse system.<\/span><\/p>\n

4. Flattening Dealers, Contractors, and Specifiers Into One Account Type<\/b><\/h3>\n

Tile sales rarely involve a single buyer. On a typical commercial project:<\/span><\/p>\n