Commercial Offer
Propose prices, quantities, scope and conditions before acceptance. Preserve what was actually offered.
Technical platform / explained
Behind the everyday screens are record identities, module boundaries, access rules, provider connections and release decisions. This guide follows those relationships: what owns each record, what can change it, and which connections are implemented or still being designed.
Choose an operating context to see how record ownership and access boundaries change.
For the person doing everything
One owner can begin with customer, quote, job and invoice records in a single context. Additional modules can reference the same source records without competing copies.
A brand is a customer-facing identity; a location is where work, people or stock are situated; a separate legal business can require its own accounting authority, access boundaries and contractual identity. Larger or multi-entity arrangements need an explicit implementation design—never an assumption that sharing a logo means sharing a ledger.
The Feature Atlas covers individual functions. Here we focus on data models, event handling, permissions and system boundaries.
01 / Module and runtime boundaries
Modules can show different views of the same customer, job, product or transaction. Explicit identifiers and source links allow records to connect while retaining distinct owners and update rules.
02 / Versioned commercial records
The planned CO / CA / POL record model links offer identity, accepted agreement versions, effective dates, policy rules and governed transactions. Source clauses and historical decisions must remain traceable when terms change.
03 / Events and record transitions
A website event, desktop command or Companion submission can begin an operation. The technical responsibility is to validate its origin, update authorised records and recover safely without duplicating payment or stock effects.
04 / APIs, webhooks and providers
Websites, payment services and freight providers can connect through configured interfaces. Each connection needs defined credentials, request or event contracts, a record owner and an error-recovery path.
05 / Authentication and data scope
Authentication establishes the requesting identity; authorisation determines which business, location, record and action it may access. Data provenance and desktop/server authority must stay explicit.
06 / Migration and verification
Migration requires mapping source identities, related records and attachments, then validating imports and exceptions. A controlled cutover should preserve original history and produce reviewable results.
Commercial agreements / CO · CA · POL
A negotiated rate, a customer exception or an accepted set of terms shouldn't become an unexplained number on an order. This is the commercial layer we're building towards: a traceable relationship between an offer, the agreement behind it and the work it governs.
Propose prices, quantities, scope and conditions before acceptance. Preserve what was actually offered.
Keep the accepted version and its parties, dates, terms, exceptions and applicable scope connected to the customer.
Define reusable rules, eligibility and boundaries for how the agreed terms should apply to transactions.
They receive an offer for a run of manufactured products. The accepted agreement might apply only to that customer, product range, quantity or time window. On the next quote or order, the system should be able to show the catalogue price, agreed price and which accepted clause explains the difference—without changing the price for everybody else.
Implementation status: This describes the planned commercial architecture, not a claim that every CO / CA / POL rule is already released or automatic. Check specific capability stages in the Feature Atlas.
A record chain shows relationships, not a mandatory operational path.
The Feature Atlas is the right place to search for detailed actions. The Workflows demonstration shows connected journeys. This guide explains modularity, boundaries and deployment. Each has a different job rather than repeating the same wall of text.
Technical foundations / accounting & stock
Accounting and physical inventory need an explainable record of what happened, not just the number the dashboard shows today.
Once an authorised entry is finalised, its original values and provenance are retained. Corrections appear as linked reversals or adjustment entries so the full sequence can still be audited. Drafts and unconfirmed movements can follow different rules.
Preserve accepted invoice figures, GST treatment, payment postings and the entries that explain their effect on the accounts. A later pricing change must not recalculate a previous sale.
Receipts, transfers, picks, production consumption and adjustments form a traceable movement history. The on-hand balance is the result of those confirmed movements, not a number with its explanation discarded.
This is the accounting and stock-record integrity principle, not a claim that every journal, permission gate, reversal path or automated posting is production-complete across every DD configuration. Final availability depends on the module and its verified workflow.
Customer applications / deployment architecture
Not one universal desktop binary with a new logo painted on. The delivery and update architecture is designed around individually identified customer builds.
Each customer's application starts from the Denver's Desk base, then is assembled and integrated for the needs, modules, data connections and working environment of that customer. Those customer builds are maintained independently — changes to the common base are selectively carried into the builds that need them.
See customer onboarding ↗Numbers are illustrative, not a promised version format.
Start from the shared foundation, configure the requested modules, and build for that customer's operation and approved integrations.
Allocate a customer/build identifier and its own version sequence. Record the package, release history and customer-facing change notes separately.
Plan authorised distribution from the customer's assigned web-domain path and storage bucket from initial provisioning, rather than one generic public installer.
Changes are selected, adapted, tested and approved for the specific customer build. Another customer's release must not silently update this one.
Applications ledger → customer-specific build → verification and checksum → assigned distribution path → authorised update manifest. The source base can evolve without forcing a one-size-fits-all update onto every installation.
Moving to Denver's Desk
We want the technical work to be supported by people who understand what real operating records mean—not just a list of import columns.