For technical and commerce teams
Connect loyalty decisions to the systems that run your commerce.
A loyalty decision is only as good as the data reaching it. The goal of an integration is to bring transaction, customer, campaign and reward data together so eligibility can be resolved at the moment of purchase — in store and online — and the outcome can be measured afterwards.
We do not publish a connector catalogue. Scope is agreed with your technical team against the systems you actually run.
Commerce systems
- POSIn-store transaction events
- eCommerceCart and order events
- CRM / customer dataMember profile and consent
Member and reporting surfaces
- Member walletPoints, coupons and rewards the customer can see
- AnalyticsIssuance, redemption and member behaviour reporting
Conceptual illustration of where loyalty decisions sit relative to systems you already run. It does not describe a specific transport, authentication method or data model — those are defined per implementation with your technical team.
Scoping
What an implementation needs to define
These are the decisions that determine whether a loyalty program behaves predictably once it is live. They are agreed together — none of them are assumed.
- 1
Event source
Which system is the source of truth for a completed transaction?
In-store and online transactions often originate in different systems. The implementation defines which system emits the event that loyalty decisions react to, and what counts as an eligible transaction.
- 2
Customer identifier
How is a customer recognised as the same member across channels?
One identifier has to link the in-store purchase, the online order and the customer record. The implementation defines that identifier and how it is captured at each touchpoint.
- 3
Transaction payload
Which transaction attributes do the loyalty rules actually need?
Rules can only use data they receive — for example order value, line items or categories. The implementation agrees the minimum set of attributes required for the campaign logic you plan to run.
- 4
Reward issuance and redemption
Where are points and rewards issued, and where are they redeemed?
Issuance and redemption may happen in different systems and channels. The implementation defines which system applies the reward to a transaction and how the member wallet reflects it.
- 5
Channel behaviour
Should the rule behave identically in store and online?
Some programs run one shared rule set, others deliberately differ by channel. This has to be an explicit decision, not an implementation side effect.
- 6
Error and retry ownership
Who owns a failed or duplicated transaction event?
Every integration eventually sees a failure, a retry or a duplicate. The implementation names the owner on each side, and the agreed behaviour when a transaction cannot be processed.
- 7
Reporting owner
Who owns loyalty reporting once the program is live?
Program measurement needs a named owner on your side who agrees the reporting definitions, the measurement period and how results are reviewed.
Evidence
Evidence from Gigatron
Gigatron integrated Scops with its eCommerce platform, POS systems and CRM infrastructure, with the program live from March 2025. That is the extent of what is published about the integration — the underlying architecture is not disclosed.
Results reflect the Gigatron implementation and its stated measurement period. Results vary by program design, commercial conditions, customer behaviour and execution.
For developers
Developer evaluation path
How a technical evaluation usually runs, from the first conversation to an agreed pilot scope.
1. Use-case discovery
We start from the commercial outcome you want and the moments where a loyalty decision has to happen — not from a systems inventory.
2. Technical review
Your technical team walks us through the systems in scope, where transaction and customer data live today, and the constraints we have to design around.
3. API and documentation access
Technical documentation is shared with your engineering team for the scope agreed in the review.
4. Pilot scope
A limited first scope is agreed — the channels, rules and reporting included in the pilot, and how success will be judged.
Documentation access
Scops does not publish a public API reference. Technical documentation is shared with your engineering team under a controlled process, after the technical review step above, and scoped to the systems in your evaluation.
- Request access by telling us which systems are in scope and who on your side will review the documentation.
- Security and procurement questions can run in parallel through the security review process.
Questions
Technical FAQ
Discuss your integration path
Bring the systems you already run. We will work through the event source, the identifier and the reporting owner with your technical team.