Objects
The concepts CCC owns and publishes, each with the sources behind it and the period each one covers.
An object is something CCC owns and publishes, as opposed to something an upstream system sent. The distinction is the same one the table prefixes make: ns_ and vkd_ are copies of what arrived, unprefixed and cm_ are CCC's own answers.
Each document says what the object means here, which tables hold it, which period came from which source, how it is built, and where two sources disagree.
Transactions
The seven NetSuite transaction types, in the order an order's life produces them.
| Object | Is |
|---|---|
| Sales orders | The order. Margin aggregates to it and customers are grouped by it |
| Prepayments | The payment. The only record of how the order was actually paid |
| Item fulfillments | The shipment out. Carries cost of goods |
| Invoices | The billing. Turns expected revenue into realised revenue |
| Return authorizations | Permission to send goods back |
| Item receipts | The goods arriving back |
| Credit memos | The money going back |
Computed
What CCC works out for itself rather than importing.
| Object | Is |
|---|---|
| Customers | Identity across accounts, and the order sequence built on it |
| Source and medium | Where a visit or an order came from, mapped onto controlled lists |
Catalogue and dimensions
What a transaction is described by.
| Object | Is |
|---|---|
| Products | The catalogue from Akeneo, and the NetSuite item beside it |
| Categories | Three category trees: Akeneo's, NetSuite's, and a retired one |
| Prices | Selling and cost prices per SKU per domain, from PriceShape |
| Stock | Availability per SKU, as a status derived from the expected date |
| Sales channels | Where an order came from. CCC's list and NetSuite's |
| Accounts | Where money books. CCC's list and the general ledger's |
| Discounts | The amount taken off, and the promotion that explains it |
| Traffic | Visitors per day per domain, split by source and medium |
The seam that runs through several of these
Source contracts differ by feed. Several objects combine data across a provenance boundary:
- sales orders: verkoopdump before 2022, NetSuite after
- source and medium: verkoopdump for 2022 to 2025, GA4 for recent orders
- customers: computed by CCC, with the old pipeline's answer imported beside it for comparison
Catalogue, stock and price feeds supply current state. Financial transactions, ledger totals, traffic and order discounts have their own dated histories and retention limits; read their source contracts before choosing a backfill.
Related
- Type
index - Status
active - Updated
2026-09-14 - Created
2026-09-13