These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Kanban Replenishment
- Data model
The tables behind SCM with Kanban Replenishment
SCM with Kanban Replenishment 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, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and identity
Organizations, Customers, team members and Users establish accounts and staff context.
Demand
Customer orders and order lines hold customer commitments and quantity progress.
Pull requests
Replenishment signals records bin-triggered demand under an order.
Evidence
Fulfillment events, payment evidence, operation receipts, review decisions and record attachments retain dated outcomes and explanations.
Catalog
Products identifies stocked items and base units.
Every table, by feature
- Customer orders6
- Order lines5
- Replenishment signals5
- Review and decisions6
- Fulfillment and payments6
- Operations overview6
- Shared and settings1
- Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Customers
Customer accounts eligible for kanban replenishment orders.
Linked to Organizations - Organizations
Organizations that buy, hold and receive replenished stock, with contact and relationship status.
- Order lines
Order lines under a customer order, carrying planned effort, owner and progress rollups.
Linked to Customer orders - Replenishment signals
Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Linked to Customer orders, Organizations - Operation receipts
Receipts for every operational action taken in the app, with result state and actor.
Linked to Customer orders
- Order lines
Order lines under a customer order, carrying planned effort, owner and progress rollups.
Linked to Customer orders - Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Products
Stocked products and their standard USD prices.
- Fulfillment events
Dated fulfillment events promised against a customer order, with outcome status and owner.
Linked to Customer orders, Products - Replenishment signals
Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Linked to Customer orders, Organizations
- Replenishment signals
Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Linked to Customer orders, Organizations - Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Organizations
Organizations that buy, hold and receive replenished stock, with contact and relationship status.
- Operation receipts
Receipts for every operational action taken in the app, with result state and actor.
Linked to Customer orders - Review decisions
Recorded review decisions on orders, order lines, signals and fulfillment events.
Linked to Customer orders, Team members
- Review decisions
Recorded review decisions on orders, order lines, signals and fulfillment events.
Linked to Customer orders, Team members - Replenishment signals
Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Linked to Customer orders, Organizations - Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Order lines
Order lines under a customer order, carrying planned effort, owner and progress rollups.
Linked to Customer orders - Operation receipts
Receipts for every operational action taken in the app, with result state and actor.
Linked to Customer orders - Team members
Replenishment staff with capacity, role and the orders, signals and runs they own.
Linked to Organizations, Users
- Fulfillment events
Dated fulfillment events promised against a customer order, with outcome status and owner.
Linked to Customer orders, Products - Payment evidence
Verified provider payment events for customer orders.
Linked to Customer orders - Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Order lines
Order lines under a customer order, carrying planned effort, owner and progress rollups.
Linked to Customer orders - Products
Stocked products and their standard USD prices.
- Record attachments
Files attached as evidence to orders, lines, signals, events, exceptions and decisions.
Linked to Customer orders, Team members
- Customer orders
Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
Linked to Organizations, Team members, Customers - Order lines
Order lines under a customer order, carrying planned effort, owner and progress rollups.
Linked to Customer orders - Replenishment signals
Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Linked to Customer orders, Organizations - Operation receipts
Receipts for every operational action taken in the app, with result state and actor.
Linked to Customer orders - Review decisions
Recorded review decisions on orders, order lines, signals and fulfillment events.
Linked to Customer orders, Team members - Team members
Replenishment staff with capacity, role and the orders, signals and runs they own.
Linked to Organizations, Users
Keys and references
Customer orders is the parent of lines, signals, events, receipts, decisions, payment evidence and attachments. It references one organization, customer and owner. A signal also references an organization. Fulfillment events reference Products. Team members links staff to Organizations and Users; reviewers and uploaders reference team members. Keep record numbers, signal identifiers, operation keys, provider event identifiers and external event identifiers stable through imports and reconciliation.
Migration order
- Import Organizations and Users, then connect team members to their organizations and users.
- Import Customers and Products, checking active state, codes, SKU and base unit.
- Import customer orders with customer, organization and owner references.
- Import order lines and replenishment signals against their parent orders.
- Import dated fulfillment events, payment evidence, operation receipts, review decisions and record attachments with their parent references intact.
- Reconcile order totals, line quantities, signal status and event identifiers before opening the pilot queue.
Set up SCM with Kanban Replenishment your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.