Cegid ORLI + Le New Black integration overview
Cegid ORLI is a French ERP and POS software specialised in fashion retail. 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 |
|
Cegid ORLI and Le New Black both push and pull files |
|
The connector requires data mapping and configuration in Le New Black and Cegid ORLI |
Data flows
| Type | Flow |
| Customers | Cegid ORLI ⇢ Le New Black |
| Products | Cegid ORLI ⇢ Le New Black |
| Prices | Cegid ORLI ⇢ Le New Black |
| Inventory stock levels | Cegid ORLI ⇢ Le New Black |
| Orders | Cegid ORLI ⇠ Le New Black |
| Orders import | Cegid ORLI ⇢ Le New Black |
| Order events | Cegid ORLI ⇢ Le New Black |
| Sales documents | Cegid ORLI ⇢ Le New Black |
Data flow: Customers
Customers are imported from Cegid ORLI with their delivery addresses, buyers and line access.
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: Name agreed during set-up (setting filename_pattern)
Separator: ;
File format: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP. The file is archived once read.
Matching keys: Customer: retailer reference (Cegid ORLI customer code, Code Client). 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 a customer code, and rows whose price list, sales rep or country is unknown in Le New Black, are rejected 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 |
columns_mapping_strict |
true / false (default) | bool | Whether every mapped column must be present in the file, even with blank values |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
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 / code (default) | 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 |
lines_map |
division code → line name(s) | list | Translation of Cegid ORLI divisions into Le New Black lines |
Callouts
- Countries must be given as ISO country codes.
- Price lists and sales reps given in the file must already exist in Le New Black.
- Your account manager sets up how Cegid ORLI divisions translate into Le New Black lines.
Data flow: Products
Products are imported from Cegid ORLI with their categories, colours, materials and sizes.
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: Name agreed during set-up (setting filename_pattern)
Separator: ;
File format: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP.
File structure: One row per size
Size position: The Cegid ORLI size position of each size is stored in Le New Black. It places quantities in the right size column of the order files exchanged with Cegid ORLI.
Matching keys: Product: model. Variant: fabric code. Collection: collection code. 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 (attached to the line given in the file), categories on three levels, fabrics and colours
Rejected rows: A model / colour / size combination given more than once in the file.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
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 |
remove_prototype_skus |
true / false | bool | With true, the sizes whose code starts with P (prototypes) are left out |
Callouts
- The set of sizes sold for each product must match a size range already defined in Le New Black, and the lines given in the file must exist.
- Publication is managed at three levels: Published for the product, Is available for the variant (an empty value means published or available), and Size is sold for the size: only the rows marked as sold ("X") are imported.
- The sizes sold set the size range of a product at its creation only: for an existing product, a different set of sold sizes is rejected and reported in the task log. To change the size range of a product, use the Product sizing update feature of the Sizings section.
Data flow: Prices
Wholesale and retail prices are imported from Cegid ORLI.
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: Name agreed during set-up (setting filename_pattern)
Separator: ;
File format: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP. Columns: price list code, model, variant, size, price.
Price level: Per variant by default, or per size when set up.
Price lists: The price list code of a row is compared with the code of each Le New Black price list (wholesale price) and with its retail code (retail price), so one file can carry both prices.
Matching keys: Price list: price list code. Product: model. Variant: fabric code. Size: size name (size-level prices only).
Rejected rows: Rows whose price list code matches no Le New Black price list are ignored.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
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 |
price_format_is_cents |
true (default) / false | bool | Whether prices are given in cents (12345 is read as 123.45) |
fabric_codes_map |
model and colour code → colour code | list | Translates the colour code of a price row into the Le New Black colour code, per model |
Callouts
- Price lists must exist in Le New Black first: your account manager creates them with the same codes as in Cegid ORLI.
- Products and variants must already exist in Le New Black: import products before prices.
- An optional price period column is supported when pricing per period is enabled on your account.
Data flow: Inventory stock levels
Available-to-sell quantities are imported from Cegid ORLI 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: inventory*.{csv,xlsx}
File format: CSV or Excel file with a header row, dropped by Cegid ORLI on your Le New Black FTP.
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.
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 |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern, inventory*.{csv,xlsx} (default) | string | Name of the file to import, agreed during set-up |
filename_pattern_exclude |
file name pattern, none (default) | string | Files matching this pattern are left out of the import |
file_compression_format |
none (default) / .zip / .tar.gz | string | Archive format the file arrives in |
import_mode |
add (default) / replace | string | With replace, the stock of every size is set to 0 before the quantities are applied |
sku_column |
ean13 (default) / sku | string | Le New Black key the stock rows are matched against |
Fields mapping
Complete mapping: every field the connector reads is listed.
| Le New Black field | File column | Comment |
EAN13 |
EAN13 | Key |
Quantity |
Quantity | Integer |
Is blocked |
Is blocked | Optional: 0 (no) or 1 (yes) |
Available from |
Available from | Optional: ISO 8601 date and time |
Incoming quantity |
Incoming quantity | Optional: integer |
Incoming date |
Incoming date | Optional: date |
Data flow: Orders
Orders you move to the exported status (Invoicing by default) are sent to Cegid ORLI. Le New Black seasons must be mapped to your Cegid ORLI season codes, and products and customers must carry the EAN13, size positions and customer references given by the products and customers data flows.
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: Name agreed during set-up (setting filename): one file per order, named with the Le New Black order number, or one file for all the exported orders (setting file_split_by_order)
Separator: ; in the standard set-up (setting export_separator)
File format: Text file without header row, placed on your Le New Black FTP for Cegid ORLI to collect.
File content: One header record per order (order number, customer reference, season code, sales division, confirmation and creation dates, PO number, order nature from the order mode, price list code, currency), then one line record per product variant with up to 20 size quantities placed by Cegid ORLI size position. A one-line-per-size layout based on EAN13 is also available.
Optional records: Delivery address (only when it differs from the billing address), order private note (split into 80-character lines), line discount
Archive: A dated copy of every exported file is kept in Le New Black
Matching keys: Customer: LNB retailer reference, sent as the Cegid ORLI customer code. Products: EAN13 and size position (the Cegid ORLI size position of each size).
Configuration
| Setting | Values | Type | Comment |
file_split_by_order |
true / false | bool | One file per order (true) or one file for all exported orders (false) |
filename |
file name | string | Name of the order file, agreed during set-up |
export_separator |
any character, ; in the standard set-up | string | Field separator of the order file |
export_fields_to_validate |
season, delivery start date, line, customer reference, EAN13, price list code, PO number, size position… | list | Checks applied before export; an order failing one of them is blocked |
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 containing a product without an EAN13 code is blocked as a whole: none of its lines is exported.
- An order whose customer has no Cegid ORLI customer reference in Le New Black is blocked. Other orders are still exported.
- With the standard checks, orders without a season, a delivery start date or a line are blocked as well, and so are orders without any product.
- After the order has been exported from Le New Black, any further change must be made directly in Cegid ORLI.
- Cegid ORLI must delete the order file once downloaded; an archived copy stays available in Le New Black.
Data flow: Orders import
Cegid ORLI sends back the full content of orders already in Le New Black, to add products or change quantities. Each file must hold every line of the order, including the lines that did not change.
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: Name agreed during set-up (setting filename_pattern)
Separator: ; by default (setting import_separator)
File format: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP. By default, one row per product variant with up to 20 quantity columns, one per Cegid ORLI size position. A one-row-per-size layout is also supported.
Prices: Taken from the price list of the order's customer
Matching keys: Order: LNB order number. Customer: retailer reference (Cegid ORLI customer code), which must be the order's customer. Product: model. Variant: fabric code. Size: size position (Cegid ORLI size position).
Import mode: Update → orders that already exist in Le New Black. The file gives the full content of the order: lines absent from the file are removed from the order.
Rejected rows: Orders with an invalid order number or customer code, lines with an invalid model or fabric code, and lines whose product has no price in the customer's price list.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
import_separator |
; (default) | string | Field separator of the file |
order_row_level |
variant (default) / sku | string | One row per product variant, or one row per size |
sku_column |
size position columns (default) / size / ean13 | string | How the sizes of a row are given: quantity columns QTE 1 to QTE 20 by size position, a size column, or an EAN13 column |
order_id_replace |
text → replacement | list | Text replaced in the order number of the file before the order is looked up |
Data flow: Order events
Order events from Cegid ORLI (confirmation, preparation, shipping) are added to the history of each order, with the tracking details when provided.
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: Name agreed during set-up (setting filename_pattern)
Separator: ;
File format: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP. Columns: order number, event code, event label, event date (DDMMYYYY), event key, then the optional shipping details.
Shipping details: Picking number, shipping number, package number, tracking number, tracking URL and carrier code
Matching keys: Order: LNB order number. Event: event code and event key.
Import mode: Create only → an event already imported is not imported twice.
Not synchronised: Events are added to the order's history in your back-office; they do not change the order status.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
Data flow: Sales documents
Sales documents from Cegid ORLI arrive in two steps: a documents list creates each sales document and links it to its order, then the PDF files are attached to them.
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: Name agreed during set-up (setting filename_pattern)
Separator: ;
Documents list: CSV file with a header row, dropped by Cegid ORLI on your Le New Black FTP. Columns: document number, document type, PDF file name, Le New Black order number.
Document types: CD: order confirmation. FA: invoice. BP and BL: packing list. BE: delivery note. Any other type is filed as "Other".
Issue date: Read from the PDF file name: the date (YYYYMMDD) that starts the last dash-separated part of the name
PDF files: Attached to the sales document whose file name they match. Up to 100 files per run; a file matching no sales document is reported as an error.
Matching keys: Document: document number. A document already in LNB is updated.
Rejected rows: Rows without an order number, a document number or a file name.
Configuration
| Setting | Values | Type | Comment |
columns_mapping |
file column per Le New Black field | list | Replaces the default columns of the file |
filename_pattern |
file name pattern | string | Name of the file to import, agreed during set-up |
Integration project
Who's assigned from your team?
Your Cegid ORLI 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 Cegid ORLI setup and sales process.
- Collaborating with Cegid ORLI as they configure the data files to import and export.
- Generating and exporting test orders to Cegid ORLI.
- Keeping your team updated throughout the process and addressing delays on either side.
- Working with you and Cegid ORLI to troubleshoot any unexpected issue after launch.
Timeline
A standard integration of the orders data flow will take 2-4 weeks to get up and running.
A standard integration of the inventory, 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
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.