Receive inbound stone
Turn expected inbound goods into controlled physical inventory.
Exact buttons and available actions can vary with company plan, role permissions and enabled capabilities. Stoneware workflow rules and server-side checks remain authoritative.
Before you begin
Confirm the purchase order and inbound shipment are the records you expect to receive against. Verify the relevant container where container-level receiving is used.
Confirm the destination warehouse and location are valid for the company. Make sure the receiving employee has the receiving permission required by the current environment.
1. Confirm expected inbound stock
Review shipment items before receiving. Expected quantity and purchase-order/lot context should match what the warehouse physically sees.
Do not repair a mismatch by silently changing master data; receiving differences belong in the receiving-exception workflow.
2. Start the receipt
Use the controlled shipment receiving action. The verified operational contract accepts container_id, warehouse_id, location_id, received_date, notes and items.
The workflow should keep the shipment, receipt, receipt items and resulting physical inventory connected for traceability.
3. Identify the physical pieces
Capture the physical slab/item identifiers required by the receiving workflow and place received stock into the correct warehouse/location.
After creation, verify the individual slab records rather than assuming that shipment completion alone proves inventory was created correctly.
4. Resolve exceptions
If quantity, identity, condition or expected-vs-received details do not match, retain the discrepancy as a receiving exception and resolve it through the controlled resolution action.
This preserves evidence of what arrived and how the difference was handled.
5. Complete inbound costing
Where landed cost is in use, received slabs can remain on hold until the current landed-cost policy releases them. Cost components and allocation are permission controlled.
Do not expose cost values to users or API credentials that do not have the relevant cost authority.
After receiving
Check that the shipment/receipt history, slab identities, warehouse/location, exceptions and landed-cost state all agree.
Continue to inventory availability only when the resulting stock is in a workflow state that permits downstream reservation or sale.