Unified Operations Console Request a demo

Built for Manhattan Active· MAO · MAWM · MATM

Every Manhattan Active environment. One console.

Run SOPs, promote SDNs in one click, and see exactly which config and response template versions live in each environment, from DEV to PROD, in every workspace.

Request a demo Watch a release move
uoc · operations overview PROD
SOP runs · 24h128+18%
Deployments14all green
Config drift3QA ≠ PROD
Messages reprocessed4120 failed
DEVv2.5.0
QAv2.5.0
UATv2.4.1
PRODv2.4.1
SDN Order routing v2.5.0 promoted to QA
SOP Store fulfillment release 12/12 passed
Drift in allocation timeout between QA and PROD
Template OrderSearch template v7 applied to 3 environments

Manhattan Active covers orders, warehouses and transport. UOC covers all three, with one place to run, deploy, compare and prove what changed.

Three workspaces · one sign-in

Switch applications without switching tools.

Each workspace shows only its own modules and records, filtered by what your company is entitled to use.

MAO

Order Management

Order pipelines, allocation, payment and fulfillment configuration, plus the SOPs that exercise them end to end.

16 modules
MAWM

Warehouse Management

Wave, task and inventory configuration, and the extension packs that customise them, promoted the same way as order changes.

15 modules
MATM

Transport Management

Carrier, shipment and rating setup, with failed-message reprocessing and response templates managed across environments.

15 modules
  • Environments
  • Projects
  • SOPs
  • SDNs
  • Response Templates
  • Config Director Profiles
  • Config Tracker
  • ConfigStore
  • Reprocess Failed Messages
  • Extension Packs
  • Mapping
  • Postman Playground
  • AI Playground
  • iFrame Views

Environment tracking

Follow every version from DEV to PROD.

A project defines the route an SDN may take. UOC records each promotion, so you always know which version each environment is running.

  1. 01
    VersionSave SDN content as an immutable version.
  2. 02
    ValidateCheck the payload against the target before it moves.
  3. 03
    PromoteDeploy to the next environment the route allows.
  4. 04
    TrackHistory shows who shipped what, and where.
Project · Order routing DEV → QA → UAT → PROD
DEVacme-dev
v2.4.1v2.5.0
DeployedDeploying…Waiting
QAacme-qa
v2.4.1v2.5.0
DeployedValidating…Waiting
UATacme-uat
v2.4.1v2.5.0
DeployedDeploying…Waiting
PRODacme-prd
v2.4.1v2.5.0
DeployedApproved · deployingNeeds review
v2.5.0 is live in PROD · history recorded for 4 environments

One-click deploys

Review it once. Ship it with one click.

Pick a version and a target the route allows, then confirm. The job runs in the background and reports queued, active and final status live, so you don't have to keep refreshing.

Promote SDN
SDN
Order routing rules
Version
v2.5.0 latest
Target
UAT · acme-uat allowed by route

Review before deploying

  • 6 configuration entries
  • 2 extension handlers
  • Replaces v2.4.1 in UAT
Deployment job QueuedActiveCompleted
  1. Accepted · job queued
  2. Validating payload against acme-uat
  3. Uploading 6 configuration entries
  4. Registering 2 extension handlers
  5. Recording history for UAT
v2.5.0 is live in UAT · 38s

Standard operating procedures

Turn runbooks into SOPs anyone can run.

SOPs are reusable request sequences built from Postman collections. Run one by hand or from a trigger, pass values from one step to the next, and keep a full history of every request and response.

  • Run manually or on a trigger
  • Chain variables across steps
  • Run history keeps the upstream HTTP status
Store fulfillment release QA
  1. POSTCreate order212ms
  2. GETFetch order status88ms
  3. POSTAllocate inventory341ms
  4. POSTRelease to store276ms
  5. PUTPick confirmation194ms
  6. POSTPack & ship305ms
  7. GETVerify fulfillment state97ms
  8. POSTPost invoice233ms
{{orderId}} captured → PS-104829
8/8 passed 1.75s

Config tracking

Spot config drift before it reaches production.

Config Tracker lines up configuration values across environments and highlights the cells that don't match.

Configuration DEV QA UAT PROD
allocation.timeoutSeconds45454530
payment.authExpiryDays7777
fulfillment.shipToStoretruetruefalsetrue
inventory.reservationTtl15m15m15m15m
ext.atpCheck.handlerv3v2v3v3
feature.splitShipmentonononon
In sync 21 Drift 3 Last checked 2 minutes ago

Config Director, upgraded

Export once. Compare any two environments.

Save export profiles for the components you care about, then export from any environment and compare side by side, with the noise filtered out and every difference marked.

  • Reusable export profiles per workspace
  • Side-by-side diff that can hide unchanged lines
  • Store snapshots in ConfigStore for later
Export profile · Order baseline
  • Order pipeline
  • Allocation rules
  • Payment configuration
  • Promotions
QA ↔ PROD 3 changes
QA 
"pipeline": "STANDARD_ORDER",
"allocation": {
  "timeoutSeconds": 45,
  "strategy": "NEAREST_NODE",
  "maxSplits": 3
},
"payment": {
  "authExpiryDays": 7,
  "retry": "EXPONENTIAL"
}
PROD 
"pipeline": "STANDARD_ORDER",
"allocation": {
  "timeoutSeconds": 30,
  "strategy": "NEAREST_NODE",
  "maxSplits": 2
},
"payment": {
  "authExpiryDays": 7,
  "retry": "LINEAR"
}

Response templates

One template version, applied to every environment.

Templates are versioned. Compare versions, then apply the one you chose to one or more environments in a single action.

OrderSearch template
v5v6v7 
{
  "OrderId": null,
  "MaxFulfillmentStatusId": null,
  "Extended": null
}
Apply v7 to 4 environments
  • DEVv6v7
  • QAv6v7
  • UATv6v7
  • PRODv6v7

The rest of the toolkit

Everything else operations teams use every day.

Reprocess Failed Messages

Find failed messages in any environment and send them through again in bulk, with every outcome tracked.

412 reprocessed · 0 failed

Extension Packs

Deploy extension packs to configured environments and keep a deployment history for each one.

History per environment

Mapping

Document field mappings and business rules between Manhattan Active and external systems, then export them to Excel.

Validated · revisioned

Postman Playground

Send a single draft request to any configured environment without building a full SOP.

Uses SOP permissions

AI Playground

Describe what you need. Supported operational actions are prepared for you to review and approve before anything runs.

Nothing runs without approval

iFrame Views

Build embedded views of Manhattan Active screens and open them right next to your operational work.

MAO workspace

Guardrails built in

Fast, without losing control.

3Manhattan Active workspaces
16operational modules
1click to promote, after review
0saved passwords ever displayed

Company-scoped records

Users only see records that belong to their own company and workspace.

Audit identity on every change

Each create and update records the account that made it and the email address it had at the time.

Review before state changes

Every action that can change an environment asks you to review and confirm first.

Secrets stay secret

Environment passwords are never shown again after you save them.

Honest background status

Runs and deployments report queued, active and final outcomes. Reopening history never re-runs anything.

Clear timeout reporting

When Manhattan Active times out, UOC says so in plain words and keeps the real upstream status.

Ship to production with confidence.

Bring your Manhattan Active environments into one console. We'll walk you through a live promotion, from DEV to PROD.