BE-Commerce on Product Documentation

Overview

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

Purpose

This page is the business entry point to the BE-Commerce module. It is written for users who are new to the module and want to understand what it is used for, which master data must be prepared, and which daily tasks follow from that setup.

Who should read this page

E-commerce coordinators who support webshop-related business processes.
Customer service or sales users who review imported documents and contacts.
Key users who are responsible for setup, data quality, and stable daily operations.

What you do with BE-Commerce

BE-Commerce connects Business Central with a webshop. The module helps you to

Setup

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

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:

Role Center

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

Purpose

The role center provides the central entry point to the operational workspaces of BE-Commerce. It consolidates the most frequently used lists and views for user and admin tasks.

Business Value

Fast access to relevant work lists.
Separation between user and admin views.
Focus on the most important operational documents and checks.

Content Focus

User View

The user view shows documents that are ready for processing, archived documents, and incorrect entries. It also includes contacts and other daily work lists.

Item Releasing

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

Purpose

This page describes how to release items to webshop channels in BE-Commerce. The goal is a repeatable approach to publish items only with complete and consistent data.

Prerequisites

Setup and channel assignments are configured.
Categories, attributes, and required descriptions are maintained.
Validation and release responsibilities are clearly assigned.

Recommended Sequence

Complete item and variant data per channel.
Run release validation and review the error protocol.
Fix issues, re-validate, and then release per channel.

Configuration Building Blocks

Release-Relevant Mandatory Data

Verify minimum requirements for category assignment and description fields.
Complete language- and channel-specific content before release.

Error Handling

Work through error protocols by root cause.
Standardize recurring corrections for repeatable quality.

Process Release Guardrails Rules for stable and traceable item publishing. +

Execute releases channel by channel with explicit validation steps.
Never skip error protocols; re-validate after each correction cycle.
For bulk updates, validate with a small item subset first.

Contact Creation and Update

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

Purpose

This page describes how to validate imported webshop contacts, create contacts in Business Central, and apply controlled updates to existing contacts.

Prerequisites

Number series for webshop contacts is configured.
Contact changes are approved per channel.
Customer templates and mandatory transfer fields are defined.

Recommended Sequence

Validate imported contact records for completeness and consistency.
Correct issues in setup, mappings, and mandatory fields.
Execute contact creation or update and document the result.

Configuration Building Blocks

Contact Validation Before Processing

Validate salutations, contact numbers, and mapping keys against valid BC values.
Distinguish new and existing customers unambiguously based on contact-number logic.

Transfer into Business Central

Run contact creation and updates only after successful validation.
Document outcomes, errors, and rework actions in a traceable way.

Process Contact Processing Guardrails Rules for consistent and safe contact transfer. +

Do not force automated transfer when salutations or number series are invalid.
For existing contacts, ensure an unambiguous mapping to the existing contact number.
Validate template and channel rule changes in test runs before production use.

Change Log

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

Zweck

The change log records relevant changes to master and transactional data for the commerce area. It serves as the basis for synchronization between Business Central and the webshop.

Was erfasst wird

Item master data
Price changes
Inventory changes
Webshop categories
Free-text attributes
Dynamic attributes
Locations and document data

Struktur

Entry number
Processed
Skip
Latest request successful
Created at
Name and code
Webshop channel code
Number of HTTP requests
Last send date and time
Latest response
Parameters 1 to 3

Fachlicher Nutzen

Traceability of changes for webshop synchronization.
Control over which data is sent to the shop.
Prevention of duplicate transmissions through existing entries.

Ergebnis

A controlled data stream for changes in the commerce context.
A traceable list for technical and business follow-up.

Sales Order Creation

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

Purpose

This page describes how imported order data is processed into a sales order in the system. It covers both the successful path and the rework path for faulty imports.

Prerequisites

The webshop provides order data to Business Central.
The import process has loaded the data into the container.
The business-critical order fields are known and maintained.

Recommended Sequence

Review the imported order data.
If the content is correct, create the sales order.
Correct faulty data in the container and process it again.

Configuration Building Blocks

Successful Sales Order Creation

The order is created from the webshop data as a sales order.
The document contains traceable header information such as number and creation timestamp.

Faulty Sales Order Creation

Invalid imports are marked with an error and an error text.
Rework happens in the container under the converted data tab.
After correction, the order can be created manually.

Process Sales Order Creation Guardrails Rules for stable processing of imported sales orders. +

Always validate imported data before creating the document.
Fix issues in the container instead of on the downstream document.
Use manual rework only for approved business exceptions.

Sales Return Order Creation

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

Purpose

This page describes how sales return orders are created in Business Central from imported webshop return data. The processing follows the same basic pattern as sales orders.

Prerequisites

The webshop sends return data to Business Central.
The import has loaded the data into the container.
The channel-specific return rules are known.

Recommended Sequence

Review the imported return data.
Correct errors in the container.
Create the sales return order manually or automatically.

Configuration Building Blocks

Processing Imported Returns

Returns are first loaded into a container.
Business Central performs the content check after import.
Error handling follows the same pattern as sales order processing.

Rework and Creation

Faulty data can be adjusted.
The sales return order is then created from the corrected data.

Process Return Guardrails Rules for safe processing of imported returns. +

Apply the same validation discipline to returns and orders.
Correct container data before manual document creation.
Document root causes for recurring return errors.

Reservation

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

Purpose

This page describes reservation processing in the BE-Commerce import context.

Prerequisites

The reservation import process is enabled.
Required locations and mappings are configured.
Business rules for reservation scenarios are defined.

Recommended Sequence

Validate reservation data in the container.
Correct functional and technical issues.
Execute reservation processing and verify the result.

Configuration Building Blocks

Difference from Sales Order Import

Processing is similar to sales order creation.
No sales order is created for the customer.
Reserved items are transferred from the branch to a reservation or selection warehouse.

Import Interfaces

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

Purpose

This page describes the available import interfaces for receiving webshop data in Business Central.

Imported Data Areas

Sales orders
Returns
Contacts
Reservations

Usage Notes

Each import interface has a field-level description with required and control fields.
In case of import errors, validate and correct container data before processing downstream documents.

Export Interfaces

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

Purpose

This page describes the main export objects that are transferred from Business Central to the webshop.

Exported Data Areas

Item master data including variants
Webshop categories
Free-text and dynamic attributes
Cross-selling items
Inventory and prices
Contacts
Vouchers
Document history and document status
Locations and branch inventory

Usage Notes

Each export interface has a dedicated field-level interface description.
Functional changes should always be aligned with the related interface documentation.

FAQ

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

FAQ Where should you start before the first productive go-live? Start with setup, master data, and one complete test run for the most important business transactions. +

Start with Setup and verify that webshop channels, language and country assignments, and the main control values are maintained completely.

Then continue with Master Data so that categories, attributes, translations, and channel-related mappings are available. After that, test at least one complete process such as item release, sales order creation, or return processing.

Reference Processes

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

Purpose

This page consolidates the webshop reference processes as a condensed process catalog in the BE-Commerce module of the Commerce Interface solution.

It provides the core building blocks for:

Webshop channel setup
Importing webshop changes into Business Central
Processing imported e-commerce documents
Exporting webshop-relevant data from Business Central

Process Catalog

Process WSE – Webshop setup Basic setup of the webshop channel in Business Central. No data is transferred to the webshop during this setup. +

Create or change a webshop channel (assign attachment types, languages, countries, and line types).
Define carriers and transport codes per channel.
Define payment methods per channel.
Define countries (optionally including an EU country/region code).
Define the languages used by the webshop.
Define webshop colors.
Maintain HTTP setup per webshop channel (including the URL binding).

Process IBC – Import BE-Commerce New and changed webshop data is imported into Business Central via the interface and made available as an e-commerce document. +

Import via the e-commerce interface: webshop data is loaded into intermediate tables (for example webshop and reservation tables).
A corresponding e-commerce document is created from the imported data so it can be processed further.
Typical import variants:
- Contacts
- Orders
- Sales return registration (sales complaint)
- Reservations
Next step: processing via PBC.

Process PBC – Process BE-Commerce Check, control by status, correct if needed, and release: this creates the corresponding system documents. +

Check the e-commerce document: the system lists errors in a structured (tabular) way.
Set the message status (for example checked/erroneous/processable).
Rework data: manual correction when validation fails.
Check and release: the system processes the document and creates follow-up documents.
Typical outcomes:
- Sales order and downstream sales documents
- Sales complaint/return
- For reservations: creation of a transfer order for the reserved items (store → reservation/selection location)

Process EBC – Export BE-Commerce Webshop-relevant data is provided when created/changed in Business Central; the webshop is notified and retrieves the data via web services. +

Create/change data: relevant data is maintained in Business Central.
Notify the shop: a ping is sent to the webshop based on the HTTP setup.
The shop retrieves the data: the webshop pulls the updated data via web services.
Typical export objects (examples):
- Webshop categories (tree structure, translations)
- Dynamic attributes (including values and translations)
- Free-text attributes (including translations)
- Webshop items (categories, attributes, cross selling, colors, multilingual descriptions, publishing per channel)
- Sales prices (including start/end date, potentially on variant level)
- Availability (single item or batch transfer)
- Contacts
- Order statuses
- Vouchers

BE-Commerce on Product Documentation

Overview

Purpose

Who should read this page

What you do with BE-Commerce

Setup

Purpose

Who this page is for

Prerequisites

Recommended Order

Relevant Setup Areas

Channels and Core Parameters

Master Data and Mappings

Quality and Release Logic

Initial Master Data

Role Center

Purpose

Business Value

Content Focus

User View

Item Releasing

Purpose

Prerequisites

Recommended Sequence

Configuration Building Blocks

Release-Relevant Mandatory Data

Error Handling

Contact Creation and Update

Purpose

Prerequisites

Recommended Sequence

Configuration Building Blocks

Contact Validation Before Processing

Transfer into Business Central

Change Log

Zweck

Was erfasst wird

Struktur

Fachlicher Nutzen

Ergebnis

Sales Order Creation

Purpose

Prerequisites

Recommended Sequence

Configuration Building Blocks

Successful Sales Order Creation

Faulty Sales Order Creation

Sales Return Order Creation

Purpose

Prerequisites

Recommended Sequence

Configuration Building Blocks

Processing Imported Returns

Rework and Creation

Reservation

Purpose

Prerequisites

Recommended Sequence

Configuration Building Blocks

Difference from Sales Order Import

Import Interfaces

Purpose

Imported Data Areas

Usage Notes

Related Pages

Export Interfaces

Purpose

Exported Data Areas

Usage Notes

FAQ

Reference Processes

Purpose

Process Catalog

Related Content