ERP connector
On-hand imported by item and by location from Dynamics 365, SAP, Oracle or any ERP with an API or file export.
Ingestion, catalogue, publication, control and orders — everything that sits between the system holding your catalogue and the places you sell it.
On-hand imported by item and by location from Dynamics 365, SAP, Oracle or any ERP with an API or file export.
Automatic pulls on a schedule, de-duplicated by checksum and logged run by run.
CSV or Excel stock files, validated server-side before anything is accepted.
The item master with category hierarchy and pricing, searchable by SKU, barcode or name.
On-hand, reserved and threshold quantities held per store rather than in aggregate.
POS codes mapped to each marketplace’s own store and item codes.
Price, promotional price and listing status maintained per marketplace.
Talabat store files and scheduled channel feeds, delivered over SFTP or API.
Percentage or fixed changes, scheduled ahead and released through an approval.
Stock and price guardrails evaluated in priority order before anything publishes.
REST, SFTP, file and ERP connectors, with credentials encrypted at rest.
Who changed what, and every sync with its checksum and row counts.
Shopify and marketplace orders collected as they land, in one queue.
Each captured order created as a sales order in your ERP against the right store.
Fulfilment and cancellation status kept in step between channel and ERP.
Orders come out ready, blocked or skipped — with the reason — before the ERP sees them.
Payment journals against the ERP invoice, one bank account per gateway — Tabby, Tamara, Stripe.
Channel shares of central warehouse stock, rounded down per item, with the remainder kept as an oversell buffer.
Sales, inventory, pricing and sync-health dashboards, plus exportable reports.
Jobs run on your schedule. Every run keeps a step-by-step log.

Orders come out ready, blocked or skipped — with the reason — before the ERP sees them.

Payment journals against the ERP invoice, one bank account per gateway — Tabby, Tamara, Stripe.

Each channel gets a share of central stock. The rest stays as an oversell buffer.

Sales, inventory, pricing and sync-health dashboards, plus exportable reports.

Jobs run on your schedule. Every run keeps a step-by-step log.
All writes pass one server-side switch.
Retries never duplicate an order.
Viewer, operator and admin.
Hashed tokens, timeouts and rate-limited sign-in.
Every change logged with who and when.
Encrypted at rest, masked on read.
A daily stock workbook emailed around and re-typed into each seller portal.
Stock pulled from the ERP on a schedule and published to every channel from one record.
A typo turns AED 420 into AED 42 — and it is live on a marketplace before anyone sees it.
Minimum-margin and max-movement rules hold the price back and count it in the run.
Orders copied from four seller centres into the ERP by hand, every morning.
Each order created as an ERP sales order against the right store, status synced both ways.
Nobody can say what a channel was sent last Tuesday.
Every export is kept with its run, checksum and row counts — provable on demand.
Every order becomes an ERP sales order. Status syncs both ways.
Order features →Any ERP. Microsoft Dynamics 365, SAP and Oracle are supported, and any other system connects through the connector studio over REST, SFTP or file exports — catalogue and on-hand in, sales orders and their status back out. SharePoint pickup of a daily stock workbook is also supported.
A rules engine evaluated in priority order before anything publishes — minimum margin, maximum price movement, dual approval above $1,362 and UAE 5% VAT validation. Items that fail are held back and counted.
Yes — each captured order is created as a sales order in your ERP against the correct store, and fulfilment and cancellation status is kept in step both ways.
Usually. The connector studio supports generic REST, SFTP and file connectors alongside the ERP ones, with credentials encrypted at rest.
Connector secrets are encrypted at rest and masked whenever they are read back. Every change is recorded in the audit log with who made it.
As an implementation with quarterly support and hosting, quoted against your channels, stores and connector count. Book a demo and ZaadCore will scope it after a short discovery.