Open core: don’t reinvent the wheel — build your fenestration software on ours.

Developers start here →
Sign in
Skip to main content

How Can We Help?

Stock is kept in a four-level tree: Warehouse → Location → Rack
→ Bin. The tree is maintained in Inventory Management → Stock Management
(the Stock Management dashboard) → Stock Management → Warehouses. The
flags on each warehouse tell OpenJanela which warehouse to use for stock, receiving and
shipping.

What, where, who, when, why

What The physical stock tree: Warehouse → Location → Rack
→ Bin, one row each, plus the flags that mark which warehouse plays which system role
(Main Stock, Ship Area, Receiving, Scrap…).
Where Inventory Management → Stock Management → Stock
Management → Warehouses — four editable panes, one per tree level. Which branch
uses which warehouse is set on the branch, not here.
Who Whoever sets up inventory. Operators never edit the tree; they pick
from it in stock transactions, requisitions, receiving and shipping.
When At go-live before the first stock transaction; when a plant adds a
building, dock or rack row; when a role flag must move (e.g. receiving moves to a new
building).
Why it matters The flags are load-bearing: stock lists, requisition
defaults, production allocation, receiving defaults, QC/Packing and finished-goods put-away all
resolve to “the first warehouse flagged X”. No flag, no default — the
feature that needs it fails.
Can’t find the Warehouses button?
It belongs to the newer inventory screens, which your administrator switches on in Company
Preferences (the setting Screens using the new interface must include 4, inventory).

The four panes

Each pane is an editable table with New, Edit, Delete, Copy, Export, Import, Save and
Cancel. While one pane is being edited the others are locked. Export writes a CSV file using the
company CSV delimiter; Import reads the same layout — rows whose id already exists update
that record, others are created.

Pane Columns
Warehouses Warehouse (name), Main Stock, Satelite Stock, Ship Area, Receiving, Building No., Returns, Scrap, Offsite.
Locations Warehouse, Location. A new location starts on the first warehouse; pick the right one.
Racks Location, Rack.
Bins Warehouse, Location, Rack, Bin, Capacity, Parent Bin, Next Bin, Next Rack, Next Location, Next Warehouse.

What each warehouse flag does

Flag Effect found in the current version
Main Stock The stock warehouses. They fill the warehouse lists of Stock Transactions, Stock Requisitions, Stock View and Cycle Count; a new part requisition goes to the first one; stock allocation for production checks only these; Qty On Order counts only PO lines for them. Production capacity scheduling uses the first one as the default stock warehouse.
Satelite Stock Included, with Main Stock warehouses, in the warehouse list sent to the Android mobile app. No other effect found.
Ship Area The shipping warehouses. They fill the warehouse lists on shipping acknowledgement and manifests, the QC monitor and Packing (which defaults to the first one). When a batch is released or items are recorded as shipped, the first Ship Area warehouse that is not Scrap receives the finished goods.
Receiving The first Receiving warehouse is the default for goods received from a supplier when the requisition has no warehouse, for the requisitions that scheduling creates for non-stock parts, and for imported Cardinal glass receipts (refused if none exists).
Scrap Excludes a Ship Area warehouse from the automatic shipping-warehouse choice above.
Building No., Returns, Offsite Stored on the warehouse; no screen or calculation that uses them was found in the current version.
Keep these three warehouses
Keep at least one Main Stock, one Receiving and one Ship Area (not Scrap)
warehouse, each with at least one location, rack and bin. Scheduling an order, batch release,
shipping and receiving pick “the first” warehouse of each kind and fail when there is
none. Order matters:
the first one created is the one used.

Bins

  • Capacity — how much the bin holds (a whole number).
  • Parent Bin — another bin this bin sits inside.
  • Next Bin / Next Rack / Next Location / Next Warehouse — the bin to fill
    after this one.

These bin values are stored only; no put-away or picking logic that reads them was found in
the current version.

Known issue — editing bins, locations and racks
In the current version Edit on the Bins pane does not save any change (the record is
written back unchanged), and Edit on Locations and Racks saves only the name, not a move to
another warehouse or location. To change a bin, delete it and create it again; to move a
location or rack, create a new one.

Worked example — one small plant

Step Value Why
Warehouse 1 “Main Plant”, flags: Main Stock + Receiving Created first, so it is “the first” Main Stock warehouse (stock lists,
production allocation) and the first Receiving warehouse (goods-receipt default).
Warehouse 2 “Dock”, flags: Ship Area Finished goods
land here when a batch is released or items are shipped. Do not flag it Main Stock, or it
joins the stock warehouse lists too.
Locations Main Plant → “Aisle A”; Dock → “Floor” Every warehouse needs at least one location, or deleting/receiving logic has nowhere to
point. New locations start on the first warehouse — re-pick the right one.
Racks & bins Aisle A → rack “A1” → bin “A1-01”,
Capacity 200		 Stock records are received into a bin; capacity and Next-bin fields are
stored for the future but not enforced.

Delete rules

  • A warehouse with locations, a location with racks, or a rack with bins cannot be
    deleted (There are locations related to the warehouse, There are racks related to the
    location    , There are bins related to the rack).
  • A bin cannot be deleted while it holds stock records, stock receipts, or shipped items
    or assemblies.

Which branch uses which warehouse is set on the branch, not here — see
Branches.

Posted
Updated
Bywebmanager