MODE 01 · MANUAL
CSV import
Vehicle master loaded by file. No ERP connection. Ideal for pilot or environments without technical access.
ERP→CSV→Stocktech
Setup
< 1 day
Client IT
Minimal
Module · ERP / DMS Integration
We don't replace your ERP/DMS. We govern it from operations.
Four integration modes (from manual import to full bidirectional), a conflict matrix that decides per field who wins, and a multi-connector framework ready to add new ERPs without touching code.
0
Integration modes
0
Protocols: REST · OData · SQL
0
Code to switch modes
0%
Auditable per event
/settings/erp
ConnectedConnectorERP/DMS REST · v2
ModeM3 · HYBRID
Last sync2 min ago · 1,847 veh.
Conflict policyPer field
Outbound queue3 pending
4 modes · 1 productLATAM standard
Start where your IT is comfortable. Scale when you're confident.
Each mode is a configuration, not a product fork. Migrating from Mode 2 to Mode 3 is changing a policy in /settings/erp, not a project.
MODE 02 · READ-ONLY
ERP read-only
Stocktech queries the ERP periodically. The ERP remains absolute master. Zero risk of overwriting data.
ERP→REST→Stocktech
Setup
3–5 days
Client IT
Endpoint + auth
MODE 03 · HYBRID
Per-field matrix
Each field has an explicit owner. The standard mode for dealer groups with an ERP/DMS in production.
ERP→MATRIX→Stocktech
Setup
1–2 weeks
Client IT
Agree policies
MODE 04 · BIDIRECTIONAL
Full outbound
Stocktech writes to the ERP with transactional outbound queue, retry and audit. For national groups / OEM policy.
Stocktech→QUEUE→ERP
Setup
3–6 weeks
Client IT
Write endpoints
i
The mode is not a permanent decision.
80% of clients start in Mode 2 (read-only) during the pilot, migrate to Mode 3 (hybrid) at go-live and reserve Mode 4 (bidirectional) for later phases once there's confidence in the policy matrix.
Per-field conflict matrix
Who wins on each field. No ambiguity.
The classic conflict: the ERP says the vehicle was sold, but the dealership has it in maintenance. The per-field matrix automatically decides, in each case, which source prevails — versioned in code, not in email.
Field
ERP
StockTech
Result
Vehicle identifier
Master
Read
ERP wins
Model
Master
Read
ERP wins
Inventory status
Signal
Read
ERP wins
Commercial status
Signal
Assignments
Controlled merge
Logistics status
Branches signal
Customs + transfers
Controlled merge
PDI status
—
Master
Stocktech wins
Maintenance status
—
Master
Stocktech wins
Branch
Locked
Master
Locked during transfer transit
Architecture
Sync is not a cron. It's a governed pipeline.
Inbound and outbound queues, versioned transformations per connector profile, retry with exponential backoff, dead-letter for manual cases, and full audit per vehicle and per event.
Source system
ERP
Customer ERP / DMS
REST · OData · SQL (via connector)
Integration layer
01
Inbound queue
Retry · DLQ
02
Connector profile
Mapping · transformations
03
Outbound queue
Mode 4 · idempotent
Policy engine
⚙
Per-field conflict matrix
4 strategies · full audit per event
Persistence & application
PG
PostgreSQL
Vehicle master + logs
S3
S3 / R2
Evidence · photos
UI
/settings/erp
IT configures without code
Want to see sync with your ERP/DMS, your data, your rules?
The 2–4 week PoC validates integration in your context before any license commitment. Fee creditable toward implementation.