uRoutes By SILODISAWarehouse floor
WMS
WMS: Full inventory visibility, intelligent stock statistics, and EDI connectivity from your corporate platform to SILODISA’s WMS.
Validated inventory
uRoutes · software ecosystem
From the warehouse to last mile on one data thread.
uRoutes · software ecosystem
From the warehouse to last mile on one data thread.
More than square meters and trucks: a closed information loop. We capture signal in the field and warehouse, consolidate it, interpret it, and return it as clear decisions: routes, locations, counts, completed deliveries, and alerts.
Explicit operating goal: on time, complete, damage-free, with inventory accuracy under control — and the fewest moves possible (fewer forklift trips, fewer round trips, fewer picking errors).
Technology reduces friction, prevents rework, and makes predictable what logistics often handles reactively.
Three uRoutes programs — WMS, TMS, and CRM — and three ways to contract: 3PL warehousing, 3PL distribution, or software only. With Silodisa warehousing or transport, all three programs ship in the same contract and platform license can be $0; what we quote by volume is moves, route destinations, cycle-count positions, dashboard hits, and API traffic — not per-user seats or “buying CRM separately.” Standalone: monthly base per module plus usage per the catalog.
Watch ecosystem videouRoutes · data loop
Closed data loop
One thread: signal on the floor → consolidation → rules/KPIs → decision → measurable result; the loop feeds the next day.
01
Signal
Field & warehouse
02
Consolidate
Single source of truth
03
Interpret
Rules & KPIs
04
Decide
Routes, slots, alerts
05
Outcome
On time & complete
Continuous loop
Today's operational outcome feeds tomorrow's orders, rules, and plans — without breaking the thread across modules.
The three programs
WMS, TMS, and CRM — what each one is, and why uRoutes
No “enter technology and guess.” These are three products we run every day in our DCs and on real routes: inventory lives where product moves, routing is solved with OR-Tools, and the customer sees proof on the same dataset — not a parallel spreadsheet.
WMS
Warehouse Management System
The system that governs DC floor operations: locations, inbound, outbound, cycle counting, inventory accuracy (IRA), and who is allowed to do what. Without a serious WMS, traceability does not hold up in an audit.
Goods → location → order → dock What it covers in operations
- Receiving, putaway, replenishment, picking, shipping, and adjustments under rules.
- WMS web terminal and floor app: rack scanning keeps the inventory master current (not to be confused with transportation routing).
- Cycle counts, QA walls, and visibility for office teams and auditors.
Why uRoutes (not a generic WMS bolted onto a different TMS)
- Our WMS: operated in live sites; not a slide-deck implementation theory.
- Same master data as TMS and CRM: a warehouse move links to delivery and the client view.
- Fewer forklift miles and pick errors because rules and UI were built for high-volume work in Mexico.
TMS
Transportation Management System
Turns orders and stops into executable routes: time windows, capacity, cost per stop, control tower, and driver app. Without a TMS, transportation lives in chat threads and spreadsheets.
Orders → route plan → execution → close What it covers in operations
- Routing and re-planning; OR-Tools with real constraints (not just “draw lines on a map”).
- Driver app, proof of delivery, document reconciliation, and read-only deliveries dashboard (map, in-transit, authorized, liquidated, POF, SOS).
- Cost per route and visibility for finance and ops.
Why uRoutes
- A serious optimization engine (VRPTW / constraints) on the same stack as the warehouse.
- Mobility and dashboards included: execute and close with evidence, not miscellaneous screenshots.
- Fewer empty miles and retries because plan and execution share one data language.
CRM
Customer view — portal and proof toward your client
CRM layer: customer delivery portal (read-only) — shipments, SLA, POF, and photos without money fields. DC inventory to the client is the WMS program (warehouse client portal). The full deliveries tower (ops dashboard) is TMS.
Ops → evidence → client view What it covers in operations
- Customer delivery portal (CRM): in transit vs liquidated, POF, evidence, and SLA (operational only, no financials).
- The inventory-to-client portal belongs to the WMS family, not CRM.
- Same WMS/TMS/Mobility thread — the client sees what was agreed, not internal tower screens.
Why uRoutes
- Fed by the same WMS and TMS: no month-end CSV reconciliation theater.
- Built for 3PL: the brand owner sees what they must audit, not cryptic internal screens.
- Retention and renewal: operational transparency as a product, not a promise.
Pages by family
Each program with its operational flow and a reserved space for video.
Overview video
One operator. Eleven modules. One source of truth.
A single narrative of the uRoutes ecosystem before you dive into each program.
uRoutes · system map
Layered architecture: from the street to the rack, one dataset.
An enterprise-style logistics platform: each layer serves a different actor (truck, forklift, inventory office, brand customer, IT). Click a module to jump to its product sheet.
- 01Distribution
- 02Warehouse · floor
- 03Warehouse · office
- 04Customer / brand
- 05IT · integration
- 06Platform
Browse by operating layer
01
Distribution
Layer · Distribution (last mile)
Like TMS + VRP optimization: plan, execution on the road, and control tower.
02
Warehouse · floor
Layer · Warehouse — floor
RF / WMS mobile terminal: moves and counts with scanning.
03
Warehouse · office
Layer · Warehouse — office & engineering
IRA, cycles, slotting, and dock analytics — labor & inventory analytics.
04
Customer / brand
Layer · Logistics customer (CRM)
uRoutes CRM (read-only): your brand sees inventory, shipments, and the same truth as the floor — no rack-operator WMS login.
05
IT · integration
Layer · Integration
Operational iPaaS / API gateway: ERP, EDI, and apps against the same base.
06
Platform
Layer · Governance & access
Multi-tenant IAM + front door: fewer loose URLs and passwords.
Suggested order: (1) last-mile family → TMS; (2) warehouse family → WMS; (3) platform family → CRM (client views, proof) + integration and governance. That locates pain on the road, in the rack, or in client-facing closure.
uRoutes · differentiation
Differentiation
Why the difference shows
Four product decisions: instrumentation, engine, visibility, and value model — direct message with technical backing.
uRoutes · product decisions
Real instrumentation
Built for actual Mexican operations — not a US template.
Modules designed for Mexico: multi-DC, delivery windows, mixed warehouse + last mile, device-grade evidence.
Enterprise-grade routing engine
Serious optimization (CVRPTW / OR-Tools), not just “drawing on a map”.
CVRPTW and OR-Tools with refinement on real maps; cost, utilization, and sustainability KPIs when applicable.
Visibility without chasing data
What happened on the floor today shows on the dashboard today — same ledger.
Inventory, dwell, shipments, receipts, and cycle counts tied to daily operations.
Integrated value model
One ecosystem: analytics + execution; not dozens of disconnected licenses.
Analytics, optimization, and execution in one ecosystem: you pay for outcomes and continuity, not every export or “extra layer”.
uRoutes · architecture
Functional architecture
WMS, TMS, and CRM — three programs, one data thread
Warehouse floor on the WMS; route, fleet, and cost on the TMS; CRM with client views and proof toward your brand — integration and governance on the same master record.
uRoutes · product architecture
Capture
If it was not logged with time and context, for the system it did not exist.
App at dock and on the road: scan, photos, signatures, GPS, auditable events.
Calculate
Fewer kilometers and fewer blind decisions; the engine proposes, you authorize.
Optimization and analytics engines: OR-Tools routes, ABC, putaway, IRA, and suggestions.
Communicate
Same figure in control tower, management, and logistics client.
Operational dashboards, uRoutes CRM (client views and proof), exports, and alerts — the same number on the floor, tower, and customer.
Editorial frame
Note: this content is narrative and operational marketing; it does not replace technical sheets, PRDs, or contracts. Commercial figures and terms: subject to formal proposal.
uRoutes · product sheets guide
How to read each product
Start with the stack-aligned map: last mile and routing (uRoutes TMS), warehouse and inventory (uRoutes WMS), customer-facing CRM plus platform governance and integration (APIs, EDI). Each sheet includes market analogy, data flow, benefits, and explicit limitations.
Each sheet includes: operating layer (distribution / warehouse / customer), who runs it, TMS / WMS / CRM analogy, data pipe, inputs and outputs, benefits, and explicit limitations.
No operational silos
One data engine, three layers
We eliminate operational black boxes. Our digital engines (WMS, TMS, and CRM) run in real time, creating an optimal ecosystem with guaranteed traceability — from accurate inventory to perfect orders and deliveries (POF), delivery confirmation, movement analytics that help you sell better, and meeting contracts, SLAs, and agreed commitments.
uRoutes By SILODISA
uRoutes By SILODISADistribution & fleet
TMS
Routing, driver app, document reconciliation, and read-only deliveries dashboard (live / authorized / liquidated, POF, map, SOS) — one Mobility thread.
Plan → route → evidence → liquidation
uRoutes By SILODISAClient facing
CRM
Read-only portals for the brand: DC inventory to the client is the WMS program (warehouse client portal); CRM covers the customer delivery portal (POF, SLA, photos, no financials). The operational deliveries tower lives in TMS.
Transparency & proof for the client
Inside uRoutes
Each module with input, engine, and output — mapped to real ops: inventory, routes, and closure with your customer.
Violet = administration (Admin), green = warehouse (WMS), blue = transport (TMS), amber = CRM to the client.
Admin — platform & compliance
Tenant governance (Web Admin) and document audit on Drive.
Admin · PlatformADMIN
ADMIN · System|webadmon / Firebase Admin
Web Administration
ADMIN-uRoutes-WebAdmin
Web Administration — central panel on Firebase and Firestore: companies, users, logs and statistics for tenant governance.
Multi-tenant (companies / projects)Firebase Auth + Firestore rulesChange logs
Operational Workflow
Inputs
- Organization and project onboarding
- Users, roles and permissions per module
- Changes subject to audit
Processing Engine
Centralized governance
After sign-in (initial credentials + Firebase Auth), the admin manages organizations and permissions with Firestore security rules.
Outputs
- Accounts with correct scope
- Consultable audit trail
- Clean separation between tenants
Web Administration
Admin · PlatformADMIN
ADMIN · System|drive-audit-tool
Document audit
ADMIN-uRoutes-DriveAudit
Document audit — Drive audit at metadata and filename level (file contents not read), FastAPI UI aligned with ecosystem login.
Metadata and namingPermissions and folder structureFastAPI
Operational Workflow
Inputs
- Authorized Drive space
- Policy configuration per project
- Compliance rules
Processing Engine
Metadata inspection
Connects to the authorized Drive space and reports naming, permissions or structure compliance per project settings.
Outputs
- Compliance report
- Findings per folder or file
- Evidence for review
Document audit
WMS — warehouse & inventory
Putaway 3D, WMS tower, cycle counts, store stock, and warehouse client portal.
WMS · WarehouseWMS
WMS · System|web_dashboard_eficiencia
Smart Putaway 3D
WMS-uRoutes-SmartPutaway3D
Smart Putaway 3D — warehouse optimizer (Flask): analyzes movement history (putaway, picking, shipping), ABC rotation, FEFO expiry when relevant, and rack topology; per-SKU scores, Smart Putaway recommendations and heat maps — with 3D visualization when deployed (`/rotacion`).
ABC and stage-time analyticsSmart Putaway and internal path hintsHeat maps and 3D view (when deployed)
Operational Workflow
Inputs
- Movement history and material master
- Layout / slot topology
- Business rules (zones, constraints, expiry)
Processing Engine
Model → score → floor tasks
Real data weights distance, rotation, and risk; suggestions become actionable work (e.g., via the floor terminal).
Outputs
- Per-SKU location scores
- Smart Putaway recommendations
- Signals for relocation projects with clearer ROI
Smart Putaway 3D
WMS · WarehouseWMS
WMS · System|uroutes-dashboard-v2 (Flask)
Control Tower (WMS)
WMS-uRoutes-WarehouseTower
Control Tower (WMS) — Flask dashboards on MySQL: indicators and APIs over operational inventory (email/token users and site selection). Consolidated supervision on Cloud Run or DB-proxied environments.
KPIs per siteConnection to operational MySQLEmail/token session
Operational Workflow
Inputs
- Operational inventory database
- Site / user selection
- Dock and floor events
Processing Engine
Dashboard consolidation
Connects to the operational database; consolidated view for supervision without replacing transactional floor capture.
Outputs
- Unified operational visibility
- Signals to prioritize actions across sites
Control Tower (WMS)
WMS · WarehouseWMS
WMS · System|uRoutes-Inventario-Conteos-Ciclicos/app
Mobility — counts & transfers
WMS-uRoutes-CyclicCountsApp
Mobility — counts & transfers — Android floor app: scan HU and location, guided transfers, cycle counts, and quantity confirmation with user, time, and context — aligned with unified uRoutes login.
Barcode / QR scanningRole-based flowsHTTP integration with warehouse backend
Operational Workflow
Inputs
- Move or count tasks per policy
- HU read and origin/destination
- Confirmed quantities
Processing Engine
Guided execution at location
The app validates against business rules; each event feeds IRA and dashboards.
Outputs
- Inventory transactions with traceability
- Cycle count results and gaps
- Early signal for supervision
Mobility — counts & transfers
WMS · WarehouseWMS
WMS · System|appInventarioTiendas
Store inventory mobility
WMS-uRoutes-StoreInventory
Store inventory mobility — Node.js and Capacitor (Android): products, in/out, low-stock alerts, stats and history with local SQLite; REST APIs for catalog, stock and reports.
Reorder alertsLocal SQLiteREST for catalog and stock
Operational Workflow
Inputs
- Sales or exits (POS or other)
- Local stock by SKU / min location
- Reorder and mix policies
Processing Engine
In-store monitoring
Staff log moves from browser or device; environment-based authentication.
Outputs
- Replenishment signals
- Shelf visibility
- Lower avoidable shrink risk
Store inventory mobility
WMS · WarehouseWMS
WMS · System|web_dashboard_cliente de bodegas
Warehouse client portal
WMS-uRoutes-ClientWarehousePortal
Warehouse client portal (WMS, read-only) — customers or external areas consult inventory, inbound and outbound, occupancy heat map and multi-site support; same operational data source as the floor, without transactional WMS access.
MySQL auth + dynamic DB bindingHeat-map APIs without write on query modelMulti-site
Operational Workflow
Inputs
- Operational core data (inventory, movements)
- What each customer is allowed to see
- Optional SLA rules
Processing Engine
Read-only view publishing
Balances and events filter per agreement; customers browse authorized information without touching parameters or transactions.
Outputs
- 24/7 portal for inquiry
- Consistency with internal boards
- Evidence for service reviews and sales
Warehouse client portal
TMS — transport & tower
OR-Tools routing, driver app, and read-only deliveries portal.
TMS · TransportTMS
TMS · System|webOptimizador
Routing engine
TMS-uRoutes-RouterEngine
Routing engine — spreadsheet import, CVRPTW optimization (OR-Tools), interactive map, manual edits with Google Maps and Firestore authorization; once authorized, the itinerary goes to Mobility.
CVRPTW / OR-Tools optimizationInteractive map and plan KPIsAuthorization handoff to mobile execution
Operational Workflow
Inputs
- Orders and destinations (import or capture)
- Fleet and constraints (capacity, windows, pickup/delivery)
- Cost parameters (fuel, tolls, service times)
Processing Engine
Route optimization engine
The solver assigns stops to vehicles and sequencing under constraints; the planner validates on the map, edits and authorizes the plan.
Outputs
- Routes and stop order per unit
- Estimated operational cost of the plan
- Authorized plan ready for Mobility / tower
Routing engine
TMS · TransportTMS
TMS · System|appEntregas
Mobility — deliveries
TMS-uRoutes-MobilityApp
Mobility — deliveries — Android app for drivers and last mile: itinerary, proof (photos, signature), incidents, settlement, Firestore/Storage sync and offline-first work.
Offline-first modePOD and stop evidenceSOS and route events
Operational Workflow
Inputs
- Authorized itinerary or trip
- Driver actions at each stop
- GPS signal and incident events
Processing Engine
Execution and capture on the road
The driver executes the trip; evidence and status sync to the cloud; tower and customer align with field reality.
Outputs
- Digital dossier per stop
- Trip states for core and TMS
- Data package for settlement and audit
Mobility — deliveries
TMS · TransportTMS
TMS · System|silo_web_dashEntregas
Deliveries portal
TMS-uRoutes-Delivery
Deliveries portal — web console (FastAPI + Firestore): order status, live fleet, settled history and analytics. Read-only; does not replace field capture (that is Mobility).
Live map and alarmsAuthorized vs liquidated layersPOF, plan vs actual, analytics, export
Operational Workflow
Inputs
- Mobility event stream and plan references
- Session and filters per tenant / DC
- POF rules and thresholds
Processing Engine
Read-only aggregation
Authorized users browse a safe read layer without mutating critical collections from this surface.
Outputs
- Unified operational dashboards
- KPIs and incidents in archive
- Exports for finance and quality
Deliveries portal
CRM — client-facing
Customer delivery portal (read-only); inventory to the client sits under WMS.
CRM · ClientCRM
CRM · System|webDashboardCliente
Customer delivery portal
CRM-uRoutes-ClientPortal
Customer delivery portal (CRM, React/Vite) — web portal for your customers: delivery status with session backed by the deliveries API (same contract as the internal portal). Narrow view: in-transit vs liquidated, POF and evidence without exposing costs or tower internals.
In transit vs closedCustomer-facing POFPOD evidenceNo cost layer
Operational Workflow
Inputs
- Customer-scoped trips and stops
- Contract SLA / POF thresholds
- POD assets from Mobility
Processing Engine
Brand-only filter + evidence-first
The customer signs in and sees map and data per API contract without calling the call center on every order.
Outputs
- Brand compliance view
- Operational in-transit vs liquidated list
- Audit-ready evidence with retailers
Customer delivery portal
uRoutes · next step
Ready for the next step?
Schedule a logistics maturity diagnostic: no giant project commitment on day one. We show how each module fits your operation.
Book a conversationuRoutes · price list
Commercial
uRoutes cost reference (MXN)
All figures in Mexican pesos (MXN), plus VAT. We do not charge by named user seats: pricing follows usage (moves, destinations, dashboard hits/API calls) and, when needed, add-ons for concurrent peak sessions on the tower (Cloud Run + SQL load). With Silodisa warehousing or distribution, platform license can be $0 and operating usage is billed. Software-only: monthly base per module plus variable rows below (aligned with B2B logistics SaaS norms and cloud infra cost).
uRoutes · cost reference
Software only
Monthly base per module (not per user) + usage: moves, destinations, dashboard hits, API calls — overages and concurrency per table.
With Silodisa warehouse / routes
$0 platform license; same usage (and hit) model so cost tracks real volume and cloud load.
Integration
APIs, EDI, and connectors so ERP and channels talk to uRoutes with data governance.
Commercial reference — same numbers as the price table
| Module | Monthly licensesoftware only (MXN) | Variable usageMXN per event, hit, or tier | With Silodisa servicelicense vs. usage |
|---|---|---|---|
| WMS — warehouse management | $52,000 MXN/mo | Internal move $6/move · Position read (cycle count) $2/pos. | $0 platform license with Silodisa warehouse · Moves and reads billed by usage (not per user) |
| Route optimizer | $38,000 MXN/mo | Destination $38 (with lat/long) · $45 without coordinates · Calc-only $3 · $4 without coords. | $0 license with Silodisa distribution · Per-destination usage; no per-seat license |
| Mobility driver app | $6,500 MXN/mo | Delivery destination $32 (with lat/long) · $38 without coordinates | $0 license with Silodisa route ops · Per destination served (drivers concurrent, not charged as “users”) |
| Deliveries dashboard (TMS) | $15,500 MXN/mo | Includes 60,000 hits/mo; +$125/1k extra hits · +$1,800/mo per +20 concurrent peak sessions | $0 license with Silodisa ops · same hit & overage rules; not priced per viewer seat |
| Counts dashboard | $13,500 MXN/mo | Includes 60,000 hits/mo; +$98/1k extra hits · +$1,800/mo per +20 concurrent peak sessions | $0 license with Silodisa DC service · usage-based queries |
| Efficiency dashboard | $16,500 MXN/mo | Includes 50,000 hits/mo (heavier queries); +$175/1k extra hits · +$1,800/mo per +15 concurrent peak sessions | $0 license with Silodisa service · hit-based metering |
| uRoutes CRM — client read-only view | $8,900 MXN/mo | Includes 40,000 hits/mo; +$145/1k extra hits · +$1,800/mo per +20 concurrent peak sessions | $0 with Silodisa service · hit overages by real traffic |
| APIs + EDI + integration | $42,000 MXN/mo | $0.24/API call (machine events and queries) | Integration scope packages; Silodisa ops often includes go-live; API overages by traffic |
MXN + VAT. Not a per-user model: cost tracks real usage. WMS: internal moves and per-position reads. TMS: per destination (higher without coordinates); Mobility vs optimizer channel rates; calculation-only mode for reference plans only. Dashboards & CRM: monthly hit bundles; overage per 1,000 requests; optional concurrency band surcharges. APIs: per call after bundle. Reference 2026; formal proposal by volume, metering, and SLA.
Integrated estimator · MXN + VAT
Reference costs and pricing
Four views: physical warehouse, distribution (freight + routing tech), uRoutes software by taxonomy, and consolidated summary. Use each tab independently for what you want to quote.
1 · Physical warehousing (DC)
Warehouse rates, pallet inbound, and logistics moves. Does not include uRoutes WMS license — use the Software tab for that.
Warehouse estimate (ranges)
Storage · DryMX$25,000 – MX$34,500 /mo
Pallet inboundMX$5,600 – MX$7,512 /mo
Monthly subtotalMX$30,600 – MX$42,012
Total 1 month (cumulative)MX$30,600 – MX$42,012
uRoutes · commercial fit
Fit
Who is software rental for?
Three typical profiles. If one fits, the next step is a short conversation with a focused demo.
uRoutes · rental profiles
You run your own warehouses
WMS, counts, and uRoutes CRM toward your customer without building a generic 3PL.
Inventory accuracy, floor efficiency, and visibility for your buyer — the same data in rack and on screen.
You own the fleet
Route plan, mobile execution, and delivery closeout in one story.
From optimizer to driver to dashboard: fewer “has it left yet?” calls.
You integrate ERP or marketplaces
Synchronized events and masters — fewer Excel bridges and double entry.
Serverless layer and API contracts meant for production, not just demos.
uRoutes · demo request
Demo & contact
We show real flows based on your priority product family.