ApparelMagic + Le New Black integration overview
ApparelMagic is a cloud-based ERP and PLM software specialised in the apparel industry. 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 the ApparelMagic API to exchange data (read docs) |
|
Le New Black drives all data flows: it triggers every push and pull operation |
|
The connector requires basic configuration in Le New Black and ApparelMagic |
Data flows
| Type | Flow |
| Customers | ApparelMagic ⇢ Le New Black |
| Products | ApparelMagic ⇢ Le New Black |
| Product images | ApparelMagic ⇢ Le New Black |
| Prices | ApparelMagic ⇢ Le New Black |
| Inventory stock levels | ApparelMagic ⇢ Le New Black |
| Orders | ApparelMagic ⇠ Le New Black |
Data flow: Customers
ApparelMagic sends your customers with their address, their main contact, their price group and their ship-to locations, imported as delivery addresses.
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.
Scope: All ApparelMagic customers, or only those of the customer categories selected during set-up
Matching keys: Customer: retailer reference (ApparelMagic 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.
Configuration
| Setting | Values | Type | Comment |
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 |
Fields mapping
Complete mapping: every field the connector reads is listed.
| Le New Black field | ApparelMagic field | Comment |
Reference |
account_number | |
Name |
customer_name | |
Contact e-mail, first name, last name |
email, first_name, last_name | |
Address, zip code, city, country |
address_1, address_2, postal_code, city, country | Used as both the main and the billing address |
Phone, fax, website |
phone, fax, website | The phone is also the billing phone |
Billing e-mail |
||
State |
state | Optional, when set up |
Price list |
price_group | Found by the price list name by default |
Comment |
notes | |
Delivery addresses |
locations: dc_reference, name, address_1, address_2, postal_code, city, country, phone | One delivery address per ApparelMagic location of the customer |
Callouts
- Countries must be given as ISO country codes.
- The price group of each ApparelMagic customer must match a Le New Black price list.
Data flow: Products
ApparelMagic sends your products with their collection, category, colours and sizes, and the composition, customs code, weight, origin and care instructions of each colour.
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.
Scope: ApparelMagic records marked as products, optionally limited to some seasons or tags during set-up
Matching keys: Product: model (ApparelMagic style number). Variant: fabric code (ApparelMagic colour code). Size: size name, from the ApparelMagic size range of the product.
Import mode: Create or update → new products and variants are created, existing ones are updated.
Created on the fly: Collections (the ApparelMagic collection followed by the season) and categories
Configuration
| Setting | Values | Type | Comment |
fabric_key |
code / 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 |
Fields mapping
Complete mapping: every field the connector reads is listed.
| Le New Black field | ApparelMagic field | Comment |
Model |
style_number | |
Name |
description | |
Collection |
collection and season | The collection followed by the season |
Season |
season | |
Category |
category | |
Fabric code, fabric name |
attribute_2, attr_2_name | One variant per product attribute |
Composition, customs code, weight, made in |
content, tariff_code, weight, origin | Same for every variant of the product |
Care instructions |
care_instructions | Of the product attribute |
Special notice |
tags | The tag texts, separated by commas |
Size |
size range | The sizes of the product size range, in their order |
SKU |
style_number, attribute_2 and size | Built as the style number, the colour code and the size name put together |
Callouts
- The size range of each product must exist in Le New Black, unless the connector is set up to create it.
Data flow: Product images
ApparelMagic sends the image URLs of each colour of your products, or the product images when a colour has none.
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.
Limit: 8 images per variant: further images are ignored
Matching keys: Product: model (ApparelMagic style number). Variant: fabric name by default, or fabric code when set up, matched against the ApparelMagic colour code.
Rejected rows: Images of a product or a variant unknown in Le New Black are ignored and reported in the task log: import products first.
Configuration
| Setting | Values | Type | Comment |
fabric_key |
name (default) / code | string | Identifies the variant of an image: by its fabric code or its fabric name |
Callouts
- ApparelMagic sends the colour code of each variant: the data flow is set up to match on the fabric code (setting fabric_key).
- The connector works in two steps: the image URLs are imported first, then the images are downloaded into each product from the image import of the Integration center.
Data flow: Prices
ApparelMagic sends the prices of your price groups, each mapped to the wholesale or retail price of a Le New Black price list. The connector can also take the price and retail price set on each product, into one 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.
Price level: Per variant: one price per variant and price list, shared by all its sizes.
Price lists: Each ApparelMagic price group mapped during set-up feeds the wholesale or the retail price of a Le New Black price list
Matching keys: Price list: price list code. Product: model (ApparelMagic style number). Variant: fabric code (ApparelMagic colour code).
Configuration
| Setting | Values | Type | Comment |
fabric_key |
code (default) / name | 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 |
import_prices_from_products |
true / false (default) | bool | With true, the price and retail price of each ApparelMagic product go to one price list, instead of the price groups |
Callouts
- Price lists must exist in Le New Black first: your account manager creates them with the same codes as in ApparelMagic.
- Products and variants must already exist in Le New Black: import products before prices.
Data flow: Inventory stock levels
ApparelMagic sends the stock quantity of each size, read from the inventory field chosen during set-up.
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.
Quantity imported: The ApparelMagic inventory quantity set in the global configuration (setting inventory_quantity_column), for each SKU
Matching keys: Size: SKU, built as the style number, the colour code and the size name put together, the same way as the products data flow builds it.
Import mode: Add by default → only the sizes in the ApparelMagic data 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: An ApparelMagic SKU unknown in Le New Black is 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 |
Callouts
- ApparelMagic stock rows carry the SKU, not the EAN13: the data flow is set up to match on the Le New Black SKU (setting lnb_sku_identifier_column).
Data flow: Orders
Orders you move to the exported status (Invoicing by default) are created in ApparelMagic as orders, with their customer, currency, season and lines.
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
Sales order: An ApparelMagic order with the Le New Black order number as customer PO, the customer, the currency, the season when mapped, the credit status set in the global configuration, and one item per ordered size with its quantity and unit price
Matching keys: Customer: LNB retailer reference, which must be the ApparelMagic account number. Products: SKU, built as the style number, the colour code and the size name put together.
Configuration
| Setting | Values | Type | Comment |
mapping_season_codes |
Le New Black season → ApparelMagic season | list | Season sent with each order (optional) |
validate_stock_ats |
true / false | bool | With true, the orders are exported in stock allocation order: by status (Invoicing first), then by date |
Callouts
- An order with a line whose SKU is unknown in ApparelMagic is blocked as a whole: none of its lines is exported.
- An order whose customer has no ApparelMagic customer reference in Le New Black is blocked. Other orders are still exported.
- After the order has been exported from Le New Black, any further change must be made directly in ApparelMagic.
Global configuration
Configuration
| Setting | Values | Type | Comment |
url |
ApparelMagic account URL | string | Address of your ApparelMagic account |
token |
ApparelMagic API token | string | Credential of your ApparelMagic account, set up with your account manager |
sku_column |
ApparelMagic inventory field | string | Set during set-up; stock and orders match sizes on the SKU built from the style number, the colour code and the size name |
inventory_quantity_column |
qty_inventory / qty_avail_sell / qty_alloc / qty_avail_alloc | string | ApparelMagic inventory quantity imported as stock (inventory data flow) |
next_order_status |
Pending (when not set) / Approved | string | Credit status of the orders created in ApparelMagic (orders data flow) |
Integration project
Who's assigned from your team?
Your ApparelMagic 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 ApparelMagic setup and sales process.
- Setting up the connection with your ApparelMagic account.
- Generating and exporting test orders to ApparelMagic.
- Keeping your team updated throughout the process and addressing delays on either side.
- Working with you and ApparelMagic to troubleshoot any unexpected issue after launch.
Timeline
A standard integration of the products and prices data flows will take approximately 4-6 weeks 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
Comments
0 comments
Please sign in to leave a comment.