01 · CUSTOMS
Customs reception
Document every vehicle at the border with photos, motives, supervisor sign-off, and automatic link to the ERP master.
Mandatory evidence3 statesERP sync
Module · Logistics
From border to customer. Every move, documented.
Three integrated flows — customs, internal transfers, and discrepancies — built for dealer groups that need vehicle-level traceability without dethroning the ERP as financial master.
0
Integrated subflows
0+
Transfer reasons
0%
Photo evidence
0×
Faster vs Excel
The three subflows
One module. Three critical flows.
Each subflow addresses a concrete dealership-operation pain point. All three share data, roles, and ERP integration policies — no duplication, no manual reconciliations.
02 · TRANSFERS
Transfer movements
Request → approval → transit → arrival. 10+ preconfigured motives with policies and approvers per branch.
Multi-branchDigital approvalETA and delays
03 · DISCREPANCIES
Incident management
Damage, missing items, or wrong models detected on arrival — captured with photos and routed to the right owner.
Immediate captureResolution workflowSLA by type
Flow detail
What your dealership operation sees.
Each subflow in detail — capabilities, states, ERP integration — with visualization of the real module. Switch between flows above to explore.
Customs with mandatory evidence.
Every vehicle crossing the border has a documented reception: mandatory photographs, categorized motives, supervisor validation, and ERP sync with the per-field policy matrix. No more lost emails or WhatsApp as a record system.
Mandatory photo evidence
Minimum 4 angles required per vehicle (front, rear, side, interior). The system will not advance without uploaded photos.
Validated states
draft → confirmed → closed flow with role-based permissions. Only the supervisor closes.
Automatic ERP sync
On confirmation, the vehicle reconciles with the ERP master. The policy matrix decides who wins on each field.
By branch and agent
Automatic assignment to the branch and responsible customs agent. Reports filterable by origin, destination, and period.
The operational shift
What changes at your dealership when Stocktech arrives.
What groups report when migrating from manual processes and Excel to Stocktech in the first 90 days of operation.
Without Stocktech
Excel masters per branch
Each branch maintains its own file, with its own columns.
Photos in WhatsApp and email
Scattered evidence, with no clear link to the vehicle or event.
Email approvals
Overflowing inboxes, lost decisions, history rebuilt manually.
Discrepancies in spreadsheets
Claims to OEM or carrier with fragile, late evidence.
Where is that vehicle?
Calls between branches to locate inventory in transit.
With Stocktech
One shared vehicle master
Same rules, same fields, scopes per branch. Connected to ERP.
Photos linked to vehicle and event
Uploaded from mobile, tagged by angle, stored in S3.
Digital approvals with policies
Who approves is defined by motive and amount. In-app notification.
Categorized discrepancies with evidence
Exportable, audit-ready reports for claims.
Dashboard with live queue
Any role sees where each vehicle is and in what state.
Measured impact
What changes for groups that migrate.
Target figures based on real implementation scenarios. Your group's specific numbers are agreed in the PoC closing report.
0×
Transfer speed
Transfers with digital approval, preconfigured motives, and automatic discrepancies.
−0%
Time on claims
Photo evidence organized by vehicle reduces time to build OEM claims.
0
Lost vehicles
Every movement documented. End-to-end traceability.
0%
Customs with evidence
System will not confirm reception without mandatory minimum photos.
Integrated logistics
How it connects to the rest of the product.
Logistics does not live in isolation. Each flow feeds and queries the master, ERP, and adjacent modules — no manual syncs or data duplication.
Inventory
The vehicle master is the same. Every Logistics movement updates the vehicle's physical status and the branch where it is.
Inventory module →ERP integration
Every customs confirmation and every transfer syncs with ERP according to the policy matrix. Your CIO sees which field wins in which situation.
ERP integration →Platform (roles)
Logistics actions (approve, confirm, close) are governed by the system's 13 roles and 35 RBAC permissions.
Platform module →Want to see the module with a real vehicle?
The 45-minute demo includes a full walkthrough of all three subflows: a sample customs reception, an end-to-end transfer, and discrepancy management.