1. SCM with Barcode/RFID
  2. Data model
Reference

The tables behind SCM with Barcode/RFID

SCM with Barcode/RFID ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
13
Features
6
Change it
Add fields and tables in Proto

How the model is organised

Organization and people:

Organizations, team members and Users define the site and the people responsible for actions.

Stock identity:

Stock items, stock lots and storage locations identify material, batch state and physical address.

Operations:

Stock requests anchors scan events, stock reservations and stock movements.

Review and evidence:

Review decisions, record attachments and operation receipts record decisions, support and outcomes.

Every table, by feature

Stock requests

10 tablesAbout this feature
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Stock items

    Defines a product or material teams stock and track across locations and lots.

    Linked to Organizations
  • Storage locations

    Represents a physical place where stock is kept, so teams know where items are stored.

    Linked to Organizations
  • Team members

    Represents a person working within an organization, used to assign roles and track activity.

    Linked to Organizations, Users
  • Record attachments

    Stores a file linked to another record, like a photo or document teams attach as proof.

    Linked to Stock requests, Team members
  • Review decisions

    Captures a reviewer's approval or rejection of a change, giving teams an audit trail of sign-offs.

    Linked to Stock requests, Team members
  • Scan events

    Records a barcode or RFID scan, letting teams confirm what was physically read and when.

    Linked to Stock requests, Organizations
  • Stock reservations

    Holds inventory set aside for a specific request so staff know what's already spoken for.

    Linked to Stock requests, Stock items, Storage locations, Stock lots
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Operation receipts

    Logs the outcome of an action taken on a record, so teams can confirm it actually went through.

    Linked to Stock requests

Scans and identification

7 tablesAbout this feature
  • Scan events

    Records a barcode or RFID scan, letting teams confirm what was physically read and when.

    Linked to Stock requests, Organizations
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Organizations

    Represents a company or site using the system, letting teams keep separate operations apart.

  • Stock items

    Defines a product or material teams stock and track across locations and lots.

    Linked to Organizations
  • Stock lots

    Tracks a batch of stock sharing an expiry and origin, letting teams follow it through storage.

    Linked to Stock items
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Operation receipts

    Logs the outcome of an action taken on a record, so teams can confirm it actually went through.

    Linked to Stock requests

Items, lots and locations

8 tablesAbout this feature
  • Organizations

    Represents a company or site using the system, letting teams keep separate operations apart.

  • Stock items

    Defines a product or material teams stock and track across locations and lots.

    Linked to Organizations
  • Stock lots

    Tracks a batch of stock sharing an expiry and origin, letting teams follow it through storage.

    Linked to Stock items
  • Storage locations

    Represents a physical place where stock is kept, so teams know where items are stored.

    Linked to Organizations
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Stock reservations

    Holds inventory set aside for a specific request so staff know what's already spoken for.

    Linked to Stock requests, Stock items, Storage locations, Stock lots
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Team members

    Represents a person working within an organization, used to assign roles and track activity.

    Linked to Organizations, Users

Reservations and movements

8 tablesAbout this feature
  • Stock reservations

    Holds inventory set aside for a specific request so staff know what's already spoken for.

    Linked to Stock requests, Stock items, Storage locations, Stock lots
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Stock items

    Defines a product or material teams stock and track across locations and lots.

    Linked to Organizations
  • Stock lots

    Tracks a batch of stock sharing an expiry and origin, letting teams follow it through storage.

    Linked to Stock items
  • Storage locations

    Represents a physical place where stock is kept, so teams know where items are stored.

    Linked to Organizations
  • Scan events

    Records a barcode or RFID scan, letting teams confirm what was physically read and when.

    Linked to Stock requests, Organizations
  • Review decisions

    Captures a reviewer's approval or rejection of a change, giving teams an audit trail of sign-offs.

    Linked to Stock requests, Team members

Review and evidence

6 tablesAbout this feature
  • Review decisions

    Captures a reviewer's approval or rejection of a change, giving teams an audit trail of sign-offs.

    Linked to Stock requests, Team members
  • Record attachments

    Stores a file linked to another record, like a photo or document teams attach as proof.

    Linked to Stock requests, Team members
  • Operation receipts

    Logs the outcome of an action taken on a record, so teams can confirm it actually went through.

    Linked to Stock requests
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Team members

    Represents a person working within an organization, used to assign roles and track activity.

    Linked to Organizations, Users

Organization and oversight

10 tablesAbout this feature
  • Organizations

    Represents a company or site using the system, letting teams keep separate operations apart.

  • Team members

    Represents a person working within an organization, used to assign roles and track activity.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Stock items

    Defines a product or material teams stock and track across locations and lots.

    Linked to Organizations
  • Storage locations

    Represents a physical place where stock is kept, so teams know where items are stored.

    Linked to Organizations
  • Stock requests

    Represents a request for stock that teams create, approve, and fulfill from start to finish.

    Linked to Organizations, Team members, Storage locations, Stock items
  • Stock reservations

    Holds inventory set aside for a specific request so staff know what's already spoken for.

    Linked to Stock requests, Stock items, Storage locations, Stock lots
  • Stock movements

    Logs a change in stock quantity, giving teams a running history of what moved and when.

    Linked to Stock requests, Stock items, Storage locations, Stock movements
  • Review decisions

    Captures a reviewer's approval or rejection of a change, giving teams an audit trail of sign-offs.

    Linked to Stock requests, Team members
  • Operation receipts

    Logs the outcome of an action taken on a record, so teams can confirm it actually went through.

    Linked to Stock requests

Keys and references

A stock requests record points to its organization, owner, item and locations. Scan events, review decisions, record attachments, operation receipts and stock movements point back to that request through Parent. Stock reservations uses Request for the same connection. Stock movements can point to another movement through Reverses, retaining the correction chain. Team members connects a person to a Users record; the reviewer and uploader references point to team members. Review the exact columns and select values below before migrating data.

Migration order

  1. Load Organizations and Users, then team members with their organization and user references.
  2. Load storage locations and stock items for each organization, then stock lots for their items.
  3. Load stock requests with valid owner, item and location references.
  4. Load record attachments and review decisions against the related requests and team members.
  5. Load scan events, stock reservations, stock movements and operation receipts, preserving their request links and original effect identities.
  6. Compare posted movement totals and active reservations against the source stock position before operating from migrated records.

Set up SCM with Barcode/RFID your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started