Roadmap

Soon

Most of what was on this roadmap shipped with release v0.99.6.1 (2026-07-03) and is now GA on production. This page tracks what remains. For what you can use today, see Availability.

Recently shipped (now GA on production)

• Full headless wizard: discovery, batch form-data ingest, readiness, traceability, components, GS1 prefixes, and withdraw. See The wizard flow.
• Schema versioning: GET /categories/{code}/diff and GET /products/{id}/schema-compatibility.
• ERP field mapping: manage mapping sets under /erp-mappings, POST /mappings/lint, GET /categories/{code}/erp-template, and a ?mapping=<id> parameter on writes. An unmapped column is rejected, never silently dropped.
• Sandbox mode: pk_test_* keys distinct from live keys, with X-Traceable-Mode: test. See Authentication → Sandbox mode.
• Key management: programmatic /api/v1/keys (mint, rotate, revoke, bulk-revoke), per-key IP allow-lists (allowedCidrs), and a Warning: 299 rotation policy.
• Signed webhooks: HMAC-signed delivery with retries and a dead-letter queue, plus delivery history and redelivery under /webhook-endpoints.
• GDPR data-subject endpoints: /api/v1/gdpr/access, /erase, /portability (live mode only).
• Platform contract: GET /api/v1/openapi.json, GET /api/v1/meta, GET /api/v1/health, plus RateLimit-* and x-traceable-api-version response headers.

Planned: not yet available

caution

The items below are planned and not available on any environment. There are no examples here for that reason.

Inline supplier creation

An opt-in path to create a supplier inline during a traceability write, via a nested supplier{} object, rather than requiring the supplier to exist first.

Label/Print Integration API

Exploratory: no committed date and not yet available via the API. The concept: once a DPP clears the publish gate, Traceable would emit a signed label.ready event carrying the QR payload (the DPP URL), product/DPP identifiers, and label template data, delivered via webhook (push) or a polling endpoint (pull). Traceable delivers the label-job payload only: the manufacturer's own print-management software or MES owns rendering and printing; Traceable does not integrate with printers, PLCs, or line hardware. An optional acknowledgment callback (printed / failed / rejected / cancelled) would close the loop for the audit trail.

Error format

A move to RFC 7807 application/problem+json for error responses is under consideration. Until then, errors use the envelope documented in Errors and conventions.

How this list may change

This roadmap is indicative, not a commitment. Items may be reordered, combined, or dropped. Breaking changes to the shipped contract would be announced in advance through the changelog. The one exception is a field the Battery Regulation requires us to correct, which may be retired in place; each retirement is listed in the API changelog.