Integration guide
Uber Eats
Compare local offers without losing delivery context.
Use this page to plan Uber Eats with NOGL. Confirm source coverage, customer authorisation and the delivery method before relying on a connection.
Start with a retail decision
Choose the review
Scope a location-specific offer review with a clearly defined comparison basket.
Make the evidence comparable
Separate item price from fees, minimum orders and location-specific promotions.
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 |
|---|---|---|
| Merchant or location · offer reference · price · fees where visible · observation time | 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
This page does not connect dispatch operations or expose merchant order data.
Do not send passwords, API keys or customer records through the contact form.