Fence Material Reservations: Connect NetSuite Stock With a Supabase Fabrication and Installation Board

What this looks like in fencing fabrication and installation

A fencing company uses the same steel sections for several custom gates. The planning board shows enough gross stock for a new order, but much of it is reserved for jobs already released to fabrication. Offcuts may be usable only for certain components. A useful view shows approved allocations and the actual material requirements of the new job, then routes any request to move stock through the inventory and production owners.

Records, ownership, and update rules

Work through the process

1. 01
   Separate inventory and production states

   Define raw stock, reserved material, work in progress and installation-ready assemblies. A single available quantity cannot describe all four. Preserve the item and job relationships so planners can see whether the constraint is purchasing, fabrication capacity or physical staging.
2. 02
   Use approved material requirements

   Compare stock against the released bill of materials or equivalent job requirement. Keep material grade, section, finish and length attributes visible where they affect suitability. Do not let the board substitute a similar material simply because its generic description matches.
3. 03
   Design reservation as a confirmed action

   Let planners submit allocation or transfer requests with a stable identifier. The inventory owner or verified system action accepts or rejects them. Return the confirmed result to the board and distinguish pending requests from stock that is actually committed.
4. 04
   Constrain the application

   Authorize users for the branches, jobs and actions they need. Supabase row policies and grants are separate from sync configuration. Keep integration credentials server-side and test a user who may view planning context but may not approve material movement.
5. 05
   Reconcile consumption and staging

   Connect reported fabrication usage and completed assemblies to the approved inventory process. Verify the exact NetSuite operations before enabling writes. Handle delayed reports and corrections with source references so the board does not consume the same material twice or declare an assembly staged before logistics confirms it.
6. 06
   Keep production progress from changing inventory silently

   A fabricator marking a task started may not have consumed the whole material allocation, and marking it complete may still leave unused material. Define how actual usage and returns are recorded through the inventory process. The board can show reported progress while the accepted inventory result remains a separate state. This distinction gives the production manager visibility without turning an approximate shop update into an unreviewed stock adjustment.

Handle the exceptions explicitly

Usable offcut has no verified dimensions

Keep it outside the available planning quantity until production confirms suitability.

Two jobs request the same stock

Use the owning reservation process to decide priority and return explicit accepted or rejected states.

Fabrication is complete but not staged

Show production completion separately from installation availability.

What to verify before expanding

• Gross stock and confirmed job allocation are distinct.
• A board edit cannot silently create an unsupported inventory action.
• Repeated requests cannot double reserve material.
• Installation availability requires verified staging evidence.

Technical references

• Stacksync NetSuite connector and object support
• Stacksync Supabase connection setup
• Supabase row level security