Integration guide
Custom
Start with the retail question, then define the handoff.
Use this page to plan Custom with NOGL. Confirm source coverage, customer authorisation and the delivery method before relying on a connection.
Start with a retail decision
Choose the review
Review whether an existing CSV, JSON or API extract can support a bounded pilot.
Make the evidence comparable
Agree schema, ownership, access method, sample records and a measurable acceptance test.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Stable product or record key · date · market · agreed measures · source reference | Read an agreed sample | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
Feasibility, implementation effort and delivery are assessed before committing to a connection.
Do not send passwords, API keys or customer records through the contact form.