Setup

Setup and core configuration of the BE-Commerce module.

Purpose

This page describes the basic setup of BE-Commerce from an end-user perspective. It shows which decisions are needed before go-live, which data should be maintained first, and in which order you make the module ready for operations.

Who this page is for

Key users who set up a new webshop channel or extend an existing one.
Business owners for master data, country logic, and release rules.
Users who need a complete picture of the setup scope before starting detailed maintenance.

Prerequisites

Access to the relevant setup pages in the BE-Commerce module.
Aligned ownership for channels, data maintenance, and release checks.
Baseline decisions for languages, countries, pricing logic, and import/export behavior.

Recommended Order

Define webshop channels and global setup values.
Maintain master data and mappings per channel.
Align validation and release rules for daily operations.
Test the relevant follow-up processes with sample data.

Relevant Setup Areas

Area	Why you need it	Typical decision
Webshop Channel	Controls the overall behavior of one shop	Which languages, countries, and customer defaults apply?
Master Data	Enables categorization and multilingual output	Which categories, attributes, and mappings are mandatory?
Validation and Release Logic	Stabilizes data quality and processing	Which mandatory fields and checks must be fulfilled?
Follow-Up Process Testing	Verifies operational readiness	Do import, release, and export run successfully with sample data?

Channels and Core Parameters

Define channel code, description, languages, and countries.
Maintain required mappings and posting-related information per channel.
Align import and export behavior for each interface context.

Master Data and Mappings

Maintain categories, attributes, and channel-specific mappings.
Align translations for multilingual output.
Use the detailed master-data pages as the operational drill-down.

Quality and Release Logic

Define mandatory fields and validation rules for releases.
Align responsibilities for data quality and corrections.
Re-test major changes with representative test cases.

Initial Master Data

Before users start working with the module in daily operations, at least these basics should be complete:

Webshop channels with languages, countries, and posting logic.
Categories and attributes used for later item release.
Translations for output-relevant content.
Validation options for release and import processing.

Best Practices

Start with one channel and complete the full setup before adding more channels.
Keep responsibilities for master data maintenance and error correction explicit.
After every larger setup change, test not only master data but also one full import and release flow.

Process Guardrails for setup and master data maintenance Core rules for consistent configuration across all channels.

Apply channel setup changes only in aligned maintenance windows.
Validate categories, attributes, and translations across all active channels.
Re-test import, export, and release checks with sample data after changes.