Managed connector · OMS
Manhattan Active Omni
Bring Manhattan Active Omni order, return and customer data onto the member record, so omnichannel orders fulfilled through Manhattan earn loyalty — and returns claw back — alongside your store and online activity.
What it brings to the member
Manhattan Active Omni data, on the one verified member.
Orders → points
Orders earn points on their total by your program rules. Manhattan gives no event-ordering guarantee, so ingestion is idempotent by order id and never infers lifecycle from arrival order.
Returns → claw-back
A return order reverses the points proportionally, anchored to the original order.
Customers → members
Customer Engagement records resolve to the member by your own ID or email.
How it connects
The standard API, the governed pipe.
The connector reads Manhattan Active Omni through its standard API and lands everything via the same governed pipe as the rest of Flash — idempotent, tenant-isolated, and matched to the right member.
API surface
Manhattan Active Omni REST APIs (Order Servicing, Returns Management, Customer Engagement). Manhattan's native path is event-driven (Pub/Sub); the connector starts with REST pulls and adds the event path later.
Authentication
OAuth 2.0 password grant — a client id/secret plus a service user — against your per-tenant Manhattan auth host.
What to expect
Honest about where it stands.
In design-partner validation. Manhattan does not publish its field and status schema, so the order / return / customer mappings are finalized against your tenant's own Interface Mapping Document during onboarding — not pre-assumed. Product / inventory sync is a later addition.
Configure a connection in-app under Settings → Data Sources: enter the endpoint and encrypted credentials, verify it, and run a dry-run to preview what would land — before anything goes live.