Managed connector · OMS
IBM Sterling
Connect IBM Sterling Order Management so orders and returns processed through Sterling earn and claw back loyalty points on the member record, keyed to your Sterling order references.
What it brings to the member
IBM Sterling data, on the one verified member.
Orders → points
Orders earn points on their total, anchored to the Sterling order header key. Status is mapped through a table configured to your pipeline, never hard-coded numeric codes.
Returns → claw-back
Return-document orders reverse the points, anchored to the original order header key.
Customers → members
The bill-to party resolves to the member by your own ID or email.
How it connects
The standard API, the governed pipe.
The connector reads IBM Sterling 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
Sterling's REST API envelope over the named APIs (getOrderList / getOrderDetails / createReturn) with tuned input/output templates. Inventory Visibility is a separate product, out of scope.
Authentication
Bearer JWT, or a login call that returns a UserToken. Sterling tokens expire, so the connector re-authenticates and retries once on a 401.
What to expect
Honest about where it stands.
In design-partner validation. Sterling's order status is a configurable pipeline, so the status and document-type codes are mapped to your Sterling configuration during onboarding — the connector ships defensive defaults and never hard-codes numeric codes. Product 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.