No recall timeline yet.
-- Import records or run a trace to build the event timeline for an investigation. -
-For enterprise systems (SAP, Oracle, NetSuite). Push events directly to our endpoints via the JSON events API; GS1 EPCIS 2.0 XML/JSON upload is in Preview.
diff --git a/frontend/src/app/ingest/page.tsx b/frontend/src/app/ingest/page.tsx index 83261482d..a7cbf4883 100644 --- a/frontend/src/app/ingest/page.tsx +++ b/frontend/src/app/ingest/page.tsx @@ -403,8 +403,8 @@ export default function IngestPage() { ? epcisResult.accepted === 0 ? 'No events accepted' : epcisResult.rejected > 0 - ? 'EPCIS partially accepted' - : 'EPCIS processed' + ? 'EPCIS (Preview) partially accepted' + : 'EPCIS (Preview) processed' : ''; const epcisTone = epcisResult ? epcisResult.accepted === 0 diff --git a/frontend/src/app/integrations/page.tsx b/frontend/src/app/integrations/page.tsx index ddf51c345..4e034c5c0 100644 --- a/frontend/src/app/integrations/page.tsx +++ b/frontend/src/app/integrations/page.tsx @@ -52,7 +52,7 @@ const CATEGORY_META: Record< CapabilityCategory, { title: string; eyebrow: string; icon: typeof Shield } > = { - developer_api: { title: "Developer APIs", eyebrow: "REST, JSON events, EPCIS export", icon: Code }, + developer_api: { title: "Developer APIs", eyebrow: "CSV upload, JSON events API, EPCIS (Preview)", icon: Code }, erp_warehouse: { title: "ERP & warehouse", eyebrow: "Files, extracts, mapping", icon: FileSpreadsheet }, food_safety_iot: { title: "Food safety & IoT", eyebrow: "Audits, sensors, cold chain", icon: Thermometer }, retailer_network: { title: "Retailer exports", eyebrow: "Outbound packages", icon: ShoppingCart }, diff --git a/frontend/src/app/proof/page.tsx b/frontend/src/app/proof/page.tsx index 5b4235333..324f1c30a 100644 --- a/frontend/src/app/proof/page.tsx +++ b/frontend/src/app/proof/page.tsx @@ -10,11 +10,11 @@ import { Card, CardHeader } from "@/components/ui/card"; export const metadata: Metadata = { title: "Proof | RegEngine", description: - "Download three verifiable sample artifacts generated by production code (FSMA 204 sortable spreadsheet, EPCIS 2.0 JSON-LD export, and a Merkle-rooted audit bundle) without signing up.", + "Download three verifiable sample artifacts generated by production code (FSMA 204 sortable spreadsheet, EPCIS 2.0 JSON-LD export (Preview), and a Merkle-rooted audit bundle) without signing up.", openGraph: { title: "Verify RegEngine without signing up", description: - "Three downloadable artifacts: FSMA 204 spreadsheet, EPCIS 2.0 JSON-LD, and a Merkle-rooted audit bundle.", + "Three downloadable artifacts: FSMA 204 spreadsheet, EPCIS 2.0 JSON-LD (Preview), and a Merkle-rooted audit bundle.", url: "https://regengine.co/proof", type: "website", }, @@ -44,12 +44,12 @@ const ARTIFACTS: Artifact[] = [ why: "FDA records requests may require records, including an electronic sortable spreadsheet under 21 CFR 1.1455(c)(3), unless an exemption or agreed alternative applies. This sample shows RegEngine's current column mapping and should be reviewed against the specific FDA request.", }, { - name: "EPCIS 2.0 JSON-LD export", + name: "EPCIS 2.0 JSON-LD export (Preview)", href: "/proof/epcis-sample.jsonld", filename: "epcis-sample.jsonld", sizeBytes: 3039, icon: FileJson, - formatLabel: "EPCIS 2.0 JSON-LD", + formatLabel: "EPCIS 2.0 JSON-LD (Preview)", summary: "A three-event payload covering harvesting, initial packing, and shipping for one traceability lot code.", why: "Several major buyers are standardizing on EPCIS 2.0 for supplier ingest. Confirm that what RegEngine emits validates against your retailer's onboarding tests before you sign a contract.", @@ -62,7 +62,7 @@ const ARTIFACTS: Artifact[] = [ icon: Hash, formatLabel: "ZIP · SHA-256 + Merkle root", summary: - "The CSV and EPCIS payload plus a manifest.json with per-file SHA-256 hashes and a Merkle root computed by production code.", + "The CSV and EPCIS (Preview) payload plus a manifest.json with per-file SHA-256 hashes and a Merkle root computed by production code.", why: "Compare each declared file's SHA-256 hash and the bundle's Merkle root with its included manifest. These checks establish internal consistency; they do not authenticate the issuer or establish that the source data is accurate.", }, ]; diff --git a/frontend/src/app/trust/architecture/page.tsx b/frontend/src/app/trust/architecture/page.tsx index fc1a92454..8e83cb2ee 100644 --- a/frontend/src/app/trust/architecture/page.tsx +++ b/frontend/src/app/trust/architecture/page.tsx @@ -89,7 +89,7 @@ const DATA_FLOW_STEPS = [ { step: '5', title: 'Export', - description: 'Compliance records may be exported in one or more supported formats such as EPCIS 2.0, FDA-oriented spreadsheets, or CSV, depending on the enabled workflow.', + description: 'Compliance records may be exported in one or more supported formats such as EPCIS 2.0 (Preview), FDA-oriented spreadsheets, or CSV, depending on the enabled workflow.', }, ]; @@ -144,7 +144,7 @@ const SYSTEM_FLOW = [ { Icon: Workflow, title: 'Evidence exports', - detail: 'FDA-oriented spreadsheets, EPCIS/CSV packages, and manifests where configured', + detail: 'FDA-oriented spreadsheets, EPCIS (Preview) and CSV packages, and manifests where configured', boundary: 'Customer review and archive', }, ]; diff --git a/frontend/src/app/trust/page.tsx b/frontend/src/app/trust/page.tsx index 7dcdcd618..1e1c35b73 100644 --- a/frontend/src/app/trust/page.tsx +++ b/frontend/src/app/trust/page.tsx @@ -139,7 +139,7 @@ const POSITIONING = [ }, { title: 'Full data portability', - detail: 'Supported workflows can export CTE events, KDE fields, lot records, and supplier relationships in EPCIS 2.0 JSON-LD, FDA-oriented sortable spreadsheet, or CSV.', + detail: 'Supported workflows can export CTE events, KDE fields, lot records, and supplier relationships in EPCIS 2.0 JSON-LD (Preview), FDA-oriented sortable spreadsheet, or CSV.', }, { title: 'Tenant isolation', @@ -210,7 +210,7 @@ const EXPORT_FORMAT_GROUPS = [ { title: 'Export formats', items: [ - 'GS1 EPCIS 2.0 JSON-LD (industry standard)', + 'GS1 EPCIS 2.0 JSON-LD (Preview, industry standard)', 'FDA-oriented sortable spreadsheet aligned to 21 CFR 1.1455 where applicable', 'CSV with all CTE/KDE fields', 'Audit evidence bundle with manifest hashing', @@ -375,7 +375,7 @@ export default function TrustCenterPage() {- EPCIS 2.0 can support trading-partner interoperability. RegEngine treats EPCIS 2.0 as a supported schema where the enabled workflow and source data allow it. + EPCIS 2.0 (Preview) can support trading-partner interoperability. RegEngine treats EPCIS 2.0 as a preview schema where the enabled workflow and source data allow it.
Verify EPCIS coverage with each vendor; some platforms layer EPCIS over legacy schemas, which can introduce conversion edges.
+ We could not load current plan pricing from our billing service, so no figures are shown here. + Plan rates are confirmed in your executed order form or design-partner agreement. +
+- Base plan includes 500 CTEs/month. Standard and Premium are unlimited. Need more on Base? Add CTEs at $0.002 each.{' '} + Base plan includes 500 CTEs/month. Standard and Premium are unlimited. Need more on Base? Additional CTE pricing is set in your agreement.{' '} See Terms for full details.
@@ -194,7 +194,7 @@ export function PricingPageClient({ RegEngine is priced around facility operations, not a long enterprise procurement cycle.- A GMA/FMI study found that the average major food recall costs companies over $10 million in lost product, logistics, and brand damage. RegEngine's Founding rate starts at $425/mo (billed annually). + A GMA/FMI study found that the average major food recall costs companies over $10 million in lost product, logistics, and brand damage. RegEngine's Founding rate is documented in your executed design-partner agreement.