Oracle to Talabat, without the spreadsheet.
Stock and prices from Oracle ERP published to Talabat Mart on a schedule — price-checked first — with every Talabat order written back to Oracle.
Oracle
TalabatIn one paragraph
Omniqlo connects Oracle ERP to Talabat Mart. It reads the item master and on-hand stock from Oracle through the Oracle ERP connector, checks every price against guardrails (minimum margin, maximum movement, dual approval and UAE 5% VAT), publishes per-store stock and price files out to Talabat through Talabat store files delivered over SFTP, and writes each Talabat order back to Oracle as a sales order.
Four flows. All logged.
| Direction | What | How | When |
|---|---|---|---|
| Oracle → Omniqlo | Item master, category, price and on-hand stock by location | the Oracle ERP connector | On a schedule, de-duplicated by checksum |
| Omniqlo rules | Minimum margin · max price movement · dual approval · 5% VAT | Rules engine, priority order | Before every publication |
| Omniqlo → Talabat | Per-store stock and price files out | Talabat store files delivered over SFTP | Each scheduled run, plus approved promotions |
| Talabat → Oracle | Orders as ERP sales orders, then fulfilment and cancellation status | Order capture → Oracle sales order | As orders land |
A bad price stops here — not on Amazon.
- Minimum margin per item or category
- Maximum price movement per run
- Dual approval above $1,362
- UAE 5% VAT validation
- Minimum margin✓ pass
- Max price movement✓ pass
- UAE 5% VAT✓ pass
- Minimum margin✕ fail
- Max price movement✕ fail
- UAE 5% VAT✓ pass
Oracle to other channels
Other ERPs to Talabat
Oracle × Talabat: quick answers.
How does Omniqlo connect Oracle to Talabat?
Omniqlo connects Oracle ERP to Talabat Mart. It reads the item master and on-hand stock from Oracle through the Oracle ERP connector, checks every price against guardrails (minimum margin, maximum movement, dual approval and UAE 5% VAT), publishes per-store stock and price files out to Talabat through Talabat store files delivered over SFTP, and writes each Talabat order back to Oracle as a sales order.
Do Talabat orders reach Oracle automatically?
Yes. Each Talabat order is captured in Omniqlo’s order queue and created as a sales order in Oracle against the correct store, and fulfilment and cancellation status is kept in step both ways.
What stops a wrong price reaching Talabat?
Every price from Oracle passes Omniqlo’s rules engine before publication — minimum margin, maximum price movement, dual approval above $1,362 and UAE 5% VAT validation. Items that fail are held back and counted in the run instead of reaching Talabat.
Can we sell on other channels from the same Oracle data?
Yes. Items are mapped once to each channel’s own codes, so the same Oracle record can also feed Amazon, noon, Shopify, Any store.
How long does a Oracle to Talabat implementation take?
It depends on catalogue size, store count and how Oracle exposes its data. ZaadCore confirms the timeline in a written quotation after a short discovery call.