Import Order

Introduction

The Import Order action in the Data Management Tool allows users to bulk create orders by importing source rows from a CSV file mapped to Younium fields. This functionality enables importing complete product structures into orders in bulk, directly through the UI using a defined grouping logic.

To access the Import Order feature, navigate to; Settings > Datamanagement

• Method: Import
• Entity: Order
• Action: Import

Minimum requirements

To successfully import orders, your CSV file must include the following fields:

1. Account Name/Number/ID
2. Product Name/Number/ID
3. Charge Plan Name/Number (if applicable) 
4. Order Grouping Identifier

As with manual order creation in the UI, any product added to an order will inherit its default settings as defined in the product catalog. The same logic applies when importing orders through the Data Management Tool.

If only the minimum required fields are used, all default values will automatically be applied to the order and its associated product charge details.

Default values

You can configure default values under:

Settings > Orders > Order Settings > Order Default Settings

The available default values include:

• Default Order type: Sales Order / Subscription Order
• Default Subscription type: Termed / Evergreen
• Default Initial term: Number of months
• Default Renewal term: Number of months 
• Default Auto renewal: Yes / No
• Default Notice period: Number of months
• Default Effective Start date: No Default / Day of Creation / First Day of Next Month
• Default Payment term: Select from payment term list
• Default Invoice separate: Yes / No
• Default Use Account invoice batch group: Yes / No
• Default Invoice batch group: Select from invoice batch group list

Other order default values not configurable via settings:

• Order status: Draft
• Order date: Same as "Order effective start date"
• Order currency: Order account default currency
• Order product charge Start on: Align to order
• Order product charge End on: Align to order

All values related to your product charges are inherited from the product catalog. Therefore, you only need to import fields where values differ from the defaults.

Grouping of Source Rows

In Younium, orders consist of four hierarchical data sets:

• Order
• Order Product
• Order Product charge
• Order product charge details (pricing)

When importing in bulk, each source row in your CSV represents one charge or charge detail. Depending on the complexity of your order setup, unique identifiers are needed to link products, charges, and pricing tiers to the correct orders.

You will configure this during import by selecting the applicable checkboxes:

1. Group each source row to an order* (Mandatory)
2. Order contains multiple products
3. Products contain multiple charges
4. Charge contains tiered pricing

1. Group each source row to an order* (Mandatory)

This field determines which rows belong to the same order. The value in the Order Grouping column can be any unique identifier, as long as it is consistent for all rows associated with the same order.

Example: 3 orders for the same account, each with 1 product

2. Order contains multiple products

Use this field to indicate which rows represent different products within the same order. The Product Group identifier must be unique for each product within a single order. However, you may reuse the same product group identifier across multiple orders, as long as it remains unique within each individual order.

Example: 3 orders, each with 2 products

3. Products contain multiple charges

Use this field to define multiple charges per product. Each Charge Group must be unique within the product.

Example: Each product has 2 charges

4. Charge contains tiered pricing

If a charge contains tiered pricing, each tier* must be listed as a separate row, using a unique Tier Group identifier.

Example: One flat rate charge, and one charge with 3 tiers

* You can import data against a single tier within a charge that has multiple tiers, if you only need to update the pricing details for that specific tier. The remaining tiers will retain the default settings from the product catalog.

Import Tips

As mentioned in the Minimum Requirements section, it is not mandatory to include all grouping fields unless your data requires additional detail. If the product charge details follow the defaults set in your product catalog, you can omit those fields to simplify the import.

However, whenever you need to add or update even one value within a specific data level, you must use the appropriate grouping field(s) to ensure a successful and accurate import.

Field mapping

After uploading your source file, you need to map your source values to the corresponding fields in Younium. The mapping interface allows you to define which Younium field each column in your source file should be mapped to, along with the accepted data type for that field.

Mapping Overview:

• Younium Field – The specific field in Younium to map your data to.
• Data Type – The type of data accepted by the Younium field.
• Source Header – The column in your source file that contains the values to be mapped to the Younium field.
• Sample Data – Example values from the first three rows under the selected source header.
• Action – Allows you to delete the corresponding mapping row if needed.

Data types in Younium

In Younium, fields can be of various data types. Below is a list of the available data types:

• Reference – Allows more than one acceptable value.
• Enum – A list of predefined selectable values.
• String – A free-text input field.
• Date – Follows the Swedish date format (YYYY-MM-DD).
• Integer – A whole number without decimals.
• Decimal – A number that allows decimal values.
• Boolean – Represents a true or false value

Field mapping 

Order

Order product

Order product charge

Order product charge details