manhattan-tms

Classifies Manhattan Active TM transportation operations into read, write, committing, and destructive gates.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill manhattan-tms-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manhattan-tms
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/transportation/manhattan-tms
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill manhattan-tms-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating Manhattan Active Transportation Management involves actions with very different risk levels—tendering a load commits carrier capacity and spend, a parcel manifest close starts billing, and Freight Audit and Payment moves money out—yet they look similar in the UI. This Skill gives an AI agent the judgment to classify each operation and pause consequential ones for human approval before committing freight spend or paying invoices. ## Core Features & Use Cases - Operation gating matrix: Classifies every Active TM operation family (orders, loads, rating, tendering, booking, manifesting, FAP settlement) as read, reversible write, committing write, or destructive, with matching approval gates. - Edge-state and recovery playbooks: Covers waterfall auto-roll, spot bid timers, partial acceptance, continuous moves, duplicate loads, EDI 204/990 races, and how to recover from cancellations, payment reversals, and closed periods. - Use Case: Before tendering a load, the agent re-reads tender status and carrier eligibility, shows carrier + mode + lane + total cost, and routes the tender through a human approval gate instead of committing freight spend autonomously. ## Quick Start Ask the agent to tender a load on Manhattan Active TM and have it classify the action, re-read carrier eligibility, and pause for approval before sending the EDI 204.

Frequently Asked Questions about manhattan-tms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely tender a load in Manhattan Active TM?

Rate and optimize the load first, show the carrier, mode, lane, and total cost, then tender through a human approval gate. Re-read tender status and carrier eligibility at the moment of commit, since an inbound EDI 990 acceptance or waterfall auto-roll can change state without any human action.

What is the difference between load optimization and tendering in Manhattan TMS?

Load building and optimization assign a carrier, mode, and cost but commit nothing—no capacity is reserved and no money is bound. The tender or booking is the commit point: it sends an EDI 204 offer to the carrier and binds freight spend and capacity.

Does this skill cover Manhattan SCALE TMS or only Active TM?

It covers both. The commit classifications are identical, but legacy SCALE/TLM differs operationally: data arrives in batch from the host rather than live, ship confirm does not auto-close the transportation document, and re-planning happens on interface cycles instead of continuously.

Why is cancelling a tendered load treated as destructive?

Cancelling a tendered or accepted load retracts a promise already made to the carrier, forfeits reserved capacity, and can trigger TONU, detention, or demurrage charges. A re-tender is a new commitment, not an undo, so it requires a named approver and a fresh state read.

When should I use a different TMS skill instead of this one?

Use oracle-otm, sap-tm, or blueyonder-tms when the connected TMS is one of those platforms. Warehouse execution belongs to manhattan-wms, order orchestration to manhattan-oms, pure tracking to project44 or fourkites, and customs screening to the GTS skill.