manhattan-oms

Classifies Manhattan Active Omni order operations into read, write, and destructive risk tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating Manhattan Active Omni (OMS) without deep platform knowledge leads to costly mistakes: overselling inventory by committing against stale availability, double-charging customers through blind payment retries, or releasing fraud holds that end in chargebacks. This Skill gives an AI agent the operator judgment to classify every order, payment, and sourcing action by risk before executing it. ## Core Features & Use Cases - Read/Write/Destructive Classification: Maps every OMS operation family (commit, allocate, release, settle, refund, appeasement, cancel) to a gating tier so consequential actions pause for human approval. - Availability & Sourcing Judgment: Explains Available-to-Commit vs raw on-hand, soft vs hard reservations, sourcing rules, node capacity, and safety stock so promises are made against real network supply. - Payment & Returns Lifecycle: Covers authorization, settlement, expiry and re-auth, refunds, multi-tender, exchanges, and appeasements, including gateway reconciliation rules that prevent double-charging. - Use Case: When asked to cancel a customer's order, the Skill guides the agent to check each line's settlement state first: void the authorization if nothing shipped (reversible), or process a refund plus physical return if settlement already occurred (destructive, requiring approval). ## Quick Start Ask the agent to commit a new order in Manhattan Active Omni and it will first re-read network availability, classify the commit as a reserving action, and request approval before proceeding.

Frequently Asked Questions about manhattan-oms

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

FAQPage Schema
How do I safely cancel an order in Manhattan Active Omni?

Cancel safety depends on line state: before release or settlement, cancel frees the reservation and voids the authorization, which is reversible. After settlement or shipment, it requires a refund plus a physical return, which is destructive and needs approval.

What is the difference between authorization and settlement in Manhattan OMS?

Authorization places a hold on customer funds at order commit without moving money; settlement or capture at ship actually moves the money. Treating an authorization as payment under-collects, and re-authorizing on top of a live auth double-holds funds.

Why does committing an order in Manhattan OMS risk overselling?

Committing reserves network inventory and decrements Available-to-Commit, which is eventually consistent across nodes. Two orders committing against the same last unit between availability reads can both succeed, so ATC must be re-read at commit time.

When should I use Manhattan WMS instead of the OMS skill?

Use the WMS skill for physical execution inside one node: LPNs, waves, pick/pack tasks, on-hand adjustments, and cycle counts. The OMS decides where an order sources; the node's WMS performs the actual pick and ship.

Why did a Manhattan OMS payment settlement fail after a long backorder?

Card authorizations commonly lapse in about 7 days (issuer-dependent, roughly 5 to 30). If a backorder ships after the auth expired without a re-authorization, settlement fails and the order can ship unpaid, so long-delayed orders must re-authorize first.