ERP and NetSuite

NetSuite Setup Guide for Distributors

Jithesh Manoharan, Chief Executive Officer. . 4 min read

In short

NetSuite for wholesale distribution lives or dies on two numbers. True landed cost per item, and margin per order line after every discount and rebate. Thin margins mean a small costing error becomes a large profitability error, and a business can run for years without knowing which customers actually make money.

Distribution is a business of small percentages repeated at volume. That single fact should shape the entire system design.

In a business with generous margins a costing error is an annoyance. In distribution it can be the difference between a profitable customer and one you are subsidising. The systems question is therefore not whether you can process orders. It is whether you know, at line level, what each one actually made.

NetSuite for wholesale distribution starts with landed cost

Most distributors know what they paid a supplier. Fewer know what an item really cost by the time it was available to sell.

Freight, duty, insurance, handling and any inbound inspection all belong on the item. Left in a general expense account they disappear into overhead, and every margin figure you produce is wrong in the flattering direction.

The distortion is not evenly spread. It is worst on low value, high volume, heavy or bulky lines, where freight is a large share of the delivered cost. Those are often exactly the lines a customer is pushing hardest on price. So the error lands precisely where the decision is most sensitive.

Landed costing is more work to set up and it is the foundation everything else stands on.

Pricing is where the margin actually leaks

Distributors rarely have one price. They have customer specific prices, contract prices, volume breaks, promotional prices and the price a salesperson agreed on a call.

Every one of those is legitimate. The problem is when they live in different places, and when the system cannot say which rule applied to a given line and why.

The design goal is that price is derived by the system from rules, with manual override possible but recorded. Then you can ask the two questions that matter. Which customers are buying below the intended margin. And how often is price being overridden, by whom, and on what.

We go deeper into this in our guide to distributor pricing and rebate management.

Rebates have to be accrued, not discovered

Rebates run in both directions. You earn them from suppliers for hitting volume. You owe them to customers for the same reason.

Both are frequently handled outside the system, in spreadsheets, and settled periodically. That produces two problems. Margin during the period is wrong, because an earned or owed rebate has not been recognised. And the settlement arrives as a surprise adjustment that distorts a month nobody can explain afterwards.

Accruing them as they are earned puts the margin in the right period and removes the surprise. It requires the agreement terms to be held in the system rather than in a contract folder, which is the part that takes the effort.

Fill rate is a customer retention number

Distributors compete on availability as much as on price. A customer who cannot get what they need will call somebody else, and often will not call back.

So fill rate deserves to be measured properly rather than approximated. That means recording what was ordered against what shipped on the first attempt, per line, and being honest about backorders rather than treating a later shipment as a fulfilled order.

Measured that way, the number is uncomfortable and useful. It tells you which product families are failing, which suppliers are unreliable, and where safety stock is set wrong.

Inventory accuracy limits everything else

Every clever thing you might do with planning depends on the stock figure being right.

The practical route to accuracy is cycle counting rather than an annual shutdown. Count high value and high movement items frequently, everything else on a slower rotation, and investigate differences while people can still remember the week in question.

Bin level locations matter here too. A system that knows an item is in the building but not where it is will produce picking errors that look like inventory errors. Our warehouse management guide covers where dedicated warehouse capability becomes worth the investment.

Dead stock is a decision, not an accident

Every distributor accumulates stock that no longer moves. It happens for good reasons. A customer changed supplier. A product was superseded. Somebody bought well on a deal that never sold through.

What turns it into a problem is that nobody owns the decision. The stock sits, the value stays on the balance sheet, and the warehouse space is consumed by something generating nothing.

A regular report of stock with no movement over a defined period, with an owner and a required action, converts this into an ordinary commercial routine. The action might be a promotion, a return to the supplier, or a write off. Any of those beats the default, which is to do nothing for another year.

What to get live first

Purchasing, inventory, order management, landed cost and the pricing rules belong in the first release. They carry the margin logic and they are painful to retrofit.

Advanced planning, supplier portals and customer electronic data interchange can follow. The implementation timeline guide covers how phases usually break down, and the data migration checklist matters here because a distributor item master is usually large and long neglected.

Where to start

TechCloudPro works with wholesale and distribution businesses on NetSuite implementation, and with the food and beverage and industrial businesses whose product they move. If you cannot currently rank your customers by actual margin, that is the gap worth closing first.

Common questions

What makes a distribution build different from a general ERP build
Margin per line matters more than anything else, because the margins are thin. That pushes landed cost, pricing rules and rebate handling to the front of the design rather than leaving them as later refinements.
Do we need a separate warehouse management system
It depends on the complexity of your picking rather than on your size. Basic bin and lot handling is usually available in the core system. Directed picking, wave planning and dense multi zone operations are where a dedicated capability starts paying for itself.
How should landed cost be handled
Freight, duty, insurance and handling should attach to the item rather than sitting in a general expense account. Otherwise every item looks more profitable than it is, and the distortion is worst on low value high volume lines.
Can we see margin by customer
Only if every deduction attaches to the transaction. Discounts, rebates, freight allowances and returns all have to carry the customer, or customer profitability becomes an estimate somebody defends in a meeting.

About the author

Jithesh Manoharan, Chief Executive Officer

An IT consultant with experience spanning more than two decades, across startups and the Big 4 alike. Jithesh has worked as a NetSuite ERP consultant, principal advisor and solution architect for companies including Wells Fargo, Hampton Creek, Anastasia Beverly Hills and JUST Inc. He runs several concurrent programmes across industry verticals, and advises boards and executives on enterprise wide technology strategy.

Related reading

Talk to the team that wrote this

If any of this matches what you are dealing with, a short conversation will get you further than another article.

Book a consultationERP and NetSuite at TechCloudPro