REST API
API-Based Custom
Core REST endpoints are available for contracted workspaces and internal integration work.
Supplier data intake
Know which sources are ready, guided, or custom scoped.
A compact view of available intake modes, guided workflows, and custom-scoped implementation paths. Named vendor and retailer workflows require scope confirmation and evidence review before being treated as production connectors. Send records by CSV upload or the JSON events API. EPCIS 2.0 is in Preview.
Current integration posture
Status labels stay conservative. Implemented and Supported mean usable in supported workspaces; Pilot means validated but guided; Preparation and Contract-only items require explicit diligence; Custom Scoped means implementation work should be explicitly estimated.
Developer APIs
CSV upload, JSON events API, EPCIS (Preview)
JSON events API (inbound)
API-Based Custom
Submit CTE events as JSON to POST /api/v1/webhooks/ingest for validation and downstream normalization (one-way inbound).
GS1 EPCIS 2.0 (Preview)
One-Way Export Adapter
EPCIS export and ingest are in Preview. Default deployments use PostgreSQL-backed task processing; legacy Kafka-compatible signing is opt-in.
ERP & warehouse
Files, extracts, mapping
CSV Import
File-Based Import
Upload CSV files for ERP and warehouse data that is not available over API.
SAP S/4HANA
File-Based Import
Implemented through exported traceability extracts and mapping review, not a turnkey native connector.
Oracle NetSuite
File-Based Import
NetSuite data can be onboarded via CSV export with RegEngine mapping review.
Fishbowl
File-Based Import
Fishbowl support relies on file exports and customer-specific data mapping.
QuickBooks
File-Based Import
QuickBooks is suitable for transaction export and reconciliation, not as a deep native traceability connector.
Food safety & IoT
Audits, sensors, cold chain
SafetyCulture
File-Based Import
Inspection and audit data can be mapped into RegEngine during guided onboarding.
FoodReady
File-Based Import
HACCP and temperature-monitoring exports can be normalized into FSMA traceability records.
FoodDocs
File-Based Import
Food safety tasks and records can be ingested through scoped integration work.
Tive Trackers
File-Based Import
Cold-chain sensor exports can be imported and linked to traceability lots.
Sensitech TempTale
File-Based Import
Sensitech CSV exports are supported in the data-import flow for temperature-linked events.
Retailer exports
Outbound packages
Walmart
One-Way Export Adapter
RegEngine can prepare EPCIS (Preview) export packages for retailer submission workflows.
Kroger
One-Way Export Adapter
Retailer-specific exports are supported as outbound packages, not a managed portal integration.
Whole Foods
One-Way Export Adapter
Use export bundles for retailer readiness and submission support.
Costco
One-Way Export Adapter
RegEngine prepares export-ready traceability packages; portal acceptance should be validated directly with the retailer.
Commercial programs
Scoped partner work
Design Partner Program
API-Based Custom
Reserved for customers needing custom integrations, advanced onboarding, or commercial pilot support.
Need another source scoped?
Bring the ERP export, supplier file, or API shape into onboarding and RegEngine will map it against the FSMA 204 event model before promising a production connector.