What Is Point-in-Time Netting in Inventory? EDGEBIC Definition

Point-in-time netting in inventory is netting a demand against the current static on-hand quantity only, without considering any future receipts that will arrive during the same planning run. It is the shelf-right-now view: when the engine checks a job's demand, it satisfies as much as it can from what is physically on hand now and ignores builds that would complete later. It is the simpler, more conservative of the netting modes the engine supports.

This entry is part of the EDGEBIC by User Solutions glossary series; for the wider vocabulary of planning, see the manufacturing glossary. Point-in-time netting is the baseline; its counterpart, forward netting, extends the idea by projecting supply through time.

How Point-in-Time Netting Works

Netting is the act of subtracting available supply from demand to find what actually has to be built or bought. Point-in-time netting answers that question with the narrowest, most literal notion of supply: the quantity sitting on the shelf at this moment. Nothing else counts.

That deliberate narrowness is the whole character of the mode. It does not look ahead at builds that are in progress and due to complete during the run, and it does not credit deliveries expected later. Each demand is measured against a single snapshot of on-hand stock, and whatever the snapshot cannot cover becomes a net requirement that the engine plans production for.

The advantage is conservatism. Because the plan only commits against stock that physically exists today, it never promises against supply that has not actually landed. The trade-off is that the plan can suggest a build for a demand that a later, in-progress receipt would have covered, because point-in-time netting cannot see that later receipt. When a planner wants the plan to take credit for in-run supply, forward netting is the mode that does so.

A Concrete Example

Imagine the finished-goods shelf holds 100 units of a product this morning, and a build already running will add 50 more by Wednesday. Two demands come through the run: one needs 80 units now, another needs 60 units on Thursday.

Under point-in-time netting, the engine looks only at the current 100 on hand. The first demand takes 80, leaving 20. The second demand needs 60 but sees only that 20 remaining, so it nets a shortfall of 40 and the engine plans new production for those 40, even though Wednesday's build will have delivered 50 more by the time Thursday's demand is due. Point-in-time netting simply never considered that Wednesday receipt.

Switch to forward netting and the picture changes: the 50 units completing Wednesday become time-phased supply, available to Thursday's demand, so the shortfall shrinks or disappears. That contrast is the clearest way to feel what point-in-time netting does by leaving future receipts out.

How EDGEBIC Uses It

Point-in-time netting is the baseline behavior of the inventory and scheduling netting path.

• The netting check compares each demand against the current on-hand quantity, satisfying what it can and turning the rest into a net requirement.
• In-run receipts are ignored under this mode, so builds completing later in the same run do not count as supply for demands checked earlier.
• It is the conservative default, committing only against stock that physically exists now, with forward netting available when a planner wants time-phased supply included.

When on-hand stock does cover a demand, the engine can satisfy it directly rather than scheduling production, which is consume-from-stock netting. To see how netted balances are carried forward bucket by bucket across the horizon, read projected available balance.