Zedonk + Le New Black integration overview
Zedonk is a UK-based production software for fashion. Le New Black offers a collaborative B2B portal for your team and retailers, and an order-taking iPad app for your sales team.
The connector uses automated file transfer via Le New Black FTP to exchange data |
|
Zedonk and Le New Black both push and pull files |
|
The connector requires basic configuration in Le New Black and Zedonk |
Data flows
| Type | Flow |
| Customers | Zedonk ⇢ Le New Black |
| Products | Zedonk ⇢ Le New Black |
| Prices | Zedonk ⇢ Le New Black |
| Current stock levels | Zedonk ⇢ Le New Black |
| Incoming stock levels | Zedonk ⇢ Le New Black |
| Orders | Zedonk ⇠ Le New Black |
Data flow: Customers
Zedonk sends your customers with their billing and delivery addresses, their buyers and their commercial terms: payment and delivery terms, shipper, discount rate and comments.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
File: customerdata_*
Separator: ;
File format: CSV file with a header row, dropped by Zedonk on your Le New Black FTP.
Matching keys: Customer: retailer reference (Zedonk Account Number). A customer not found by it is looked up by name and country.
Import mode: Create or update → new customers are created, existing ones are updated.
Rejected rows: Rows without an Account Number are ignored and reported in the task log.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
import_mode |
add (default) / replace | string | With replace, the line associations of each imported customer are reset before the imported associations are applied |
price_list_key |
name (default) / code | string | Identifies the price list of each customer: by its code or its name |
sales_rep_key |
email (default) / code | string | Identifies the sales rep of each customer: by its e-mail or its code |
sales_manager_key |
email (default) / code | string | Identifies the sales manager of each customer: by its e-mail or its code |
sales_admin_key |
email (default) / code | string | Identifies the sales admin of each customer: by its e-mail or its code |
Callouts
- Countries must be given as ISO country codes.
- Every column of the template must be present in the file: a file with a missing column is rejected as a whole and reported in the task log.
- Price list and sales rep assignments are not part of the default file: set them in Le New Black.
Data flow: Products
Zedonk sends your products with their collections, categories, colours and variant details. The Zedonk Description becomes the product name, minimum and maximum order quantities are imported per product, and the wholesale and retail prices of the file go to your default price list.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
File: productdata_*
Separator: ;
File format: CSV file with a header row, dropped by Zedonk on your Le New Black FTP.
File structure: One row per size: Model (product), Fabric Name (colour), Size and EAN13
Matching keys: Product: model. Variant: fabric name. Size: size name, with its EAN13.
Import mode: Create or update → new products and variants are created, existing ones are updated.
Created on the fly: Collections and categories
Rejected rows: An EAN13 already used by another item in Le New Black is ignored and reported in the task log.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
fabric_key |
code (default) / name | string | Identifies a variant within a product: by its fabric code or its fabric name |
product_create_is_allowed |
true (default) / false | bool | With false, products missing from Le New Black are not created: only existing products are updated |
sizing_create_is_allowed |
true / false (default) | bool | Whether a size range missing from Le New Black is created |
product_sizing_update_is_allowed |
true / false (default) | bool | Whether the import can change the size range of an existing product |
Callouts
- The size range of each product must already exist in Le New Black: a product whose set of sizes matches no existing size range is rejected.
- Every colour of a product must have the same sizes as the product.
- The size range of a product that already exists in Le New Black cannot be changed through the import.
- Every column of the template must be present in the file: a file with a missing column is rejected as a whole and reported in the task log.
Data flow: Prices
Zedonk sends a wholesale and a retail price for each of your price lists.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
File: pricelistdata_*
Separator: ;
File format: CSV file with a header row, dropped by Zedonk on your Le New Black FTP.
Price level: Per variant: one wholesale price and one retail price per variant and price list, shared by all its sizes.
Matching keys: Price list: price list code. Product: model. Variant: fabric name.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
fabric_key |
name (default) / code | string | Identifies the variant of a price row: by its fabric code or its fabric name |
price_list_key |
name / code (default) | string | Identifies the price list of a price row: by its code or its name |
price_level |
variant (default) / sku | string | Level of the prices: one per variant or one per size |
Fields mapping
Complete mapping: every field the connector reads is listed.
| Le New Black field | File column | Comment |
Price list |
Price list | |
Model |
Model | |
Variant |
Variant | |
Price |
Price | |
Retail price |
Retail price |
Callouts
- Price lists must exist in Le New Black first: your account manager creates them with the same codes as the price list values sent by Zedonk.
- Products and variants must already exist in Le New Black: import products before prices.
Data flow: Current stock levels
Zedonk sends the available-to-sell quantity of each EAN13.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
File: atsdata_*
Separator: ;
File format: CSV file with a header row, dropped by Zedonk on your Le New Black FTP.
Required columns: EAN13, Quantity
Matching keys: Size: EAN13.
Import mode: Add by default → only the sizes in the file are updated, the others keep their quantity. Replace, when set up → the stock of every size is set to 0 before the quantities are applied. Negative quantities are imported as 0.
Rejected rows: Rows whose EAN13 is unknown in Le New Black are ignored and reported in the task log: import products first.
Configuration
| Setting | Values | Type | Comment |
import_mode |
add (default) / replace | string | With replace, the stock of every size is set to 0 before the quantities are applied |
lnb_sku_identifier_column |
ean13 (default) / sku | string | Le New Black key the stock rows are matched against |
lnb_stock_column |
quantity (default) / incoming_quantity | string | Le New Black quantity updated |
Data flow: Incoming stock levels
Zedonk sends future stock quantities with their expected date, for each EAN13.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
File: atsincoming_*
Separator: ;
File format: CSV file with a header row, dropped by Zedonk on your Le New Black FTP.
Required columns: EAN13, Quantity, Date
Matching keys: Size: EAN13.
Import mode: Add by default → the incoming quantity and date are updated for the sizes in the file, the others keep their values. Replace, when set up → the incoming quantity and date of every size are cleared before the file is applied. Negative quantities are imported as 0.
Rejected rows: Rows whose EAN13 is unknown in Le New Black are ignored and reported in the task log: import products first.
Configuration
| Setting | Values | Type | Comment |
import_mode |
add (default) / replace | string | With replace, the incoming quantity and date of every size are cleared before the file is applied |
lnb_sku_identifier_column |
ean13 (default) / sku | string | Le New Black key the stock rows are matched against |
update_incoming_date |
true (default) / false | bool | Whether the incoming date is updated along with the incoming quantity |
Data flow: Orders
Orders you move to the exported status (Invoicing by default) are sent to Zedonk.
Reference
Trigger: Scheduled task, active once Le New Black has set up the flow for your brand. It can also be run on demand from the Integration center.
Orders exported: Status Invoicing
Integration status: Only orders whose integration status is Pending are exported, and it becomes Successfully sent after export. The selection can be adapted during set-up.
Status after export: Closed
Blocked orders: An order that fails a check keeps its status and gets the integration status Blocked, with the reason in the task log. It is not sent again until you set its integration status back to Pending from the orders list (action Set integration status to Pending).
Limit: No limit
File: orders- followed by the export date and time, .csv: one file per export
Separator: ;
File format: CSV file with a header row, placed on your Le New Black FTP for Zedonk to collect.
File content: One row per ordered size: order details, customer reference, billing and delivery addresses, product, colour, size, EAN13, SKU, quantity, unit price, discount rate, currency and suggested retail price
Matching keys: Customer: LNB retailer reference, sent as the Zedonk Account Number. Products: EAN13.
Configuration
| Setting | Values | Type | Comment |
validate_skus |
true / false | bool | With true, an order with a line whose product has no EAN13 is blocked |
Callouts
- An order containing a product without an EAN13 code is blocked as a whole: none of its lines is exported.
- An order whose customer has no Zedonk customer reference in Le New Black is blocked. Other orders are still exported.
- Order lines with a zero quantity are left out of the file; an order without any line is blocked.
- After the order has been exported from Le New Black, any further change must be made directly in Zedonk.
Integration project
Who's assigned from your team?
Your Zedonk administrator, or an IT profile within your company who is familiar with your specific setup. A Sales Manager who understands your business and your merchandising strategy.
Who's in charge at Le New Black
Your account manager at Le New Black takes care of the whole process from day 1:
- Asking questions about your specific Zedonk setup and sales process.
- Collaborating with Zedonk as they configure the data files to import and export.
- Generating and exporting test orders to Zedonk.
- Keeping your team updated throughout the process and addressing delays on either side.
- Working with you and Zedonk to troubleshoot any unexpected issue after launch.
Timeline
A standard integration will take a few hours to get up and running.
Integration monitoring
Once the connector is set up, the Integration center of your back-office gives you a set of tools to manage and monitor the integration:
- Task logs, for continuous monitoring and troubleshooting (for example a missing EAN13 or retailer reference that prevents an order from being exported)
- Running a task on demand, to push or pull data at once
- A preview of the data before the actual import (only available on some connectors)
- E-mail notifications per task, set up on request: exported and blocked orders, import errors
- The integration status of each order in the orders list (Pending, Successfully sent, Blocked), which you can set back to Pending to send an order again
Each import task processes one file per run: when several files are waiting, the next ones are processed on the following runs. A file that cannot be read or misses a required column is set aside and reported in the task log, so it does not hold back the next files.
Comments
0 comments
Please sign in to leave a comment.