Data model

An illustrated overview of the dCommerce data model - how business objects relate, without a field-level schema.

This page shows the data model at business-object level - how the main records in dCommerce connect. It is an overview for evaluation - not a field-by-field schema. The merchant administers these objects in the admin console. Trade customers encounter them in the customer portal. Exact mapping to an ERP, if you have one, is worked through during onboarding.

At a glance

             ┌──────────────────────────────────────────────┐
             │                 Your business                │
             │         (system owner/administrator)         │
             │                                              │
             │  System Users · Product Catalogue · Pricing  │
             └──────────────────────┬───────────────────────┘
                                    │
                                    ▼
┌───────────────────────────────────────────────────────────────────────┐
│                         Customer Organisations                        │
│                                                                       │
│  Status · Contract pricing · Product eligibility · Ship-to addresses  │
├─────────────────┬─────────────────┬───────────────────────────────────┤
│    Contacts     │      Users      │              Orders               │
│                 |                 |                                   │
│ (associated     │  (from contacts │  Contact on order · Lines →       │
│  with Orders;   │   who get       │  Batches → Shipments              │
│  login optional)│   sign-in)      │  from Warehouses                  │
└─────────────────┴─────────────────┴───────────────────────────────────┘
         │                 │                          │
         │                 │                          │
         ▼                 ▼                          ▼
   Named person on    Roles control             Fulfilment status
   the account and    what each person          flows back to
   on each order      can see and do            buyers & staff

Core relationships

FromToSummary
OrganisationContactsA customer account has one or more named contacts
ContactUserA contact may be given sign-in access; contact is required before a user
OrganisationUsersCustomer users act for the organisation after access is granted
OrganisationOrdersOrders are placed for a customer organisation
ContactOrderAn order is associated with a contact - login is not required
OrganisationPrice listsContract pricing is tied to the account
OrganisationProductsSome products may only be visible or purchasable for certain accounts
ProductOrder linesEach line on an order references a catalogue product
Price listOrder linesLine prices reflect the account’s pricing rules
OrderBatchesOne order can split into batches (e.g. different warehouses or schedules)
BatchOrder linesLines belong to a batch within the order
OrderShipmentsShipments record fulfilment progress against the order
WarehouseShipmentsGoods ship from an assigned warehouse
UserRoleRoles define what each person is allowed to see and do
ProductMediaImages and documents support catalogue presentation

Order flow (simplified)

  Customer / staff creates order
            │
            ▼
  Contact associated (no login required)
            │
            ▼
  Lines added (products, quantities, prices applied)
            │
            ▼
  Optional: split into batches (warehouse / schedule)
            │
            ▼
  Validated & submitted (to ERP when integrated)
            │
            ▼
  Shipments recorded → status visible in admin console & customer portal

What this page deliberately omits

Prospect documentation stops here. It does not list database fields, API payloads, integration tokens, or internal sync mechanics. Those details belong in implementation and operator documentation once you are a customer - not on the public marketing site.

If you are evaluating portal fit - with or without an ERP - book a call and we can walk through your data model against this structure.

Explore each concept

ConceptPage
OrganisationOrganisation
ContactContact
UserUser
ProductProduct
Product pricingProduct pricing
OrderOrder
ShipmentShipment
MediaMedia