30+ Manufacturing Terms Every Salesforce Professional Should Know

One of the fastest ways to lose credibility with a manufacturing operations leader is to talk about "pipeline" when they're thinking about production capacity, or to use "forecast" when they mean something entirely different than you do. Manufacturing has its own vocabulary — built over decades of supply chain practice — and it differs materially from CRM terminology.

This manufacturing glossary covers the 31 terms that come up constantly in manufacturing conversations, especially on Salesforce Manufacturing Cloud projects. For each term, you'll get a clear definition, the Salesforce Manufacturing Cloud context where relevant, and a real-world example. Bookmark it before your next manufacturing discovery call, S&OP discussion, or implementation kickoff.

Use it as a quick reference for manufacturing terminology, supply chain terminology, and manufacturing vocabulary — categorized by function so you can find what you need fast.

Forecasting & demand planning terms

These are the terms that dominate the Salesforce Manufacturing Cloud world — anything tied to building, locking, and measuring a demand plan.

1. Demand plan

Definition: The consolidated, agreed-upon view of expected demand across all accounts, channels, and product families for a defined horizon. The output of the S&OP demand review.

Salesforce Manufacturing Cloud context: Represented through the collection of Account Forecasts across all accounts for a given Forecast Set period.

Example: The Week 3 demand plan showed $4.2M for Q1 — that's what went into the financial model.

2. Forecast accuracy

Definition: How close forecasted values were to actuals over a given period. Typically measured as MAPE (Mean Absolute Percentage Error) or forecast bias.

Salesforce Manufacturing Cloud context: Calculated by comparing Account Forecast Period forecast values to actual values after actuals load. Requires the ERP actuals integration to work correctly.

Example: Our 3-month MAPE is running at 14% — our improvement target is below 10% by year end.

3. Forecast bias

Definition: Systematic tendency to forecast high or low. Positive bias (consistently over-forecasting) leads to inventory buildup; negative bias (under-forecasting) leads to shortages.

Salesforce Manufacturing Cloud context: Trackable through Account Forecast Period records by comparing the direction of variance (actual minus forecast) consistently over time.

Example: Sales reps in EMEA have a positive bias of +18% — we apply a regional adjustment in the consolidation.

4. MAPE (Mean Absolute Percentage Error)

Definition: A standard forecast accuracy metric. Calculates the average absolute percentage difference between forecast and actual values across a set of periods.

Salesforce Manufacturing Cloud context: Tracked in custom reports using Account Forecast Period forecast and actual fields. CRM Analytics templates often include pre-built MAPE calculations.

Example: Our MAPE improved from 19% to 11% after we tightened the forecast lock process. Still above our 8% target.

5. Run rate

Definition: Expected steady-state revenue or volume based on current trends, projected forward with no assumed change. Used as a baseline before applying judgmental adjustments.

Salesforce Manufacturing Cloud context: Often used to populate the baseline in Account Forecast Period records before sales rep adjustments. Some implementations auto-calculate run rate from the trailing three-month average actuals.

Example: Our run rate business is about $1.8M/month. Anything above that needs a specific deal or design win to justify it.

6. Commit

Definition: A number the business is formally committing to — to the CEO, investors, or board. Higher confidence than a forecast.

Salesforce Manufacturing Cloud context: Different from the Salesforce Forecast Category called "Commit" on Opportunities. Manufacturing commit is a period-lock decision, not an opportunity stage. This terminology collision causes frequent confusion in cross-functional discussions.

Example: Finance locked the Q4 commit last Friday. That's the number we're defending to the board.

7. Upside

Definition: Potential demand above the current committed forecast — opportunities that could materialize but aren't yet committed in the plan.

Salesforce Manufacturing Cloud context: Often tracked as a separate field on Account Forecast Period records or as a distinct account forecast set. Represents the optimistic scenario versus the committed scenario.

Example: We have $600K of identified upside in Q4 from two design wins that could ramp early. Not in the commit, but real.

8. S&OP (Sales and Operations Planning)

Definition: The monthly executive process that reconciles demand forecasts with supply capabilities and financial targets. The demand review is typically the first step; the supply review and executive reconciliation follow.

Salesforce Manufacturing Cloud context: Manufacturing Cloud is, in concept, the system of record for the demand review phase of S&OP. A well-implemented org gives the meeting leader a single dashboard view rather than a manually assembled Excel workbook.

Example: Our S&OP runs the third week of every month. Demand review is Tuesday, supply review Wednesday, exec sign-off Friday.

9. Build plan

Definition: The manufacturing schedule produced by the supply chain team based on the demand forecast. Specifies how much to produce, in what configuration, and by when.

Salesforce Manufacturing Cloud context: The build plan lives in ERP/MRP systems. Manufacturing Cloud feeds it through actuals integration — what the demand forecast says flows into the supply planning system.

Example: We froze the build plan for September. Any forecast changes after August 15 won't affect this production run.

Supply chain terminology

The terms below show up in any supply chain terminology discussion, whether you're scoping an integration, mapping a process, or sitting in on a planning review.

1. Lead time

Definition: Time between when an order is placed and when it's received. In manufacturing, lead time can range from days (off-the-shelf components) to 52+ weeks (complex or custom materials).

Salesforce Manufacturing Cloud context: Lead time determines how far ahead a manufacturer needs to forecast. A 26-week lead time on a key component means the demand forecast needs to be accurate 26+ weeks out for procurement decisions to be correct.

Example: Our DRAM supplier has a 28-week lead time right now. We're committing to POs in October for Q2 delivery.

2. MRP (Material Requirements Planning)

Definition: The supply planning system that translates demand forecasts into component and material purchase orders. MRP runs in ERP, not Salesforce.

Salesforce Manufacturing Cloud context: Feeds MRP indirectly — the demand forecast flows to supply planning teams who enter it into the MRP system. Direct integration between Manufacturing Cloud and MRP is an architectural possibility, not a standard pattern.

Example: Once we lock the demand plan, supply planning runs MRP to generate component POs for the next 12 weeks.

3. ERP (Enterprise Resource Planning)

Definition: The back-office system of record for financial transactions, inventory, production orders, and supply chain operations. Common platforms: SAP S/4HANA, Oracle ERP Cloud, Infor, Microsoft Dynamics.

Salesforce Manufacturing Cloud context: ERP is the source of actuals. Getting ERP data into Salesforce is almost always the most complex integration in a Manufacturing Cloud project.

Example: Our ERP is SAP. All shipped revenue hits SAP first; we then load it into Manufacturing Cloud nightly via MuleSoft.

4. Allocation

Definition: The process of distributing constrained supply across multiple customers or regions. When demand exceeds supply, someone must decide who gets product.

Salesforce Manufacturing Cloud context: Allocation decisions affect Account Forecast Period values — some accounts' forecasts get adjusted down to reflect supply constraints, not demand constraints. Manufacturing Cloud reflects the allocation decision but doesn't make it automatically.

Example: We had a 20% supply shortfall in Q2. Our top three distributors got full allocation; smaller accounts were reduced to 70%.

5. Safety stock

Definition: Inventory held by a distributor or manufacturer above the minimum needed to fulfill expected orders — a buffer against forecast error or supply disruption.

Salesforce Manufacturing Cloud context: Safety stock levels at distributors affect sell-in demand. When distributors are building safety stock, sell-in exceeds end demand; when they're drawing it down, sell-in is below end demand. Essential for interpreting distributor forecast data.

Example: Our distributors built 6 weeks of safety stock coming out of the pandemic. That pull-forward inflated our sell-in for 18 months.

6. Hubbing

Definition: A logistics arrangement where the manufacturer places inventory at a regional distribution hub, and the distributor's inventory position is maintained at that hub. Revenue is recognized differently than a standard sale.

Salesforce Manufacturing Cloud context: Hubbing has implications for Sales Agreement Product Schedules — when does revenue recognize? What triggers "sell" from the hub? Implementation teams need to understand the hubbing model before configuring recognition logic.

Example: About 30% of our APAC volume goes through a hub in Singapore. Revenue recognizes when the distributor pulls from the hub, not when we ship to it.

7. VMI (Vendor-Managed Inventory)

Definition: An arrangement where the manufacturer (vendor) is responsible for monitoring and replenishing distributor inventory levels, rather than the distributor placing individual orders.

Salesforce Manufacturing Cloud context: VMI changes the demand signal model. The manufacturer has visibility into distributor stock levels directly and makes replenishment decisions without waiting for purchase orders. This visibility can feed Manufacturing Cloud's forecasting if integration is in place.

Example: We run VMI with our top two distributors. We see their stock levels daily and ship to replenish without waiting for a PO.

Distribution & channel terms

If your Manufacturing Cloud project touches distributors, reps, or two-tier channels, these terms will dominate every conversation.

1. Channel inventory

Definition: Product sitting in distributor warehouses that has been sold to distributors but not yet sold to end customers. Different from finished goods inventory at the factory.

Salesforce Manufacturing Cloud context: Relevant to the sell-through vs. sell-in distinction. Manufacturing Cloud tracks sell-in (what distributors buy from the manufacturer) in Sales Agreements; tracking channel inventory requires additional distributor data integration.

Example: We have 8 weeks of channel inventory in North America. Until that burns down, distributors won't be placing new orders regardless of end demand.

2. Sell-in vs. Sell-through

Definition: Sell-in = what distributors buy from the manufacturer. Sell-through = what distributors sell to their customers. The gap between these numbers reflects channel inventory changes.

Salesforce Manufacturing Cloud context: Sales Agreements and Account Forecasts typically track sell-in (what the manufacturer invoices). Understanding sell-through requires POS data integration.

Example: Sell-in was strong last quarter, but POS data shows sell-through was flat. Channel inventory is building — that's a leading indicator of reduced orders next quarter.

3. POS (Point of Sale) Data

Definition: Data showing what a distributor actually sold to its customers in a given period. Sell-through data. Distinct from PO (purchase order) data, which shows what the distributor ordered from the manufacturer.

Salesforce Manufacturing Cloud context: POS data is distributor-provided and needs to flow into Manufacturing Cloud — either through portal submission or file upload. Often the most important input to the demand planning process.

Example: Our distributors provide weekly POS reports. It's the real demand signal. Their POs are a lagging indicator.

4. Stocking order

Definition: An order placed by a distributor to build inventory, not in response to specific end-customer demand. Stocking orders can distort demand signals if not distinguished from orders tied to real demand.

Salesforce Manufacturing Cloud context: Stocking order visibility requires data from distributors about order intent — typically not captured in standard data flows. Some companies add a custom field or process to flag stocking versus consumption-driven orders.

Example: That spike in July was a stocking order from our largest distributor. End demand didn't change — they were building buffer inventory ahead of fiscal year end.

5. Turns (Inventory turns)

Definition: How many times inventory is sold and replaced in a given period. Higher turns indicate efficient inventory management; lower turns indicate buildup.

Salesforce Manufacturing Cloud context: Not a native Manufacturing Cloud metric, but relevant to understanding distributor behavior and channel health. Distributors managing for turns may reduce orders even when end demand is stable.

Example: We target 8–10 turns annually for our distributors. Anyone below 6 is holding too much inventory and will reduce orders until it normalizes.

6. Distribution channel

Definition: The network of distributors, representatives, and resellers through which a manufacturer sells products. May be one-tier (manufacturer → distributor → end customer) or multi-tier.

Salesforce Manufacturing Cloud context: Channel structure determines Experience Cloud architecture — how many portal types are needed, what data each tier submits, and how forecasts roll up through the channel hierarchy.

Example: We sell 60% of our volume through two-tier distribution. The rep firm takes the order; the distributor stocks and ships.

Sales, revenue & customer terms

The vocabulary at the intersection of finance, sales, and operations.

1. Actuals

Definition: Real, confirmed revenue or volume that has been shipped and invoiced for a completed period. Actuals come from ERP systems, not Salesforce.

Salesforce Manufacturing Cloud context: Loaded into Account Forecast Period records (Actual Revenue, Actual Quantity fields) and Sales Agreement Product Schedule records. They are the denominator in every accuracy calculation.

Example: Our Q3 actuals came in at $2.1M against a forecast of $2.4M — a 12.5% miss.

2. Book-to-bill ratio

Definition: Orders received in a period (book) divided by product shipped in the same period (bill). A ratio above 1.0 means backlog is building; below 1.0 means it is burning down. Book-to-bill ratio is one of the most-watched leading indicators of demand health, especially in semiconductors and electronics.

Salesforce Manufacturing Cloud context: Not a native metric, but commonly tracked in custom reports or CRM Analytics. Requires both order data (often in ERP) and shipment data to calculate.

Example: Our book-to-bill was 1.18 last quarter — demand is running ahead of supply, which suggests upward pressure on pricing.

3. Net 30 / Net 60 / Net 90

Definition: Payment terms on invoices — the customer has 30, 60, or 90 days to pay after invoice date. Affects cash flow and revenue recognition timing.

Salesforce Manufacturing Cloud context: Payment terms are typically ERP data, not Salesforce data. Relevant when Manufacturing Cloud is being used to project revenue — the difference between shipped revenue and collected revenue is material for Finance.

Example: We extended Net 90 to our top distributor in APAC to match local market norms. That's a meaningful cash flow difference.

4. Design win

Definition: A manufacturer's product has been selected by an OEM or customer for use in their product design. Revenue does not flow until production ramps, often 6–18 months later.

Salesforce Manufacturing Cloud context: Tracked as Opportunities in Sales Cloud, often in a custom stage like "Design Win" or "Production Ramp." The future revenue should eventually flow into Account Forecast Period upside or committed values once ramp timing is clearer.

Example: We won the socket at DataTech for their next-gen router. Won't show up in actuals until Q2 next year, but it's $800K annually once it ramps.

5. Named account

Definition: A specific end customer account that receives special commercial treatment — dedicated rep coverage, custom pricing, or dedicated inventory. Distinct from distribution accounts.

Salesforce Manufacturing Cloud context: Named accounts typically have their own Sales Agreements and Account Forecasts. The distinction between named accounts and distribution accounts often drives the account hierarchy and sharing model.

Example: Our top 50 named accounts are direct relationships. Everything else runs through distribution. Named accounts get custom pricing and dedicated forecast treatment.

6. OEM (Original Equipment Manufacturer)

Definition: A company that manufactures products (or components) sold to another company for branding and sale under that company's name. In semiconductor contexts, OEMs design products that incorporate components from component manufacturers.

Salesforce Manufacturing Cloud context: OEMs are often the "end demand" signal — even if sales flow through distribution, the OEM's production schedule drives the demand. OEM accounts often warrant their own Account Forecast records even when they buy through distribution.

Example: Apple is the OEM. They design their own chips but buy memory from us. Their production forecast drives demand even though the PO goes through our distributor.

Product & operations terms

The product, calendar, and lifecycle vocabulary that shapes how Manufacturing Cloud is configured.

1. SKU (Stock Keeping Unit)

Definition: A unique identifier for a specific product in a specific configuration. A product family might have dozens of SKUs representing different specifications, package types, or configurations.

Salesforce Manufacturing Cloud context: Products in Sales Agreement Products typically map to Product2 records in Salesforce. The granularity of SKU-level vs. product-family-level tracking is a key configuration decision.

Example: We have 4,200 active SKUs but forecast at the product family level — 14 families. SKU-level forecasting isn't practical at our scale.

2. End-of-Life (EOL)

Definition: A product being discontinued. Manufacturers manage EOL programs to help customers transition to successor products and to clear remaining inventory.

Salesforce Manufacturing Cloud context: EOL products should be reflected in Sales Agreement Products and Account Forecast Periods with decreasing future period values and a clear transition plan to replacement SKUs.

Example: We announced EOL on the legacy module in March. Distributors have 12 months to place last-time-buy orders.

3. Fiscal week / Fiscal period

Definition: Manufacturers often operate on non-calendar fiscal periods — a "4-4-5" quarter structure (two four-week periods plus one five-week period) is common. Fiscal calendars rarely align with calendar months.

Salesforce Manufacturing Cloud context: Account Forecast Set configuration must reflect the company's actual fiscal calendar. Misalignment between the Salesforce period structure and the ERP/Finance fiscal calendar is a common and painful integration problem.

Example: Our fiscal Q1 ends January 28th, not January 31st. The 4-4-5 calendar means our periods never match the calendar month.

A note on terminology collisions

Several terms in this manufacturing glossary mean different things in Salesforce vs. manufacturing contexts:

Clarifying definitions early in any discovery process saves significant time. If you're walking into a manufacturing customer for the first time, assume your audience uses the manufacturing definition unless they explicitly tell you otherwise.

Frequently asked questions

What is book-to-bill ratio?

Book-to-bill ratio is the value of orders received (booked) in a given period divided by the value of product shipped (billed) in the same period. A book-to-bill ratio above 1.0 means a manufacturer is taking in orders faster than it can ship them — backlog is building. A ratio below 1.0 means shipments are outpacing new orders, and backlog is burning down. It's one of the most-cited leading indicators in semiconductors, electronics, and industrial manufacturing because it signals the direction of near-term demand before it shows up in revenue.

What is the difference between sell-in and sell-through?

Sell-in is what distributors buy from the manufacturer. Sell-through is what distributors sell to their end customers. The gap between the two reveals what is happening in channel inventory: rising sell-in with flat sell-through means distributors are stockpiling, while flat sell-in with rising sell-through means channel inventory is being depleted.

What is MAPE in manufacturing forecasting?

MAPE stands for Mean Absolute Percentage Error. It measures forecast accuracy by averaging the absolute percentage difference between forecasted and actual values across multiple periods. Lower MAPE = better forecast. Manufacturers typically target MAPE under 10–15% at the product family level, depending on industry volatility.

What is the difference between ERP and Salesforce Manufacturing Cloud?

ERP (e.g., SAP, Oracle, Microsoft Dynamics) is the back-office system of record for financial transactions, inventory, and production. Salesforce Manufacturing Cloud is the front-office system for managing customer relationships, sales agreements, and account forecasts. The two systems integrate — actuals flow from ERP into Manufacturing Cloud, and demand plans built in Manufacturing Cloud inform supply planning in ERP/MRP.

What is S&OP and where does Salesforce Manufacturing Cloud fit?

S&OP (Sales and Operations Planning) is the monthly executive process that reconciles demand, supply, and financial targets. Salesforce Manufacturing Cloud is designed to be the system of record for the demand review portion of S&OP — replacing the manually assembled Excel workbooks most companies still rely on with a single, structured view of forecasts across accounts, products, and periods.

What does "allocation" mean in manufacturing?

Allocation is the process of dividing constrained supply across multiple customers when demand exceeds available product. The manufacturer decides which accounts receive full quantity and which receive a reduced share. In Salesforce Manufacturing Cloud, allocation decisions are reflected in Account Forecast Period values but are not generated automatically by the system.

Closing thought

Manufacturing vocabulary isn't just jargon — it encodes how the business actually runs. Misusing a term in front of a supply chain leader signals you don't understand the operating model; using it correctly signals you do. Whether you're scoping a Salesforce Manufacturing Cloud implementation, sitting in on an S&OP demand review, or building product strategy, this manufacturing glossary should give you the working vocabulary to keep up.

Bookmark it, share it with your team, and treat it as a starting point — every manufacturer adds local terminology of their own.