Skip to content
2finity.com
2finity.com
2finity.devSign in

CORE layer 07 of 10

Commerce

Products, services, catalogs, quotes, carts and orders: what an organization sells and how it is bought.

2finity CORE and the interfaces and participants connected to it
COREWebsiteApplicationsChatAgentsPeopleCompaniesPartnersEnterprise
CORE
The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
Website (interface)
Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
Applications (interface)
Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
Chat (interface)
2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
Agents (interface)
Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
People (participant)
Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
Companies (participant)
Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
Partners (participant)
Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
Enterprise (participant)
Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.

Scope

What it holds

What do we sell?

Commerce models the offer and the transaction. Products and services sit in catalogs with prices and variants; quotes, carts and orders record what a person or organization is buying. Because buyers are People and sellers are Organizations, a webshop, a sales agent and a partner portal operate on the same order. Payment and invoicing hand over to Finance.

Model

Example entities

  • Product
  • Service
  • Catalog
  • Variant
  • Price
  • Quote
  • Cart
  • Order

Contract

Capabilities

Every action on this layer is a named capability with a permission check and, where something changes, an event.

  • catalog.list

    List published products and services, optionally by category.

    Public
  • catalog.product.get

    Read one product with variants and prices.

    Public
  • catalog.product.update→ catalog.product.updated

    Change product data as a draft.

    Member of the organization
  • catalog.product.publish→ catalog.product.published

    Make a product visible in the catalog.

    Privileged role or approval
  • quote.create

    Named in the layer model; not yet described in the catalogue.

  • cart.add

    Named in the layer model; not yet described in the catalogue.

  • order.create

    Named in the layer model; not yet described in the catalogue.

  • order.update→ order.updated

    Change an order's state, lines or delivery.

    Member of the organization
The full catalogue

Connections

Relationships

The layers Commerce reads from and writes to most often.

  • 03

    People

    Who do we work with?

    Customers, employees, professionals, suppliers and leads: the people an organization works with, as one record each.

    Open layer
  • 08

    Finance

    What is owed and paid?

    Invoices, payments, costs and financial records: the money side of every order, contract and relationship.

    Open layer
  • 06

    Workflows

    How does work move?

    Tasks, approvals, automations, processes, triggers and state transitions: how work moves and who signs off.

    Open layer
  • 05

    Knowledge

    What do we know and publish?

    Documents, structured knowledge, policies, published content and context: what the organization knows and shows.

    Open layer

Consumers

How interfaces use it

The interfaces and participants on the CORE graph that read or write this layer, with the capabilities of this layer they name.

  • Website interface

    Public sites and portals that read content and catalog data and submit forms through CORE.

    catalog.list

  • Companies participant

    Organizations that own their data, run their workflows and decide who and what may act inside them.

    order.update

  • Partners participant

    Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants.

    catalog.product.getorder.update