Customer Configuration
Customers are at the heart of your revenue cycle. Proper customer configuration ensures accurate invoicing, correct tax calculation, appropriate credit management, and meaningful sales analytics.
Customer Record Fundamentals
The customer record in NetSuite serves multiple purposes: it's the bill-to entity for invoices, the anchor for sales history, the target for marketing campaigns, and the subject of credit decisions.
Key Customer Fields
- Company Name: The legal entity name—used on invoices and legal documents
- Customer ID: Auto-generated or custom format; consider using legacy system IDs during migration
- Category: High-level customer classification (Enterprise, SMB, Government, etc.)
- Status: Customer lifecycle stage (Lead, Prospect, Customer, Inactive)
- Subsidiary: Which company entity owns this customer relationship (OneWorld only)
- Currency: Primary transaction currency for this customer
- Price Level: Default pricing tier (Base Price, Wholesale, VIP, etc.)
- Payment Terms: Default terms applied to invoices (Net 30, Net 60, etc.)
- Credit Limit: Maximum allowed open balance before holds apply
- Tax Item/Tax Exempt: How tax is calculated on sales to this customer
Customer Hierarchy Design
Many businesses need to track relationships between customers—parent companies and their divisions, franchisors and franchisees, or buying groups and their members.
Customer Hierarchy Approach
Customer Addresses
NetSuite distinguishes between billing addresses (where invoices go) and shipping addresses (where goods are delivered). A customer can have multiple of each.
| Address Type | Purpose | Drives |
|---|---|---|
| Default Billing | Primary invoice address | AR correspondence, dunning letters |
| Default Shipping | Primary delivery location | Tax nexus, shipping cost calculation |
| Additional Shipping | Alternate delivery locations | Drop ship destinations, branch offices |
Credit Management Configuration
NetSuite's credit management features help control customer risk exposure.
Set Credit Limit
Establish the maximum open balance allowed for the customer based on credit analysis or corporate policy.
Configure Hold Rules
Enable credit hold preferences at Setup → Accounting → Accounting Preferences. Choose whether holds apply to sales orders, fulfillments, or both.
Define Override Roles
Specify which roles can override credit holds. Typically limited to credit managers or finance directors.
Set Up Alerts
Configure workflow alerts when customers approach or exceed credit limits. Consider alerts at 80% and 100% of limit.
Customer Categories & Custom Fields
Beyond standard fields, you'll likely need custom fields to capture business-specific customer attributes.
Common Custom Fields for Customers
- Account Manager: Employee field linking customers to their sales rep (if not using standard Sales Rep)
- Industry Vertical: Custom list for more granular industry classification
- Customer Tier: Strategic classification (Platinum, Gold, Silver)
- Acquisition Source: How the customer was acquired (Trade Show, Referral, Website)
- Contract Expiration: Date field for subscription/contract customers
- NDA on File: Checkbox for compliance tracking
- EDI Capable: Checkbox flagging customers set up for electronic transactions
Duplicate Prevention
Duplicate customer records are a data quality nightmare. They fragment sales history, complicate collections, and produce misleading reports.
Native Duplicate Detection
NetSuite offers built-in duplicate detection based on configurable criteria. Enable at Setup → Company → Duplicate Detection Rules.
- Exact Match: Flags identical company names or emails
- Fuzzy Match: Catches near-duplicates like "ABC Corp" vs "ABC Corporation"
- Phone Number Match: Useful for catching duplicates entered with different name variations
Pre-Go-Live Customer Configuration
Vendor Configuration
Vendors are your supply chain partners. Proper vendor configuration ensures smooth purchasing, accurate AP aging, proper tax reporting (1099s), and effective spend analysis.
Vendor Record Fundamentals
The vendor record in NetSuite manages your relationships with suppliers, service providers, and contractors. It drives purchasing workflows, payment processing, and regulatory compliance like 1099 reporting.
Key Vendor Fields
- Company Name: Legal name as it appears on invoices and 1099s
- Vendor ID: Unique identifier—consider matching legacy system IDs during migration
- Category: Vendor classification (Raw Materials, Services, Utilities, etc.)
- Subsidiary: Which company entity purchases from this vendor (OneWorld)
- Currency: Transaction currency for purchases
- Payment Terms: Default terms (Net 30, Net 45, 2% 10 Net 30)
- Tax ID: Federal EIN or SSN for 1099 reporting
- 1099 Eligible: Flag for US tax reporting requirements
- Default Expense Account: GL account for non-inventory purchases
Vendor Categories
Categorizing vendors enables meaningful spend analysis and helps route approvals appropriately.
| Category | Description | Examples |
|---|---|---|
| Raw Materials | Components used in manufacturing | Steel suppliers, chemical vendors |
| Finished Goods | Resale inventory suppliers | Product distributors, dropship vendors |
| Services | Professional and consulting services | Law firms, accountants, consultants |
| Utilities | Infrastructure services | Electric, water, internet providers |
| MRO | Maintenance, repair, operations | Office supplies, janitorial, equipment maintenance |
| Contractors | 1099 independent contractors | Freelancers, temp agencies |
1099 Configuration
US companies must issue 1099 forms to vendors who receive over $600 in non-employee compensation during a tax year.
Enable 1099 Features
Go to Setup → Company → Enable Features → Accounting tab. Enable "1099 Tracking" feature.
Configure 1099 Accounts
Mark expense accounts that typically involve 1099-reportable payments (professional services, rent, legal fees).
Set Vendor 1099 Flag
On each eligible vendor, check "1099 Eligible" and enter their Tax ID. Select appropriate 1099 type (NEC, MISC, etc.).
Verify Address Information
1099s are mailed to vendors—ensure mailing addresses are complete and current.
Three-Way Matching Setup
Three-way matching compares PO, receipt, and vendor bill to ensure you only pay for what was ordered and received.
Matching Level
Payment Terms Configuration
Payment terms define when vendor bills are due. Standard terms should be created before vendor records are imported.
| Term | Description | Discount |
|---|---|---|
| Net 30 | Due 30 days from invoice date | None |
| Net 45 | Due 45 days from invoice date | None |
| Net 60 | Due 60 days from invoice date | None |
| 2% 10 Net 30 | 2% discount if paid in 10 days, otherwise due in 30 | 2% |
| Due on Receipt | Payment due immediately | None |
| Prepaid | Payment required before goods/services | None |
Vendor Approval Workflow
New vendors should go through an approval process before they can be used in transactions. This prevents unauthorized spend and ensures proper due diligence.
Typical Vendor Approval Workflow
- Requestor submits: Employee creates vendor record with basic information
- Procurement review: Purchasing validates vendor legitimacy and negotiates terms
- Finance review: AP verifies tax information, bank details for ACH
- Compliance check: Verify against denied party lists, check for conflicts of interest
- Final approval: Manager or director approves based on spend threshold
Vendor Banking for ACH Payments
If you pay vendors via ACH/EFT, their banking information must be stored securely on the vendor record.
Banking Fields
- Bank Name: Name of vendor's financial institution
- Account Number: Vendor's bank account number
- Routing Number: ABA routing number for US banks
- Account Type: Checking or Savings
- IBAN/SWIFT: For international vendors
- Require dual approval for any bank account changes
- Verify changes via phone call to a known number (not from the change request)
- Send confirmation to vendor's registered email when banking changes
- Review all banking changes in weekly AP meeting
Pre-Go-Live Vendor Configuration
Employee Configuration
Employees are system users, approval participants, and cost centers. Proper employee configuration enables expense management, time tracking, project costing, and organizational reporting.
Employee Record Overview
The employee record in NetSuite serves dual purposes: it's both an HR record containing personal and organizational information, and a system identity that can be granted login access.
Core Employee Fields
- Name: Legal first and last name
- Employee ID: Unique identifier, often matching HRIS system
- Email: Required for system access—typically corporate email
- Subsidiary: Which entity employs this person (OneWorld)
- Department: Organizational department for reporting
- Location: Physical work location
- Supervisor: Reporting manager—drives approval routing
- Hire Date: Employment start date
- Job Title: Current position title
Employee vs. User Access
A critical distinction in NetSuite: every user is an employee, but not every employee is a user.
| Type | Has Employee Record | Has Login Access | License Impact |
|---|---|---|---|
| Full User | Yes | Yes (Full Access) | Consumes full user license |
| Employee Self-Service | Yes | Yes (Limited) | Free (limited to employee center) |
| No Access Employee | Yes | No | None—reference only |
Organizational Hierarchy
The supervisor field creates organizational hierarchy used for approval routing and organizational reports.
Approval Hierarchy
Role Assignment
Employee access is controlled through role assignment. Roles determine what an employee can see and do in NetSuite.
Identify Required Roles
Map employee job functions to NetSuite roles. A single employee may need multiple roles for different functions.
Assign Primary Role
Set the default role the employee sees at login. This should be their most-used role.
Add Secondary Roles
Assign additional roles the employee can switch to. Employees can change roles via the role dropdown.
Test Access
Log in as the employee (if administrator) or have them verify they can access required features.
Employee Defaults
Default values on the employee record streamline transaction entry by auto-populating fields.
Key Default Fields
- Default Expense Account: Account used when employee submits expenses
- Default Subsidiary: Pre-selected subsidiary on transactions
- Default Location: Pre-selected location on transactions
- Default Department: Pre-selected department on transactions
- Default Class: Pre-selected class on transactions
- Currency: Employee's preferred transaction currency
Time and Expense Configuration
If using NetSuite for time tracking or expense management, additional employee configuration is required.
Time Tracking Setup
- Time Approver: Who approves this employee's timesheets
- Labor Cost: Internal cost rate for project costing
- Billable Rate: Rate charged to customers for this employee's time
- Work Calendar: Which calendar defines their work schedule
- Overtime Eligible: Whether overtime rules apply
Expense Setup
- Expense Approver: Who approves expense reports
- Expense Limit: Maximum single expense without additional approval
- Corporate Card: Link to corporate credit card for statement reconciliation
- Reimbursement Method: How employee receives reimbursement (check, ACH, payroll)
Sales Rep Configuration
Employees involved in sales need additional configuration to track commissions and sales credit.
Sales Rep Fields
- Is Sales Rep: Checkbox enabling sales rep functionality
- Sales Territory: Assigned territory for territory management
- Commission Plan: Which commission plan applies to this rep
- Sales Target: Quota for reporting and dashboards
- Give Access to All Customers: Whether rep can see customers outside their territory
Employee Lifecycle
- Remove all roles (revokes access)
- Set "Give Access" to No
- Set Release Date/Termination Date
- Update supervisor for their direct reports
- Reassign any open transactions, opportunities, or cases
Pre-Go-Live Employee Configuration
Contact Strategy
Contacts are the people at customer, vendor, and partner organizations. A well-designed contact strategy enables effective communication, proper transaction routing, and comprehensive relationship management.
Understanding Contacts in NetSuite
Contacts are individual people associated with entity records (customers, vendors, partners). Unlike the entity itself, which represents the company or organization, contacts represent the humans you interact with.
Contact vs. Entity
- Entity (Customer/Vendor): The company you do business with—bills, pays, and has a balance
- Contact: A person at that company—receives emails, makes decisions, attends meetings
Contact Roles
Contact roles define the function a contact plays at their company. Roles enable targeted communication and workflow automation.
| Role | Typical Use | Transaction Association |
|---|---|---|
| Primary Contact | Main point of contact for general business | Default on most communications |
| Billing Contact | Receives invoices and billing inquiries | Invoice emails, AR statements |
| Shipping Contact | Coordinates deliveries | Fulfillment notifications, tracking info |
| Purchasing Contact | Places orders, negotiates pricing | Order confirmations, quotes |
| Technical Contact | Handles technical issues and support | Support cases, product updates |
| Executive Sponsor | Senior decision maker | Escalations, strategic communications |
Contact Creation Strategy
There are multiple ways contacts enter NetSuite. Your strategy should define which methods are appropriate for your organization.
Contact Creation Approach
Contact Fields Configuration
Configure contact fields to capture information relevant to your business communication needs.
Standard Contact Fields
- Name: First name, middle name, last name, salutation
- Company: Associated customer, vendor, or partner record
- Email: Primary email address for communications
- Phone: Office phone, mobile phone, fax
- Title: Job title at their company
- Role: Contact role (from your configured list)
- Subsidiary: For multi-subsidiary filtering
Common Custom Fields
- Preferred Communication: Email, phone, or text preference
- LinkedIn URL: Professional profile link
- Last Contact Date: Track engagement recency
- Marketing Opt-In: Email marketing consent status
- Decision Authority: Budget owner, influencer, end user
- Birthday: For personalized outreach
Contact Access Control
By default, contacts are visible to anyone with access to the parent entity. Configure access controls based on your security requirements.
Access Options
- Global Access: All employees can view all contacts
- Role-Based: Contacts visible based on user's role permissions
- Sales Rep Restricted: Contacts visible only to assigned sales rep
- Subsidiary Restricted: Contacts visible only within subsidiary
Transaction Contact Assignment
Contacts can be assigned to transactions to specify who should receive communications about that transaction.
| Transaction Type | Contact Use | Email Trigger |
|---|---|---|
| Quote/Estimate | Purchasing or Decision Maker | Quote PDF email |
| Sales Order | Purchasing Contact | Order confirmation |
| Item Fulfillment | Shipping Contact | Tracking notification |
| Invoice | Billing Contact | Invoice email |
| Support Case | Technical Contact | Case updates |
Customer Portal Access (Contact Login)
Contacts can be granted access to the Customer Center portal to view invoices, track orders, and submit support cases.
Enable Web Access
On the contact record, check "Give Access" and assign a Customer Center role.
Set Login Credentials
Enter email and password, or enable password reset email for the contact to set their own.
Configure Access Level
Determine what the contact can see—their own orders only, or all orders for their company.
Send Welcome Email
Trigger onboarding email with login instructions and portal URL.
Duplicate Contact Prevention
Contact duplication is common, especially when multiple teams create contacts. Implement controls to minimize duplicates.
Prevention Strategies
- Email Uniqueness: Configure duplicate detection to flag matching emails
- Search Before Create: Train users to search for existing contacts first
- Workflow Validation: Check for duplicates on save and alert user
- Regular Cleanup: Schedule periodic duplicate review and merge
Pre-Go-Live Contact Configuration
Partner & Competitor Records
Partners and competitors round out NetSuite's relationship management capabilities. Partner records track referral relationships and commissions, while competitor records support competitive intelligence in sales cycles.
Partner Records Overview
Partner records represent organizations or individuals who refer business to you, resell your products, or collaborate with you in delivering solutions.
Common Partner Types
- Referral Partners: Introduce leads and earn referral fees
- Resellers: Purchase and resell your products (may also be vendors)
- Implementation Partners: Deliver services using your platform
- Technology Partners: Integrate complementary solutions
- Affiliates: Promote products through online channels
Partner Commission Tracking
NetSuite can track partner commissions on transactions they influence or refer.
| Commission Model | Description | Configuration |
|---|---|---|
| Flat Percentage | Fixed % of deal value | Set default rate on partner record |
| Tiered | Rate varies by volume or product | Custom commission schedules |
| Revenue Share | Ongoing % of recurring revenue | Workflow calculation on renewals |
| Fixed Fee | Set amount per referral | Custom field calculation |
Partner Portal Access
Partners can be granted portal access to view leads, register deals, track commissions, and access marketing materials.
Partner Center Capabilities
- Lead Registration: Partners submit leads for approval
- Deal Registration: Protect partner opportunities from channel conflict
- Commission Statements: View earned and pending commissions
- Marketing Resources: Download approved collateral and campaigns
- Training Materials: Access product and sales training
Competitor Records
Competitor records track companies you compete against in sales situations. They support sales intelligence and win/loss analysis.
Key Competitor Fields
- Name: Competitor company name
- URL: Competitor website for quick reference
- Strengths: What they do well—inform sales strategy
- Weaknesses: Where you can differentiate
- Strategies: How to compete against them
- Win Rate: Calculated from opportunities
Using Competitors in Sales
Link competitors to opportunities to track competitive situations and analyze win/loss patterns.
Competitor Tracking Depth
Partner & Competitor Reporting
Both partners and competitors enable valuable reporting when used consistently.
Partner Reports
- Partner Performance: Revenue generated per partner
- Commission Accrual: Outstanding commission obligations
- Partner Pipeline: Opportunities by partner
- Lead Conversion: Partner lead to customer conversion rate
Competitor Reports
- Win Rate by Competitor: How often you win against each competitor
- Competitor Frequency: Which competitors appear most often
- Loss Reasons: Why you lose to specific competitors
- Deal Size Impact: How competitor presence affects deal size
Pre-Go-Live Configuration
Item Types Deep Dive
Items are what you sell, buy, and track. NetSuite provides numerous item types, each with specific behaviors. Choosing the right item type is critical—changing later often requires recreating the item.
Item Type Overview
NetSuite's item types determine how an item behaves in transactions, inventory tracking, GL posting, and reporting.
Core Item Types
| Item Type | Tracks Inventory | Typical Use |
|---|---|---|
| Inventory Item | Yes | Physical goods you stock and ship |
| Non-Inventory Item | No | Physical goods you don't track (office supplies, low-value items) |
| Service Item | No | Labor, consulting, professional services |
| Other Charge Item | No | Freight, handling, fees, miscellaneous charges |
| Discount Item | No | Line-level discounts (%, $, or formula) |
| Markup Item | No | Line-level surcharges |
| Payment Item | No | Customer payments applied to invoices |
| Subtotal Item | No | Subtotals within transactions |
Inventory Items
Inventory items are physical products you purchase, stock, and sell. They drive perpetual inventory tracking, costing, and valuation.
Key Configuration Fields
- Costing Method: FIFO, LIFO, Average, or Standard (set at subsidiary level)
- Track Landed Cost: Include freight and duties in item cost
- Lot Numbered: Track items by lot for traceability
- Serialized: Track individual serial numbers
- Location Inventory: Track quantity by location
- Reorder Point: Trigger purchase orders when stock falls below threshold
- Preferred Vendor: Default vendor for purchasing
Costing Method
Service Items
Service items represent labor or professional services. They don't track inventory but do track revenue and may track time.
Service Item Subtypes
- For Sale: Services you sell to customers (consulting, support)
- For Purchase: Services you buy from vendors (contractors, outsourced work)
- For Resale: Services you buy and resell (subcontracted services)
Non-Inventory Items
Non-inventory items represent physical goods you don't track in inventory—either because they're low-value, consumed immediately, or fulfilled via drop ship.
Common Uses
- Office Supplies: Pens, paper, toner—not worth tracking individually
- Drop Ship Items: Products shipped directly from vendor to customer
- Special Orders: One-time items ordered specifically for a customer
- Consumables: Items used internally (cleaning supplies, break room items)
Other Charge Items
Other Charge items capture miscellaneous fees and charges that aren't products or services.
Common Uses
- Freight: Shipping charges billed to customers
- Handling: Packaging and handling fees
- Setup Fees: One-time configuration charges
- Restocking Fees: Charges for returned items
- Rush Charges: Expedited processing fees
Discount and Markup Items
These items modify line amounts within transactions.
Discount Items
- Percentage: Reduce by % of subtotal above discount line
- Fixed Amount: Reduce by flat dollar amount
- Rate: Apply discount based on item-level calculation
Markup Items
- Same options as Discount: Increase rather than decrease amounts
- Use for surcharges: Fuel surcharges, expedited handling
Item GL Impact
Each item type has default accounts that control GL posting. Understanding this is essential for accurate financial reporting.
| Item Type | Key Accounts |
|---|---|
| Inventory Item | Asset (Inventory), COGS, Income (Revenue), Expense |
| Service Item | Income (Revenue), Expense (if purchased) |
| Non-Inventory | Income, COGS or Expense |
| Other Charge | Income or Expense |
| Discount | Contra-revenue or expense |
Special Item Types
| Type | Purpose | Common Use |
|---|---|---|
| Kit/Package | Bundle items for sale as a single unit | Product bundles, starter kits |
| Assembly/BOM | Items manufactured from components | Manufactured products |
| Group Item | Group items for entry convenience | Standard order templates |
| Description Item | Add text to transactions | Special instructions, notes |
| Gift Certificate | Store credit instruments | Retail gift cards |
| Download Item | Digital products | Software, digital content |
Before Creating Items
Assembly & BOM Items
Assembly items represent products manufactured from component parts. The Bill of Materials (BOM) defines the recipe, and assembly builds consume components to produce finished goods.
Understanding Assembly Items
Assembly items are central to manufacturing in NetSuite. When you build an assembly, the system consumes the component items and adds the finished product to inventory—all with proper GL entries.
Assembly vs. Kit
| Feature | Assembly Item | Kit/Package |
|---|---|---|
| Components consumed? | Yes, during assembly build | No, consumed at sale |
| Finished item tracked? | Yes, as separate inventory | No, components tracked |
| Build transaction? | Yes, required | No |
| Typical use | Manufacturing | Product bundles, combos |
Bill of Materials (BOM)
The BOM defines what components make up an assembly and in what quantities. This is the recipe for your manufactured product.
BOM Configuration
- Component Item: The raw material or sub-assembly used
- Quantity: Amount of component per unit of assembly
- Item Source: Stock (from inventory), Work Order, or Phantom
- Component Yield: Expected yield percentage (for loss/scrap)
- BOM Revision: Version control for BOM changes
Work Orders
For more complex manufacturing, Work Orders provide additional control over the build process.
Work Order Features
- Planned vs. Released: Stage builds through planning approval
- Component Issuance: Track when components are issued to production
- Labor Tracking: Record labor time against production
- Routing: Define production steps and operations
- Partial Completions: Complete builds in stages
- Scrap Tracking: Record and account for production scrap
Assembly Build Process
Assembly builds are transactions that consume components and create finished goods.
Create Assembly Build
Navigate to Transactions → Manufacturing → Build Assemblies. Select the assembly item and quantity to build.
Verify Components
System displays required components based on BOM. Verify availability. Adjust quantities if actual usage differs.
Execute Build
Save the assembly build. Components are consumed from inventory, finished goods added.
Review GL Impact
Verify proper COGS/inventory entries. WIP (Work in Progress) account used if applicable.
Build Location
Assembly Costing
Assembly item costs roll up from components. Understanding how cost flows is essential for accurate product costing.
Cost Components
- Material Cost: Sum of component item costs × quantities
- Labor Cost: Direct labor applied to production
- Machine Cost: Equipment/overhead applied to production
- Overhead: Indirect costs allocated to production
Phantom Items
Phantom items are sub-assemblies that exist in the BOM but aren't stocked as separate inventory items.
Phantom Item Behavior
- Components "pass through" to parent assembly build
- No separate inventory tracking for the phantom itself
- Useful for logical groupings of components
- Simplifies BOM management for common sub-assemblies
BOM Revisions
As products evolve, BOMs change. BOM revisions track these changes and maintain history.
Revision Management
- Effective Dates: When each revision becomes active
- Reason Codes: Why the BOM changed (engineering change, cost reduction)
- Component Substitution: Replace one component with another
- Quantity Changes: Adjust component quantities
- Historical Builds: Builds reference the BOM revision active at build time
Pre-Go-Live Assembly Configuration
Matrix Items
Matrix items manage products with variations like size, color, or style. They simplify management of variant products while maintaining separate SKUs for inventory tracking and order fulfillment.
Understanding Matrix Items
Matrix items solve the challenge of managing products that come in multiple variations. Instead of creating hundreds of individual items, you create one matrix parent with options that generate child items automatically.
Matrix Structure
- Matrix Parent: The template item defining common attributes
- Matrix Options: The variation dimensions (Size, Color, etc.)
- Matrix Children: Individual SKUs for each combination (Small/Red, Large/Blue, etc.)
Matrix Options Configuration
Matrix options define the variation dimensions. Each option creates a level in the matrix.
Common Matrix Options
| Option | Example Values | Industry Use |
|---|---|---|
| Size | XS, S, M, L, XL, XXL | Apparel, footwear |
| Color | Black, White, Navy, Red | Apparel, consumer goods |
| Width | Narrow, Regular, Wide | Footwear |
| Capacity | 64GB, 128GB, 256GB | Electronics |
| Material | Cotton, Polyester, Silk | Textiles, furniture |
Matrix Item Pricing
Matrix items support flexible pricing at both parent and child levels.
Pricing Approach
Creating Matrix Items
The matrix item creation process builds the parent and generates children in one workflow.
Create Matrix Parent
Start with a new Inventory Item. Check "Matrix Item" on the item record. Fill common fields (name, vendor, category).
Select Matrix Options
Choose which matrix options apply to this item. Select specific values available for each option.
Configure Combinations
Review the matrix grid showing all combinations. Deselect any invalid combinations (e.g., XXL not available in certain colors).
Set Pricing
Set base price on parent. Optionally set different prices for specific children (size surcharge, material upcharge).
Generate Children
Save the matrix item. NetSuite generates all child SKUs automatically based on your selections.
Child Item Naming
Child items need unique names/SKUs. NetSuite can auto-generate these based on configurable patterns.
Naming Pattern Options
- Parent + Options: TSHIRT-001-RED-LARGE
- Option Abbreviations: TSHIRT-001-R-L
- Sequential Numbers: TSHIRT-001-001, TSHIRT-001-002
- Custom Pattern: Configure via item preferences
Inventory Tracking
Matrix children are full inventory items—each tracks quantity separately. The parent doesn't hold inventory.
Inventory Considerations
- Location Tracking: Each child tracks quantity by location independently
- Lot/Serial: Children can be lot-numbered or serialized individually
- Reorder Points: Set reorder points on children, not parent
- Committed/Available: Standard inventory fields apply to children
Transaction Entry
When adding matrix items to transactions, users can select from the parent level or child level.
Entry Methods
- Matrix Popup: Select parent item, popup shows grid of options to choose variant
- Direct Child Entry: Type or scan child SKU directly
- Barcode Scanning: Scan child item barcode for direct entry
Managing Matrix Changes
Products evolve—new colors launch, sizes discontinue. Matrix items handle this through adding and inactivating children.
Adding New Options
- Edit the matrix parent item
- Add new option values to the matrix grid
- Save to generate new child items
- Set pricing and configure new children as needed
Discontinuing Options
- Sell through remaining inventory
- Inactivate child items (don't delete—preserves history)
- Optionally remove from matrix grid display
Pre-Go-Live Matrix Configuration
Pricing Configuration
Pricing determines profitability. NetSuite offers multiple pricing mechanisms from simple base prices to complex quantity schedules and customer-specific pricing.
Pricing Fundamentals
Every item needs a price, but how that price is determined varies significantly across business models.
Key Pricing Concepts
- Base Price: The default price on the item record
- Price Level: Named pricing tiers (Wholesale, Retail, VIP)
- Quantity Pricing: Price varies by quantity ordered
- Customer-Specific Pricing: Custom prices for individual customers
- Promotional Pricing: Time-limited price changes
Price Levels
Price levels create named pricing tiers that can be assigned to customers. This is the most common approach for B2B pricing.
Common Price Level Structures
| Level Name | Discount from Base | Typical Use |
|---|---|---|
| Base Price | 0% | Walk-in customers, retail |
| Wholesale | 20-30% | Resellers, large buyers |
| Distributor | 30-40% | Distribution partners |
| VIP/Preferred | 10-15% | Long-term loyal customers |
| Employee | 40-50% | Internal employee purchases |
Price Level Approach
Quantity Pricing Schedules
Quantity pricing provides discounts based on order quantity, encouraging larger purchases.
| Minimum Qty | Maximum Qty | Price | Discount |
|---|---|---|---|
| 1 | 9 | $100.00 | 0% |
| 10 | 49 | $95.00 | 5% |
| 50 | 99 | $90.00 | 10% |
| 100 | ∞ | $85.00 | 15% |
Customer-Specific Pricing
Sometimes standard price levels aren't enough—specific customers need unique pricing for specific items.
Implementation Options
- Item Pricing Subtab: On customer record, set specific prices for individual items
- Group Pricing: Create pricing groups, assign customers, set item prices at group level
- Custom Price Lists: Use custom records for complex pricing matrices
Promotional Pricing
Promotional pricing provides temporary price changes without modifying permanent item prices.
Promotion Methods
- Sale Price: Set temporary sale price with date range on item
- Promotion Codes: Customer enters code for discount
- Automatic Discounts: Rules-based discounts applied at checkout
- Bundle Pricing: Discount when buying items together
Multiple Currencies
For international sales, items need prices in multiple currencies. NetSuite handles this through multi-currency pricing.
Currency Pricing Options
- Base + Exchange Rate: Set base price, system calculates foreign currency using exchange rates
- Fixed Currency Prices: Set specific prices in each currency (e.g., $100 USD = €95 EUR)
- Rounded Currency Prices: Auto-calculate but round to psychological price points
Pricing Hierarchy
When multiple pricing rules apply, NetSuite follows a hierarchy to determine which price wins.
Customer-Specific Price
If customer has a specific price for this item, use it.
Group Price
If customer belongs to a pricing group with item price, use it.
Customer Price Level
Apply customer's assigned price level to item's price matrix.
Quantity Schedule
Apply quantity-based pricing if configured.
Base Price
Fall back to item's base price.
Pre-Go-Live Pricing Setup
Industry Item Patterns
Different industries have distinct item requirements. This chapter provides industry-specific guidance on item structures, custom fields, and configuration patterns.
Manufacturing Item Patterns
Typical Item Structure
- Raw Materials: Inventory items with vendor sourcing, landed cost tracking
- Components: Inventory items or non-inventory (consumables like fasteners)
- Sub-Assemblies: Assembly items built from components, sometimes phantoms
- Finished Goods: Assembly items with full BOMs, serialized if required
- MRO Supplies: Non-inventory items expensed when purchased
Key Custom Fields
- Engineering Drawing Number: Link to CAD/engineering documentation
- Revision Level: Track engineering changes
- Lead Time (Days): Manufacturing or procurement lead time
- Quality Hold: Flag for quarantine status
- RoHS Compliant: Regulatory compliance checkbox
- Shelf Life (Days): For perishable materials
Wholesale Distribution Item Patterns
Typical Item Structure
- Stocked Items: Inventory items purchased and warehoused
- Drop Ship Items: Non-inventory for resale, shipped direct from vendor
- Special Order: Non-inventory ordered per customer request
- Kits/Bundles: Kit items combining related products
Key Custom Fields
- Manufacturer: Brand/manufacturer (if multi-brand distributor)
- Manufacturer Part Number: MPN for cross-reference
- UPC/EAN: Barcode for scanning
- Hazmat Classification: For shipping compliance
- Cube/Weight: Shipping dimensional data
- Country of Origin: Import/tariff tracking
- Min Order Qty: Vendor minimum order requirements
Retail Item Patterns
Typical Item Structure
- Matrix Items: Products with Size/Color variations
- Simple Items: Non-variant products
- Gift Cards: Gift certificate items
- Services: Delivery, assembly, warranty services
Key Custom Fields
- Season: Spring/Summer/Fall/Winter or Year
- Style Number: Fashion industry style identifier
- Web Enabled: Flag for e-commerce visibility
- POS Category: Point-of-sale grouping
- Markdown Eligible: For promotional planning
- Display Location: Store merchandising placement
Software/SaaS Item Patterns
Typical Item Structure
- Subscription Items: Recurring revenue products (monthly, annual)
- License Items: Perpetual or term licenses
- Implementation Services: Professional services items
- Support/Maintenance: Ongoing support items
- Usage Items: Consumption-based pricing (API calls, storage)
Key Custom Fields
- Subscription Term: Monthly, Annual, Multi-Year
- Revenue Recognition Rule: Ratable, milestone, etc.
- Renewal Type: Auto-renew, opt-in, opt-out
- Product Tier: Basic, Pro, Enterprise
- User Count Basis: Named users, concurrent users
- ARR/MRR Impact: For SaaS metrics tracking
Professional Services Item Patterns
Typical Item Structure
- Time & Materials Services: Billable by hour/day
- Fixed Fee Services: Project-based deliverables
- Retainer Services: Ongoing availability fees
- Expense Pass-through: Reimbursable expenses
Key Custom Fields
- Billing Rate Tier: Partner, Manager, Staff rates
- Internal Cost Rate: For profitability calculation
- Service Category: Advisory, Implementation, Support
- Skill Required: Required qualifications
- Non-Billable Flag: For internal/pro-bono work
Nonprofit Item Patterns
Typical Item Structure
- Donation Items: General donations, annual fund, capital campaign
- Grant Items: Restricted and unrestricted grants
- Program Fees: Event registrations, membership dues
- Merchandise: Items sold for fundraising
Key Custom Fields
- Fund/Campaign: Link to fundraising campaign
- Restriction Type: Unrestricted, temporarily restricted, permanently restricted
- Tax Deductible Amount: For donor acknowledgment
- Grant Period: Start/end dates for grant tracking
- Program Area: Link to program for allocation
Healthcare Item Patterns
Typical Item Structure
- Medical Supplies: Lot-tracked inventory items
- Pharmaceuticals: Serialized, lot-tracked with expiration
- Medical Devices: Serialized equipment with warranty tracking
- Services: Procedures, consultations, therapy sessions
Key Custom Fields
- NDC Number: National Drug Code for pharmaceuticals
- HCPCS Code: Healthcare Common Procedure Coding System
- FDA Class: Device classification
- Controlled Substance Schedule: DEA scheduling
- Expiration Date: For lot tracking
- Storage Requirements: Temperature, handling instructions
Industry Pattern Summary
| Industry | Primary Item Types | Key Considerations |
|---|---|---|
| Manufacturing | Assembly, Inventory | BOMs, costing, lot/serial |
| Wholesale | Inventory, Non-inventory | Pricing, vendor management |
| Retail | Matrix, Inventory | Variants, promotions |
| Software/SaaS | Service, Non-inventory | Revenue recognition |
| Services | Service | Billing rates, time tracking |
| Nonprofit | Service, Non-inventory | Fund accounting |
| Healthcare | Inventory, Service | Compliance, lot/serial |
