Roadmap
Planned future products
The long-term platform evolution (§135), written down concretely: what each future product would do, and what has to exist first. Every item below is planned, not built.
None of these products exists yet.
They are not available, not in beta, and not purchasable. This page exists so the plan is concrete: scope and prerequisites in writing, instead of vapor. When something ships, it appears in the changelog.
01Supplier compliance
Planned. Not built yet.Track the compliance posture of a customer's suppliers: which factories and component vendors hold which certifications, which are expiring, and which supplier gaps block a product's market access.
Prerequisites
- Supplier entity model (today the platform models products, not suppliers)
- Evidence items attachable to supplier records, not just products
- Monitoring subscriptions scoped to supplier certifications
02Procurement intelligence
Planned. Not built yet.Advise buyers before they order: given a target market and product category, which requirements a candidate supplier's offering already satisfies and which evidence the buyer must still collect.
Prerequisites
- Supplier compliance (above)
- Read-only supplier assessment flow that does not require supplier onboarding
03Market-entry forecasting
Planned. Not built yet.Estimate the effort and timeline of entering a new market for a given product (requirement count, evidence gaps, typical certification lead times, and monitoring load), from verified platform data, never invented timelines.
Prerequisites
- Historical lead-time data captured from real assessments (evidence turnaround, certification durations)
- Requirement-effort model validated against completed market entries
04Product launch readiness
Planned. Not built yet.A launch checklist that turns an approved assessment into a go/no-go: requirements met, evidence attached, labels and documentation ready, monitoring enabled for the target markets.
Prerequisites
- Assessment lifecycle states already exist; readiness needs a formal launch gate and sign-off workflow
- Labeling/packaging requirement coverage for target markets
05Marketplace compliance
Planned. Not built yet.Help marketplaces verify that third-party sellers' listings meet the market's product-compliance rules before they go live, with seller-facing remediation steps.
Prerequisites
- Multi-tenant seller workspaces under one marketplace account
- Bulk assessment API with listing-level granularity
- Seller notification and remediation workflow
06AI-agent commerce compliance
Planned. Not built yet.Let AI shopping and commerce agents ask compliance questions on behalf of buyers and sellers (can this be sold here, what is missing, what is required), with answers grounded in verified platform data.
Prerequisites
- AI-agent APIs (below) with machine-readable, cited answers
- Answer provenance: every claim traceable to a verified source
- Rate limiting and abuse controls for agent traffic
07Cross-border catalog intelligence
Planned. Not built yet.Analyze an entire product catalog against many markets at once: which SKUs are ready where, which are blocked, and the cheapest remediation path per SKU.
Prerequisites
- Portfolio intelligence at catalog scale (10k+ SKUs)
- Batch assessment pipeline with cost controls
- Catalog import from PIM/ERP systems
08Product passports
Planned. Not built yet.Generate digital product passports (e.g. EU DPP-style) from the platform's verified product, material and compliance data: a shareable, versioned record per product.
Prerequisites
- Stable product identity (below)
- Material/composition data model beyond current product attributes
- Versioned, tamper-evident passport rendering and sharing
09Product identity
Planned. Not built yet.A persistent, deduplicated identity for every product across assessments, evidence, reports and integrations, so the same physical product is never assessed twice under two names.
Prerequisites
- Identity resolution rules (GTIN, brand + model matching, fuzzy dedupe)
- Merge/split workflows with audit history
10Automated evidence collection
Planned. Not built yet.Pull evidence from connected systems instead of manual upload: test reports from labs, certificates from certification bodies, declarations from suppliers, matched automatically against open requirements.
Prerequisites
- Testing-lab and certification integrations (below)
- Document-content checking (deeper document intelligence)
- Requirement-to-evidence matching with confidence scoring
11Testing-lab integrations
Planned. Not built yet.Send test requests to partner labs and receive results back into the platform, attached to the right product and requirement automatically.
Prerequisites
- Partner lab agreements and API contracts
- Secure result ingestion with provenance (lab identity, test method, date)
- Quote/ordering flow or deep link into lab portals
12Certification integrations
Planned. Not built yet.Track certification applications with certification bodies (e.g. notified bodies): application status, outstanding items, and certificate issuance reflected in the product's compliance state.
Prerequisites
- Certification-body partner integrations or standardized status feeds
- Certificate document model with expiry and scope
13Customs integrations
Planned. Not built yet.Connect customs and tariff data to assessments: HS classification suggestions with official rulings, duty estimates from verified tariff sources, and import-document requirements per market.
Prerequisites
- Verified tariff-rate sources (today the platform deliberately does not publish unverified rates)
- HS classification helper hardened with binding-ruling references
14ERP integrations
Planned. Not built yet.Sync product master data from ERP systems (SAP, NetSuite, Dynamics) so assessments always run against current bills of materials and product attributes.
Prerequisites
- Product identity (above) to match ERP items to platform products
- Connector framework with per-tenant credentials and sync scheduling
- Change detection: re-assess when the BOM changes
15PIM integrations
Planned. Not built yet.Two-way sync with product information management systems (Akeneo, Salsify, inRiver): push compliance attributes and readiness states back into the PIM, pull enriched product data in.
Prerequisites
- Product identity (above)
- Attribute mapping UI per PIM tenant
- API write-back with conflict handling
16AI-agent APIs
Planned. Not built yet.Machine-first API surface for AI agents: ask compliance questions, submit products for assessment, and retrieve cited answers, with agent identity, budgets and audit trails.
Prerequisites
- Current REST API hardened for agent-scale traffic
- Structured, cited answer format (claim + source + confidence)
- Agent API keys with spend caps and full audit logging