Omniqlo Omniqlo
Integration · Custom & API × noon

Custom & API to noon, without the spreadsheet.

Stock and prices from Custom integrations & APIs published to noon on a schedule — price-checked first — with every noon order written back to Custom & API.

In one paragraph

Omniqlo connects Custom integrations & APIs to noon. It reads the item master and on-hand stock from Custom & API through the connector studio, checks every price against guardrails (minimum margin, maximum movement, dual approval and UAE 5% VAT), publishes offers, stock levels and prices out to noon through the noon marketplace API, and writes each noon order back to Custom & API as a sales order.

What moves, which way

Four flows. All logged.

DirectionWhatHowWhen
Custom & API → OmniqloItem master, category, price and on-hand stock by locationthe connector studioOn a schedule, de-duplicated by checksum
Omniqlo rulesMinimum margin · max price movement · dual approval · 5% VATRules engine, priority orderBefore every publication
Omniqlo → noonOffers, stock levels and prices outthe noon marketplace APIEach scheduled run, plus approved promotions
noon → Custom & APIOrders as ERP sales orders, then fulfilment and cancellation statusOrder capture → Custom & API sales orderAs orders land

Not on Dynamics 365, SAP or Oracle? Omniqlo’s connector studio reaches most systems over REST, SFTP or scheduled file exports, with credentials encrypted at rest.

Pricing guardrails

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
Wireless earbudsAED 349.00 → AED 319.00
  • Minimum margin✓ pass
  • Max price movement✓ pass
  • UAE 5% VAT✓ pass
Published to 4 channels
Leather sneakersAED 420.00 → AED 99.00
  • Minimum margin✕ fail
  • Max price movement✕ fail
  • UAE 5% VAT✓ pass
Held back · counted in the run
FAQ

Custom & API × noon: quick answers.

How does Omniqlo connect Custom & API to noon?

Omniqlo connects Custom integrations & APIs to noon. It reads the item master and on-hand stock from Custom & API through the connector studio, checks every price against guardrails (minimum margin, maximum movement, dual approval and UAE 5% VAT), publishes offers, stock levels and prices out to noon through the noon marketplace API, and writes each noon order back to Custom & API as a sales order.

Do noon orders reach Custom & API automatically?

Yes. Each noon order is captured in Omniqlo’s order queue and created as a sales order in Custom & API against the correct store, and fulfilment and cancellation status is kept in step both ways.

What stops a wrong price reaching noon?

Every price from Custom & API 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 noon.

Can we sell on other channels from the same Custom & API data?

Yes. Items are mapped once to each channel’s own codes, so the same Custom & API record can also feed Amazon, Talabat, Shopify, Any store.

How long does a Custom & API to noon implementation take?

It depends on catalogue size, store count and how Custom & API exposes its data. ZaadCore confirms the timeline in a written quotation after a short discovery call.