For inventory
Connect the item, the supplier and the work around it.
Model items, suppliers and stock movements in an inventory app, then give each team a view suited to the work it handles.
| Company | Owner | Stage | Value |
|---|---|---|---|
| 1Northstar | SSam | In progress | €18,000 |
| 2Fieldwork | AAlex | In review | €24,500 |
| 3Orbit Studio | SSam | Won | €12,000 |
| 4Common Ground | AAlex | In progress | €32,000 |
Give the work a relational home
Start with connected tables. A shared name in two spreadsheets is not a relationship.
- Items
- Store the item reference, category and supplier relationship.
- Suppliers
- Link purchasing details to the supplier rather than repeating them per item.
- Movements
- Record item, quantity, location and date on each stock movement.
Decide who sees what, before the first screen
Groups grant access per table, row, field and action. Every surface follows those rules.
- Warehouse
- Grant reads and movement creation for the relevant operational records.
- Purchasing
- Grant access to suppliers and purchasing fields.
- Finance
- Make cost fields readable to finance without widening warehouse access.
Different jobs deserve different screens
The Data grid is the starting point. Interface ideas can be described to the assistant and built over the same authorized data.
- Item catalogue
- A grid grouped by category with related supplier information.
- Movement entry
- A focused interface for recording a movement.
- Purchasing overview
- An interface over the purchasing records its viewer may read.
Try this as your app brief
“Create Items, Suppliers and Movements. Warehouse users create movements but cannot edit unit costs. Purchasing manages supplier details. Review computed stock rules before using the app for reconciliation.”
This is an app design example, not a ready-made template. gtable is a work in progress and not open yet. Explore the product or other use cases.