ERPNext Zalando Partner Connector

Key Features

Scheduled Zalando order pull via a Frappe scheduler event that maps each order to a standard ERPNext Sales Order with SKU resolution against the Item master

Dedicated DocTypes (`Zalando Settings`, `Zalando Article Map`, `Zalando Order`, settlement child tables) instead of overloading core doctypes with custom fields

Two-way inventory sync: `doc_event` hooks on Bin / stock changes push availability to Zalando; a scheduler job reconciles the reverse direction idempotently

Two-way price sync from ERPNext Item Price lists to the Zalando catalog, with configurable price list and currency (EUR) per channel

Separate handling for partner-fulfilled and ZFS (Zalando Fulfillment Solutions) stock so ERPNext never double-counts inbound-to-Zalando inventory

Article / listing push built from Item attributes — EAN/GTIN, size, colour, brand, season — through an article-map DocType your merchandisers control

Settlement file ingestion into settlement DocTypes with automatic reconciliation against the originating Sales Invoices (commission, returns, fees)

Idempotent sync using external-id keys and status flags so retries and webhook replays never create duplicate orders or documents

Whitelisted server methods (`@frappe.whitelist()`) for on-demand actions — force order pull, re-push a listing, re-run a settlement import — callable from the UI or the Frappe REST API

Dedicated Zalando role and role profile so channel operators work the integration without GL or purchasing permissions

Error handling and retry with rows in the Frappe Error Log plus a per-record sync-status field, so failed pushes are visible and re-runnable rather than silent

Client scripts add channel buttons, status filters and quick actions on Sales Order / Item without moving business logic into the browser

Configurable field mapping via the settings DocType so warehouse, tax template, and price list defaults are set once, not hard-coded

Built and tested against Frappe/ERPNext v15 and v16, packaged as a standard installable Frappe app on your bench

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

European fashion brands selling on the Zalando Partner Program quickly hit a wall with ERPNext out of the box. ERPNext has no concept of a Zalando order, a Zalando Fulfillment (ZFS) stock pool, or a monthly Zalando settlement — so teams end up rekeying orders from the Zalando Partner portal into Sales Orders by hand, updating stock and prices in two places, and reconciling payouts in spreadsheets. As volume grows, oversells, stale prices, missed ship-by SLAs and unexplained settlement deltas become a weekly fire drill. ERPNext's native marketplace/e-commerce integrations don't speak the Zalando Partner APIs, and generic connectors ignore the wholesale and partner-program models that European fashion actually runs on.

ECOSIRE builds a proper Frappe application — a versioned app installed on your bench alongside ERPNext — that makes Zalando a first-class channel inside your existing instance. We model the integration with dedicated DocTypes (for example Zalando Settings, Zalando Article Map, Zalando Order, and a settlement-line child table), wire behavior through hooks.py document events and scheduler events, and expose whitelisted server methods for on-demand actions. Inbound Zalando orders are pulled on a scheduled job and mapped to standard ERPNext Sales Orders (and Delivery Notes / Sales Invoices where you want them), with SKU resolution against your Item master so nothing is created blind. The connector supports both the partner-fulfilled model and ZFS, keeping the two stock realities distinct instead of collapsing them.

Technically, inventory and price sync run two-way and idempotently: a doc_event on Item / Item Price and Bin changes queues an outbound push to Zalando, while a scheduler event reconciles availability the other direction so ERPNext and the Zalando catalog converge rather than fight. Article and listing data is pushed from ERPNext Item attributes (EAN/GTIN, size, colour, brand, price) through the article-map DocType, so your merchandisers manage listings from the system they already use. Settlement files and payout data are ingested into settlement DocTypes and reconciled against the originating Sales Invoices, surfacing commission, returns and fee deltas as a report you can actually close the books against. Everything respects ERPNext permissions — we ship role profiles and a dedicated role so channel operators see Zalando data without touching your GL, and we use client scripts only for the UX niceties (buttons, filters) on top of server-side logic.

Because this is build-to-order, you are not downloading a fixed marketplace app and hoping it fits. We start with a short scoping call, confirm which flows you need (order sync only, or the full inventory/price/article/ZFS/settlement scope), and agree the exact DocType and field mapping against your ERPNext v15 or v16 instance. Typical delivery is 2–4 weeks from confirmed scope. You get the installable source for your version, deployment on a staging bench for UAT with a rollback plan, technical documentation and a user guide, a training session for your team, and a post-go-live support window. The full git repository is handed over to you, so the code is yours to keep and extend.

What you get

Installable Frappe app source code built for your ERPNext version (v15 or v16), packaged for `bench get-app` / `bench install-app`

Installation and configuration on your environment, including `Zalando Settings`, API credentials wiring, and field/warehouse/price-list mapping

Technical documentation covering DocType schema, `hooks.py` events, scheduler jobs, whitelisted methods and the sync architecture

End-user guide plus a live training session for your channel and finance teams

UAT deployment on a staging bench with a documented test plan and a rollback plan before production go-live

Post-go-live support window for bug fixes and adjustments after launch

Full git repository handover so the code is yours to own, audit and extend

Who this is for

Zalando channel / marketplace manager

Owns the Zalando Partner relationship and needs orders, listings and availability to flow into ERPNext automatically instead of being rekeyed from the partner portal, with clear visibility when a sync fails.

Operations & fulfillment lead

Runs picking, shipping SLAs and ZFS replenishment, and needs partner-fulfilled and Zalando-fulfilled stock kept separate so ERPNext availability reflects reality and oversells stop.

Finance / accounts controller

Closes the books each month and needs Zalando settlement files reconciled against Sales Invoices — commissions, returns and fees itemised — rather than reverse-engineered from a payout total in a spreadsheet.

ERPNext administrator / systems owner

Maintains the bench and instance and wants a clean, versioned Frappe app with proper permissions, scheduler events and its own DocTypes — not a pile of custom fields and manual scripts they can't upgrade.

How ERPNext Zalando Partner Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Zalando order sync	Scheduled pull into standard Sales Orders with SKU resolution	Possible but you specify and build every mapping	Generic marketplace apps rarely speak Zalando Partner APIs
Two-way inventory & price sync	Idempotent doc-event push + scheduler reconcile both ways	Achievable, but retry/idempotency is on you to get right	Often one-way or not Zalando-aware
ZFS (Zalando Fulfillment) support	Partner-fulfilled and ZFS stock modelled separately	Requires deep Zalando-model knowledge to build	Typically unsupported
Settlement reconciliation	Settlement DocTypes matched to Sales Invoices with fee breakdown	Build it yourself from scratch	Rarely included
ERPNext v15/v16 fit	Built and tested for your version as a clean Frappe app	Depends entirely on your developer's rigor	Version support varies and may lag
Permissions & roles	Dedicated Zalando role and role profiles shipped	You design and maintain them	Generic or none
Ownership & handover	Full git repo handed over — yours to extend	You own it but built it from zero	Often closed-source or subscription-locked
Delivery & support	2–4 weeks from scope, UAT + rollback + support window	Timeline and support depend on your team	Install-yourself, community support

Frequently Asked Questions about ERPNext Zalando Partner Connector

Is this a ready-made app I can download and install today?

No. It is build-to-order. ECOSIRE builds the connector against your specific ERPNext v15 or v16 instance and the flows you actually need, then installs and supports it. There is no instant download — you request a quotation and we scope it first.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on how much of the range you need — order sync alone is faster than the full inventory, price, article, ZFS and settlement scope. We confirm the exact schedule in writing after the scoping call.

How are updates and support handled after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments. Because you receive the full git repository, your team can maintain and extend the app independently, and we can quote an ongoing support or enhancement retainer if you prefer we handle upgrades across future ERPNext versions.

Does it support ZFS (Zalando Fulfillment Solutions)?

Yes. The connector keeps partner-fulfilled and ZFS stock as distinct realities so ERPNext availability and inventory sync stay accurate for both models. The exact ZFS flows (inbound, availability, returns) are confirmed during scoping.

Will it work with our existing ERPNext instance and customizations?

Yes. It installs as a standard Frappe app on your bench alongside ERPNext v15/v16 and uses its own DocTypes plus `hooks.py` doc events and scheduler events, so it integrates with your Item master, Sales Orders and Invoices without overwriting your existing setup. We validate compatibility on a staging bench during UAT before production.

How does settlement reconciliation work?

Zalando settlement files and payout data are ingested into settlement DocTypes and matched against the originating Sales Invoices, breaking out commission, returns and fees as a reconciliation report your finance team can close the month against instead of reverse-engineering a payout total.

Do we own the code?

Yes. The full git repository is handed over to you on delivery. The installable app source for your ERPNext version is yours to keep, audit and extend — there is no lock-in to a proprietary hosted service.