A customer asks for something you don’t normally sell. Maybe it’s a small change to an existing product, a special configuration, or something made specifically for that customer.
The sales team knows what needs to be done. They just need to get the order into the system.
But the item isn’t there.
So someone creates a new product record, adds it to the order, and moves on. The customer gets what they asked for, and the order is done.
The problem comes later.
That new item is still sitting in the ERP. If the customer never orders it again, the record is now just another product sitting in the system. Over time, a few one-off orders can turn into dozens of product records that nobody really uses but someone still has to maintain.
This raises a simple question: does every one-off or custom sale really need to become a permanent SKU?
When Every Special Order Becomes a New SKU
One extra item doesn’t hurt anybody. Most teams would say that, and they’d be right. A single unused record changes nothing.
What changes things is the habit. When “create a new item” becomes the default answer to anything unusual, the records pile up quickly. Think about what usually triggers it:
- A customer asks for something once and never again.
- A standard product gets changed slightly and becomes its own custom configuration.
- Something is made for one particular customer and carries their name.
- An item is created even though everyone already knows it won’t sell again.
Once the orders are sent out, all of the aforementioned factors remain within the systems. Later on, a certain employee looks up a particular product and ends up getting results for five instances with almost identical names. However, employees are not sure which instance has outdated information, and thus they may choose the wrong instance or may ask for someone’s help, which delays the process even more.
So the real issue isn’t the one extra SKU. It’s what your product list looks like once this becomes the normal way of working.
Not Every Sale Is a Regular Inventory Item
A lot of this stems from handling each transaction as if it were the same thing. In reality, there are different types of transactions that require different ways of handling.
Everyday inventory products are ones that are sold over and over again. You keep them in stock, buy more and restock when they get low. These are the core of your catalog.
Non-inventoried products still have to appear on a transaction, but you don’t manage them as stocked inventory. There’s no shelf count to maintain.
Services or charges get sold and billed, but they aren’t physical inventory at all.
Then there are one-off or custom transactions, which are created for a specific situation or a specific customer.
Seen side by side, it’s easy to understand why forcing all four through the same process causes problems. Not every unusual transaction should be treated like a regular stocked product just because it showed up on an order.
When Should You Actually Create a New Product Record?
Creating a new product is sometimes the right call. You just need a quick way to decide, so it isn’t a guess made under pressure. These questions help:
- Will we sell this again? If the honest answer is no, that’s a strong sign to stop.
- Will we keep it in inventory? If it never goes on a shelf, it may not need inventory-style handling.
- Will purchasing need to replenish it? Nobody reorders a custom job.
- Does it need its own inventory tracking? Only if someone will actually track it.
- Does it need separate reporting? If you’ll want numbers on it by itself, that counts.
- Will other customers buy it? A product only one buyer wants is a different case from one many want.
- Has it become part of our regular product range? Then it probably deserves a permanent record.
Create a permanent product record when there’s a real business reason to keep it around.
What About One-Off and Custom Orders?
However, this does not imply that one-off orders should be processed casually. Each single order has to be properly recorded, which people tend to underestimate.
Customer details are always to be included with the order. It is important to provide a proper description of the products or services sold, so that this description could be interpreted correctly even in six months after the transaction. Required quantity and price for invoicing should be provided in addition.
There should be no need to compromise transaction information in order to eliminate SKU clutter. One can easily go through the transaction history with the customer even if this item is not included in the regular catalog.
How Versa Cloud ERP Can Fit Into This Process
Versa Cloud ERP supports inventoried products, non-inventoried products and services. So there’s more than one way to set up what goes onto a sale, depending on what you’re actually selling.
Sales orders in Versa capture customer and transaction information. They can carry quantity, UOM, pricing, taxes, descriptions and other details. That means the order holds what your team needs to process it properly, whatever kind of item is on it.
Choosing the right product or service structure is what makes the difference here. A regular item that you stock and replenish fits as an inventoried product. Something that has to show up on a transaction without being managed as stock is a different case. A billable charge or a service is another.
In the event that the structure coincides with the sale, the businesses do not have to run several sales in the same way as if it were the case of stocked item sales.
So when considering a sale transaction, take a moment to think if a non-inventory structure is the right option to use instead of using it as a standard stocked item sale transaction.
Before You Create Another SKU, Ask These Questions
Next time someone on the team is about to add a new item, run through this short list first:
- Will we sell it again?
- Do we need to stock it?
- Will we purchase it again?
- Does it need separate inventory tracking?
- Does it need separate reporting?
- Is this actually a new product?
These questions aren’t there to stop anyone from creating SKUs. If the answers show a genuine need, go ahead and create the record. They just help you avoid the unnecessary ones, so you only add something to the catalog when it has a reason to be there.
Keep the Transaction, Not the Clutter
One-off sales happen in every business. So do custom requests. Nobody did anything wrong by getting them.
The mistake comes later, when each exception gets treated as a permanent product. That’s how a catalog ends up full of records that nobody uses and everybody has to work around.
Businesses benefit from a clear line between regular inventory and other types of transactions. And the goal was never to have the fewest SKUs possible. It’s to have product records that are useful and that exist for a reason.
Your ERP should keep a record of what you sold without making every unusual sale part of your permanent product catalog.
Stop Creating Permanent Records for Temporary Needs
Not every unusual sale needs to become another permanent inventory record. With the right ERP structure, your team can keep one-off and custom transactions organized while keeping regular inventory separate from non-inventoried products and services.
See how Versa Cloud ERP can help your team manage different types of transactions in one system. Explore product and inventory management to see how your products and transactions can be structured around the way your business actually operates.
Request a Versa Cloud ERP Demo and talk with our team about how you currently handle one-off and custom orders.
