TMS & WMS consoles
At a glance
- TMS (Transport Management System) — the core Shipsy product. Manages orders, consignments, trips, carriers, route optimization, tracking.
- WMS (Warehouse Management System) — inventory, putaway, picking, packing, dispatch.
- Both are the source of truth that agents read from and write to via ProjectX APIs.
- CS teams need console fluency to demo, debug, and configure customer deployments.
Why this matters
Every agent ultimately reads or writes data that lives in TMS or WMS. When a WISMO agent fetches tracking status, it queries TMS. When an address checker updates a consignment address, it writes to TMS. Understanding the console means you can trace what an agent did, verify data, and debug issues without needing engineering.
TMS console — key areas
| Area | What it manages | Where agents touch it |
|---|---|---|
| Orders | Customer orders, consignments | WISMO reads order status; address checker updates addresses |
| Trips | Vehicle trips, route plans | Atlas/control tower monitors trip progress |
| Tracking | Real-time shipment location | WISMO reads last scan, ETA |
| Carriers | Third-party carrier management | RFQ agent looks up carrier rates |
| Route optimization | Auto-allocation, territory planning | Driver attendance triggers re-optimization |
| Alerts | Exception alerts (delays, SLA breaches) | Atlas/Maya receives alerts as incident tickets |
| COD reconciliation | Cash-on-delivery tracking | Nexa handles COD disputes |
WMS console — key areas
| Area | What it manages | Relevant agents |
|---|---|---|
| Inventory | Stock levels, locations, SKUs | CPG agents query inventory for fulfillment |
| Inbound | Purchase orders, GRN, putaway | — |
| Outbound | Pick lists, packing, dispatch | Order fulfillment agents |
| Returns | Reverse logistics, quality checks | Dispute/returns agents |
Accessing the consoles
| Environment | URL pattern | Auth |
|---|---|---|
| Demo | *.demo.shipsy.in | Demo credentials (ask your team lead) |
| Staging | *.staging.shipsy.in | Staging credentials |
| Production | Customer-specific URLs | Customer admin grants access via ProjectX |
Tip: Always use demo or staging for exploration. Never modify production data without explicit approval.
Common CS tasks in the console
Debugging a WISMO issue
- Open TMS → Orders → search by AWB/order number.
- Check the tracking timeline — verify last scan, current status, ETA.
- Compare what the agent told the customer vs what the console shows.
- If they differ, check: Was the agent pulling from cache? Was there a delay in carrier sync?
Verifying an agent’s tool call
- Open the AgentFleet Dashboard → find the job.
- Look at the
fetch_informationtool call — what did it request and what did it get back? - Cross-reference with the TMS console — does the data match?
Setting up demo data
For customer demos, you need realistic data in the demo environment:
- Create sample orders with various statuses (in-transit, delivered, exception).
- Assign them to carriers with tracking events.
- Configure alert rules to generate incident tickets.
- The agent can then process these in the demo.
Sources
- Slack: #projectx-support — for console access issues
- See Cowork & Claude tools for navigating the codebase behind the console
- See The agent-platform repo for how agents call ProjectX APIs
Changelog
- 26 May 2026: Full content with console areas, access patterns, and common CS tasks.