Consule Solutions builds six native manufacturing add-ons for NetSuite. Almost nobody needs all six. Each one closes a different gap in NetSuite’s native manufacturing module, so the useful question is not what the suite does — it is which product fixes the thing that is costing you money this quarter.
This page is the decision guide. Start from the symptom rather than the product name; the full documentation for each product is linked throughout. If you want the commercial overview of the suite instead, that lives on the Consule Solutions products page.
Find the line that sounds most like your plant. If several apply, start with whichever one is costing you the most right now — the products are independent and can be added in any order, so there is no sequencing penalty for beginning in the middle.
| What you are dealing with | The product | Why that one |
|---|---|---|
| Formulas and recipes do not fit NetSuite’s bills of material | ProShop | Formula masters with automatic component scaling, and batch work orders built from them |
| Finished weight is never exactly the ordered weight | CatchIQ | Catch weight with dual UOM across sales, purchasing and production |
| One run produces two or three saleable outputs | CoYield | Co-products and by-products recorded against the completion, with their own lot and status |
| Components get substituted mid-run and the BOM never matches | FlexBom | Dynamic bills of material with substitution and version control |
| You cannot see what is running where, or spot a bottleneck early | FactorySync | Gantt, Kanban and calendar views over work orders, plus work-center load analysis |
| Schedules slip and nobody finds out until the due date | FactorySync alerts | Due-date risk analysis and automated alerts on overdue and blocked work |
| Production is recorded on paper and keyed into NetSuite later | FactoryBridge | The operator records the run at the station and it writes straight to NetSuite |
| You cannot trace which lot went into which finished item | FactoryBridge | Components issued against a specific lot, bin and inventory status |
| Nobody knows why the line stopped, only that it did | FactoryBridge | A pause cannot be recorded without a coded reason, chosen at the moment it happens |
| Setup time is invisible because it is bundled into run time | FactoryBridge | Setup and run are timed as two separate phases, so changeover cost is a number |
| Machine utilization is guesswork | FactoryPulse | Counts come from the equipment itself rather than from a clipboard |
| You sell board feet, not eaches | LumberSuite | Board-foot calculation, tally management and sawmill yield analysis |
| Every order is engineered to order and costed as a project | Project2Prod | Project tasks, costs and timesheets tied to the work orders that deliver them |
NetSuite’s native manufacturing was built for discrete assembly: a bill of materials, a work order, a finished unit. If that describes you, you may not need ProShop or LumberSuite at all. If you run formulas, recipes or campaigns, where quantities scale and a single run yields more than one saleable thing, that is the batch world and ProShop is where to start — the longer version is on the NetSuite batch manufacturing page. If your unit of sale is board feet or a tally rather than an each, that is LumberSuite. If the job is a project before it is a work order, that is Project2Prod.
There are two very different failures that both get described as “we have no visibility”. One is not knowing what should happen: what runs where, in what order, and whether the due date is still realistic. That is a planning problem, and it is FactorySync. The other is not knowing what did happen: how long setup really took, why the line stopped, which lot went into the batch, how much came out. That is an execution problem, and it is FactoryBridge — the layer most manufacturers mean when they search for a NetSuite MES. Being clear about which of the two you have saves the most time of anything on this page.
FactoryBridge captures what a person records, and does it far more reliably than paper. FactoryPulse captures what the machine did, whether or not anyone recorded it. If your operators are already honest and diligent and the problem is simply that nothing is written down, FactoryBridge is enough. If you need machine-level availability and OEE that nobody can round off, FactoryPulse is the layer that supplies it.
Choose it if your bills of material are really formulas, if quantities scale by batch size, if you weigh what you ship, or if a run yields co-products and by-products. You probably do not need it if you assemble a fixed set of components into one finished unit. Six modules: BatchWizard, CatchIQ, CoYield, FlexBom, YieldCraft and Repack Orders.
Choose it if the schedule lives in a spreadsheet or someone’s head, if you find out about a slipped date from the customer, or if you cannot say which work center is the constraint. You probably do not need it yet if you run one line and the sequence is obvious. See scheduling and capacity planning.
Choose it if there is paper on the floor, if traceability is reconstructed after the fact, or if downtime has no reasons attached to it. You probably do not need it if your operators already work directly in NetSuite and the record is complete. See the operator console, batch execution and offline sync.
Choose it if you want OEE you can defend, or if measured machine time and recorded machine time do not agree. You probably do not need it first — it is most useful once execution is already being captured, because it corroborates a record rather than creating one.
Choose it if you buy, cut or sell in board feet, keep tallies, or need sawmill recovery rates. It does not overlap with the others: lumber companies commonly run LumberSuite alongside FactorySync or FactoryBridge.
Choose it if work arrives as a project, is quoted as a project, and has to be costed as one while still being manufactured. You probably do not need it if you build to stock against a forecast.
Three pairings account for most implementations. ProShop plus FactoryBridge is the batch manufacturer who wants formula-driven work orders and then wants them executed without paper. FactorySync plus FactoryBridge is the plant that has both halves of the visibility problem — a plan nobody can see and an actual nobody records. FactoryBridge plus FactoryPulse is the operation that already captures execution and now wants the machine’s own account of the same shift. Anything can follow anything; none of these is a prerequisite for another.
Ask what you would fix if you could fix exactly one thing. If the answer involves a formula or a weight, start with ProShop. If it involves paper, start with FactoryBridge. If it involves a date, start with FactorySync. Everything else can wait for the second phase.
All six read and write standard NetSuite records using SuiteScript, SuiteFlow and SuiteBuilder. That is what makes starting small safe: there is no integration to build before anything works, no second database to reconcile, no duplicate item or lot master, and no separate login for operators. Locations, work centers, items, lots and bins are read from NetSuite as they already exist, so adding a second product later does not mean modeling your plant again.
If you would rather start from your industry than your symptom, the same choices are laid out for food & beverage, chemical manufacturing, pharmaceutical, jewelry & precious metals, lumber & timber and plastics & injection molding.
Browse the Product DocumentationNo, and most customers never buy all six. Each product is independent and solves a different problem. Start with the one that addresses your biggest pain point — ProShop for batch and formula manufacturers, FactoryBridge for anyone still recording production on paper — and add others when there is a reason to.
FactorySync is the planning layer: it decides what should run where and when, and shows load, dependencies and bottlenecks. FactoryBridge is the execution layer: it records what actually happened on the floor — timed setup and run, coded downtime, material issued by lot and bin, and yield. Plan versus actual. Many plants need both, but rarely at the same moment.
Whichever addresses the loss you can already quantify. If you cannot quantify one, FactoryBridge is usually the safest opening move, because it creates the production record everything else is measured against. There is no technical ordering requirement — the products do not depend on each other.
They cover the same shift from two directions. FactoryBridge captures what the operator records; FactoryPulse captures what the equipment did. FactoryPulse is most valuable once execution is already being captured, because its job is to corroborate and complete that record rather than to replace it.
Timelines vary with product and requirements. A single product is typically 2-4 weeks and a fuller suite 6-8 weeks. Because these are native add-ons there is no separate system to stand up and no integration to build before anything works.
Yes, and that is the normal path. All six read the same NetSuite records, so a second product inherits the locations, work centers, items, lots and bins already in use. Adding one later costs configuration, not re-implementation.
Yes. The products use standard NetSuite records and APIs and are designed to coexist with your saved searches, workflows, scripts and third-party integrations. They also support OneWorld, reading locations and subsidiaries from NetSuite so a multi-site manufacturer can run different settings per subsidiary in one instance.