Data trust
Connections & data trust
Synchronised information is the production goal. Every source below is a candidate: no account is connected, no endpoint, entitlement, refresh speed or write capability is verified, and no credentials exist in this demo.
Cultivera
Wholesale operations, stock, orders and fulfillment. Custom API access is unverified.
- Candidate data:
- Candidate accounts, Candidate products, Candidate orders, Candidate fulfillment records
- Intended direction:
- Read-only into this platform (proposed)
- Source ownership:
- Cultivera is the proposed authoritative source for orders and fulfillment — to confirm
- Last successful simulated refresh:
- 2026-03-03 06:15 PT
- Fallback mode:
- If API access is unavailable: assess verified export/import or structured manual capture.
- Duplicate risk:
- Confirm whether Market/Storefront orders are the same source records to avoid duplicate ingestion.
Cultivera Market / Storefront
Wholesale online ordering channel. Must be deduplicated against Cultivera Pro by mapped source IDs.
- Candidate data:
- Candidate online wholesale orders (retail stores ordering from Pure Extract)
- Intended direction:
- Read-only into this platform (proposed)
- Source ownership:
- Unconfirmed — may share records with Cultivera
- Last successful simulated refresh:
- 2026-03-03 06:15 PT
- Fallback mode:
- Link-only access would not populate metrics.
- Duplicate risk:
- MKT-ORD-5512 held for review as a possible duplicate of CLT-ORD-9104.
Nutshell
CRM accounts, contacts, leads and sales activity. A REST API is documented.
- Candidate data:
- Candidate contacts, Candidate accounts, Candidate sales activities
- Intended direction:
- Read-only into this platform (proposed)
- Source ownership:
- Proposed authoritative source for contacts — to confirm
- Last successful simulated refresh:
- 2026-02-27 21:40 PT
- Sample error:
- Simulated: last refresh attempt returned no new activity records.
- Fallback mode:
- Structured manual capture of visits until access is verified.
Headset
Retail sell-through, stock cover and velocity, only for retailers who actively share data. A documented read-only MCP does not automatically create a published-app integration.
- Candidate data:
- Candidate retail analytics, Candidate account insights
- Intended direction:
- Read-only (proposed), subject to product, permissions and coverage
- Source ownership:
- Third party — coverage unknown
- Last successful simulated refresh:
- Never
- Fallback mode:
- Link-only card until product entitlement is verified. Does not populate metrics.
A link-only card does not populate any metric on any screen.
Your Weed Data
Broader Washington CCRS market intelligence and operator, product and category context. REST access is advertised, but usable fields and coverage need validation.
- Candidate data:
- Candidate market intelligence — exact product and access to confirm
- Intended direction:
- Undetermined
- Source ownership:
- Third party — unconfirmed
- Last successful simulated refresh:
- Never
- Fallback mode:
- Add link when the correct product and login are confirmed.
A link-only card does not populate any metric on any screen.
QuickBooks Online
Optional invoices, receivables and payments. Current business usage is unconfirmed.
- Candidate data:
- Candidate invoices, Candidate payments, Candidate receivables
- Intended direction:
- Read-only first; any writeback requires separate validation
- Source ownership:
- Appears in notes as training only — confirm whether it is the active accounting system
- Last successful simulated refresh:
- 2026-02-27 21:40 PT
- Sample error:
- Simulated error: refresh attempt 2026-03-03 06:15 PT failed (authorization not configured). Showing last successful data from 2026-02-27 21:40 PT.
- Fallback mode:
- Manual capture of invoice and payment records; balances shown with a staleness warning.
How stale and failed feeds appear elsewhere
Affected screens and assistant answers keep the true last-successful timestamp and show a warning instead of implying fresh data.
| Simulated condition | Where it shows | What the user sees |
|---|---|---|
| Nutshell CRM feed is stale | Accounts due for follow-up, contact-next answers, sales activity | Stale-feed warning with the last successful timestamp; recent visits may be missing. |
| QuickBooks Online refresh failed | Outstanding and overdue balances, aging, collection follow-up, assistant balance answers | Values from the last successful refresh, flagged stale — never silently refreshed or zeroed. |
| Headset not configured | Retail sell-through and stock cover | Unknown rather than zero, with coverage stated for sharing retailers only. |
Production guidance
What a real integration would require.
- Read-only connections first; any writeback is separately validated, human-approved and audited.
- One explicit authoritative source per entity and field. No two competing systems of record.
- Stable source IDs with a reviewable mapping table; similar names alone never trigger an automatic merge.
- Duplicate prevention and idempotent processing, so one order is never ingested twice.
- Retries, reconciliation, timezone handling and error logs.
- Credentials held server-side and never in the browser.
- Data synchronisation kept separate from AI reasoning.
Source: Mock connector adapters feed one shared normalised dataset in this demo, including a deliberately stale feed and a deliberately failed refresh.
Freshness: Simulated connector run 2026-03-03 06:15 PT
Reference material for later connection work
Read-only links. Nothing is activated now.