NetSuite for Beauty Brands and What Breaks First

A beauty brand runs on a date. The launch is booked. The influencer schedule is set. A retail buyer has an on shelf week. All of that was agreed months before anyone knew whether the components would turn up on time.

That is worth sitting with before you start a NetSuite build. You are not buying a general ledger. You are buying something that can absorb a fixed launch date and still tell you the truth about stock, cost and margin.

NetSuite for beauty brands starts with the launch calendar

Most ERP projects open with a process map. For a beauty brand the more useful document is next year launch calendar. Everything else falls out of it.

Work backwards from a launch date and the requirements get concrete fast. Components have to be ordered against a forecast that does not exist yet. A new item has to be created before anyone knows its final cost. A bundle has to be sellable before every component has landed. Demand has to be split across direct, wholesale and retail before you know how the launch will go.

A setup that assumes a stable catalogue will break on the first limited edition. That is why the item master deserves more design time than the chart of accounts.

Kits, sets and the item master

The item master is where beauty brands lose control. A range that started with twenty products becomes several hundred records once you count shades, sizes, sets, gift boxes, retailer exclusives and the value packs that exist for one quarter only.

NetSuite gives you two honest ways to hold a bundle. It also leaves room for one bad habit.

• Kit item. Sold and priced as a single line. Components come out of stock when the kit ships. Nothing is physically built. Right for a set that is picked and packed at the moment it goes out.
• Assembly item. A real stocked record with a bill of materials, built through a work order. Right for a gift box that is assembled in advance and counted as one unit on a stock take.
• The bad habit. Selling the bundle as a non inventory item and adjusting components out by journal afterwards. It works for one season. Then the stock numbers stop reconciling and nobody can say when they started drifting.

Decide the rule per product family before go live. Not per product during go live. A brand that can answer whether a bundle is picked or pre built keeps an item master it can still maintain three seasons later.

Stock you own but cannot see

Very few beauty brands run their own filling lines. Production sits with contract manufacturers. That means a large share of the inventory you own is standing somewhere else.

Leave that unconfigured and the inventory goes invisible. Components get bought, the purchase order is receipted, and the stock either disappears into an expense account or sits in a location that has nothing to do with where it really is. At quarter end somebody rebuilds the position by email.

The fix is not exotic. Set the outsourced site up as a location. Transfer components to it rather than consuming them. Record what was produced there against a work order. Receive finished goods into your own warehouse when they physically move. At every step the balance sheet shows owned stock where it actually stands.

This is also where you find out whether your costing is honest. Freight, duty, tooling and component scrap are real costs of a finished unit. Leave them off the item and your margin report is wrong in a direction that always flatters.

Four channels, one ledger

A modern beauty brand sells direct, through wholesale accounts, through marketplaces and often through its own retail. Each one reports differently. Each one carries a different set of deductions.

Direct revenue arrives with payment fees and a return rate. Wholesale arrives with chargebacks, marketing deductions and payment terms. Marketplaces arrive net of commission with a settlement file that never matches an invoice. Retail arrives as sell in when the number you care about is sell through.

You want all of that landing in one ledger with the deductions attached. Then comparing channels is a report rather than a project. Our omnichannel retail guide goes deeper on multi channel inventory. The Shopify integration guide covers the direct side.

Margin by item, not by brand

Brand level margin is easy and nearly useless. Item level margin is hard and it decides the range.

The pricing conversation that matters happens when a buyer wants a deeper discount on one product. Or when a set has to hit a price point. Or when a component cost moves. Answering any of those needs landed cost per item, deductions allocated per channel, and a returns rate attached to the product rather than averaged across the catalogue.

That is a reporting decision you make during the build. Bolting it on later means reprocessing history, which is expensive and rarely gets done.

What to do first and what can wait

Launch dates do not move for ERP projects. So sequence matters.

Settle these before go live. Item master structure. Costing method. The contract manufacturing flow. Channel revenue mapping. Opening stock. All of them are painful to change once transactions exist.

Leave these until after. Demand planning. Advanced reporting. Retailer electronic data interchange. The automation that saves the team time. None of it needs to be live on day one and trying to land it all at once is a common reason a date slips. The implementation mistakes guide covers the pattern more generally.

Where this usually goes wrong

Three failures come up again and again.

The first is treating data migration as a job for the last fortnight. An item master carrying years of retired shades, duplicate records and inconsistent units needs cleaning long before anyone loads it. The data migration checklist is the honest version of how much work that is.

The second is going live between a launch and a retail delivery window. There is no good week. There are clearly bad ones. Pick the quiet gap even if it costs you time.

The third is designing for the range you have today. A beauty range changes every season by definition. If the setup only works for the current catalogue it has already started expiring.

Getting it built

TechCloudPro builds NetSuite for beauty brands and for the wider set of consumer and beauty brands, through NetSuite implementation and then support and optimisation once it is live. When a launch date is fixed and the team is short, specialists can join your team rather than running a separate project alongside it.

If any of this sounds like where you are, a short conversation about the calendar and the item master will get you further than another article.