1. E-commerce Fulfillment SCM
  2. Data model
Reference

The tables behind E-commerce Fulfillment SCM

E-commerce Fulfillment SCM 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

Every table, by feature

Orders and customers

4 tablesAbout this feature
  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Customers

    Ordering parties served by the operation

    Linked to Organizations
  • Organizations

    Fulfillment operating entities

  • Team members

    People with an authorized fulfillment role

    Linked to Organizations, Users

Order lines and products

4 tablesAbout this feature
  • Order lines

    Ordered, allocated and shipped quantities per SKU

    Linked to Customer orders
  • Products

    Sellable SK us with base unit and standard price

  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Fulfillment events

    Actual allocated, picked, shipped, delivered and returned events

    Linked to Customer orders, Products

Fulfillment events

5 tablesAbout this feature
  • Fulfillment events

    Actual allocated, picked, shipped, delivered and returned events

    Linked to Customer orders, Products
  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Products

    Sellable SK us with base unit and standard price

  • Order lines

    Ordered, allocated and shipped quantities per SKU

    Linked to Customer orders
  • Operation receipts

    Idempotent record of each executed operation

    Linked to Customer orders

Carrier labels

4 tablesAbout this feature
  • Carrier labels

    Packed-order carrier labels under review

    Linked to Customer orders, Organizations
  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Review decisions

    Independent review outcomes per source revision

    Linked to Customer orders, Team members
  • Operation receipts

    Idempotent record of each executed operation

    Linked to Customer orders

Review and operations

5 tablesAbout this feature
  • Operation receipts

    Idempotent record of each executed operation

    Linked to Customer orders
  • Review decisions

    Independent review outcomes per source revision

    Linked to Customer orders, Team members
  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Fulfillment events

    Actual allocated, picked, shipped, delivered and returned events

    Linked to Customer orders, Products
  • Carrier labels

    Packed-order carrier labels under review

    Linked to Customer orders, Organizations

Payment and attachments

5 tablesAbout this feature
  • Payment evidence

    Provider-confirmed authorization, capture and refund events

    Linked to Customer orders
  • Record attachments

    Supporting evidence files per order

    Linked to Customer orders, Team members
  • Customer orders

    E-commerce orders moving through pick-pack-ship

    Linked to Organizations, Team members, Customers
  • Fulfillment events

    Actual allocated, picked, shipped, delivered and returned events

    Linked to Customer orders, Products
  • Team members

    People with an authorized fulfillment role

    Linked to Organizations, Users

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Customer orders is the anchor for line, event, label, payment, attachment, review and receipt history. External order ID, external event ID, provider event ID and operation key identify incoming or executed work. Check these values and the relevant Revision before writing an effect. Team members links the operational owner or reviewer to a Users identity and organization.

Migration order

  1. Load Organizations, Users and team members, then Customers and Products.
  2. Load customer orders with its organization, customer and owner references.
  3. Load order lines and reconcile SKU and unit quantities.
  4. Load fulfillment events, carrier labels and their external identifiers.
  5. Load payment evidence, record attachments, review decisions and operation receipts with their order references.

Set up E-commerce Fulfillment SCM your way.

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

How to get started