_1777711377206.png)
Plan & Procure
Platform Essentials
Traqo Platform Essentials is the foundational layer every Traqo deployment ships with — role-based access, SSO, audit logs, custom workflows, master data, document storage and the API/webhook fabric that lets every module talk to your ERP, WMS, accounting and BI stack with zero custom code.
Plants, transporters, vehicles, lanes, SKUs, users, roles. The unsexy foundation every other Traqo module sits on. Set it up once, run it for years.
Powering 100+ shipper deployments globally
Master data hub
SOC 2
Plants
24
Lanes
180
Users
240
Roles
12
MUM-01Mumbai · Andheri42 users
DEL-01Delhi · Manesar38 users
BLR-01Bengaluru · Whitefield51 users
CHE-01Chennai · Sriperumbudur29 users
100+
shipper deployments
SSO + MFA
day one
Before & After
Two ways to run platform essentials.
Without Traqo
7 spreadsheets · 3 owners
no audit trailplants_master_v7.xlsx3 conflicts
users_oct.xlsxoutdated
lanes (Anita).xlsxno owner
transporters_FINAL.xlsxduplicate IDs
— same plant, four codes
- —Master data lives in 7 spreadsheets and 3 people's heads
- —Same plant has 4 different codes across teams
- —New-user onboarding takes a week of permission tickets
With Platform Essentials
single source · validated
SSO + MFAPlants · 24
Lanes · 180
Users · 240
Roles · 12
audit log · liveSOC 2 ready
- Single source of truth for plants, transporters, lanes, SKUs
- Role-based access control — assign once, audit forever
- Bulk imports with validation, no silent overwrites
How it works
Three steps. From your first day.
1
Step 01Masters loaded
Plants, vehicles, lanes, transporters — bulk-imported with validation.
2
Step 02Roles configured
Procurement, dispatch, finance, audit — granular permissions per role.
3
Step 03Users invited
SSO, MFA, audit log on day one. New joiners productive in minutes.
What's inside
Everything you need. Nothing you don't.
Master data hub
Plants, lanes, SKUs, transporters — versioned and validated.
Role-based access
Granular permissions per module, per geography, per role.
SSO + MFA
Okta, Azure AD, Google Workspace — wired up on day one.
Audit log
Every config change and login, exportable for SOC 2 audits.
The number that matters
100+
shipper deployments built on these foundations
across India, SEA, Africa and the Middle East
Trend · last 12 weeks
+412%
now
W1
W6
W12
Peak W12Avg week-on-week +14.2%
Sourced from active accounts
"We onboarded 4 plants and 240 users in two weeks. The masters held up — no clean-up tickets after go-live."
Tata Hitachi
IT Operations
The result
240 users in 2 weeks
Their morning view
100%
live · auto-orchestrated
All caught up
Today
✓
Open
0
Pairs perfectly with
One module is good. Three is a system.
FAQ
Frequently asked questions about Platform Essentials
- What is a logistics platform master data hub?
- A master data hub is the central, authoritative repository for all the reference data that every other module in your logistics platform depends on: plant codes and addresses, transporter and vendor records with GST details, vehicle types and capacity specifications, lane definitions with origin-destination pairs, SKU and product catalogue, contracted rate cards, user accounts, and organisational hierarchy. Without a managed master data hub, the same plant, carrier, or product appears with different codes in different teams' spreadsheets — causing mismatches in every downstream workflow. Traqo.ai's Platform Essentials module provides the master data hub that all 11 Traqo.ai product modules consume from a single, validated source of truth.
- How does role-based access control work in Traqo.ai?
- Role-based access control (RBAC) in Traqo.ai lets administrators define exactly what each user role can see, create, approve, and export within the platform. Standard roles include Procurement Manager (can view RFQs and auctions, cannot modify contracted rates), Dispatch Executive (can create and approve indents, cannot access financial settlement data), Finance Analyst (can view and approve invoices, cannot modify trip records), Plant Operations (can see their plant's indents and tracking, cannot see other plants), and Platform Admin (full access to all modules and master data). Custom roles can be created with granular permission sets down to the individual feature level. All access is logged in the audit trail.
- Which SSO providers does Traqo.ai support?
- Traqo.ai supports Single Sign-On (SSO) via SAML 2.0 and OpenID Connect, compatible with all major identity providers: Okta, Microsoft Azure Active Directory (now Entra ID), Google Workspace, OneLogin, Ping Identity, and ADFS. With SSO enabled, your employees log into Traqo.ai using their existing company credentials — no separate password to remember or manage. When an employee leaves the company and their corporate account is deactivated, their Traqo.ai access is automatically revoked. Multi-factor authentication (MFA) is enforced at the identity provider level and extends to Traqo.ai automatically when SSO is active.
- What is an audit log and why is it important in logistics software?
- An audit log is a permanent, tamper-proof record of every action taken in the platform: who logged in, when, from where; who created, modified, or deleted each record; what approvals were granted and by whom; what configuration changes were made and when. Traqo.ai's audit log covers all modules and all user actions, timestamped to the second. It is exportable for compliance reporting, internal audits, and regulatory reviews. For enterprises pursuing SOC 2 Type II certification, ISO 27001 certification, or internal finance audit requirements, the audit log provides the evidence trail auditors require. It is also invaluable for fraud investigation and operational accountability.
- How does Traqo.ai handle master data for multi-plant operations?
- For enterprises with multiple manufacturing plants, distribution centres, or country operations, Traqo.ai maintains a hierarchical master data structure: a global master at the enterprise level contains shared reference data (common carrier codes, product catalogue, global rate cards), while each plant or country entity has its own local master data overrides (local carrier additions, plant-specific lane rates, local compliance configurations). Plant-level users see only their relevant master data, while enterprise-level admins have visibility across all entities. When a carrier is updated at the enterprise level, the change propagates to all plants automatically — unless a plant has a local override that should be preserved.
- How long does it take to onboard a new company to Traqo.ai?
- Standard Traqo.ai onboarding takes 2–4 weeks from contract signature to full go-live, depending on the number of modules deployed, the ERP integration complexity, and the volume of master data to be loaded. Traqo.ai provides a dedicated customer success manager, a structured onboarding playbook, and pre-built data import templates for all master data types. The fastest route to go-live is to start with a single module — typically RFQ and Auctions or Indent Automation — on one or two lanes, validate the workflow, then expand to additional modules and lanes in subsequent waves. Traqo.ai customers typically see full operational value within the first 30 days of deployment.
- What security certifications does Traqo.ai hold?
- Traqo.ai is built on a security-first architecture with data encryption in transit (TLS 1.3) and at rest (AES-256), role-based access control, MFA, SSO, and a comprehensive audit log. The platform infrastructure is hosted on AWS with SOC 2 Type II compliant cloud services, regular penetration testing, and automated vulnerability scanning. For enterprise customers with specific compliance requirements — ISO 27001, GDPR, PDPA (Singapore), DPDP (India) — Traqo.ai's security team provides a Data Processing Agreement (DPA) and answers security questionnaires as part of the procurement process.
- Can Traqo.ai be configured for different freight regulations in different countries?
- Yes. Traqo.ai's Platform Essentials module supports country-specific compliance configurations that activate or deactivate relevant features based on the operational geography. For India, this includes e-way bill automation, GSTIN validation, and NIC API integration. For Southeast Asia, this includes waybill format configurations, cross-border customs documentation fields, and local carrier compliance requirements. For the Middle East and Africa, it includes multi-currency support, Arabic language interfaces for carrier-facing communications, and regional compliance document templates. Each geography can have its own configuration without affecting other countries on the same platform.
Your stack →
0 of 14 modules · one platform✓ Platform Essentials active
Get started
See Platform Essentials
in your warehouse.
30-minute walkthrough on your own data. No IT team. No commitment.
Step 1 of 425%
Let's start with your company
Get Started
Talk to a freight expert.
Tell us about your fleet. We'll set up a pilot, walk you through the dashboard, and show you live tracking on your own trucks — no GPS hardware required.
- Pilot on up to 10 trucks, free for 14 days
- Live in under 5 minutes — just the driver's phone
- Direct line to our solutions team
Prefer email? Write to sales.support@traqo.io