If you use ServiceM8 to quote jobs, add materials and keep pricing consistent, naming your inventory properly matters more than most trade businesses realise. A small decision, such as whether to rely on SKUs or product names in ServiceM8, can affect how quickly your team finds items, how easily prices get updated, and how much admin your office ends up handling.
For UK plumbing, heating and electrical firms heading into autumn, this becomes even more important. September is often when workloads build, supplier price lists change, and teams start preparing for a busier season. If your item naming is unclear, mistakes tend to show up at the worst possible time.
So, should you use a SKU, a product name, or both in ServiceM8? In most cases, the best answer is both, but each should do a different job.
What is the difference between a SKU and a product name?
A SKU is a stock keeping unit, usually a code used to identify a specific product. It may come from a supplier, or you may create your own internal item code.
A product name is the plain English description your team actually recognises, such as:
- 15mm copper elbow
- 22mm lever valve
- Worcester filling loop
- 1.5m white trunking
Both fields help, but they solve different problems.
What SKUs are good at
SKUs are useful when you need consistency. They help with:
- matching items to supplier lists
- spotting whether two records are actually the same product
- comparing old and new prices
- syncing data between Google Sheets and ServiceM8
- reducing confusion when similar products have nearly identical names
What product names are good at
Product names are useful when a human being needs to search quickly. They help with:
- engineers finding parts on mobile
- office staff building quotes faster
- reducing the chance of choosing the wrong item
- making inventory easier to review and tidy up
In ServiceM8, should you search by SKU or by name?
For most trade businesses, searching by product name is easier in day to day work.
Your engineers are unlikely to remember a supplier code when standing in a plant room or pricing a boiler breakdown. They are far more likely to search for “22mm iso valve” than something like “BES-78421”. That is why product names should be clear, consistent and written in a way your team naturally uses.
That said, relying only on names can create problems behind the scenes. Different people may enter the same item as:
- 15mm elbow copper
- copper elbow 15mm
- elbow 15 mm
- end feed elbow 15mm
Now you have several versions of one product, which makes price updates harder and reporting less reliable.
This is where SKUs become valuable. Even if the visible product name is what your team uses every day, the SKU can act as the fixed reference point in your master price list.
The best setup for ServiceM8 inventory
For most ServiceM8 users, the simplest approach is this:
- Use the product name for easy searching.
- Use the SKU as the unique reference.
- Keep both in your master price list.
- Make sure everyone adds new items in the same format.
If you manage your prices in a spreadsheet first, this becomes much easier. Many businesses use Google Sheets as their central product database, then push approved changes into ServiceM8. That gives you one source of truth for pricing and naming.
At Materialm8, this is exactly the sort of problem we help ServiceM8 users solve, especially when inventories have grown quickly over time.
A simple naming format that works well
A practical format for product names is:
Size + type + key detail + brand if needed
For example:
- 15mm elbow end feed
- 22mm isolation valve chrome
- 32mm waste bend white
- Worcester filling loop braided
This keeps names readable for engineers and office staff, while the SKU handles the exact product match in the background.
When should you rely more on SKUs?
There are some situations where SKUs matter more than names:
When supplier price lists change regularly
If you receive supplier spreadsheets and need to compare old prices with new ones, SKUs make matching far easier. Names may vary slightly between suppliers, but a consistent code gives you a more dependable link.
When you have a large inventory
Once your ServiceM8 account contains hundreds or thousands of items, manual checking becomes messy. SKUs help you identify exact matches and avoid accidental duplicates.
When you want cleaner syncs and updates
If you plan to automate updates between Google Sheets and ServiceM8, unique identifiers matter. A SKU is usually the safest way to control what should update and what should not.
When should you rely more on product names?
Product names matter more when speed and usability are the priority.
If engineers add materials on site, or office staff need to build quotes quickly during a busy September and October period, names should be obvious at a glance. A neat product name can save small amounts of time on every job, and those minutes add up across a full team.
This is especially relevant for plumbing and heating firms preparing for colder weather across the UK. As reactive work increases, nobody wants to scroll through vague item labels trying to guess which valve or fitting is the right one.
Common mistakes to avoid
If you are deciding between SKU and product name in ServiceM8, avoid these common issues:
- using only supplier codes that your team does not recognise
- using only free-typed names with no unique reference point
- letting different staff add items in different formats
- shortening names so much that they become unclear
- changing naming rules halfway through without cleaning old items up
A tidy structure now saves a lot of admin later.
The practical answer for most ServiceM8 users
If you want the short answer, use product names for people and SKUs for systems.
That usually gives you the best of both worlds. Your team can find items quickly, while your business keeps a reliable reference for pricing, syncing and ongoing inventory control.
If your current setup is inconsistent, autumn is a good time to fix it before the winter rush. Review your top-used materials first, agree a naming format, and make sure your master price list includes a unique SKU for each item.
If you want a simpler way to keep your ServiceM8 inventory aligned with your spreadsheet, take a look at Materialm8. Materialm8 helps UK ServiceM8 users manage pricing data more cleanly, with less manual admin and fewer avoidable mistakes.