Step-by-step instructions
Products, ingredients, supplies, write-offs, and production areas know where stock is stored and consumed.
Use the interactive screenshot walkthrough first. Switch steps with the step dots, then read what to fill and why it matters.
Fields on this screen
Storages list
How to fill: Start from the list and check existing rows before adding a new storage.
Why: Duplicate warehouses make supplies, write-offs, and stock balances hard to trust.
Add
How to fill: Click Add only when you need a new physical storage location.
Why: The app creates a draft storage row with a list number and default location context.
Storage name
How to fill: Use a clear operational name such as Main Warehouse, Kitchen Stock, Bar Stock, or Dry Storage.
Why: Staff need to choose the correct stock location when receiving supplies or checking leftovers.
Name translations
How to fill: Expand the name field and fill every enabled company language.
Why: Multilingual interfaces, reports, imports, and AI explanations depend on readable storage names.
Storage address
How to fill: Search or enter the real warehouse, receiving, or back-room address.
Why: This separates branch address, customer-facing address, and physical storage address.
Address details
How to fill: Verify address line, apartment or entrance, city, state, postal code, and country before saving.
Why: Transfers, receiving, support, and audit checks depend on precise address data.
In location
How to fill: Confirm the establishment that owns or uses this storage.
Why: Stock must not be consumed from the wrong branch or production location.
Save
How to fill: Save only after the names, address, and location are checked.
Why: Unsaved storage cannot be reliably connected to products, supplies, write-offs, transfers, or workshops.
Saved row
How to fill: Return to the Storages list and verify name, number, address, and location.
Why: The saved row confirms the warehouse is ready for later stock setup.
Common mistakes
- Editing quantity manually without creating a supply, transfer, or write-off record.
- Using product price as inventory cost.
- Mixing units, for example entering grams into a kilogram field.
- Forgetting to assign stock to the correct storage location.
AI Agent Field Reference for implementation
This block is intentionally below the human instructions. It explains storage names and downstream dependencies for automation, support, and future AI agents.
| Field | Stored as | Purpose | Why it matters |
|---|---|---|---|
| Storage ID | storage.id | Unique storage or warehouse identifier. | Products, supplies, write-offs, transfers, and workshops need a stable storage reference. |
| List number | storage.number | Visible order number in the Storages list. | Managers use it to distinguish storage rows and audit the order in which they were created. |
| Storage name translations | storage.name | Multilingual storage name stored as language/text objects. | Staff, reports, imports, and AI explanations need the correct name in each enabled language. |
| Storage address | storage.address | Physical address object for the warehouse or storage entrance. | Delivery, receiving, transfers, support, and audit explanations need to know where stock is stored. |
| Establishment link | storage.establishments | The establishment or location connected to this storage. | Keeps stock from different branches separated and prevents products or workshops from consuming the wrong warehouse. |
| Company | storage.company | Company workspace that owns the storage row. | Prevents warehouses from different companies from appearing in the wrong inventory workflow. |
| Created at | storage.created_at | Timestamp when the storage row was created. | Useful for audit history and setup troubleshooting. |
| Updated at | storage.updated_at | Timestamp when the storage row was last changed. | Agents can use it to explain whether warehouse setup data is fresh. |
| Product ID | stock.productId / products.id | Product or ingredient connected to stock. | Links inventory to catalog, orders, technical cards, and cost reports. |
| Quantity | stock.quantity | Current amount in storage. | Primary value for availability, write-offs, purchasing, and low-stock alerts. |
| Unit | stock.unit | Measurement unit such as pcs, kg, liter, or portion. | Agents must use units when explaining stock; raw numbers are not enough. |
| Cost | stock.cost / supply.cost | Purchase or weighted cost. | Used for cost of goods, margin, and profitability reports. |
| Supplier | supplies.supplier | Vendor or source of inventory. | Supports procurement, supplier history, and issue tracking. |
| Supply ID | supplies.id | Unique supply document. | Connects received items, invoice data, stock changes, and audit trail. |
| Transfer from | transfer.fromStorage | Source storage in a transfer. | Prevents agents from treating transfer movement as new supply. |
| Transfer to | transfer.toStorage | Destination storage in a transfer. | Explains why one location decreased and another increased. |
| Write-off reason | writeOff.reason | Reason for stock removal. | Required for waste, damage, expiration, and audit explanations. |
| Batch | stock.batch | Batch, lot, or receipt group. | Important for traceability, expiration, and recalls. |
| Expiration date | stock.expirationDate | Date when item expires. | Supports FIFO, safety checks, and stock recommendations. |
| Minimum stock | stock.minQuantity | Threshold for reorder alert. | Agents can recommend purchasing when quantity falls below this value. |
| Inventory consumed | orders.spentStore | Stock used by an order. | Connects sales to actual warehouse movement and cost calculation. |
| Spent image | orders.spentImage | Visual proof or attached image for consumed stock. | Useful when a workflow requires visual confirmation. |
| Updated at | stock.updatedAt | Last stock update timestamp. | Agents should mention freshness when answering stock questions. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.