Capture · POS, OMS & ERP
Your POS, OMS and ERP — on the customer record, through one API.
The systems that run your business — point of sale, order management, ERP — hold your richest customer signals. Flash brings their data onto the one verified member through a single governed API — with managed connectors for the systems you run, and one documented integration for everything else.
PoS
Point of Sale
OMS
Order Management
ERP
Enterprise Resource Planning
Lands on
One verified member record
orders & sales → points · refunds → claw-back
The problem
Your richest customer data is trapped in operations.
In-store sales, fulfilled orders and your product catalog decide who your best customer really is — yet they live in the POS, OMS and ERP, far from the marketing record.
The richest signals never arrive
Register sales, fulfilled orders and the product catalog rarely reach the customer record — so the member profile stays half-empty, and loyalty rewards the wrong behavior.
Every system speaks differently
Each POS, OMS or ERP has its own format, auth and quirks. Wiring them one at a time means each integration breaks in its own way.
Operational truth lags marketing
When order and refund truth lives only in operations, points, tiers and next-best-actions run on stale or missing data.
Three systems, one record
What each system brings to the member.
POS, order management and ERP each connect the same way — your system calls Flash, and the data lands on the verified member.
Point of Sale
Earn and redeem at the register.
- Award loyalty points the moment a sale rings up in store
- Look up an existing member — or enroll a new one — right at the counter
- Redeem a coupon at the register: checked and burned in a single call
Order Management
Orders earn. Refunds claw back.
- Every completed order awards points automatically, by your own earn rules
- A refund reverses those points proportionally — no manual cleanup
- Your OMS calls Flash on each order and refund — no fragile webhook to host
Enterprise Resource Planning
Your master data, kept in sync.
- Push store, member and full product-catalog master data — brands, categories, products, variants, stock
- Keyed to your own system's IDs, so re-sending never creates duplicates
- Re-sync only what changed since last night — incremental, not a full reload
Shopify, Amazon and TikTok Shop have native connectors; SAP, Dynamics 365, Manhattan Active Omni, IBM Sterling and Salesforce have managed connectors. Everything else connects through the same governed API. See the developer guide →
Managed connectors
Named connectors for the systems you run.
Configure a connection in-app — no code — for these five enterprise systems. Each one sits on the same governed API and lands on the same verified member. Open any connector for the details.
Salesforce →
CRM / Order Management
Orders, customers and products via the standard REST + SOQL API.
SAP S/4HANA →
ERP
Sales orders, business partners and product master via the OData services.
Microsoft Dynamics 365 →
ERP / CRM
Sales orders and customers — Dynamics 365 CE validated; Finance & Operations scaffolded.
Manhattan Active Omni →
OMS
Orders, returns and customers — mappings finalized against your tenant document.
IBM Sterling →
OMS
Orders and returns via the REST API — status codes configured to your pipeline.
How it works
One governed API does the heavy lifting.
Whether a system uses a managed connector or calls the API directly, it runs on one documented, governed pipe — matched to the right customer, harmless to retry, and locked to your data.
One API, not a pile of connectors
Your POS, OMS and ERP — whatever the vendor or version — connect through a single documented API. Nothing to wait on a connector roadmap for.
Landed on the one member
Every sale, order and refund is matched to the same verified member — by your own ID or their email — so operations data never becomes a sixth fragment.
Safe to send twice
Send the same order or refund again and it still counts once. No double points, no double claw-backs — retries are built to be harmless.
Yours, and only yours
Each API key is permission-scoped to exactly what it needs and isolated to your data. Customer identity comes from the key, never from the request body.
Why it's different
Built to fit the stack you already run.
Most approaches either hand you a logo wall that doesn't fit, or dump operational data somewhere it can't act. Flash lands it on the live customer record, where it drives the loop.
Typical approach
Connector marketplaces
A wall of logos — but your specific POS or ERP version is the one that's “coming soon,” or fits badly.
Flash, by design
One governed API your systems call directly — vendor-agnostic, so it fits the stack you actually run.
Typical approach
Raw data dumps / reverse ETL
Operational data lands in a warehouse, disconnected from the live customer record.
Flash, by design
Orders, sales and refunds land directly on the verified member — and immediately drive points, tiers and the loop.
Typical approach
Point-to-point builds, system by system
Each integration reinvents auth, retries and de-duplication — and breaks in its own way.
Flash, by design
One auth model, retry-safe writes and incremental sync across POS, OMS and ERP alike.
What changes for the business
Operational data stops sitting in silos and starts compounding on the customer record.
Orders → points
awarded automatically by your own earn rules
Refunds → claw-back
reversed proportionally, with no manual cleanup
One member
every sale and order matched to one verified record
POS, order management and ERP landing on one verified member through a single governed API.