Connector Commerce Interface to Fashion on Product Documentation

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is the business entry point to Connector Commerce Interface to Fashion. It is written for users who need to place the connector for the first time and understand which fashion-specific master data is required in addition to the general BE-Commerce scope.

Who should read this page

Key users in a fashion context who maintain channels, colors, and attribute-based data.
Business users who need to understand which additional maintenance tasks exist beyond the BE-Commerce standard.
Teams that must distinguish between general BE-Commerce functionality and fashion-specific extensions.

What the connector adds

The connector extends the general BE-Commerce usage with fashion-specific requirements. This especially includes

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Setup Goal

This page describes the core setup for Connector Commerce Interface to Fashion from an end-user perspective. It shows which additional settings must be checked compared to BE-Commerce and how to prepare the fashion-specific master data for daily operations.

Who this page is for

Key users who set up or extend a fashion webshop.
Users who align colors, attributes, and country logic for the webshop.
Teams that need to make sure the business setup is ready before the first live run.

Prerequisites

Access to the relevant setup pages in the Commerce Interface and BE-Commerce context.
Defined webshop channels, languages, and countries for the connected shops.
A dedicated integration user for data exchange via web services.

Setup Steps

First confirm that the general BE-Commerce setup is complete.
Create the required webshop channel with languages, countries, and core parameters.
Add the fashion-specific master data such as colors, attributes, and categorization.
Align validation options and release logic for later data publication.
Finally clarify the technical connection and test one full process with sample data.

Relevant Setup Areas

Area	Why you need it	Typical decision
Webshop Channel	Business basis per shop	Which languages, countries, and sales locations apply?
Country and Pricing Logic	Correct posting and assignment	Which price groups, shipping charges, and voucher types apply per country?
Validation Options	Data quality before release	Which mandatory checks must be active per channel?
Fashion Master Data	Variant and attribute logic	Which colors, attributes, and categories are needed in the shop?
Technical Connection	Coordination with data exchange	Which endpoints and handover rules are relevant for operations?

Define the Webshop Channel

Create one channel per shop and maintain the control data relevant to the connector. This includes the location group, the sales location for webshop documents, allowed contact changes, and the active languages.

Master Data for Fashion

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page consolidates the fashion-specific master data you maintain in addition to the general BE-Commerce standard. It helps new users understand the main data objects and the order in which they should be prepared.

Who this page is for

Users who prepare categories, attributes, and colors for a fashion webshop.
Key users responsible for master-data quality and channel-related maintenance.
Teams that need to decide which data is maintained in the connector and which belongs to the shared BE-Commerce area.

Recommended Sequence

First review the basics in BE-Commerce Master Data.
Then define the channel-related foundation for the fashion webshop.
Continue with categories as well as dynamic and free-text attributes.
Finish with colors, supplier colors, and item-related webshop data.

Webshop Channels

Each shop is managed through its own channel. Per channel you maintain, among other things, the location group for available inventory calculation, the sales location for webshop documents, allowed contact changes, and the active languages.

Color Management

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the maintenance of colors and supplier colors for Connector Commerce Interface to Fashion.

Webshop Colors

For colors stored in the system, you can maintain webshop descriptions in multiple languages. These descriptions support a consistent presentation of colors in the shop across all relevant channels.

Click to enlarge

Supplier Colors

Dedicated webshop descriptions can also be stored for supplier colors. This makes it possible to translate supplier-specific color naming into a shop-ready presentation.

Reference Processes

Mon, 01 Jan 0001 00:00:00 +0000

This page consolidates the main reference processes for Connector Commerce Interface to Fashion. The focus is on setup, import, processing, and export together with fashion-specific master data.

Process WSE – Webshop Setup Channel, languages, countries, colors, and HTTP connection are set up for the connected shop. +

A dedicated channel with the required control data is created per webshop.
Countries, languages, and validation options are maintained per channel.
Colors and supplier colors are prepared so they can later be transferred to items and variants.

Process JQE – Job Queue Setup Recurring validation and processing runs are scheduled for import, release, and export. +

Background processing ensures that import and release steps run regularly.
Faulty records remain traceable and can be processed again after correction.

Process IBC – Import BE-Commerce Contacts, sales orders, and reservations are transferred from the shop into Business Central container and target structures. +

The shop provides documents and master data changes through web services.
Processing validates the data and creates target documents only after successful validation.

Process PBC – Process BE-Commerce Imported data is validated, corrected, released, and moved into the operational flow. +

Release logic evaluates mandatory fields, categorization, language-dependent descriptions, and price availability.
Error lists support follow-up actions before documents or item releases are checked again.

Process EBC – Export BE-Commerce Changes to items, prices, inventory, and other shop-relevant data are made available to the shop. +

Change logs control which data is exported or signaled through HTTP calls.
The shop retrieves the provided data through the defined export interfaces.

Technical Connection

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the technical connection between Business Central and the connected shop in the context of Connector Commerce Interface to Fashion.

Technical Structure

Web Services for Master Data and Transaction Data

Data exchange is based on provided web services. The shop supplies sales orders, returns, reservations, and contact changes in container structures. After successful validation, the target documents are created in Business Central.

HTTP Calls for Change Control

Changes to items, contacts, prices, inventory, categories, and attributes are stored in a change log. Configurable HTTP calls notify the shop that updated data is available for retrieval.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ When do you need the connector in addition to BE-Commerce? The connector is needed when a fashion webshop uses additional colors, attributes, variant logic, or channel-specific fashion master data. +

Use the connector when the general BE-Commerce standard must be extended with fashion-specific requirements. Typical examples are webshop colors, supplier colors, attribute-based variant presentation, or fashion-specific categorization.

If you want to understand the base module first, start with BE-Commerce Overview. Then continue with the connector-specific pages such as Setup and Master Data for Fashion.