Connect Zalando to your inventory, from sandbox to live
Agilo publishes your catalog to Zalando through zDirect. The connection starts in the sandbox with a client ID and secret: you pick the merchant, sales channels, and default logistic centre. Production stays locked until the sandbox checks pass and zDirect opens live access. Stock and prices follow your channel price lists. Orders land in Agilo. Returns wait for a decision, and every shipment still needs a return label.
Sandbox first, then production
Enter the API credentials of your zDirect app. Agilo checks the merchant, channels, and logistic centres, then asks you to confirm which channels to manage. Production writes stay closed until the sandbox checks succeed, zDirect opens live access, and you confirm Agilo will be the only system writing to Zalando. After that, Agilo imports the state already in production instead of overwriting it.
Outlines and attributes before every submit
Zalando only accepts values from its outlines: category, size, color, size chart, and composition have to be confirmed before a new article is published. Agilo proposes matches (exact or from AI) and stores them. An uncertain value stays in review. From the product drawer you set size chart and materials, recheck the draft, and submit once. In the sandbox that submit stays validation-only.
Stock and prices per sales channel
Each Zalando channel has its own currency and price list. Agilo starts from the variant EANs, computes the price from the channel list, and sends stock and price only for the channels you selected. In the sandbox those updates are validated and do not go on sale.
Orders and returns with a decision when needed
Imported orders land in Orders. The Zalando console lists exceptions only: unmatched EAN, insufficient stock, or an invalid GTIN. Before acceptance, Agilo reads the order from Zalando again and checks every line and stock level. Returns arrive with tracking and a reason; you accept or refuse them after a refresh, and accepted items go through inspection.
Shipping with a return label and package insert
Zalando requires a return label in every parcel. From the fulfillment panel you generate it with a connected broker, or you enter the return tracking and upload the PDF. In Zalando settings you set the store name, return address, instructions, reason codes, and legal footer printed on the package insert.
Frequently asked questions
- What do I need to connect Zalando to Agilo?
- A zDirect app with a client ID and client secret, plus permissions on catalog, stock, prices, orders, and returns. You connect from Agilo's Integrations page: Agilo verifies the credentials in the sandbox, lists merchants and channels, and asks you to pick them. Zalando portal email and password are neither requested nor stored.
- When does Agilo start writing to production?
- After three conditions at once: the sandbox checks have passed, zDirect has opened production access, and you have confirmed Agilo is the only system writing to that account. Before any write, Agilo imports the state already there, so it does not overwrite the live catalog.
- What happens when Zalando rejects a product?
- The product stays in the console with the status codes Zalando returned. Open the drawer, fix attributes or mappings, recheck the draft, and submit again. A second submit does not post if the payload is unchanged.
Bring your catalog to Zalando
Connect zDirect in the sandbox, confirm the mappings, and review the first sync.
Start with Agilo