Manufacturing preferences in NetSuite are the control panel for how your entire production system operates. Before recent updates, these settings were scattered throughout the accounting section, making them hard to find and harder to configure correctly. NetSuite consolidated these preferences into a dedicated manufacturing section under Setup > Manufacturing, creating a more intuitive workflow that actually makes sense for production managers.
Think of manufacturing preferences as the bridge between your theoretical production plans and what actually happens on the shop floor. These settings determine everything from how work orders get scheduled to whether your system considers actual resource availability or just assumes you have unlimited capacity.
The manufacturing preferences dashboard gives you control over critical production elements:
When these preferences align with your actual shop floor capabilities, your schedules become predictable. When they don't, you end up with work orders that look great on paper but fail in reality.
Production scheduling connects every part of your manufacturing operation. Your bill of materials, routings, and material requirements planning all feed into the scheduling engine. The scheduling preferences you configure determine whether this engine produces realistic schedules or fantasy timelines that frustrate your production team.
The impact shows up immediately in your key metrics. Manufacturers with optimized configurations see reduced lead times and higher user adoption among shop floor personnel. When your system reflects reality, people actually use it.
Before you can configure anything, you need the right access. NetSuite's role-based security means not everyone can modify manufacturing preferences, which is actually a good thing when you consider how much these settings affect production.
Manufacturing configuration requires administrator-level permissions. Specifically, you need:
If you're logged in but can't see the Manufacturing Preferences menu, check your role permissions. Missing permissions are the most common reason people can't access these settings.
Once you have proper access, finding the manufacturing preferences is straightforward:
The preferences page contains numerous settings, but don't panic—only about 15 directly impact scheduling. Focus on those first before exploring advanced configurations.
Work orders and assembly builds are the fundamental transaction types that drive production scheduling. Understanding when to use each type matters because the wrong choice creates scheduling headaches down the line.
The distinction comes down to complexity:
Assembly Builds work best for:
Work Orders make sense for:
Most manufacturers start with assembly builds and graduate to work orders as complexity increases. There's no shame in keeping it simple—we believe most companies don't need the highest-complexity features unless their processes genuinely require them.
The key work order preferences that affect scheduling include:
For the Default Scheduling Method, finite scheduling considers resource availability while infinite scheduling assumes unlimited capacity. Unless you truly have unlimited capacity (you don't), finite scheduling produces more realistic timelines.
Enabling "Show Planned Capacity on Work Orders" gives you visibility into resource requirements before production begins. This single setting helps manufacturers identify bottlenecks during scheduling.
Your bill of materials drives everything about production scheduling. If your BOM data is wrong, no amount of preference configuration will fix your schedules.
Effective BOM setup requires attention to several preference areas:
The yield and scrap settings directly affect your material requirements. If you consistently see 5% scrap but your BOM doesn't account for it, you'll constantly run short on components mid-production.
Multi-level BOMs add complexity to scheduling calculations. When you have assemblies within assemblies, the scheduling engine needs to calculate lead times at each level. Your preference settings determine whether the system:
Get these settings right during initial implementation and you'll avoid scheduling surprises later.
Work in progress (WIP) tracking and routing operations represent the advanced tier of NetSuite manufacturing capabilities. These features give you operation-level visibility into production, but they also add configuration complexity.
Advanced routing lets you define specific operations within each work order:
Before enabling advanced routing, honestly assess whether you need this level of detail. A manufacturer producing custom assemblies with multiple operations definitely benefits. A company doing simple kit assembly probably doesn't.
WIP tracking shows you exactly where each work order stands in the production process. Configuration involves:
The preference settings control how much detail gets tracked. You can track labor at the operation level, capture machine time separately, and even account for setup time versus run time. But each additional tracking point adds data entry requirements for shop floor workers.
We often see manufacturers get excited about detailed tracking capabilities and over-configure their system. Start simple, prove value, then add complexity if needed.
Labor represents a significant portion of manufacturing cost, and accurate labor tracking depends on proper preference configuration. These settings determine how NetSuite calculates labor costs and schedules human resources.
Labor categories let you track different types of work at different cost rates:
The preference settings control whether labor gets applied at the work order level or operation level. Operation-level tracking gives more accuracy but requires more shop floor data entry.
Resource capacity planning prevents over-scheduling your workforce and equipment. Key preferences include:
Companies using finite capacity scheduling with proper resource configuration experience less production downtime because the system won't schedule more work than resources can handle.
Manual scheduling wastes time and introduces errors. NetSuite workflow automation transforms scheduling from a daily chore into an automatic process that runs in the background.
Workflows can automatically create work orders based on triggers like:
A simple workflow might monitor inventory levels and automatically create work orders when safety stock gets breached. More sophisticated workflows can analyze demand patterns and generate production schedules for the next planning period.
The automation capabilities significantly reduce production planning time, freeing your planners to focus on exceptions and optimization rather than routine schedule generation.
Automated alerts keep everyone informed without constant manual checking:
Configure these through workflow actions that send emails based on specific conditions. The key is balancing useful information with email overload—send alerts only for situations requiring human intervention.
Production scheduling and inventory management are inseparable. Your inventory preferences directly affect whether your schedules are realistic or fantasy.
Backflushing automatically consumes component inventory when work orders complete, eliminating manual component issue transactions. The preferences control:
Backflushing works brilliantly for high-volume, consistent production. It's less suitable for job shops with significant variation in actual component usage versus planned amounts.
Material requirements planning (MRP) uses your production schedule to calculate component needs. Key preferences include:
These settings work together to ensure components arrive when needed. If your lead times are inaccurate in the system, your schedules will consistently miss reality.
Production calendars tell NetSuite when your facility actually operates. Without accurate calendars, the system will schedule production on weekends, holidays, and other times when nobody's actually working.
Each work center can have its own calendar reflecting actual availability:
The calendar configuration affects all scheduling calculations. If you tell the system your facility operates 24/7 but you actually run only the first shift, your schedules will be consistently too aggressive.
Shift configuration defines when resources are available and at what capacity:
Be honest about capacity. It's tempting to tell the system your line can produce 100 units per hour when it really averages 85, but this guarantees scheduling problems.
No manufacturing preference configuration survives first contact with actual production without testing. Validation before going live prevents the painful discovery of configuration errors during real production runs.
If you have access to a sandbox environment, use it. Test your configuration with representative scenarios:
Watch how the system schedules each scenario. Does it match your expectations? When it doesn't, you've found a preference that needs adjustment.
Before unleashing your configuration on real production, verify:
Proper testing in a sandbox environment prevents months of production problems.
Even experienced NetSuite administrators make predictable configuration errors. Learning from others' mistakes is cheaper than learning from your own.
The biggest mistake is enabling every available feature because it sounds useful. Common over-configuration problems include:
Each additional feature adds configuration complexity and ongoing maintenance burden. Start with basic functionality and add complexity only when you have clear business justification.
This aligns with our philosophy that most manufacturers don't need the highest-complexity features unless their specific processes require them.
Manufacturing preferences interact with NetSuite roles in ways that create frustrating access problems:
Test your roles thoroughly with actual users before going live. What works for administrators often fails for frontline workers.
Manufacturing preference configuration isn't a one-time event. Your production needs evolve, NetSuite releases updates, and what worked last year might not work today.
Schedule regular reviews of your manufacturing configuration:
These reviews identify opportunities for improvement before they become problems. Companies that invest in ongoing optimization see strong ROI within months.
Configuring NetSuite manufacturing preferences correctly the first time requires expertise that comes from seeing dozens of implementations across different manufacturing environments. That's where working with local NetSuite consultants who nerd out about manufacturing makes the difference.
At Anchor Group, we've configured manufacturing preferences for everything from simple assembly operations to complex multi-level BOMs with sophisticated routings. Our team knows which preferences actually matter for your specific manufacturing process and which ones just add unnecessary complexity.
We take the time to understand your shop floor reality before touching any settings. When a client tells us they need advanced WIP tracking, we ask about their actual production processes first. Sometimes they genuinely need operation-level visibility. Often, they just need better work order status reporting, which requires much simpler configuration.
Our approach delivers results:
We're Midwestern born and bred, which means we cut through the complexity and give you straight talk about what you actually need. No overselling features you don't need, no under-configuring critical capabilities you do need—just practical manufacturing configuration that helps you earn your keep.
Working with us should feel like calling up your neighbor for a hand—familiar, reliable, and no fuss. Because when it comes to NetSuite manufacturing configuration, you deserve consultants who understand that optimal scheduling comes from matching system settings to real-world capabilities, not implementing every available feature.
You need the Manufacturing Administrator role or a custom role with Setup > Company permissions enabled. Specifically, you must have Manufacturing Preferences access rights and Work Order transaction permissions. If you're logged in but don't see the Manufacturing Preferences menu under Setup > Manufacturing > Manufacturing Preferences, check your role permissions. Missing permissions are the most common reason administrators can't access these critical settings.
No, and you probably shouldn't unless you have specific requirements for operation-level tracking. Advanced routing adds configuration complexity and requires more shop floor data entry. If your manufacturing process is relatively simple—even if you produce complex products—basic scheduling preferences often suffice. The key is matching system complexity to actual business needs. Our manufacturing team helps clients avoid over-configuration that creates more problems than it solves.
Use NetSuite workflow to monitor triggers like sales order entry, inventory reorder points, or forecast changes. Set up workflows under Customization > Workflow > Workflows that create work order records when conditions are met. The most common approach monitors inventory levels and generates work orders when safety stock gets breached. More sophisticated implementations analyze demand patterns and create production schedules for the next planning period. Proper workflow configuration significantly reduces production planning time.
Yes, NetSuite supports sophisticated multi-level BOMs with phantom assemblies, revision control, effectivity dates, and component yield settings. The system calculates lead times at each BOM level and can automatically create purchase requisitions for long-lead components. However, multi-level BOM complexity requires careful preference configuration to ensure scheduling calculations account for all levels properly. Our team regularly configures multi-level BOMs for manufacturers with complex assembly processes, ensuring the scheduling engine produces realistic timelines across all component levels.
Start with these three preferences before anything else: Default Scheduling Method (choose finite over infinite unless you truly have unlimited capacity), Show Planned Capacity on Work Orders (for visibility into resource requirements), and Automatically Fill Actual Production Start and End Dates (to reduce manual entry). Best practice recommends configuring scheduling preferences before implementing routings and BOMs. These foundational settings determine how all subsequent manufacturing configuration behaves, making them the logical starting point for any implementation.