Warehouse Management in Jules

Product documentation — How Jules models warehouse operations, from inbound reception through stockpile management to outbound dispatch, and how warehouse-specific settings control the flow.

---

Table of Contents

1. Overview
2. Warehouse as a Special Operation Mode
3. Inbound Flow
4. Outbound Flow
5. Inventory Tracking & Stockpiles
6. Yard Reception — Local Market
7. Recycling Processing
8. Recurring vs Spot Purchases
9. Logistic Costs for Warehouse Operations
10. Warehouse Settings
11. Key Business Rules
12. Glossary

---

Overview

The Warehouse module in Jules manages the full physical lifecycle of materials at a warehouse site: purchasing goods into stock (inbound), tracking what is available (inventory), and dispatching goods to customers or export (outbound).

A warehouse is a Site of type WAREHOUSE. It acts as the physical location that holds material between a purchase and a subsequent sale. Most of the warehouse workflow is driven through standard operations and containers, but with a distinct inbound approval gate and stockpile assignment step that do not exist in direct trading flows.

---

Warehouse as a Special Operation Mode

In Jules, a warehouse operation is still a standard operation (purchase or sale) — the difference lies in the flow: instead of goods going directly from supplier to customer, they pass through an intermediate warehouse site.

An operation is a warehouse operation when its destination or source is a warehouse site. This changes how margins are calculated (buy cost is separated from sell revenue across two distinct operations) and enables stockpile assignment on each container.

Site type WAREHOUSE

A site must be of type WAREHOUSE to appear in the warehouse module. Warehouse sites carry additional configuration fields compared to regular sites:

---

Inbound Flow

An inbound represents a container or truck load of material arriving at a warehouse site. The inbound flow covers three stages: container creation, reception recording, and stockpile assignment.

1. Purchase operation

The inbound starts with a BUY operation whose destination site is the warehouse. This operation defines the material (quality), contracted quantity, price, and supplier.

2. Container arrival and reception

When goods arrive, a reception is recorded on the container. The Reception entity captures:

A reception is linked to the purchase operation and optionally to a specific allocation.

3. Inbound approval workflow

Before goods are formally accepted into inventory, the inbound can be subject to an approval gate. Each container carries an inbound status:

From the Warehouse Inbounds page, authorized users can:

• Approve — goods enter inventory
• Reject — inbound is flagged as cancelled
• Cancel — container is removed from the inbound queue

Approvals and rejections can be performed in batch for multiple containers at once.

4. Weighing and quality data

Each container in the inbound carries weight data:

CargoSnap integration: For containers with a reference number, Jules can pull photographic and weight data from CargoSnap automatically using the container reference number. This returns container images, sealed number, VGM, and tare/net/gross weights automatically, reducing manual data entry.

5. Stockpile assignment

Once approved, each container or delivery is assigned to a stockpile at the warehouse:

• The stockpile assignment on a delivery links the goods to a specific stockpile.
• The delivery type (MATERIAL or ITEM) indicates whether the stock is tracked by weight or by individual items.
• Stock records are created, recording quantity, quality, conditioning, and stockpile assignment.

---

Outbound Flow

An outbound is the dispatch of material from a warehouse stockpile to a customer. It is modelled as a SELL operation whose source is the warehouse.

Stock picking

When creating the outbound, the system picks stock from the stockpile using the configured stock picking rule:

The picking rule can be set at three levels (from most to least specific): stockpile level overrides quality level, which overrides warehouse level.

The system supports limit-based picking: given a target quantity and a picking rule, it returns the deliveries to pick in the correct order. Multiple stockpile limits can be specified simultaneously.

Loading and dispatch

Once stock is picked, the container is loaded:

• Loading and delivery records track the quantities and qualities at each stage.
• The outbound quantity on a delivery tracks how much of that delivery was consumed for the outbound.
• The container is linked to the outbound sale operation.

Warehouse Journey Tracking

Containers passing through a warehouse have a specific status tracking their warehouse journey:

---

Inventory Tracking & Stockpiles

Stockpiles

A stockpile is a named physical location within a warehouse where materials are stored. Each stockpile belongs to one warehouse site and can hold one or more material qualities.

Stockpile statuses

Stockpile KPIs

Jules provides aggregate inventory KPIs for a set of stockpiles:

Each KPI includes both a quantity figure and a container count, combining both tonnes and container counts, giving a dual tonnes / containers view.

Inventory view

The Warehouse Inventory page shows all current stock across warehouses and stockpiles. Filters include:

• Filters by warehouse, quality, status
• Stockpile status
• Location
• Show available stock only

Stock entries (Deliveries)

Individual stock entries are modelled as deliveries at the warehouse level. Key fields on a stock entry:

Deviation tracking

Deliveries can carry a deviationType to record quality or quantity anomalies:

---

Yard Reception — Local Market

Recycling yards

A recycling yard is a named pick-up point in the local collection network. Yards are referenced on deliveries and on MQC (Minimum Quality Commitment) calculations to contextualise where material was collected.

Recycling yards appear as a filterable dimension on the MQC suggestion query, which suggests a baseline MQC based on historical deliveries at a given site and yard combination.

CargoSnap integration

For local market receptions (truck loads, walk-in material), Jules integrates with CargoSnap — a container and load inspection platform. Jules connects to CargoSnap using the container reference to retrieve:

This integration reduces manual entry errors and provides photographic proof of load condition at the point of reception.

Assay status

For materials requiring laboratory analysis (metals, plastics with specific purity grades), Jules tracks an assay status per container. The organization configures the list of available assay statuses (e.g., "Pending analysis", "Certified", "Rejected").

The assay status and the assay report value (reportAmount) are stored on the container and can be filtered from the Warehouse Inbounds view.

---

Recycling Processing

The RECYCLING page mode is used for organizations that operate recycling yards as part of their supply chain. In this context:

• The site type is RECYCLING_YARD — a specialized supplier site that delivers material to a warehouse or processor.
• The defaultRecyclingYard field on a site defines the yard associated with that supplier.
• Quality definitions carry recycling-specific thresholds:

These thresholds allow Jules to flag deliveries where the recovery rate falls outside the acceptable range for a recycled quality, supporting quality control at the intake stage.

Contracts in the recycling flow use recurring or spot contract types (see Recurring vs Spot Purchases).

---

Recurring vs Spot Purchases

The warehouse module distinguishes two types of purchase flows, each with its own UI page and permission role:

This distinction mirrors the broader recurring / spot split in offer types, applied across warehouse management contracts.

How contracts drive the warehouse purchase flow

A WM contract (waste management contract) prefills key fields on a warehouse purchase operation:

• Supplier and site
• Quality and pricing terms
• Logistic defaults (logistic material, area, forwarder)

The contract provides the standing commercial terms; each individual purchase event is an operation child of that contract, allowing Jules to track total volumes received against the contract.

---

Logistic Costs for Warehouse Operations

Estimated Logistic Costs

A pre-agreed cost per site-to-destination route enables Jules to pre-populate logistic cost estimates on warehouse operations:

These costs serve as a baseline for margin calculations. Multiple cost estimates can be created or updated in batch.

Pre-carriage rates

For local transport legs between the pick-up point and the warehouse (or between the warehouse and the port), pre-carriage rates define the logistics cost structure:

Pre-carriage rates can be validated or invalidated in batch. An invalid rate is flagged as expired and excluded from automatic cost suggestions.

Local Logistic Rates

For end-to-end domestic deliveries (warehouse to customer without international shipping), local logistic rates provide rates with a similar structure to pre-carriage but with an explicit destinationArea:

Like pre-carriage rates, local logistic rates support batch validation/invalidation and rate validity windowing.

---

Warehouse Settings

The Warehouse Settings page is the administration area for managing warehouse sites and their configuration.

Warehouse list

The Warehouse Settings page displays all warehouse sites with search and create/edit/delete actions.

Warehouse detail tabs

Each warehouse has a warehouse detail page with three tabs:

Preference settings

Licenses

Warehouse sites can carry site licenses, governing which materials the site is authorized to handle:

Licenses are visible on both the warehouse site detail and on supplier sites, ensuring that collection and processing authorizations are tracked end-to-end.

---

Key Business Rules

1. Warehouse operations use stockpile-based margin calculation

For warehouse operations, the buy and sell sides of a trade are costed separately. The purchase cost is captured at reception time (including pre-carriage and estimated logistic costs); the sale margin is computed at dispatch time. This differs from direct trading where buy and sell are matched at allocation time.

2. Stock picking order is enforced

The FIFO / LIFO rule is applied consistently: when picking stock for outbound, Jules always returns deliveries in the correct age order, respecting the most specific rule set (stockpile > quality > warehouse default).

3. Negative stock requires explicit authorization

By default, Jules prevents dispatching more than the available quantity in a stockpile. This guard can be disabled per warehouse for workflows where goods are recorded retroactively.

4. Inbound approval is a hard gate

Containers with pending inbound status cannot be considered available inventory until explicitly approved. Approvals can be performed individually or in batch, but cannot be bypassed.

5. Stockpile assignment may be mandatory

If stockpile assignment is required, every container in an inbound must be assigned to a named stockpile. Containers without a stockpile assignment are incomplete and will not appear in available inventory.

6. License quotas are tracked per site

If a warehouse holds a license with a quota, Jules tracks cumulative received quantities against that quota. Exceeding the quota requires a license update before further receptions can be processed.

7. Pre-carriage and local logistic rate validity is time-windowed

Rates outside their validity window are automatically flagged as invalid and excluded from cost suggestions. Rates should be reviewed and renewed before expiry.

8. CargoSnap data is read-only in Jules

Jules only reads data from CargoSnap via the reference number — it does not push data back. The integration is one-directional and requires the container reference to match exactly.

---

Glossary