Dynamics 365 to Talabat, without the spreadsheet.
Stock and prices from Microsoft Dynamics 365 published to Talabat Mart on a schedule — price-checked first — with every Talabat order written back to Dynamics 365.
Dynamics 365
TalabatIn one paragraph
Omniqlo connects Microsoft Dynamics 365 to Talabat Mart. It reads the item master and on-hand stock from Dynamics 365 through the Dynamics 365 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 Dynamics 365 as a sales order.
Four flows. All logged.
| Direction | What | How | When |
|---|---|---|---|
| Dynamics 365 → Omniqlo | Item master, category, price and on-hand stock by location | the Dynamics 365 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 → Dynamics 365 | Orders as ERP sales orders, then fulfilment and cancellation status | Order capture → Dynamics 365 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
Dynamics 365 to other channels
Other ERPs to Talabat
Dynamics 365 × Talabat: quick answers.
How does Omniqlo connect Dynamics 365 to Talabat?
Omniqlo connects Microsoft Dynamics 365 to Talabat Mart. It reads the item master and on-hand stock from Dynamics 365 through the Dynamics 365 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 Dynamics 365 as a sales order.
Do Talabat orders reach Dynamics 365 automatically?
Yes. Each Talabat order is captured in Omniqlo’s order queue and created as a sales order in Dynamics 365 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 Dynamics 365 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 Dynamics 365 data?
Yes. Items are mapped once to each channel’s own codes, so the same Dynamics 365 record can also feed Amazon, noon, Shopify, Any store.
How long does a Dynamics 365 to Talabat implementation take?
It depends on catalogue size, store count and how Dynamics 365 exposes its data. ZaadCore confirms the timeline in a written quotation after a short discovery call.