Questions a careful team should ask.

No. The Ghana cocoa organization is retained synthetic demo data. It is realistic enough to show the journey, but it should not be described as a live customer deployment.

Yes. The demo supports a no-hardware path with preloaded farmer profiles, QR-only lots, purchase records, reports and public passports.

It should sit in field-first staging. Staged records are not reportable, customer-visible or passport-ready until assigned and reviewed.

Yes. Demo organization names can be changed for a walkthrough using browser-local values. Those changes do not write to Supabase or live tenant records.

Cards identify a person or operating role, such as farmer, field agent, buyer or verifier. They do not grant access by themselves.

Smart tags identify a bag, lot, receipt or passport reference. Phone taps support individual bag lookup; bulk scanning can support inventory at aggregation points. The tag is a lookup handle for the evidence journey, not a private database.

No by default. Private farmer identity, payment details, contact information, signatures and exact locations stay off-tag and inside protected systems.

The smart tag program is intended for field use, including heat, dust, humidity, transport handling and rough buying-station conditions. Final tag models still need supplier datasheets and physical pilot validation for exact temperature, water, impact and chemical-resistance claims.

The tag strategy assumes rugged field inventory suitable for hot environments and commodity transport. Before production, each selected tag batch should carry a manufacturer temperature rating and field validation record, rather than relying on a generic claim.

TRACRS supports QR-only and tagless exception flows. Replacement or reprogramming should be recorded as a controlled lifecycle event with reason, user, timestamp and old/new identifier.

Yes, but it should never be an invisible overwrite. Reprogramming belongs in an admin-controlled flow with role permission, password or stronger authentication, and an audit trail.

A tap helps identify the object being handled. Production hardening should add signed payloads, token revocation and online verification where available.

No. Cards, tags and QR codes identify records. Authorization comes from authentication, organization membership, role permissions and policy.

Only authorized roles. A farmer sees their own identity and receipts; a field agent sees assigned work; an organization sees its workspace; buyers/customers see authorized supplied lots and evidence; public passports expose a deliberately limited layer.

No. Buyer and customer access should be limited to lots, due-diligence status, evidence and passports they are authorized to inspect.

The admin model should support platform operations, staging, inventory and support. Live customer record access should be role-scoped, reasoned and auditable.

Public passports are a selective publication layer. Exact coordinates, payment information, signatures, contact details, private photos and internal evidence are excluded by default.

Demo data is synthetic. Staging data is field-captured but not yet assigned. Live data belongs to an organization workspace and is governed by membership, roles and RLS.

No. TRACRS supports evidence collection, readiness and traceability workflows. Legal conclusions and certification remain subject to organization review and applicable law.

TRACRS Origin is designed around evidence workflows relevant to EUDR, CSRD/ESRS, CSDDD, the EU Forced Labour Regulation, GDPR and buyer-specific responsible-sourcing programs. It supports evidence collection and reporting readiness; it is not a legal opinion or certification.

European Commission materials currently state 30 December 2026 for large and medium operators, 30 June 2027 for micro and small operators, and 30 December 2026 for micro and small operators already covered by the EU Timber Regulation.

Covered products such as cocoa and coffee need evidence that they are deforestation-free, produced in accordance with relevant production-country law, and covered by due diligence before being placed on or exported from the EU market.

TRACRS organizes the underlying evidence and readiness workflow. Any formal due diligence statement submission should be made by the responsible operator or authorized party through the required official process.

Farmer consent, plot or farm geography, crop and product form, quantity, purchase records, chain-of-custody events, supplier/customer links, external source observations, risk conclusions and supporting evidence files.

No. A passport is a selective communication layer. Regulatory due diligence requires controlled private evidence, review, retention and responsibility beyond what is made public.

No. TRACRS can connect plots and lots to evidence signals and review workflows. Deforestation-free conclusions should remain documented, reviewable and attributable to the responsible organization.

Deadlines should be shown as configurable governance dates with official-source references, because regulatory implementation dates and guidance can change.

Retention should follow the applicable law, customer role and legal basis. For EUDR-style evidence, the system should preserve due-diligence work files, evidence references and audit history long enough to support regulatory review.

Evidence readiness is not legal certification. TRACRS helps organizations capture, organize, review and selectively share evidence; the accountable operator remains responsible for legal conclusions and submissions.

The broader pull comes from forced-labour import controls, corporate sustainability reporting, corporate due-diligence laws, digital product passport rules, food traceability recordkeeping and private buyer assurance programs.

From 14 December 2027, products made with forced labour may not be sold in or exported from the EU market. Companies may need better supply-chain visibility, supplier engagement records, risk evidence and remediation history.

CSRD/ESRS reporting can require companies to report sustainability impacts, risks and opportunities across their value chain. That often creates data requests for suppliers that are not themselves directly in scope.

CSDDD is a due-diligence framework for human-rights and environmental impacts across operations, subsidiaries and global value chains. Even where small suppliers are not directly in scope, larger buyers may need evidence from them.

The Uyghur Forced Labor Prevention Act creates a rebuttable presumption against certain goods connected to Xinjiang or listed entities. Importers need supply-chain evidence capable of showing origin, actors and material flow.

Yes as a pattern. EU Digital Product Passports are being introduced across selected product groups to make product information accessible through a data carrier. TRACRS uses the same basic idea for first-mile product memory, while keeping private farmer data protected.

Yes in principle. Rules such as the U.S. FDA Food Traceability Rule require certain food supply-chain records around critical tracking events and key data elements. Coffee and cocoa are not the same as every listed food category, but the direction of travel is clear: more structured origin and movement records.

TRACRS is a first-mile evidence layer. It helps organizations collect primary records that can later support different compliance, assurance and reporting needs without rebuilding the origin workflow each time.

Yes. The model separates farmers, farms, plots, lots, tags, receipts, confirmations, passports, due-diligence cases, evidence, organizations, memberships and external sources.

Organization tenancy is the main boundary. The reporting portal should rely on Supabase Auth, memberships and RLS rather than frontend filtering.

The field workflow is designed for offline-first capture and later sync. Reporting, public passport lookup and external enrichment require connectivity.

Yes. The tag identifies the bag, the local device records the event, and TRACRS synchronizes later. Known cached tags can resolve immediately; unknown tags are still recorded and resolved after sync.

Field teams can capture drafts locally and sync later. Sync failures, conflicts and retries should be visible and auditable before production pilot.

Yes. Crop, country, source, organization, evidence and passport fields are explicit. Coffee and cocoa are the current focus, but the structure can extend.

External sources such as NASA POWER and Global Forest Watch are treated as attributed evidence signals, separate from farmer declarations and human review.

RLS regression tests, environment separation, signed tag payloads, staging assignment workflow, audit tables, observability, incident procedures and physical-device testing.

Yes. The Documentation page includes a review risk register covering privacy, engineering, legal, hardware, regulatory, agronomy and data-science risks, with mitigations and production-pilot gates.

No. Submitted manuals do not automatically become app advice. Source, owner, license, permission and allowed use must be reviewed first.

Each manual should track publisher, edition, language, country/crop relevance, license, permission evidence, approved use, reviewer, checksum and superseded status.

It can be listed as reference or permission-pending, but it should not be indexed for farmer-facing AI answers until rights are confirmed.

Farmers should choose from clear categories such as pests, soil, pruning, shade, harvest, weather and compliance. Answers should cite approved sources and say when the system does not know.

Not unless supported by approved local sources and review. Severe disease, poisoning, major crop loss, pesticide selection and dosage questions should escalate to a human or approved local authority.

Farmers should not pay. TRACRS is funded by the organizations that need evidence: cooperatives, buyers, exporters, brands, programs and verification partners.

Yes. Start with demo mode or QR-only workflows, then add identity cards and smart tags as inventory arrives.

Its profile, users, roles, field agents, farmer claims, programs, staged-record approvals, lots, passports, compliance evidence and sharing rules.

Demo orgs, live org setup, field staging, master card/tag inventory, reprogramming controls, manual permissions, audit support and platform operations.

Use a retained demo org first, then run a small field-first pilot with staging, then assign reviewed records to a live organization workspace.