Business Parameters

Overview

returns.cloud provides a standard data model designed for typical e-commerce use cases.
However, every business process is unique. To adapt the platform to your specific needs, you can extend the standard data model using business parameters.

Business parameters allow you to add custom fields that store and manage additional data beyond what’s included in the default model.

Purpose of Business Parameters

Business parameters enable you to:

Extend the returns.cloud data model.
Capture information specific to your business processes.
Map and process data from external systems.
Display and interact with custom fields in the Self Service and Management portals.
They act as flexible placeholders for any data that’s not covered by the standard model.

Ways to Use Business Parameters

Extend Data via Integration

When importing data from your integration, you can fill business parameters directly.

Example:
If your source system contains an attribute that doesn’t exist in the returns.cloud standard data model, you can:

Create a corresponding business parameter in returns.cloud.
Map it to the source attribute within your integration configuration.
This ensures that all relevant data is transferred and stored properly.

Use in Self Service or Management Portal

You can also create business parameters that appear in the:

Self Service portal, where customers provide information.
Management portal, where internal users can fill in or adjust values.
These parameters can influence subsequent processes — for example, determining a specific workflow or return handling rule.
Additionally, returns.cloud can populate business parameters automatically using internal business logic.

Typical Use Cases

The following examples illustrate how business parameters are commonly used in practice. They are not exhaustive — the strength of this layer is precisely that it adapts to your own processes without changing the core platform.

Case 1 — Capturing data during warehouse grading

Quality Management often needs information about a returned item that can only be assessed while the item is physically in the hands of a warehouse employee. By defining business parameters for the grading step, the corresponding input fields appear directly in the grading interface of the Management portal. The captured values flow into reports and are available via the API alongside the standard grading data.

Typical fields:

Damage category
Accessories complete
Visible defects
Resale grade
Manufacturer Code

Case 2 — Item attributes that drive the compensation decision

One of our customers enriches items with specific attributes that influence which compensation alternatives the platform should offer. returns.cloud evaluates these attributes in its decision logic to determine the options presented during the return process. The same parameters are used in both portals, but with different thresholds: a stricter rule set applies in the Self Service portal where the consumer acts, and a more permissive one applies when a customer service agent handles the case in the Management portal.