One operational layer. Many possibilities.

OMS covers channel orders, different statuses and currencies, B2B customer recognition and VAT information. Telephone orders can also enter operational processing. Price lists and customer groups connect product data to commercial terms.

Variants, sets and attributes structure the catalogue. Channel and country prices, price lists and customer groups represent different commercial contexts. Four-eyes approvals support quality assurance. Product Manager adds CSV and API import and export, image processing, rules and AI-assisted text and translation.

Multiple warehouses, picking documents and shipping labels support fulfilment. Supplier portal and dropshipping bring external stock and shipping sources into the process. Returns and credits connect logistics to after-sales. Warehouse or supplier allocation and handovers are defined for each project.

Minimum and target stock levels can support procurement. Supplier purchase orders, delivery dates and goods receipt are considered in the operational context. Relevant data and responsibilities are aligned with existing ERP and purchasing systems.

The platform describes payment service provider connections, reconciliation and release following advance payment. Payment methods, providers and workflows depend on the selected solution and integration.

Documented RISK capabilities include duplicate and address checks, scoring and rules. These support defined review workflows. The rules deployed and decision ownership form part of project design.

Reports and monitoring provide insight into operations. The existing platform description covers inventory, order and payment data, with Excel and API access. Required data, reports and access permissions are agreed for the project.