Introduction

The Data Management Tool in Younium enables you to import, update, and edit products and orders in bulk. To prepare your files correctly and avoid errors, it’s important to first understand both the workflow for importing data and the hierarchies that structure products and orders.

This guide covers:

  1. The general workflow when importing or updating data.

  2. The product and order hierarchies.

  3. Simple examples to help you visualize how data is organized.


General Workflow: Importing and Updating Data

When you go to Settings > Data Management, you’ll follow the same basic steps whether you’re importing new data or updating existing records:

  1. Choose Method

    • Currently supported: Import (used for both creating and updating data).

  2. Select Entity

    • Pick which object you want to work with, such as Product or Order.

  3. Select Action

    • Choose the action you want to perform (e.g., Import Products, Import Orders, Update Products).

  4. Add Source File

    • Upload your prepared CSV file.

    • Supported format: CSV

    • File size limit: 10 MB

  5. Apply Data Mapping Template (optional)

    • Re-use a saved mapping template if your files follow a consistent format.

    • Templates can be updated or saved as new templates.

    • This saves time and ensures consistency across imports.

  6. Map Fields

    • In the Data Mapping step, connect your CSV file columns (Source Headers) to the correct Younium Fields.

    • Define Grouping Identifiers (Order, Product, Charge, Price Group) to tell Younium how rows belong together.

    • At the bottom of the page, you’ll find a log that tracks:

      • Unmapped rows.

      • Errors that must be fixed before the import can run.

    • 💡 Tip: You can update your CSV file directly on your computer, then simply re-upload it into the same mapping session — no need to exit and restart.

  7. Run Import

    • Once mapping is complete, run the import.

    • The system validates your file and processes all rows into Younium


Product Hierarchy

Product data in Younium is structured across four hierarchical layers:

  • Product

  • Charge Plan

  • Charge

  • Charge Detail

Example: Simple Product

Description

  • Product: “Basic Subscription”

    • Charge Plan: Standard Plan

      • Charge: Monthly Fee

        • Charge Detail: €100 / month

Model (CSV-style):

Product NameProduct TypeProduct Group IdentifierCharge Plan NameCharge Plan Group IdentifierCharge NameCharge TypeCharge Group IdentifierPriceCurrency
Basic SubscriptionSimpleAStandard PlanAMonthly FeeRecurringA100EUR

 

Example: Product with Multiple Charges

Description

  • Product: “Enterprise Subscription”

    • Charge Plan: Premium Plan

      • Charge 1: Base Fee → €1,000 / month

      • Charge 2: Support Fee → €200 / month

Model (CSV-style):

Product NameProduct TypeProduct Group IdentifierCharge Plan NameCharge Plan Group IdentifierCharge NameCharge TypeCharge Group IdentifierPriceCurrency
Enterprise SubscriptionFullAPremium PlanABase FeeRecurringA1000EUR
Enterprise SubscriptionFullAPremium PlanASupport FeeRecurringB200EUR

Order Hierarchy

Order data in Younium is also structured into four hierarchical layers:

  • Order

  • Order Product

  • Order Product Charge

  • Order Product Charge Detail

Example: Single Product Order

Description

  • Order: Customer A, Subscription Order

    • Order Product: Basic Subscription

      • Order Product Charge: Monthly Fee

        • Order Product Charge Detail: €100 / month

Model (CSV-style):

Account NameOrder GroupProduct NameProduct GroupCharge NameCharge GroupPriceCurrency
Customer AABasic SubscriptionAMonthly FeeA100EUR

 

Example: Order with Multiple Products

Description

  • Order: Customer B, Subscription Order

    • Order Product 1: Enterprise Subscription

      • Charge: Base Fee → €1,000 / month

      • Charge: Support Fee → €200 / month

    • Order Product 2: Implementation Package

      • Charge: One-Off Fee → €5,000

Model (CSV-style):

Account NameOrder GroupProduct NameProduct GroupCharge NameCharge GroupPriceCurrency
Customer BAEnterprise SubscriptionABase FeeA1000EUR
Customer BAEnterprise SubscriptionASupport FeeB200EUR
Customer BAImplementation PackageBOne-Off FeeC5000EUR

Summary

  • Products and orders both follow four-layer hierarchies.

  • Products: Product → Charge Plan → Charge → Charge Detail

  • Orders: Order → Order Product → Order Product Charge → Order Product Charge Detail

  • Examples above illustrate the difference between simple and complex setups.

As soon as you introduce multiple layers, Younium needs to understand what details belong to what product or order.
The grouping identifiers act as little helpers to define whether the information on a source row is unique or should be linked together with other rows.

👉 Next steps:

  • In Guide: Import / Update / Upsert Products, you’ll learn how to apply grouping identifiers to product

  • In Guide Import & Edit Orders, you’ll learn how to use grouping identifiers when importing orders.