# Welcome

Welcome to Lidia Commerce Platform documentation.

**Lidia** is a powerful headless digital commerce product suite for creators who are building modern applications. It is a set of stable micro-service API’s which can be used as BaaS, can be hosted on-premises or on the cloud and management apps on top.

{% hint style="info" %}
**Learn More**\
To discover more about Lidia products and explore additional details, please visit the [Official Lidia Commerce Website](https://www.lidiacommerce.com).
{% endhint %}

## **Introduction to Lidia**

* **Overview**: Lidia provides cutting-edge digital commerce solutions tailored for a wide range of industries. Whether you are launching a marketplace, enhancing your B2B or B2C operations, or managing complex product information, Lidia offers a flexible, scalable, and efficient platform.

### **Our Mission**

* **Empowering Digital Commerce**: At Lidia, our mission is to empower businesses with the tools needed to excel in today’s digital-first world. We focus on helping you grow through innovative, scalable solutions that integrate seamlessly into your operations.

## **How to Use This Documentation**

* **Getting Started**: This documentation is structured to help you navigate Lidia’s platform efficiently. Whether you're a developer, business user, or technical administrator, you can find the relevant sections linked below:

<table><thead><tr><th width="243">Sections</th><th width="398">Descriptions</th><th data-type="content-ref">Links</th></tr></thead><tbody><tr><td>Suites</td><td></td><td></td></tr><tr><td></td><td>Business-to-business</td><td><a href="/pages/v5rObScFBzIwXjAPTbku">/pages/v5rObScFBzIwXjAPTbku</a></td></tr><tr><td></td><td>Business-to-consumer</td><td><a href="/pages/MtStNxkk9w9CEdS0PyBf">/pages/MtStNxkk9w9CEdS0PyBf</a></td></tr><tr><td></td><td>Marketplace Suites</td><td><a href="/pages/CwF2vsbm9rbJ8EXNd9ms">/pages/CwF2vsbm9rbJ8EXNd9ms</a></td></tr><tr><td>Products</td><td></td><td></td></tr><tr><td></td><td>Lidia Commerce Engine</td><td><a href="/pages/EhGYZMosJSejUxRIag6y">/pages/EhGYZMosJSejUxRIag6y</a></td></tr><tr><td></td><td>Product Information Management</td><td><a href="/pages/OK98jbiHdU45uL4wUwRv">/pages/OK98jbiHdU45uL4wUwRv</a></td></tr><tr><td></td><td>Lidia Rating &#x26; Reviews</td><td><a href="/pages/wkcK0Mhn0AWtTsq9uaet">/pages/wkcK0Mhn0AWtTsq9uaet</a></td></tr><tr><td></td><td>Lidia Promotion Engine</td><td><a href="/pages/TCRttHbb0e7ZPrq4m76K">/pages/TCRttHbb0e7ZPrq4m76K</a></td></tr><tr><td>Product Setup Guides</td><td></td><td><a href="/pages/ruc4cwv3RuhRKtJGC6Bu">/pages/ruc4cwv3RuhRKtJGC6Bu</a></td></tr><tr><td></td><td>PIM Quick Start Guide</td><td><a href="/pages/STR8jDFUy24DMirRs8Yz">/pages/STR8jDFUy24DMirRs8Yz</a></td></tr><tr><td>User Guides</td><td></td><td></td></tr><tr><td></td><td>Lidia Console</td><td><a href="/pages/maQ7JXAhoXjjPOs00bAc">/pages/maQ7JXAhoXjjPOs00bAc</a></td></tr><tr><td></td><td>Lidia Merchant Console</td><td><a href="/pages/FFFSHrstLjUVy9LWBxjn">/pages/FFFSHrstLjUVy9LWBxjn</a></td></tr><tr><td></td><td>PIM</td><td><a href="/pages/ZClV5fu9nDEqPmWb0ERG">/pages/ZClV5fu9nDEqPmWb0ERG</a></td></tr><tr><td></td><td>Lidia Network Console</td><td><a href="/pages/rOEGWjTBaFLCavRdsRRe">/pages/rOEGWjTBaFLCavRdsRRe</a></td></tr><tr><td>Developer Documantation</td><td></td><td></td></tr><tr><td></td><td>Lidia API</td><td><a href="/pages/0d8NN6sPaD91QKah5uzP">/pages/0d8NN6sPaD91QKah5uzP</a></td></tr><tr><td>Support&#x26;FAQs</td><td></td><td></td></tr><tr><td></td><td>If you need any further assistance, feel free to reach out to our support team, or visit our support center.</td><td><a href="/pages/9PoxEAdfcwwuRmHlQVKS">/pages/9PoxEAdfcwwuRmHlQVKS</a></td></tr><tr><td></td><td>Find answers to the most common questions about Lidia’s platform, features, and usage.</td><td><a href="/pages/mryRCeCyJIeBpHA5SFEp">/pages/mryRCeCyJIeBpHA5SFEp</a></td></tr><tr><td></td><td>Stay up to date with the latest updates, features, and improvements in Lidia’s platform.</td><td><a href="/pages/3PpqZuCkymVjTvwgfGwc">/pages/3PpqZuCkymVjTvwgfGwc</a></td></tr></tbody></table>


# Why Lidia

Lidia offers a powerful, comprehensive platform designed to meet the evolving needs of digital commerce. Our solutions empower businesses by providing faster integrations, efficient processes, cost savings, and scalable architecture. Here’s why Lidia is the best choice for your business:

***

<div><figure><img src="/files/aILZkhy7OJVghqXzUEl1" alt=""><figcaption></figcaption></figure> <figure><img src="/files/vbIR9hFyZeSxjXVarFDF" alt=""><figcaption></figcaption></figure></div>

<div><figure><img src="/files/YsPYaPWe6o0y9KURyvpy" alt=""><figcaption></figcaption></figure> <figure><img src="/files/gmmmtTYZ6XXy8cGVPZgA" alt=""><figcaption></figcaption></figure></div>

***

### **Faster and Easier Integrations**

Lidia accelerates your business capabilities by offering seamless integration with your existing systems and third-party services. Our well-documented APIs make it easy to connect Lidia with your existing tools, reducing the time and effort needed to get up and running. Whether integrating with ERP systems, payment gateways, or logistics providers, Lidia ensures a smooth and efficient process, allowing your business to scale quickly.

***

### **More Efficient Processes**

Lidia enhances operational efficiency across all aspects of digital commerce, from order management to customer service. Our platform streamlines workflows through automation, reducing manual tasks and minimizing errors. This leads to faster order processing, improved customer satisfaction, and a more agile business operation overall. Lidia enables you to focus on growth rather than getting bogged down by operational inefficiencies.

***

### **Lower Total Cost of Ownership**

With Lidia, you can reduce the total cost of ownership (TCO) through a modular and scalable architecture. Instead of investing in monolithic, one-size-fits-all solutions, Lidia allows you to choose only the modules and features that your business needs, lowering acquisition and integration costs. Moreover, our platform’s ease of maintenance reduces the need for costly, ongoing technical support, allowing you to allocate resources more effectively.

***

### **Composable Architecture**

Lidia’s composable architecture offers unmatched flexibility and adaptability. You can select and combine different modules and services to create a tailored solution that fits your specific business requirements. This modularity not only makes it easy to scale as your business grows but also allows you to quickly adapt to new market opportunities or operational changes without needing a complete overhaul of your system.

***

### **Enterprise-Grade Solutions**

Lidia is built to handle the demands of large-scale enterprise operations. Our platform provides robust, secure, and scalable solutions that ensure reliability and performance, even during peak business periods. From high-volume transactions to complex order management, Lidia supports your business with enterprise-grade capabilities that keep operations running smoothly and securely.

***

### **Centralized Control**

With Lidia, you gain centralized control over your entire digital commerce ecosystem. Our platform consolidates the management of products, orders, and customer data across all your channels into a single, unified system. This not only simplifies oversight but also enhances decision-making by providing comprehensive insights and analytics from a single source of truth.

***

Lidia is more than just a digital commerce platform—it’s a strategic partner that helps you drive growth, improve efficiency, and stay ahead in a competitive market. Lidia is an effective solution for businesses to unlock their full potential.


# Lidia Solutions

Lidia offers a comprehensive suite of digital commerce solutions designed to help businesses streamline their operations, engage with customers, and adapt to rapidly changing market dynamics. With a modular, API-first architecture, Lidia provides flexibility, scalability, and the ability to customize solutions for various business models, including B2C, B2B, and marketplace environments.

## **Core Product Suites**

{% content-ref url="/pages/CwF2vsbm9rbJ8EXNd9ms" %}
[Lidia Marketplace Suite](/suites/lidia-marketplace-suite)
{% endcontent-ref %}

{% content-ref url="/pages/MtStNxkk9w9CEdS0PyBf" %}
[Lidia B2C Suite](/suites/lidia-b2c-suite)
{% endcontent-ref %}

{% content-ref url="/pages/v5rObScFBzIwXjAPTbku" %}
[Lidia B2B Suite](/suites/lidia-b2b-suite)
{% endcontent-ref %}

### **Flexibility and Customization**

* **Deployment Options**: Lidia supports both on-premise and cloud-based deployments across multiple platforms, including AWS, Azure, and Kubernetes. This allows businesses to scale their infrastructure as needed, ensuring optimal performance​.
* **No-Code Tools**: Lidia offers no-code schema design tools, allowing companies to easily configure product data schemas without developer support. This makes it easier to manage product information for different sales channels​.

### **Consulting and Support Services**

* **Expert Consultation**: Lidia provides senior consultancy services to help businesses define their requirements, design their commerce platforms, and manage successful implementations​.
* **Training and Documentation**: Comprehensive training sessions and detailed documentation are provided for all platforms to ensure that teams can operate Lidia’s tools effectively​​.

## Key Components of Lidia Solutions

**Lidia,** is a complete e-commerce solution for enterprises. It includes a micro-service based, scalable e-commerce engine for developers and management apps for admins and merchants. It can run both on cloud and on-premise.

<figure><img src="/files/yP7iB075U2vE4iRjrrfJ" alt=""><figcaption><p>Lidia Commerce Platform </p></figcaption></figure>

Lidia Commerce Platform includes a **digital commerce engine** developed with a MACH (Microservices-based, API-first, Cloud-native, and Headless) approach. Every service in this engine exposes it's own api's. More details about API endpoints you can found in our developer site.

### Components

{% content-ref url="/pages/PF9BGFMyWJewBIOk4Hsz" %}
[Lidia Console](/components/lidia-console)
{% endcontent-ref %}

{% content-ref url="/pages/dIBVSpBkQno0NPzJQ0Gr" %}
[Lidia Merchant Console](/components/lidia-merchant-console)
{% endcontent-ref %}

{% content-ref url="/pages/LzHFRfs1rcHtnVNngMJT" %}
[Broken mention](broken://pages/LzHFRfs1rcHtnVNngMJT)
{% endcontent-ref %}

{% content-ref url="/pages/0d8NN6sPaD91QKah5uzP" %}
[API Documantation](/products/lidia-commerce-engine/api-documantation)
{% endcontent-ref %}

{% content-ref url="/pages/SjGQSYc8I9teOeQE7XTk" %}
[Lidia Worker](/components/lidia-worker)
{% endcontent-ref %}

{% content-ref url="/pages/qqO2VcYV80GeyVJXHLdp" %}
[Lidia Static](/components/lidia-static)
{% endcontent-ref %}

## [More details about the platform](https://www.lidiacommerce.com/)


# Onboarding

### Registration

In order to use any Lidia Commerce solution, you need to have a valid user account on the Lidia platform.

Please go to <https://www.lidiacommerce.com/register> <https://www.lidiacommerce.com/get-in-touch> and complete your registration.

After a successful registration, our system will send you an e-mail including further instructions.

### Lidia Cockpit


# Lidia Marketplace Suite

## Overview

The Lidia Marketplace Suite is a comprehensive set of tools designed to enable businesses to build, manage, and scale state-of-the-art online marketplaces. Tailored to enterprise needs, it facilitates digital transformation for companies from diverse industries by centralizing catalog management, integrating payment solutions, streamlining logistics, and providing tools for customer support, dispute resolution, and more. This suite is built on Lidia’s API-first, micro-service architecture, making it versatile, scalable, and ready for integration into various digital commerce ecosystems.

### Don't build a store, build a shopping mall.

Lidia Marketplace Suite is a bundle of cloud ready digital commerce tools enabling you to create, manage, and scale a state-of-the-art, competitive, successful enterprise-grade online marketplace.

{% hint style="info" %}

### Go, launch your own online marketplace.

Once deployed on to your favorite infrastructure you can start managing your product catalog and on-boarding merchants immediately. Multiple customized user interfaces built on top of the engine will help you build an omni-channel strategy, get more orders. Existing integrations will enable you getting payments, delivering packages easily.

[Request Demo](https://www.lidiacommerce.com/get-in-touch)
{% endhint %}

<figure><img src="/files/mlFS6vqJlBOf5iUzQ2Zu" alt=""><figcaption></figcaption></figure>

The Lidia Marketplace Suite is a robust solution for building and managing state-of-the-art online marketplaces. Here's how it aligns with the topics you've highlighted:

{% hint style="info" %}
To view Marketplace suite features in detail, please follow the [link](https://app.gitbook.com/o/-LelnTxjc6Q8VcVJf2Bf/s/-LelnWMSgdO9EDQG73lr/~/changes/268/suites/lidia-marketplace-suite/features).
{% endhint %}

### Allows you to run an online marketplace business.

The Lidia Marketplace Suite provides all the necessary tools to create, manage, and scale an online marketplace, enabling you to host multiple sellers on a single platform. Key features include:

* **Multi-Vendor Management:** Facilitates onboarding and management of numerous sellers, supporting a variety of products and services​​.
* **Centralized Catalog Management:** Ensures a cohesive presentation of products from different vendors, improving searchability and comparison for customers​.
* **Comprehensive Order and Inventory Management:** Streamlines operations for vendors and administrators alike, enhancing marketplace efficiency​​.

### Creates a network effect with more sellers and buyers joining the platform.

The suite is designed to foster network effects by providing:

* **Merchant-Centric Tools:** Easy-to-use merchant consoles for inventory and order management, encouraging vendor participation​​.
* **Customer-Centric Features:** An engaging user interface and integrated payment and logistics solutions that attract buyers, thereby enticing more sellers​​.
* **Analytics-Driven Growth:** Advanced reporting tools to track marketplace performance and customer behavior, enabling informed decision-making to enhance platform appeal​.

### Enables multiple streams of revenue include transaction fees, listing fees, advertising revenue, and premium services.<br>

The Lidia Marketplace Suite supports diverse monetization strategies:

* **Transaction Fees:** Commission on sales made through the platform.
* **Listing Fees:** Charges for merchants to list their products on the marketplace.
* **Advertising Revenue:** Opportunities for vendors to promote their products through featured listings and sponsored ads.
* **Premium Services:** Subscription plans for advanced features or additional visibility​​​.


# Key Capabilities

## Key Capabilities

### **Multi-Vendor Environment**

* **Onboarding and Management**: The suite supports a multi-merchant setup, enabling the seamless onboarding and management of multiple sellers on a single platform. This structure increases product variety and service offerings, enhancing the marketplace’s appeal.
* **Catalog Consistency**: Lidia’s centralized catalog management ensures product listings are consistently presented, making it easier for customers to browse, compare, and purchase products.

### **Centralized Catalog Management**

* **Unified Product Listings**: The suite provides a cohesive catalog that unifies product data from all vendors, ensuring a streamlined and user-friendly experience for customers.
* **Metadata and Bulk Updates**: Advanced tools are available to improve product metadata, ensuring accurate and up-to-date product information with easy bulk update capabilities for efficiency.

### **Integrated Payment Systems**

* **Secure Payment Gateway**: Built-in payment processing ensures secure transactions and provides timely payouts for vendors, reducing administrative workload for the marketplace operators.
* **Alternative Payment Options**: Especially useful for clients in regulated sectors, like banking, the suite supports alternative payment methods, such as BNPL (Buy Now, Pay Later) options or loan integration for purchase financing.

### **Order Management and Fulfillment**

* **Order Processing and Tracking**: The suite includes tools for handling order processing, tracking, and fulfillment across vendors, reducing errors and improving order accuracy.
* **Logistics Integrations**: Lidia Marketplace Suite supports integrations with logistics providers for shipping, inventory management, and returns, ensuring a seamless post-purchase experience for both buyers and sellers.

### **Customer Support and Claim Management**

* **Dispute Resolution**: The suite offers dedicated support for handling inquiries and resolving disputes, fostering trust and reliability between buyers and sellers.
* **Efficient Returns and Refunds**: Robust tools manage order cancellations, returns, and refunds, ensuring that customer claims are resolved promptly.

### **Analytics and Reporting**

* **Comprehensive Data Insights**: Advanced analytics tools provide valuable insights into sales, customer behavior, and vendor performance, enabling data-driven decision-making to optimize marketplace operations.

### **Security and Compliance**

* **Enterprise-Grade Security**: Lidia Marketplace Suite adheres to industry standards for data security and compliance, protecting sensitive data and ensuring safe transactions.


# Key Components

{% content-ref url="/pages/EhGYZMosJSejUxRIag6y" %}
[Lidia Commerce Engine](/products/lidia-commerce-engine)
{% endcontent-ref %}

Serves as the backbone, managing all critical marketplace functionalities such as catalog, order, inventory, and payment processing.&#x20;

Offers integration with payment gateways, logistics providers, and other third-party services.&#x20;

***

{% content-ref url="/pages/PF9BGFMyWJewBIOk4Hsz" %}
[Lidia Console](/components/lidia-console)
{% endcontent-ref %}

Provides centralized administration for managing marketplace operations, including catalog and customer data.&#x20;

***

{% content-ref url="/pages/dIBVSpBkQno0NPzJQ0Gr" %}
[Lidia Merchant Console](/components/lidia-merchant-console)
{% endcontent-ref %}

Allows merchants to onboard, manage inventory, fulfill orders, and handle customer interactions.&#x20;

***

{% content-ref url="/pages/euWGj4CnAUmJrFK86NQK" %}
[Lidia API](/components/lidia-api)
{% endcontent-ref %}

Facilitates seamless integration with external systems like ERPs, CRMs, and custom applications through its open API framework.&#x20;

***

{% content-ref url="/pages/uy1pqu34d5k3IR9uVSyB" %}
[Lidia Custom UI](/components/lidia-custom-ui)
{% endcontent-ref %}

Supports the creation of tailored user interfaces to meet specific marketplace branding and user experience needs.&#x20;

***

{% content-ref url="/pages/SjGQSYc8I9teOeQE7XTk" %}
[Lidia Worker](/components/lidia-worker)
{% endcontent-ref %}

&#x20;Automates backend workflows and processes, ensuring efficient operations.


# Quickstart


# Lidia B2C Suite

## Overview

The **Lidia B2C Suite** is a comprehensive platform designed to empower businesses to build and optimize their direct-to-consumer (D2C) operations. Perfectly suited for enterprises across industries, it facilitates seamless e-commerce experiences by centralizing product catalogs, streamlining order and customer management, and integrating with payment and logistics providers. Built on Lidia’s API-first, micro-service architecture, the suite offers unmatched flexibility, scalability, and integration capabilities, enabling businesses to adapt to the evolving digital commerce landscape.

<figure><img src="/files/BZAZhYKKPVnfQmZ71pHD" alt=""><figcaption></figcaption></figure>

### State of the art omnichannel shopping experience

Lidia B2C Suite equips you with an agile, feature-rich platform tailored for the dynamic needs of B2C commerce. It integrates cutting-edge tools for sales, marketing, and customer service into one seamless solution to build a modern omni-channel capable 7/24 accessible sales channel.

{% hint style="info" %}

### Engage, Manage, Thrive!

Empower your direct-to-consumer business with the Lidia B2C Suite. Transform your B2C strategy with advanced digital commerce tools, ensuring seamless customer engagement and efficient order management. Unleash the power of direct sales to boost your brand's reach and enhance customer satisfaction.\
[Request Demo](https://www.lidiacommerce.com/get-in-touch)
{% endhint %}

### 24/7 Sales Channel Accessibility

The **Lidia B2C Suite** ensures that your business remains open and accessible to customers around the clock. With robust infrastructure and seamless integration, it supports continuous operations without downtime, enabling customers to browse, purchase, and engage with your platform whenever they want. This feature maximizes sales opportunities and improves customer satisfaction by catering to modern consumer expectations for always-available shopping experiences.

***

### Omni-Channel Capabilities for a Unified Customer Experience

The **Lidia B2C Suite** integrates online and offline channels to create a seamless and cohesive customer experience. By leveraging tools like the optional **Lidia Network Console**, businesses can synchronize inventory, orders, and customer data across physical stores, mobile apps, and online platforms. This approach allows for features like in-store pickups, returns of online purchases at physical locations, and consistent communication across all touchpoints, strengthening customer loyalty and enhancing brand perception.

***

### Tailor-Made, Flexible, and Scalable Architecture

The suite is built on Lidia’s API-first, micro-service architecture, offering unparalleled customization and adaptability. Businesses can tailor the platform to their specific needs, whether it's custom user interfaces, unique checkout flows, or specialized integrations with existing systems like ERP or CRM. The scalable design ensures that the suite grows with your business, effortlessly handling increased traffic, larger catalogs, and expanded geographic reach without compromising performance.


# Key Capabilities

## Capabilities of the **Lidia B2C Suite**

#### **Product and Digital Asset Management**

* Centralizes product data and digital assets, ensuring consistency and accuracy across all sales channels.
* Allows for efficient updates to product descriptions, images, and variants, maintaining a unified brand experience.

#### **Inventory Management**

* Ensures real-time stock level synchronization across sales channels.
* Streamlines product availability to prevent over- or under-selling, enhancing operational efficiency.

#### **Content Management**

* Provides tools for easy updates and management of website content without reliance on technical staff.
* Enables businesses to quickly adapt to market trends with dynamic content changes.

#### **Customer Management**

* Offers smart tools for managing customer profiles, addresses, billing information, and payment data.
* Enhances personalization through insights into customer preferences and purchase history.

#### **Promotion Management**

* Features a dynamic rule engine for creating and managing promotions, discounts, and loyalty programs.
* Encourages customer engagement and drives sales with tailored campaigns.

#### **Order Management**

* Handles the entire lifecycle of an order, from placement to fulfillment, efficiently.
* Supports cancellations, modifications, and order tracking to provide a smooth customer experience.

#### **Payment & Logistics Integrations**

* Seamlessly integrates with diverse payment gateways and logistics providers for global and local markets.
* Ensures secure transactions and optimized delivery processes, enhancing customer satisfaction.

#### **After-Sales Services**

* Manages returns, refunds, and cancellations effectively through the **Solution Center**.
* Acts as a ticket management system to resolve customer issues efficiently, fostering loyalty and trust.

These capabilities ensure the **Lidia B2C Suite** empowers businesses with robust tools to deliver exceptional customer experiences and streamline operations.


# Key Components

## The key components of the **Lidia B2C Suite**&#x20;

{% content-ref url="/pages/EhGYZMosJSejUxRIag6y" %}
[Lidia Commerce Engine](/products/lidia-commerce-engine)
{% endcontent-ref %}

The core of the platform, providing robust capabilities for managing digital commerce operations, including catalog, customer, and order management.

***

{% content-ref url="/pages/PF9BGFMyWJewBIOk4Hsz" %}
[Lidia Console](/components/lidia-console)
{% endcontent-ref %}

A user-friendly administrative interface for managing business operations and customer interactions.

***

{% content-ref url="/pages/euWGj4CnAUmJrFK86NQK" %}
[Lidia API](/components/lidia-api)
{% endcontent-ref %}

Open and well-documented APIs to integrate with third-party systems like ERP and PIM.

***

{% content-ref url="/pages/uy1pqu34d5k3IR9uVSyB" %}
[Lidia Custom UI](/components/lidia-custom-ui)
{% endcontent-ref %}

Allows for the development of tailored user interfaces to fit specific customer and brand needs.

***

{% content-ref url="/pages/SjGQSYc8I9teOeQE7XTk" %}
[Lidia Worker](/components/lidia-worker)
{% endcontent-ref %}

Facilitates the execution of background processes, such as data synchronization and automated tasks.

The suite can also be enhanced with the **Lidia Network Console** for omni-channel capabilities, enabling seamless integration with physical stores for activities such as assisted sales or logistics coordination​​​.


# Quickstart


# Lidia B2B Suite

## **Overview**

The **Lidia B2B Suite** is a robust platform tailored to meet the complexities of business-to-business (B2B) commerce. Designed to empower organizations across diverse industries, it supports seamless operations by centralizing product and service catalogs, optimizing partner relationships, and automating order and logistics management. Its API-first, micro-service architecture ensures high flexibility, scalability, and easy integration with existing ERP, CRM, and other enterprise systems. Equipped with tools like the Lidia Network Console, the suite enhances collaboration, simplifies payment tracking, and provides advanced features for tender management and bulk ordering. With the Lidia B2B Suite, businesses can streamline their workflows, scale their operations, and adapt to the unique demands of the B2B digital commerce landscape.

<figure><img src="/files/E83wmaKn24bAp6c5doDW" alt=""><figcaption></figcaption></figure>

### Traditional commerce re-defined

Lidia B2B Suite is engineered to address the unique complexities of B2B business model, offering robust tools to manage partner relationships, product / service portfolio, orders, and logistics seamlessly.

{% hint style="info" %}

### Seamless collaboration with your network!

Transform your B2B commerce with the Lidia B2B Suite, designed to streamline partner management, order processing, and logistics. Benefit from robust capabilities that enhance efficiency, reduce costs, and improve customer relationships through seamless integrations and advanced digital solutions. Elevate your business operations and stay competitive with tools tailored for the unique demands of B2B transactions.\
[Request Demo](https://www.lidiacommerce.com/get-in-touch)
{% endhint %}

### Enables Quick Digital Reseller or Partner Onboarding

The Lidia B2B Suite streamlines the onboarding process for resellers and partners, allowing them to join the platform with minimal friction. By using simple online forms and automated validation processes (e.g., ID, email, and phone verification), businesses can onboard new partners in just a few steps. Additionally, customizable workflows enable the generation and submission of contracts, ensuring that compliance requirements are met. This rapid onboarding reduces time-to-market for resellers and allows businesses to scale their partner network efficiently.

### Makes Hundreds of Different B2C-Type Promotions Available for B2B Transactions

Lidia B2B Suite incorporates a flexible promotions engine, enabling businesses to create and manage a variety of marketing campaigns traditionally associated with B2C commerce. These include volume-based discounts, bundle offers, loyalty rewards, and time-sensitive deals. Such features help businesses attract and retain partners by providing incentives for bulk purchases, repeat orders, or seasonal promotions. This adaptability drives engagement and creates opportunities for partners to benefit from competitive pricing and special offers.

### Serves Partners with Real-Time Product Catalog and Related Digital Assets

The suite provides partners with a centralized, real-time product catalog integrated with rich digital assets like high-quality images, specifications, and marketing materials. Powered by the Lidia Commerce Engine and its advanced APIs, the platform ensures that partners always have access to up-to-date product information. This reduces miscommunication, enhances transparency, and enables partners to make informed purchasing decisions. The real-time synchronization ensures that any changes in inventory, pricing, or product details are immediately reflected across all channels.


# Key Capabilities

## Key Capabilities

The **Lidia B2B Suite** is a robust digital commerce solution tailored to meet the unique needs of B2B businesses, with capabilities that enhance efficiency, streamline operations, and ensure superior customer experiences. Below are the key features and benefits, mapped to your descriptions:

{% hint style="info" %}

#### Comprehensive Advantages

The **Lidia B2B Suite** combines these features to empower businesses with:

* Increased operational efficiency.
* Enhanced partner and reseller collaboration.
* Reduced dependency on legacy systems through robust integrations.
* Scalable solutions for growing commerce ecosystems.
  {% endhint %}

### **Product and Digital Asset Management**

* **Centralization of Product Data**: Consolidates product information and digital assets, ensuring consistency and accuracy across all sales channels. It eliminates dependencies on legacy systems, offering tools like no-code schema design and bulk update capabilities​​.
* **Data Enrichment**: Allows businesses to enrich product data with easy-to-use tools like Excel, making the system accessible even to non-technical users​.

### **Partner, Reseller, and Store Management**

* **Streamlined Onboarding**: Simplifies partner and reseller onboarding with features like automated registration and user-friendly interfaces. Supports collaboration through custom workflows for tenders and offers​.
* **Reseller Empowerment**: Offers inventory and order management tools that allow partners to list, track, and fulfill orders seamlessly. Distributors can participate actively in sales, contributing to their revenue growth​​.

### **Inventory Management**

* **Real-Time Visibility**: Provides accurate stock levels across channels via a centralized system, enhancing transparency and reducing stockouts​​.
* **Custom Synchronization**: Integrates with ERP systems for periodic updates, ensuring inventory data is always current​.

### **Order and Bulk-Order Management**

* **Bulk Order Facilitation**: Offers tailored order management capabilities for bulk transactions, enabling efficient processing, fulfillment, and tracking​.
* **Smooth Checkout Processes**: Mimics familiar e-commerce experiences, making the platform intuitive for users while accommodating complex order workflows​​.

### **Payment and Logistics Integrations**

* **Seamless Payment Gateways**: Supports a range of payment providers, including innovative options like Buy Now, Pay Later (BNPL) and installment payments​​.
* **Integrated Logistics**: Ensures efficient delivery and returns management through partnerships with multiple logistics providers, giving users flexibility and reliability​​.

### **Solution Center and Ticket Management**

* **Customer Support Automation**: Features a dedicated solution center for managing returns, cancellations, and disputes. This enhances the customer experience and improves response times​.
* **Internal Ticketing System**: Streamlines after-sales operations and fosters accountability in customer service​​.

This platform is designed for organizations seeking to modernize their B2B operations, create seamless partner networks, and adapt to evolving market demands.


# Key Components

## The key components of the **Lidia B2B Suite**&#x20;

{% content-ref url="/pages/EhGYZMosJSejUxRIag6y" %}
[Lidia Commerce Engine](/products/lidia-commerce-engine)
{% endcontent-ref %}

The core of the platform, providing robust capabilities for managing digital commerce operations, including catalog, customer, and order management.

***

{% content-ref url="/pages/PF9BGFMyWJewBIOk4Hsz" %}
[Lidia Console](/components/lidia-console)
{% endcontent-ref %}

A user-friendly administrative interface for managing business operations and customer interactions.

***

{% content-ref url="/pages/euWGj4CnAUmJrFK86NQK" %}
[Lidia API](/components/lidia-api)
{% endcontent-ref %}

Open and well-documented APIs to integrate with third-party systems like ERP and PIM.

***

{% content-ref url="/pages/uy1pqu34d5k3IR9uVSyB" %}
[Lidia Custom UI](/components/lidia-custom-ui)
{% endcontent-ref %}

Allows for the development of tailored user interfaces to fit specific customer and brand needs.

***

{% content-ref url="/pages/SjGQSYc8I9teOeQE7XTk" %}
[Lidia Worker](/components/lidia-worker)
{% endcontent-ref %}

Facilitates the execution of background processes, such as data synchronization and automated tasks.

The suite can also be enhanced with the **Lidia Network Console** for omni-channel capabilities, enabling seamless integration with physical stores for activities such as assisted sales or logistics coordination​​​.


# Quickstart


# Lidia Commerce Engine

## What is a Headless Commerce Engine?

A headless commerce engine separates the front-end customer experience from the back-end business processes. This architecture allows businesses to deliver seamless and consistent shopping experiences across multiple channels—be it web, mobile, social media, or IoT devices—by decoupling the presentation layer from the commerce logic. Unlike traditional systems, headless commerce provides the flexibility to innovate rapidly, enhance user interfaces, and customize workflows without being constrained by back-end limitations. This approach enables organizations to create unique, tailored experiences while maintaining robust commerce capabilities on the back end.

## Key Aspects of Lidia Commerce Engine

The Lidia Commerce Engine is a powerhouse designed for modern digital commerce needs, providing unmatched flexibility, scalability, and reliability. Key aspects include:

* **Faster Time-to-Market Faster**&#x20;

  Time-to-Market  Accelerates development and deployment processes, enabling businesses to launch new features and updates quickly, thus reducing time-to-market.
* **Flexibility and Customization**&#x20;

  Offers unparalleled flexibility to customize the front-end user experience independently of back-end commerce logic, allowing for tailored and unique digital storefronts.&#x20;
* **Omnichannel Capabilities**&#x20;

  Supports omnichannel strategies, allowing businesses to provide a seamless and integrated shopping experience across all customer touchpoints.&#x20;
* **Scalability**

  Easily scales with business growth, supporting increased traffic and transaction volumes without compromising performance.&#x20;
* **API-First Architecture**&#x20;

  Provides robust APIs that allow seamless integration with any front-end framework, enabling businesses to deliver consistent experiences across web, mobile, and other channels.&#x20;
* **Enhanced Security**&#x20;

  Ensures that sensitive data and transactions are secure, with robust security protocols and compliance with global standards.

## **Target Audience / Sectors**

Sectors illustrate the broad industry categories where Lidia PIM can drive substantial value. By identifying the unique needs and trends within these industries, we can strategically position our suite to address their specific challenges and opportunities.

<div><figure><img src="/files/ATQOfFSXXdMgA1OsiXUw" alt=""><figcaption></figcaption></figure> <figure><img src="/files/l0piYNQeocZ30aj6wRVK" alt=""><figcaption></figcaption></figure> <figure><img src="/files/tl4MKdNkmIGjOoRySmDK" alt=""><figcaption></figcaption></figure> <figure><img src="/files/jVxQi1czIJH7C3svzAEF" alt=""><figcaption></figcaption></figure></div>

<div><figure><img src="/files/AmpzPNtmia5WXFP3U82m" alt=""><figcaption></figcaption></figure> <figure><img src="/files/urqTJF8XCi5WSOoJcZPJ" alt=""><figcaption></figcaption></figure> <figure><img src="/files/D8YDhKFXMee9alE0k2Vo" alt=""><figcaption></figcaption></figure> <figure><img src="/files/D6UZ2rFXuztSN8Lhhrhx" alt=""><figcaption></figcaption></figure></div>

The **Headless, API-first, Micro-service Based Scalable Platform** **Lidia Commerce Engine** emphasizes flexibility, modularity, and scalability, supporting businesses to manage diverse digital commerce operations seamlessly. Here's how these features are reflected:

1. **Headless Architecture**: Lidia Commerce Engine is designed to be "headless," meaning the backend operations (like managing orders, inventory, etc.) are decoupled from the frontend presentation layer. This allows businesses to create custom user interfaces tailored to their needs, whether it's for a website, mobile app, or other digital touchpoints, without being restricted by the backend system​​.&#x20;
2. **API-First Approach**: Lidia Commerce Engine is built with an API-first approach, ensuring that all functionalities are accessible via well-documented, open APIs. This makes it easy to integrate with existing systems such as ERP, CRM, or PIM systems, and to extend capabilities with third-party services, including payment gateways and logistics providers. This API-first architecture supports businesses in building scalable, flexible ecosystems​​.
3. **Microservice-Based Platform**: The engine is composed of 18 distinct microservices (such as inventory, order, identity, and marketing), each handling specific tasks. This modular structure enhances scalability, maintainability, and flexibility, allowing businesses to scale individual services independently.&#x20;

The Lidia Commerce Engine offers flexible deployment options, allowing it to be run both in the cloud and on-premises. Here’s an overview of this capability:

1. **Cloud Deployment**:
   * Lidia Commerce Engine supports deployment on leading cloud platforms like **Amazon AWS**, **Microsoft Azure**, and **Huawei Cloud**. This allows businesses to leverage cloud scalability, cost-efficiency, and flexibility.
   * Cloud deployments are ideal for companies looking to scale quickly, manage infrastructure less directly, and utilize the built-in security and disaster recovery mechanisms provided by cloud vendors.
2. **On-Premises Deployment**:
   * For businesses that prefer or require data to be stored and managed in their own infrastructure due to regulatory, security, or legacy system integration needs, Lidia Commerce Engine can also be deployed on-premises.
   * This option provides more control over data and infrastructure and is particularly useful for organizations with strict compliance requirements or specific industry regulations.
3. **Platform Flexibility**:
   * Whether in the cloud or on-premises, Lidia Commerce Engine can run on **Kubernetes** or **Virtual Machines (VMs)**. This ensures that businesses can tailor the infrastructure based on their needs, whether they seek containerized environments for faster scaling or VM-based setups for stability and legacy system compatibility.

This flexibility in deployment allows Lidia Commerce Engine to adapt to various business environments, providing options for organizations with diverse infrastructure needs​​​.

<br>


# Features

## The Powerhouse for Your Digital Success!

Lidia Commerce Engine is the core component of Lidia Commerce Platform and the powerhouse behind all operations.It is a state-of-the-art Backend as a Service (BaaS) solution, designed to empower mid and large businesses with the tools and flexibility needed to excel in the digital commerce space.

<figure><img src="/files/KsX0Tqsa39peM1j0iodF" alt=""><figcaption><p>Lidia Commerce Engine</p></figcaption></figure>


# API Documantation

The **Lidia API** is a comprehensive, open API designed to provide seamless integration with the Lidia Commerce Engine. It offers an extensive set of endpoints for managing products, customers, orders, payments, and other e-commerce operations. The API follows RESTful principles and supports JSON format for request and response payloads.

#### Key Features

* **Microservice Architecture**: Leverages 18 microservices for modular and scalable integration.
* **Headless Commerce Support**: Provides back-end commerce capabilities while allowing custom front-end experiences.
* **Integration Ready**: Supports integration with third-party systems such as ERP, CRM, logistics providers, and payment gateways.
* **Comprehensive Documentation**: All API endpoints are fully documented with example requests and responses for quick implementation.

{% hint style="info" %}
This section provides a high-level overview of the Lidia API, focusing on core services for developers. For detailed technical documentation, please refer to our external; [API documentation link](https://dev.lidiacommerce.com/).
{% endhint %}

<table><thead><tr><th width="140">Services</th><th width="450">Descriptions</th><th width="236" data-type="content-ref">Page Links</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td>Identity</td><td><p>Manages roles, users, authentication and consents</p><p><br></p></td><td><a href="/pages/-M7WQGRNwprI52I-AMyN">/pages/-M7WQGRNwprI52I-AMyN</a></td></tr><tr><td>Metadata</td><td>Manages product, category, trademark and list data. This is the PIM (Product Information Management) of the Lidia Platform.</td><td><a href="/pages/d67d9bOgxZCORrWoaK53">/pages/d67d9bOgxZCORrWoaK53</a></td></tr><tr><td><p>Inventory</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-metadata"><br></a></p></td><td><p>Manages store, warehouse and inventory data. Inventory concept includes SKU's, price and stock.</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-metadata"><br></a></p></td><td><a href="/pages/JOtBFUp2J4EbRCZ93efm">/pages/JOtBFUp2J4EbRCZ93efm</a></td></tr><tr><td><p>Content</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-inventory"><br></a></p></td><td><p>Manages storefronts(showcases), menus and dynamic pages, acts as a headless CMS for your application.</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-inventory"><br></a></p></td><td><a href="/pages/JanW7Sgt4LxWT5MXT8Ms">/pages/JanW7Sgt4LxWT5MXT8Ms</a></td></tr><tr><td>Order</td><td><p>Manages cart, orders, deliveries and claims (cancellation, return).</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-content"><br></a></p></td><td><a href="/pages/6lFrY1zp6tNIJhRuEIm8">/pages/6lFrY1zp6tNIJhRuEIm8</a></td></tr><tr><td>Marketing</td><td><p>Manages promotions and coupons with a smart condition-award engine.</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-order"><br></a></p></td><td><a href="/pages/nq0win1H5LoU7CUOQfMq">/pages/nq0win1H5LoU7CUOQfMq</a></td></tr><tr><td>Organization</td><td><p>Manages organizations, branches, contacts for your application.</p><p><a href="https://docs.lidiacommerce.com/archive/architecture/services/lidia-marketing"><br></a></p></td><td><a href="/pages/yCFMnmVO68P8uA4JtFgZ">/pages/yCFMnmVO68P8uA4JtFgZ</a></td></tr><tr><td>Subscription</td><td> Manages subscription-based services, including renewals, cancellations, and customer access.</td><td><a href="/pages/Qi9kfmkNJqOuCgDKH5tL">/pages/Qi9kfmkNJqOuCgDKH5tL</a></td></tr><tr><td>Collector</td><td>Gathers and consolidates data from multiple sources, enabling comprehensive analytics and reporting.</td><td><a href="/pages/raUC629QfXcTUeooMlNw">/pages/raUC629QfXcTUeooMlNw</a></td></tr><tr><td>Notifications</td><td>Manages the creation and delivery of notifications to users, ensuring timely updates for various events.</td><td><a href="/pages/6jRhefLOXB6BcuvSZtFl">/pages/6jRhefLOXB6BcuvSZtFl</a></td></tr><tr><td>Delivery</td><td>Handles the logistics of order delivery, integrating with shipping providers and managing tracking information.</td><td><a href="/pages/RIdtaSMjfRVgBMVrsFoK">/pages/RIdtaSMjfRVgBMVrsFoK</a></td></tr><tr><td>Case</td><td>Manages customer service cases, providing tools for tracking, resolving, and reporting issues.</td><td><a href="/pages/cttXZWPp4dSOvv1pOY4c">/pages/cttXZWPp4dSOvv1pOY4c</a></td></tr><tr><td>Social</td><td>Integrates social media platforms and enables social commerce functionalities within the application.</td><td><a href="/pages/vM8MlOhIX7EC0D1iiogN">/pages/vM8MlOhIX7EC0D1iiogN</a></td></tr><tr><td>Document</td><td>Manages document storage and retrieval, facilitating the handling of contracts, invoices, and other critical files.</td><td><a href="/pages/jZZHIUfFXjGeFnulF1om">/pages/jZZHIUfFXjGeFnulF1om</a></td></tr><tr><td>Commander</td><td>Provides tools for administrators to control and configure system-wide settings and operations.</td><td><a href="/pages/6WVNpoxP3XV8REie6se7">/pages/6WVNpoxP3XV8REie6se7</a></td></tr><tr><td>Analytics</td><td>Collects and analyzes data across your digital commerce platform, providing insights into performance, customer behavior, and sales trends.</td><td><a href="/pages/WOFejfUuAyyfihUhSBt3">/pages/WOFejfUuAyyfihUhSBt3</a></td></tr><tr><td>Procurement</td><td><p></p><p>Manages supplier relationships, purchase orders, and procurement workflows to streamline the sourcing of products and services.</p><p></p></td><td><a href="/pages/BgaVFg1oTviveqNRPkLR">/pages/BgaVFg1oTviveqNRPkLR</a></td></tr><tr><td>Search</td><td>Powers the search functionality, enabling users to efficiently find products, categories, and content within the application.</td><td><a href="/pages/o8a0DhoxZdnTKT1Lth0Z">/pages/o8a0DhoxZdnTKT1Lth0Z</a></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


# Lidia Identity

Lidia Identity manages roles, users, authentication and consents

## Overview

[Lidia Identity](https://dev.lidiacommerce.com/#aa23960a-325c-4f94-8c54-698dfce9308e) is an API-first product exposing functions to manage roles, users and consents. Details about these concepts you can find below.

Before using Lidia Identity API, you have to log in to the Lidia Commerce Administration Interface with your credentials, **create your application** and get your **ClientId** and **AppKey**.

For more details about registration and creating your applications please click the link below:

If you have a valid Lidia Identity subscription, you will the following options when you log in to the administration interface of Lidia Commerce Platform:

* Create, update, delete your applications (you have to create your
* List roles
* See details of each role
* Create, update and delete roles
* List users
* See details of each user
* Create, update and delete users
* Add users to roles

So here is a quick example of using Lidia Identity.

1. You create two roles with the names "Administrator" and "User"
2. You create your admin users by using the Lidia Commerce Platform Administration Interface and assign the "Administrator" role to these users.
3. You use the Rest API to create your users with the standard "User" role
4. While logging in users in your application, you query the user role and assign rights to the user based on it's role

{% hint style="info" %}
For more details about registration and creating your applications, please click the [link](https://dev.lidiacommerce.com/#aa23960a-325c-4f94-8c54-698dfce9308e).
{% endhint %}

## Concepts

### Roles

We use multiple roles in today's applications to realize the requirement of different user groups with different set of rights. As an easy example you might think of normal users of your e-commerce application who does not have any kind of access to the administrative features of the application and the team handling the customer care with access to user's contact information, order history and so on.

Lidia Identity allows you to create multiple roles and add users to these roles. It is also possible that one user has more than one role.

### Users

Modern applications use membership scenarios very often. Most of the time the requirement as easy as getting the username and/or email address, first name, last name and password during the registration process and saving into the database. The email address and password will be used to sign in users where other data (for some applications even more data like gender, date of birth etc) will be used to create user segments for marketing purposes.

Lidia Identity has a large set of out-of-the-box fields for the user data in addition to two extension options, tags and properties.

### Consents

Legal restrictions lately forced us to record explicit consents of users for different types of engagements. To reach out to users by using communication channels such as e-mail and text messages requires marketing consents where processing personal data requires consent of the user especially asked for this purpose. We also have to consider to get separate consents for different legal regions such as Europe (EU) and United States even to use cookies. One consent for everything does not work anymore.

Lidia Identity helps you record user consents in a chronological way. We do not use one record for each user and do updates on it, we save every consent-related activity as a new record so we can say exactly at a specific point of time which consents do we have for a specific user.

## Versions

### Current

* Added create, update, delete and query functions for users
* Added create, update, delete and query functions for user addresses
* Added create, update, delete and query functions for user billing information
* Added create, update, delete and query functions for user properties and tags
* Added create, delete and query functions for user pictures
* Added create, delete and query functions for user roles
* Added create, update, delete and query functions for user consents
* Added simple stats functions for user data

If you have questions or you need help, please use the link below to reach possible communication channels.


# Lidia Marketing

Manages promotions and coupons with a smart condition-award engine.

## Overview

[**Lidia Marketing**](https://dev.lidiacommerce.com/#9e703fe1-7883-437e-9abb-73cb8b99ee0c) is one of the key microservices in the Lidia Commerce Engine that enhances a business's ability to engage customers effectively through targeted promotional strategies and personalized marketing campaigns. It empowers users with robust tools for creating promotions, discounts, and special offers, while leveraging customer data for segmentation and precision marketing.

{% hint style="info" %}
For more details about registration and creating your applications, please click the [link](https://dev.lidiacommerce.com/#9e703fe1-7883-437e-9abb-73cb8b99ee0c).
{% endhint %}

## Key Concepts

1. **Customer Segmentation:** Lidia Marketing allows businesses to group their customers based on specific criteria such as behavior, purchase history, demographics, or interests. This ensures more personalized and relevant marketing efforts, boosting engagement and conversion rates.
2. **Promotion Management:** The system provides tools for managing different types of promotions such as percentage discounts, buy-one-get-one offers, and time-sensitive campaigns. It supports advanced features like tiered discounts or loyalty programs, allowing businesses to build long-term customer loyalty.
3. **Campaign Automation:** With automated workflows, businesses can set up email campaigns or in-app notifications that trigger based on customer actions. This includes sending personalized messages when a customer abandons a cart or providing tailored offers during key events like birthdays or holidays.
4. **Data-Driven Insights:** The service integrates with [Lidia Analytics](/products/lidia-commerce-engine/api-documantation/lidia-analytics) to track campaign performance in real-time, offering insights into customer behavior and the effectiveness of marketing efforts. This data helps refine future campaigns to maximize ROI.

## Example

Suppose a retail business using Lidia wants to increase sales during the holiday season. They could segment their customers based on previous holiday purchases and use Lidia Marketing to set up targeted promotions. For instance, they might offer a 20% discount on home decor to customers who bought furniture last year. Automated emails would be sent to these customers with personalized offers, and the business could monitor the promotion's success via Lidia’s analytics tools.

In summary, **Lidia Marketing** provides businesses with powerful tools to engage customers through personalized, data-driven marketing initiatives. It simplifies campaign management while ensuring a strategic approach to driving sales and customer retention.


# Lidia Metadata

Manages product, category, trademark and list data. This is the PIM (Product Information Management) of the Lidia Platform.

## **Overview**

[**Lidia Metadata**](https://dev.lidiacommerce.com/#68a8a237-fcdd-4c5e-b6fd-223265f49f77) is an API-first product that exposes functions to manage and structure metadata for your digital commerce platform. Metadata helps organize information related to products, categories, and other core elements of your business. Details about these concepts are provided below.

{% hint style="info" %}
For more details about registration and creating your applications, please click the [link](https://dev.lidiacommerce.com/#68a8a237-fcdd-4c5e-b6fd-223265f49f77).
{% endhint %}

Here is a quick example of using **Lidia Metadata**:

* You create a custom metadata schema for "Data Schemas" in the Lidia Commerce Platform Administration Interface.
* You define fields like "Material," "Weight," and "Color."
* You use the **Lidia Metadata API** to assign these specifications to each product in your catalog.
* When customers browse your products, the metadata you've created helps filter, categorize, and display the relevant details.

You can find a sample implementation of the scenario above here.

## Concepts

### **Metadata Schemas**

Metadata schemas are structured sets of information that help define the attributes of products, categories, and other core entities. By using metadata, you can add detailed specifications like size, material, or region to any element in your application. Lidia Metadata allows you to create custom schemas to tailor your commerce platform's information structure to your business needs.

### **Metadata Types**

Metadata types define the categories of information that can be assigned to your products or other entities. For example, you might create metadata for product specifications, content management, or customer preferences. This allows flexibility in how information is stored and accessed throughout your application.

### **Custom Fields**

Custom fields are user-defined fields that allow you to extend the basic structure of your metadata. These fields can represent any type of data your business needs, such as technical specifications for products or custom categorizations for different regions.


# Lidia Inventory

Manages store, warehouse and inventory data. Inventory concept includes SKU's, price and stock.

## **Overview**

[**Lidia Inventory**](https://dev.lidiacommerce.com/#a4531581-d17e-40db-b2a6-063b7d154202) is an API-first solution designed to manage store, warehouse, and inventory data for your digital commerce platform. It keeps stock levels, pricing, and SKU details synchronized, ensuring accurate tracking and smooth order fulfillment. More information on these concepts is provided below.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#a4531581-d17e-40db-b2a6-063b7d154202).
{% endhint %}

You can find a sample implementation of the scenario below;

* You create an inventory structure for your warehouses and stores in the Lidia Commerce Platform Administration Interface.
* You define SKUs for each product, setting attributes like quantity, price, and location.
* You use the [**Lidia Inventory**](https://dev.lidiacommerce.com/#a4531581-d17e-40db-b2a6-063b7d154202) **API** to track stock levels across multiple warehouses and update the availability in real-time.
* When customers place orders, the inventory data ensures accurate stock levels, allowing smooth order fulfillment and restocking alerts.

## Concepts

### **SKUs (Stock Keeping Units)**

A **SKU** represents an individual product variant in your inventory. SKUs are used to manage stock levels, pricing, and availability for each product across multiple locations. **Lidia Inventory** allows you to create and manage SKUs to ensure accurate tracking of all products in your catalog.

### **Stock Management**

**Lidia Inventory** provides powerful stock management features, allowing you to track and update stock levels in real-time. You can manage inventory across multiple locations, ensuring that stock is correctly allocated and visible to customers, reducing the chances of overselling.

### **Price Management**

With **Lidia Inventory**, you can set and update prices for each product variant (SKU) across different sales channels. This flexibility ensures that price changes are reflected in real-time, whether due to promotions, discounts, or regional pricing variations.


# Lidia Content

Manages storefronts(showcases), menus and dynamic pages, acts as a headless CMS for your application.

## **Overview**

[**Lidia Content** ](https://dev.lidiacommerce.com/#77966ef9-6236-4520-8145-3f7563dfdbed)manages  digital content across your commerce platform. It helps organize and maintain assets like product descriptions, images, videos, and other multimedia, ensuring a seamless and engaging customer experience. Details about these concepts are provided below.

{% hint style="info" %}
You can find a sample implementation of the scenario below here.
{% endhint %}

## Quick Example

* You create a content structure for your digital assets in the Lidia Commerce Platform Administration Interface.
* You define fields like "Product Description," "Image URL," and "Video Links."
* You use the [**Lidia Content**](https://dev.lidiacommerce.com/#77966ef9-6236-4520-8145-3f7563dfdbed) **API** to assign relevant content to each product or category in your catalog.
* When customers browse products, the content you've added enhances their experience by providing detailed information and multimedia support.

## Concepts

### **Content Types**

Content types define different categories of digital assets, such as product descriptions, images, or videos. **Lidia Content** allows you to manage various content types to enhance product pages and other areas of your application.

### **Content Management**

**Lidia Content** offers powerful tools for managing and organizing digital assets, enabling you to easily create, update, and assign content to specific products or categories. This ensures consistency across your platform and keeps content fresh and relevant.

### **Multimedia Support**

With **Lidia Content**, you can manage different forms of media—like images, videos, and documents—across your digital channels. This allows you to deliver rich, interactive experiences to customers by integrating multimedia directly into your product catalog.


# Lidia Order

Manages cart, orders, deliveries and claims (cancellation, return).

## Overview

[**Lidia Order**](https://dev.lidiacommerce.com/#79ba0e4b-5257-47eb-9f06-24ee52efbdfd) manages orders across your commerce platform, handling everything from creation to fulfillment. It ensures that customer orders are processed efficiently and accurately, providing a smooth purchasing experience. Details about these concepts are provided below.

{% hint style="info" %}
You can find a sample implementation of the scenario below here.
{% endhint %}

## Quick Example

* You create an order structure within the **Lidia Commerce Platform Administration Interface**.
* You define order stages like "Pending," "Processing," and "Shipped."
* You use the [**Lidia Order**](https://dev.lidiacommerce.com/#79ba0e4b-5257-47eb-9f06-24ee52efbdfd) **API** to create and update orders based on customer actions and inventory availability.
* As customers place orders, the **Lidia Order Service** ensures that the order is processed and tracked through each stage until fulfillment.

## Concepts

### **Order Lifecycle**

The order lifecycle consists of various stages, such as creation, payment confirmation, fulfillment, and shipment. **Lidia Order** manages the entire process, ensuring each stage is handled smoothly and that customers are updated on the status of their orders.

### **Order Management**

**Lidia Order** provides tools to create, update, and track orders across multiple sales channels. It integrates seamlessly with other services like **Lidia Inventory** and **Lidia Delivery** to ensure orders are fulfilled based on real-time inventory and shipping data.

### **Payment and Fulfillment**

**Lidia Order** supports payment verification and connects with delivery services to ensure orders are shipped correctly. This integration allows your platform to offer a complete order management solution, from payment to the final delivery.


# Lidia Organization

Manages organizations, branches, contacts for your application.

## **Overview**

[**Lidia Organization**](https://dev.lidiacommerce.com/#f6a9175e-5a99-4147-9720-fabc395e77e3) is a microservice within the Lidia Commerce Engine that provides a structured framework for managing complex organizational hierarchies, permissions, and user roles across various business functions. It is designed to simplify the management of multi-level organizations, including roles, departments, and business units, ensuring that operations run smoothly within larger and more distributed businesses.

## Key Concepts

1. **Role-Based Access Control (RBAC):** Lidia Organization enables businesses to define roles and permissions for users based on their specific responsibilities. For instance, administrators can grant access to different parts of the system (e.g., product management, customer service, or financial data) based on the user’s role, ensuring that employees only access the information relevant to their job functions.
2. **Multi-Tenant Support:** This service supports businesses with multiple divisions, subsidiaries, or partner organizations by providing a flexible structure for managing these separate entities within one platform. Each unit can operate with its own configurations, workflows, and permissions, while still being part of the overarching organization.
3. **Hierarchy Management:** Lidia Organization allows businesses to create and manage a hierarchy of departments, teams, or business units. This structure ensures clear reporting lines and accountability, while making it easier to organize workflows and operational processes across different organizational layers.
4. **Collaboration Across Entities:** The system facilitates collaboration between different teams and departments by defining shared resources, access levels, and inter-department workflows. It supports seamless cooperation across the organization, ensuring that operations remain cohesive even in larger enterprises.

{% hint style="info" %}
You can find a example of the scenario below here.
{% endhint %}

## Example

Consider a multinational corporation using Lidia that operates in different regions with distinct teams for sales, marketing, and logistics. Using Lidia Organization, they can set up separate organizational structures for each regional division. For example, the European division can have its own marketing team with permissions restricted to marketing operations, while the logistics team has access to order management and shipping workflows. The head office administrators can oversee all divisions and manage permissions globally.

In this setup, Lidia Organization ensures that each team has the right tools and access to perform its tasks efficiently while maintaining overall control at the corporate level. This leads to enhanced operational efficiency, clear accountability, and streamlined collaboration across the enterprise.


# Lidia Subscription

Manages subscription-based services, including renewals, cancellations, and customer access.

## **Overview:**

[**Lidia Subscription**](https://dev.lidiacommerce.com/#385f59c6-4f23-41c7-aef2-a587d99c1174) is a microservice in the Lidia Commerce Engine that enables businesses to offer, manage, and optimize subscription-based products or services. It allows companies to create flexible subscription plans, handle recurring billing, and manage customer lifecycles effectively. Lidia Subscription is ideal for businesses operating with a subscription model, offering a seamless experience for both the business and its customers.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#385f59c6-4f23-41c7-aef2-a587d99c1174).
{% endhint %}

## Key Concepts

1. **Subscription Plan Management:** Lidia Subscription allows businesses to create and manage various subscription plans. These can include different tiers (e.g., basic, premium), billing cycles (e.g., monthly, yearly), and pricing options. Businesses can also offer custom or promotional plans to attract new customers or retain existing ones.
2. **Recurring Billing and Payment Handling:** This service supports automated recurring billing, ensuring that customers are charged on time for their subscriptions. It integrates with multiple payment gateways to handle secure transactions, enabling smooth payment processing and reducing friction for both businesses and customers.
3. **Customer Lifecycle Management:** Lidia Subscription provides tools for managing the entire lifecycle of a subscriber. Businesses can track customer activity, handle upgrades or downgrades between plans, process cancellations, and offer retention strategies like discounts or special offers for long-term subscribers.
4. **Automated Notifications and Reminders:** The service includes automated notifications for subscription renewals, payment reminders, and subscription expirations. This helps businesses keep their customers informed and minimizes the risk of involuntary churn due to missed payments.
5. **Analytics and Insights:** Lidia Subscription integrates with analytics tools to provide businesses with insights into their subscription performance. Metrics such as churn rate, customer retention, lifetime value, and active subscribers are available, helping businesses make data-driven decisions to optimize their subscription offerings.

## Example

Suppose a streaming service uses Lidia Subscription to manage its customer base. The company offers three subscription plans: Basic, Standard, and Premium. With Lidia Subscription, the business can easily set up these plans with different pricing structures and billing cycles. When customers sign up, the service automatically handles their recurring payments, sends reminders before renewal, and allows customers to upgrade or downgrade their plans at any time.

In this case, Lidia Subscription ensures that the streaming service can manage its growing subscriber base without manual intervention, providing a smooth experience for both the business and its customers. Additionally, the business can track performance data, like subscription growth and churn rate, to continuously improve its offerings.


# Lidia Case

Manages customer service cases, providing tools for tracking, resolving, and reporting issues.

## **Overview**

[Lidia Case](https://dev.lidiacommerce.com/#8bb5d64a-86a8-481d-9078-feeba22116b3) is a microservice in the Lidia Commerce Engine designed to manage customer support and aftersales processes efficiently. It provides businesses with the tools to track, resolve, and manage customer inquiries, complaints, and service requests. Lidia Case ensures that customer issues are addressed in a structured and timely manner, improving customer satisfaction and retention.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#8bb5d64a-86a8-481d-9078-feeba22116b3).
{% endhint %}

## Key Concepts

1. **Case Management and Tracking:** Lidia Case allows businesses to create, assign, and track customer cases from initiation to resolution. Each case can be categorized based on its type (e.g., inquiry, complaint, technical issue), and support agents can track its progress across multiple stages.
2. **Multi-Channel Support:** The service supports customer interactions across various channels, including email, phone, live chat, and social media. This ensures that customer issues are captured regardless of where they originate, creating a unified case management experience.
3. **Automated Workflows:** Lidia Case includes automated workflows for assigning cases to the right department or team based on predefined criteria. For example, technical issues can be routed to the technical support team, while billing inquiries go to the finance department. This ensures quicker response times and better resource allocation.
4. **Service-Level Agreement (SLA) Management:** The platform helps businesses define and monitor service level agreements (SLAs), ensuring that customer cases are resolved within the agreed-upon timeframes. Alerts and notifications can be set up to remind teams when a case is approaching its SLA deadline, reducing the risk of delayed responses.
5. **Customer Communication and History:** All interactions with a customer regarding a specific case are documented in the system, providing agents with full visibility into the case history. This helps improve communication with the customer, as agents can refer to previous conversations or actions taken.
6. **Reporting and Analytics:** Lidia Case provides detailed reports and analytics on case handling performance, customer satisfaction, and agent productivity. Businesses can use these insights to optimize their customer service processes, identify bottlenecks, and improve overall service quality.

## Example

Imagine an electronics retailer using Lidia Case to handle post-purchase customer issues. If a customer reports a malfunctioning device, the retailer can create a case in Lidia Case, categorize it as a "technical issue," and assign it to the appropriate support team. The system tracks the case from the initial report, through troubleshooting, and finally to resolution (e.g., device replacement or refund).

The customer support agent handling the case can access all previous communication, ensuring the customer doesn’t have to repeat information. The retailer can also set an SLA for technical issues, ensuring the case is resolved within, say, 48 hours. If the deadline approaches, automated alerts will notify the team to take action, ensuring timely support.


# Lidia Search

Powers the search functionality, enabling users to efficiently find products, categories, and content within the application.

## **Overview**

**Lidia Search** is a powerful microservice within the Lidia Commerce Engine, designed to optimize product discovery and enhance the customer search experience on digital commerce platforms. It provides fast, accurate, and intelligent search capabilities, helping users find products, services, or content quickly, which ultimately improves engagement and conversion rates.

## Key Concepts

1. **Full-Text Search:** Lidia Search enables full-text search capabilities, allowing users to input keywords or phrases and receive relevant results. The service indexes all searchable content, including product descriptions, names, SKUs, and metadata, ensuring a comprehensive search experience.
2. **Search Filters and Facets:** The service supports the use of filters (e.g., price, category, brand) and facets, enabling customers to refine their search results based on specific criteria. This allows for more targeted product discovery, especially when browsing large catalogs with many product options.Explore Filters and Facets Setup
3. **Autocomplete and Suggestions:** As users type into the search bar, Lidia Search provides real-time autocomplete suggestions and popular search queries. This helps guide users to relevant results faster, improving the overall search experience and reducing the effort needed to find products.
4. **Synonyms and Misspellings Handling:** Lidia Search accounts for common typos, misspellings, and synonyms, ensuring that users still find the right products even if they don’t spell or phrase their queries perfectly. For example, searching for "smartfone" will still return results for "smartphone."
5. **Personalized Search Results:** Lidia Search can deliver personalized search results based on user behavior, preferences, or past interactions. This means that customers are more likely to see results tailored to their interests, leading to increased relevance and a higher likelihood of conversion.
6. **Ranking and Relevance Tuning:** The service allows businesses to customize how search results are ranked. Product relevance can be fine-tuned based on factors like popularity, recency, availability, or business priorities (e.g., promoting high-margin products at the top of search results).
7. **Search Analytics and Insights:** Lidia Search provides insights into user behavior, such as popular search terms, search success rates, and queries that lead to no results. This helps businesses understand what customers are looking for, enabling them to optimize their product catalog and search functionality.

{% hint style="info" %}
You can find a example of the scenario below here.
{% endhint %}

## Example

Suppose an online fashion retailer uses Lidia Search to improve the customer experience. When a customer types "red dress," the search service quickly provides autocomplete suggestions like "red summer dress" or "red cocktail dress." After submitting the search, the customer can refine their results by selecting filters like "size," "brand," or "price range." Even if the customer types "redd dress," Lidia Search will correct the query and show relevant products.

The retailer can also promote certain products, like highlighting new arrivals or best-selling dresses at the top of the results page, ensuring that important or high-margin items are easily discoverable.


# Lidia Social

Integrates social media platforms and enables social commerce functionalities within the application.

## **Overview**

Lidia Social is a microservice within the Lidia Commerce Engine that focuses on integrating social interactions into the digital commerce experience. It enables businesses to leverage social engagement, user-generated content, and social sharing to enhance customer interaction, drive traffic, and increase conversions. Lidia Social helps businesses build a community around their brand, fostering greater customer loyalty and engagement.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#d4ebbc4d-64ed-4c87-9857-43076c7ffffa).
{% endhint %}

## Key Concepts

1. **User-Generated Content (UGC):** Lidia Social allows customers to leave reviews, ratings, and comments on products or services. This content becomes a valuable part of the purchase decision process, as potential buyers often rely on peer feedback to make informed decisions. UGC can be displayed on product pages, boosting trust and social proof.
2. **Community Engagement:** Lidia Social enables businesses to create and manage online communities within their platform. Customers can participate in discussions, ask questions, and interact with other users, making the platform more interactive and engaging. It can also foster stronger connections between the brand and its customers.
3. **Social Listening and Monitoring:** The service includes social listening capabilities, allowing businesses to track brand mentions and customer sentiment across social media platforms. By monitoring conversations and trends, businesses can respond proactively to customer feedback and stay engaged with the community.
4. **Content Moderation and Management:** Lidia Social provides moderation tools to ensure that user-generated content remains appropriate and aligned with the brand’s values. Automated and manual content moderation options help filter out spam, offensive language, or irrelevant comments, maintaining a positive online environment.
5. **Social Commerce Features:** Lidia Social can integrate social commerce features, enabling customers to discover and purchase products directly from social platforms. This seamless connection between social media and e-commerce enhances the customer journey and simplifies the buying process.

## Example

A beauty brand using Lidia Social could encourage customers to leave product reviews and share their skincare routines on social media. When a customer buys a product, they are prompted to review it and share their purchase on Instagram using a custom hashtag. Other users can engage with these posts, fostering a sense of community and excitement around the brand.

The brand can also collaborate with beauty influencers who post tutorials using their products, and Lidia Social helps track the performance of these collaborations by monitoring social media engagement and tracking sales attributed to the influencer campaigns.


# Lidia Procurement

Manages supplier relationships, purchase orders, and procurement workflows to streamline the sourcing of products and services.

## **Overview**

**Lidia Procurement** is a specialized microservice in the Lidia Commerce Engine designed to streamline and automate the procurement processes for businesses. It enables efficient supplier management, procurement of goods and services, and negotiation workflows within a digital commerce ecosystem. By leveraging Lidia Procurement, businesses can optimize their sourcing operations, manage vendor relationships, and ensure timely procurement of necessary resources.

## Key Concepts

1. **Supplier Relationship Management (SRM):** Lidia Procurement provides robust tools for managing relationships with multiple suppliers. Businesses can track supplier performance, maintain a directory of approved vendors, and manage contracts. The SRM functionality supports negotiation workflows, vendor onboarding, and rating systems, ensuring a high level of compliance and quality in supplier partnerships.
2. **Automated Purchase Orders and Requisitions:** The service automates the creation and tracking of purchase orders (POs) and requisitions. It ensures that once procurement needs are identified, the system automatically generates POs, sends them to approved suppliers, and tracks order fulfillment. This reduces manual intervention, speeding up the procurement process and minimizing errors.
3. **Inventory-Linked Procurement:** Integrated with the Lidia Inventory microservice, Lidia Procurement ensures that procurement actions are directly linked to real-time inventory levels. This enables businesses to automate reorders when stock reaches predefined thresholds, ensuring smooth operations without overstocking or understocking issues.
4. **Spend Management and Budget Control:** The service includes advanced spend management capabilities, allowing businesses to set procurement budgets, track expenses, and optimize cost savings. Businesses can enforce procurement policies to ensure that all spending aligns with approved budgets and that procurement activities stay within financial guidelines.
5. **RFQ and Tender Management:** Lidia Procurement facilitates the Request for Quotation (RFQ) and tendering processes. Businesses can issue RFQs to multiple suppliers, collect bids, and compare offers based on price, delivery terms, and quality metrics. This functionality helps businesses get the best deals while maintaining a competitive procurement process.
6. **Supplier Performance Analytics:** With integrated analytics, Lidia Procurement provides insights into supplier performance, order accuracy, delivery times, and cost-efficiency. These metrics allow businesses to optimize their supply chain by identifying high-performing suppliers and negotiating better terms with underperforming ones.
7. **Compliance and Auditing:** Lidia Procurement ensures that all procurement activities comply with internal policies and external regulations. Auditing tools help maintain a complete history of all procurement transactions, contracts, and supplier communications, ensuring full traceability and regulatory compliance.

## Example

Imagine a large-scale electronics manufacturer using Lidia Procurement to manage its sourcing of raw materials and components. The system tracks inventory levels in real time, and when the stock of a critical component reaches a predefined threshold, Lidia Procurement automatically generates a purchase order to the preferred supplier. Meanwhile, the procurement team uses the RFQ functionality to solicit quotes from multiple suppliers for a new product line, evaluating bids not just on price but also on delivery speed and historical performance metrics captured by the system.

Simultaneously, the manufacturer tracks all procurement spending against the allocated budget, ensuring that all activities align with financial targets, and leverages Lidia Procurement’s auditing tools to ensure full compliance with global trade regulations.


# Lidia Analytics

Collects and analyzes data across your digital commerce platform, providing insights into performance, customer behavior, and sales trends.

## **Overview**

**Lidia Analytics** is a critical microservice in the Lidia Commerce Engine that provides comprehensive data analytics and reporting capabilities. It allows businesses to gather, process, and analyze vast amounts of data generated across their digital commerce operations. By offering insights into sales performance, customer behavior, operational efficiency, and marketing effectiveness, Lidia Analytics helps businesses make informed, data-driven decisions to optimize their operations and drive growth.

## Key Concepts

1. **Real-Time Data Analysis:** Lidia Analytics processes data in real-time, allowing businesses to monitor their operations as they happen. This includes tracking sales, customer interactions, inventory levels, and marketing campaign performance, providing immediate insights into key metrics.
2. **Customizable Dashboards and Reports:** The service enables businesses to create customizable dashboards that display relevant KPIs and metrics, tailored to different roles or departments (e.g., sales, marketing, operations). Users can generate detailed reports on specific aspects of their business, like sales trends, product performance, or customer demographics.
3. **Customer Behavior Insights:** Lidia Analytics provides deep insights into customer behavior, helping businesses understand purchasing patterns, preferences, and engagement levels. This includes tracking customer journeys, analyzing cart abandonment rates, and identifying the most popular products or services, allowing for more effective marketing and product strategies.
4. **Sales Performance Tracking:** The service allows businesses to track their sales performance over time, across different channels, products, and customer segments. Sales data can be segmented by geographic region, product category, or time period, helping businesses identify opportunities for growth or areas needing improvement.
5. **Predictive Analytics:** Lidia Analytics leverages advanced data models to offer predictive analytics, helping businesses forecast future trends based on historical data. For example, it can predict demand spikes during certain seasons or identify customer segments most likely to respond to specific marketing campaigns.
6. **Operational Efficiency Monitoring:** The service helps monitor and optimize operational efficiency by tracking metrics such as order fulfillment times, supply chain performance, and inventory turnover rates. By identifying bottlenecks or inefficiencies, businesses can take proactive steps to streamline operations.
7. **Marketing Performance Analytics:** Integrated with Lidia Marketing, Lidia Analytics tracks the effectiveness of marketing campaigns, helping businesses measure ROI, conversion rates, and customer acquisition costs. This enables more precise targeting and optimization of future marketing efforts.
8. **Advanced Segmentation and Targeting:** Businesses can segment their data based on customer demographics, purchase history, or engagement levels. This segmentation helps in crafting targeted strategies, such as personalized product recommendations or loyalty rewards programs, aimed at specific customer groups.
9. **Data Export and Integration:** Lidia Analytics supports data export in various formats and can integrate with other BI (Business Intelligence) tools, CRMs, or external systems. This flexibility ensures that businesses can analyze data across platforms and systems, making it easy to consolidate and cross-reference insights.

## Example

A global retail company using Lidia Analytics might want to track the performance of its holiday sales campaign. The service allows them to set up a real-time dashboard showing key metrics such as total sales, most purchased products, and regions with the highest sales volume. They can also analyze customer behavior data to see which marketing channels drove the most traffic and conversions.

In another example, the company could use predictive analytics to forecast demand for popular products based on previous holiday seasons, allowing them to adjust inventory levels and optimize logistics accordingly. This minimizes the risk of stockouts or overstocking, ensuring better customer satisfaction and reduced operational costs.


# Lidia Notification

Manages the creation and delivery of notifications to users, ensuring timely updates for various events.

## **Overview**

[Lidia Notification](https://dev.lidiacommerce.com/#3487a081-296c-4620-86df-2de3e030994a) is a microservice within the Lidia Commerce Engine that manages and automates communication with customers and internal users through various channels. It is designed to deliver real-time alerts, messages, and notifications across multiple platforms such as email, SMS, in-app notifications, and push notifications. This service ensures that businesses can maintain timely and relevant communication with their customers, enhancing engagement and improving customer satisfaction.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#3487a081-296c-4620-86df-2de3e030994a).
{% endhint %}

## Key Concepts

1. **Multi-Channel Communication:** Lidia Notification supports a variety of communication channels, including email, SMS, in-app notifications, and push notifications. This allows businesses to reach customers through their preferred platform, ensuring a seamless and effective notification strategy.
2. **Event-Driven Notifications:** The service triggers notifications based on predefined events or customer actions, such as order confirmations, shipping updates, payment reminders, or promotions. This ensures that customers are informed in real-time about the status of their orders or relevant offers.
3. **Customizable Notification Templates:** Businesses can create and customize notification templates for different communication needs. This includes personalizing messages based on customer preferences, order details, or campaign specifics, ensuring that all communications align with the brand's tone and style.
4. **Segmentation and Targeting:** Lidia Notification integrates with customer segmentation tools to ensure that messages are tailored to specific groups of customers. For example, businesses can send targeted notifications based on a customer's purchase history, behavior, or geographic location.
5. **Automated Campaigns:** Businesses can set up automated notification campaigns to engage customers at different stages of the buying journey. For example, abandoned cart reminders, promotional offers, or subscription renewal reminders can be sent automatically based on triggers and customer data.
6. **Real-Time Status and Tracking:** Lidia Notification provides real-time tracking of notifications, allowing businesses to monitor the delivery status, open rates, and customer engagement with the messages. This helps in optimizing communication strategies by identifying which channels and messages are most effective.
7. **Compliance and Opt-In Management:** The service ensures that all notifications comply with local regulations (e.g., GDPR, CAN-SPAM). It includes tools for managing customer opt-ins and preferences, ensuring that businesses only send notifications to users who have given consent.
8. **Internal Alerts and System Notifications:** In addition to customer notifications, Lidia Notification can also be used for internal alerts. Businesses can notify employees about important events, such as system updates, inventory shortages, or order fulfillment delays, ensuring that operations run smoothly.

## Example

Imagine an e-commerce company using Lidia Notification to enhance customer communication. When a customer places an order, they receive an order confirmation via email and an SMS with an expected delivery date. As the order progresses, the system sends push notifications through the company's app to update the customer on shipping status and delivery time.

Additionally, if a customer abandons their cart, Lidia Notification automatically triggers a personalized email reminder with a discount code to encourage them to complete the purchase. The business can monitor how many customers opened the reminder email and how many completed the purchase after receiving the notification.


# Lidia Commander

Provides tools for administrators to control and configure system-wide settings and operations.

## **Overview**

[Lidia Commander](https://dev.lidiacommerce.com/#c2bd95b5-26fe-4a7e-930f-6af81dd306cc) is a critical microservice within the Lidia Commerce Engine, designed to orchestrate and automate business processes across the platform. It acts as a central controller for workflows, tasks, and system events, enabling businesses to streamline their operations and ensure that various components of the platform work together seamlessly. Lidia Commander is essential for handling complex workflows, integrating different services, and ensuring that tasks are executed in the right sequence and on time.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the[ link](https://dev.lidiacommerce.com/#c2bd95b5-26fe-4a7e-930f-6af81dd306cc).
{% endhint %}

## Example

An online retailer using Lidia Commander might have a complex order fulfillment workflow that includes multiple steps:

* After a customer places an order, Lidia Commander triggers the following tasks:
  1. Verifies product availability with the [**Lidia Inventory**](https://dev.lidiacommerce.com/#a4531581-d17e-40db-b2a6-063b7d154202) service.
  2. Processes the payment through the **Lidia Payment** service.
  3. If payment is successful, triggers [**Lidia Delivery**](https://dev.lidiacommerce.com/#44584ab4-5c93-4d03-aa44-6ab7382e6965) to handle shipping and logistics.
  4. Sends an order confirmation email to the customer via [**Lidia Notification**](https://dev.lidiacommerce.com/#3487a081-296c-4620-86df-2de3e030994a).
* If the payment fails, Lidia Commander will retry the payment process or notify the customer to update their payment details.
* Throughout the process, Lidia Commander monitors each step, ensuring that the tasks are executed in the correct sequence and within the expected time frame.

If an error occurs at any point (e.g., the product is out of stock), Lidia Commander can trigger a fallback workflow that notifies the customer and suggests alternatives or backorders.

## Summary

Lidia Commander is the backbone of workflow automation and task orchestration within the Lidia Commerce Engine. It ensures that complex processes are executed smoothly, integrates with other systems, and provides real-time monitoring, making it indispensable for businesses looking to automate and optimize their digital commerce operations.


# Lidia Delivery

Handles the logistics of order delivery, integrating with shipping providers and managing tracking information.

## **Overview**

[Lidia Delivery](https://dev.lidiacommerce.com/#44584ab4-5c93-4d03-aa44-6ab7382e6965) is a service integrated into the **Lidia Commerce Engine**, designed to manage the logistics and fulfillment aspects of digital commerce. It works with multiple logistics providers to facilitate the shipping, returns, and inventory management processes for online orders. By offering these integrations, it ensures a smooth post-purchase experience for both buyers and sellers, streamlining the delivery process and enhancing customer satisfaction.

This capability is particularly useful for marketplaces and businesses using Lidia products, as it provides flexibility in choosing logistics providers and simplifies the fulfillment workflow​​​.

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#44584ab4-5c93-4d03-aa44-6ab7382e6965).
{% endhint %}

## **Key Concepts**

The **key concepts** related to the Lidia Delivery service include

1. **Integrated Logistics Providers**: Lidia Delivery connects seamlessly with various third-party logistics companies, allowing businesses to choose from multiple options for shipping and fulfillment. This ensures flexibility in delivery solutions depending on geographic reach, pricing, and service quality.
2. **Post-Purchase Experience**: Lidia Delivery enhances the customer experience by managing shipping, returns, and inventory updates. It ensures that orders are processed, tracked, and delivered smoothly, reducing friction in the post-purchase process.
3. **Order Tracking**: Lidia provides real-time order tracking, enabling customers to monitor the status of their deliveries. This improves transparency and reduces customer inquiries about the delivery status.
4. **Return and Refund Management**: Lidia Delivery includes support for managing order cancellations, returns, and refunds efficiently, ensuring that these processes are handled fairly and promptly to maintain customer satisfaction.
5. **Seamless Integration**: Lidia Delivery is fully integrated with other aspects of the Lidia Commerce Engine, such as **Order Management** and **Inventory Management**, ensuring that logistics operations are streamlined with other core business processes like payment and order tracking.
6. **Logistics Automation**: The platform supports automated delivery workflows, reducing the need for manual interventions and improving operational efficiency for businesses managing large volumes of orders.

These concepts are foundational to the Lidia Delivery service, enhancing logistics management within the broader e-commerce ecosystem​​​.


# Lidia Collector

Gathers and consolidates data from multiple sources, enabling comprehensive analytics and reporting.

[**Lidia Collector**](https://dev.lidiacommerce.com/#a8a612e2-9be0-44ff-89fe-f71332027db5) is one of the 18 microservices in the [**Lidia Commerce Engine**](/products/lidia-commerce-engine) that plays a vital role in **data collection and aggregation**. Here's an overview of its key concepts:

1. **Data Aggregation**: Lidia Collector gathers and consolidates data from various sources across the platform. This data includes user interactions, transactions, product information, inventory updates, and more. It serves as a centralized service to streamline the flow of information across different systems.
2. **Reporting and Analytics**: The data collected by Lidia Collector can be used for **advanced reporting** and **analytics**. This service is essential for businesses to derive insights into customer behavior, sales performance, inventory levels, and operational efficiency. The aggregated data helps businesses make **data-driven decisions**.
3. **Integration with Other Services**: Lidia Collector works seamlessly with other microservices, such as [**Lidia Analytics**](/products/lidia-commerce-engine/api-documantation/lidia-analytics) for deeper data analysis and [**Lidia Order**](https://dev.lidiacommerce.com/#79ba0e4b-5257-47eb-9f06-24ee52efbdfd) for tracking order-related data. This integration ensures that the collected data is consistent, real-time, and available across the platform.
4. **Data Enrichment**: It enables **enrichment of collected data**, combining it with external data sources, such as third-party services or customer databases, to improve the quality and relevance of insights.
5. **API-first Design**: Being part of the **API-first** architecture of the Lidia Commerce Engine, Lidia Collector allows easy access to collected data through APIs. This enables external systems to interact with and extract data for various purposes, such as external analytics tools or customer engagement platforms.

In summary,[ **Lidia Collector**](https://dev.lidiacommerce.com/#a8a612e2-9be0-44ff-89fe-f71332027db5) is essential for consolidating and analyzing data, providing the foundation for insights, optimization, and business intelligence​​.


# Lidia Document

Manages document storage and retrieval, facilitating the handling of contracts, invoices, and other critical files.

## **Overview**

[**Lidia Document** ](https://dev.lidiacommerce.com/#b7f7e572-047e-46f1-9566-9b470498c008)is one of the microservices within the **Lidia Commerce Engine**, focused on managing **digital documents and files** throughout the platform. It plays a key role in handling various documentation processes within an e-commerce environment.&#x20;

{% hint style="info" %}
To learn more about how to register and create your applications, please follow the [link](https://dev.lidiacommerce.com/#b7f7e572-047e-46f1-9566-9b470498c008).
{% endhint %}

## Concepts

1. **Document Storage and Management**: Lidia Document is responsible for storing and organizing all types of documents, such as invoices, purchase orders, contracts, product manuals, and customer receipts. It ensures that documents are easily accessible and properly categorized within the system.
2. **Automation of Document Generation**: The service enables the automatic generation of key documents, such as invoices and order confirmations, as part of the customer journey. This reduces manual effort and ensures that the required documents are always consistent and accurate.
3. **Document Version Control**: It supports versioning, allowing businesses to track changes and maintain historical records of important documents. This feature is especially useful for maintaining audit trails and ensuring compliance with business or legal requirements.
4. **Integration with Other Services**: Lidia Document integrates with other microservices like [**Lidia Order**](/products/lidia-commerce-engine/api-documantation/lidia-order) (for generating order-related documents) and [**Lidia Identity**](/products/lidia-commerce-engine/api-documantation/lidia-identity) (for user-related documents). This ensures that documents are tied to relevant transactions, customers, and business processes, creating a seamless document flow.
5. **Secure Document Handling**: Security is a crucial part of the Lidia Document service, ensuring that sensitive files, such as contracts or customer data, are securely stored and accessed by authorized users only. The platform adheres to **compliance** and **security standards** for document storage and management.
6. **APIs for Document Access**: The service is API-driven, allowing external systems to integrate with Lidia Document for document retrieval, updates, or uploads. This allows businesses to connect external CRMs, ERPs, or third-party tools for broader document management needs.
7. **Document Sharing**: It enables sharing of documents between different stakeholders (e.g., between merchants and customers, or business partners), supporting streamlined communication and workflow within the platform.

In summary, **Lidia Document** helps businesses efficiently manage their digital documentation, ensuring proper storage, security, automation, and seamless integration with other e-commerce processes​​​.


# Lidia PIM

Lidia PIM (Product Information Management)  is a centralized platform designed to simplify the management of product data and digital assets across various digital channels. It addresses the challenges businesses face in maintaining accurate and consistent product information, ensuring that all customer touchpoints are aligned with the latest data.

<figure><img src="/files/ilbxGwTY1sF32onDmhck" alt=""><figcaption></figcaption></figure>

#### Product History

With the rise of the Internet in the 2000s, businesses began to use the web as an active sales and marketing channel, which highlighted the need for enriched product data. While ERP systems initially managed product data, the increasing demand for high-resolution images, product videos, and detailed descriptions for online sales surpassed the capabilities of these traditional systems. This need led to the development of specialized PIM systems, and Lidia PIM emerged as a solution to these challenges.

Development of Lidia PIM began in 2021 by T\&G Workshop, with its first alpha version released in mid-2022. The system was designed to address the modern needs of digital product data management, moving beyond the limitations of ERP systems by offering tools for product data enrichment, media management, and seamless data distribution across digital channels.

Product data can be imported into the Lidia PIM application by integration using the Lidia PIM API or by using Excel files.

**Ability to edit and enrich product data (Product data management & enrichment)**

Within the Lidia PIM application, it is possible to manage product data according to certain standards and The following processes can be operated / capabilities can be used for enrichment.

**Product catalog design;**&#x20;

* Product features / options o Product labels
* &#x20;Product relationships o Size / Dimension uses
* Product brands
* Product categories and their data schemas (now called product families)&#x20;
* Product lists (special lists)

**Media management;**&#x20;

* Product images
* Product documentation&#x20;
* Product videos

**Additional requirements for product data management;**

* Data locks Ability to transfer product data to external stakeholders without the need for technical support (Product publication)&#x20;

With the help of Lidia PIM application, channels to be fed with product data can be created and feeds can be set up for these channels. Filters can be added for the products to be included in the feeds, and the envelope (including/excluding which fields) of the products to be exported as a result of the filter can be set.


# Overview

Product Information Management (PIM) refers to the process of centralizing and managing product information in a structured and organized manner to ensure consistency and accuracy across all channels. The three main features of PIM are:

1. **Product data acquisition and enrichment:** Data enrichment in PIM (Product Information Management) refers to the process of enhancing or adding value to product information by enriching it with additional details, such as images, videos, descriptions, features, specifications, and other relevant information.

   Data enrichment in PIM can involve the following:

   * **Categorizing and grouping products:** Companies can categorize and group products based on their attributes, such as color, size, style, or material, to make it easier for customers to find and compare products.
   * **Adding product images and videos:** Companies can add images and videos to the product information to provide customers with a better understanding of the product's appearance and functionality.
   * **Enhancing product descriptions:** Companies can enhance product descriptions by adding detailed information about the product's features, benefits, and specifications.
   * **Adding customer reviews and ratings:** Companies can add customer reviews and ratings to the product information to provide customers with social proof and help them make informed purchase decisions.

   Data enrichment in PIM is important because it improves the quality of product information and makes it more useful and engaging for customers. It also helps companies to differentiate their products from competitors and increase sales.

   Regenerate response
2. **Product Inclusion:** Product inclusion in PIM (Product Information Management) refers to the practice of ensuring that product information is structured, organized, and enriched in a way that is accessible, understandable, and relevant to a diverse range of users, including those with disabilities, different cultural backgrounds, and varied preferences.

   To achieve product inclusion in PIM, companies can adopt several practices, such as:

   * **Using clear and concise language:** Companies can ensure that product information is written in clear and concise language that is easy to understand for all users, including those with limited English proficiency or cognitive impairments.
   * **Providing multiple formats and languages:** Companies can provide product information in multiple formats, such as text, audio, and video, and in multiple languages to cater to different user preferences and needs.
   * **Incorporating accessibility features:** Companies can incorporate accessibility features, such as alt text for images, keyboard navigation, and screen reader compatibility, to ensure that users with disabilities can access the product information.

   By incorporating product inclusion in PIM, companies can create a more inclusive and diverse customer experience, improve customer satisfaction, and increase their market reach.
3. **Data Feeding:** Product data feeding in PIM (Product Information Management) refers to the process of importing or exporting product information between the PIM system and other systems or channels where the product information is used.

   In PIM, product data feeding can involve the following:

   * **Importing data:** Companies can import product data from various sources, such as spreadsheets, databases, or other systems, into the PIM system to ensure that the product data is up-to-date and accurate.
   * **Exporting data:** Companies can export product data from the PIM system to various channels, such as e-commerce websites, marketplaces, or print catalogs, to ensure that the product information is consistent and accurate across all channels.
   * **Synchronizing data:** Companies can use data synchronization tools to ensure that product data is consistent and up-to-date across all systems and channels. This ensures that customers receive accurate and consistent product information, regardless of the channel they use.

   Product data feeding is an essential component of PIM, as it enables companies to centralize and manage product information efficiently and ensure that it is consistent and accurate across all channels.


# Quick Start Guide

## Introduction

Lidia Product Information Management (PIM) software is used by companies to collect, organize, and process product information, including product descriptions, features, technical specifications, images, videos, pricing, and product documents.

Here is a summary of how the PIM software operates within an organization:

* Any modifications made to an existing product by the relevant team in the organization are added to the central PIM system.
* The central PIM system updates or overwrites unlocked product data and makes it accessible to all teams.
* The product management team reviews these changes, adjusts the product price based on the modifications, and the PIM system automatically updates the price across all distribution channels.
* The product team can access updated information without concerns about accuracy and update product descriptions. The PIM system then synchronizes these updates across all distribution channels.

The core features of Lidia PIM typically include:

* Centralized product information storage
* Integration with various systems such as e-commerce platforms, marketplaces, SAP, and ERPs
* Data enrichment and validation workflows
* Collaboration and approval workflows
* Data management and quality rules
* Product categorization management
* Product variant management
* Multi-language and multi-channel support
* Analytics and reporting capabilities

## Getting Started

To begin, visit <https://pim.lidiacommerce.com/>. You will be greeted by the login screen, where you can log in using your assigned email and password.

Once logged in, you will be redirected to the homepage.

### Homepage

<figure><img src="/files/Ydob91NRT4vPWyPJHpPP" alt=""><figcaption><p>Dashboard</p></figcaption></figure>

## Bulk Product Addition

Before adding products, you must define options and option values. Navigate to **Configuration > Catalog > Option Management > Options** and add necessary options such as size and color.

When adding a product, first ensure that the product category and brand are assigned. You can view, edit, and add brands under **Catalog > Brands**.

To add a product brand: **Catalog > Brands > Add New Brand** or use a previously added brand.

Adding a category is another crucial step. You can either use an existing category or add a new one. To view categories: **Catalog > Categories** To add a new category: **Catalog > Categories > Add Category**

Each category must be linked to a data schema. For example, a computer or mobile phone should be linked to the "Electronics" category. To add a new data schema: **Configuration > Catalog > Data Schemas** Once the schema is created, add fields by clicking **New Field**, entering the field name, and filling in the required details.

After completing these steps, navigate to **Catalog > Products** to view and manage existing products. To add a new product: **Catalog > Products > Add New Product**

Another method to add products is through pools:

1. Go to **Services > Pools** and open the relevant pool.
2. Click **Edit**.
3. Click **Import Data** to upload an Excel file.
4. Download the template schema and fill in the product data.
5. Ensure required fields like size, color, category, and brand are pre-defined in the system.
6. Upload the completed Excel file and verify the data before approval.

## Media Management

Media management is accessible via **Media** in the left menu, where you can manage images, videos, and documents. In the **Images** section, you can add, rename, delete, and view image details. When uploading products, image names must match the image code. The **Media > Documents** section allows you to manage all documents.

## Publishing a Pool

To publish a pool:

1. Go to **Services > Pools > Edit**.
2. Select the products to be published using one of two methods:
   * Hold **Ctrl** and select the desired products.
   * Set the product status to **1** in the Excel file (all products marked as **1** will be published).
3. Click **Publish Pool** to complete the process.

## Verifying Published Pools

To verify published pools, navigate to **Catalog > Products** and check the status of the selected products.

## Exporting Product Data

Product data can be exported to external stakeholders without requiring technical assistance (**Product Publication**). Using Lidia PIM, channels can be created to supply product data, and data feeds can be established for these channels. Filters can be applied to determine which products are included in the feed, and the data format (included/excluded fields) can be customized before export.


# Veri şeması nasıl oluşturulur?

Lidia PIM’e hoş geldiniz. Bu rehber, ilk ürününüzü sisteme sorunsuz şekilde ekleyebilmeniz için gerekli temel adımlarda size yol göstermek amacıyla hazırlanmıştır.

Ürün ekleme süreci belirli bir kurulum sırasını takip eder. Bu rehberde ilerledikçe:

* ürün veri modelinizi hazırlayacak,
* gerekli özellik ve seçenekleri tanımlayacak,
* ürün havuzunuzu oluşturacak
* ve ürünlerinizi içeri aktaracaksınız.

En sorunsuz deneyim için adımları sırayla tamamlamanız önerilir.

{% hint style="info" %}
**Başlamadan önce**

Gerekli kullanıcı yetkilerine sahip olduğunuzdan emin olun.
{% endhint %}

### :rocket:<mark style="color:$primary;background-color:purple;">Veri modelinizi inşa edin</mark>

Lidia PIM’de ürünlerinizi sorunsuz yönetebilmek için ilk ve en kritik adım veri şemasını doğru şekilde kurgulamaktır. Doğru yapılandırılmış bir veri şeması, benzer ürünleri düzenli bir yapı altında toplar ve ürün verisinin kategori bazında kontrollü ve sürdürülebilir şekilde ilerlemesini sağlar.

#### :arrow\_forward: <mark style="color:$info;">Veri Şeması Nedir?</mark>

Veri şeması, ürünleriniz için hangi bilgilerin tutulacağını ve bu bilgilerin hangi kurallara göre yönetileceğini belirleyen temel veri modelidir.

Basitçe ifade etmek gerekirse veri şeması:

* <mark style="background-color:purple;">ürün kartında hangi alanların görüneceğini belirler</mark>
* <mark style="background-color:purple;">bu alanların veri tipini tanımlar</mark>
* <mark style="background-color:purple;">hangi bilgilerin zorunlu olduğunu kontrol eder</mark>
* <mark style="background-color:purple;">benzer ürünlerin aynı yapıda yönetilmesini sağlar</mark>

Veri şeması sayesinde ürünleriniz rastgele değil, tanımlı ve kontrol edilen bir yapı içinde ilerler.

> **Örneğin** benzer ürünler için her seferinde yeni alanlar tanımlayıp yeni kural setleri oluşturmak yerine, oluşturduğunuz televizyon veri şemasını hem televizyon hem de HD televizyon ürünleri için kullanabilirsiniz. İhtiyaç duyduğunuz durumlarda ise bu ürün grupları için ayrı veri şemaları tanımlayarak her birini kendi alan ve kural yapısıyla yönetebilirsiniz.&#x20;

#### :arrow\_forward: <mark style="color:$info;">Neden Gereklidir?</mark>

Lidia PIM’de ürün verisinin sağlıklı ilerleyebilmesi için kategori, havuz ve ürün yapıları veri şemasına bağlı çalışır.

Veri şeması sayesinde:

* ürün verisi standart bir yapıda toplanır
* zorunlu alanlar kontrol altına alınır
* hatalı veya eksik veri girişleri önlenir
* ürün grupları kategori bazında doğru şekilde yönetilir

#### :arrow\_forward: <mark style="color:$info;">Veri Şeması Nasıl Oluşturulur?</mark>

{% stepper %}
{% step %}

#### Veri şeması sayfasına gidin

Şu yolu izleyin:\ <mark style="background-color:purple;">**Ayarlar > Katalog > Ürün Aileleri**</mark>\
Sonuç: Veri şeması boş liste ekranı açılır.
{% endstep %}

{% step %}

#### Yeni veri şeması oluşturun

<mark style="background-color:purple;">**Yeni Veri Şeması Ekle**</mark> butonuna tıklayın.\
Açılan pencerede:

* <mark style="background-color:purple;">**Veri Şeması Türü**</mark> alanı <mark style="background-color:purple;">varsayılan olarak</mark> <mark style="background-color:purple;"></mark>*<mark style="background-color:purple;">Ürün</mark>* gelir
* <mark style="background-color:purple;">**Şema Adı**</mark> alanını doldurun
* <mark style="background-color:purple;">**Eşleştirme Anahtarı**</mark> alanını doldurun

<div align="left" data-with-frame="true"><figure><img src="/files/3X6w1NeFPoC8GyhSaiSb" alt="" width="235"><figcaption></figcaption></figure></div>

Kaydet butonuna tıklayın.\
Sonuç: Veri şeması oluşturulur ve detay sayfasına yönlendirilirsiniz.
{% endstep %}
{% endstepper %}

> **Eşleştirme Anahtarı**, Lidia PIM ile Lidia Console’daki veri şemaları arasında alanların birbiriyle bağlanmasını sağlar.
>
> Müşteri hem **Lidia PIM** hem de **Lidia Console** kullanıyorsa, iki tarafta da ayrı veri şemaları bulunur.\
> Bu alan, PIM’de oluşturulan bir alanın Console’daki hangi alanla eşleşeceğini tanımlar.

#### :arrow\_forward: <mark style="color:$info;">Veri Şeması Alanları Nasıl Eklenir?</mark>

Veri şeması alanları, ürün kartında hangi bilgilerin toplanacağını belirleyen yapı taşlarıdır.&#x20;

{% stepper %}
{% step %}
**Oluşturduğunuz&#x20;**<mark style="background-color:purple;">**veri şemasının detay**</mark>**&#x20;sayfasını açın.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Veri Şeması Alanları**</mark>**&#x20;sekmesine gidin.**

<div align="left" data-with-frame="true"><figure><img src="/files/xdofT4ZlsEGwNOygrWHg" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Alan Ekle**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**alan bilgilerini**</mark>**&#x20;doldurun ve kaydedin.**
{% endstep %}
{% endstepper %}

Alan kaydedildiğinde veri şemasına eklenir ve ürün yapısında kullanılabilir hale gelir.

> &#x20;**Not:** İhtiyaca göre aynı şemaya <mark style="background-color:purple;">birden fazla alan</mark> ekleyebilirsiniz.

Yeni Alan Ekle butonuna tıkladığınızda açılan pencerede yer alan alanlar ve bu alanların veri tipleri aşağıda listelenmiştir.

<table><thead><tr><th width="155.1851806640625">Veri Tipi</th><th>Kullanım</th><th>Örnek Alan</th></tr></thead><tbody><tr><td><em>Text</em></td><td>Serbest metin girişi gereken alanlar</td><td><mark style="background-color:purple;">Alan Adı</mark>, Açıklama, Stil</td></tr><tr><td><em>Select</em></td><td>Önceden tanımlı seçeneklerden seçim yapılacak alanlar</td><td><mark style="background-color:purple;">Alan Türü</mark>, <mark style="background-color:purple;">Alan Değeri</mark>,  Alan (Eşleştirme), Veri Tipi, Nesne Alanı, Dil</td></tr><tr><td><em>Boolean</em></td><td>Açık/Kapalı veya Evet/Hayır kontrolü gereken alanlar</td><td>Liste Ayracı, Kilitli, Veri Tipi Eşleşsin, Zorunlu</td></tr><tr><td><em>Number</em></td><td>Sayısal değer girilmesi gereken alanlar</td><td>Sıralama, Minimum Aralık Değeri, Maksimum Aralık Değeri</td></tr></tbody></table>

***

{% columns %}
{% column %}
:new\_moon:<mark style="background-color:purple;">**Yeni Alan Ekle**</mark>

Bu ekran, ürün ve varyant verilerinin PIM içerisinde nasıl tutulacağını ve yayına nasıl taşınacağını belirleyen alanların tanımlandığı ekrandır.

<figure><img src="/files/ogR6V2zi9v9PBPYa9ToI" alt=""><figcaption></figcaption></figure>

#### <mark style="background-color:purple;">1. Temel Bilgiler</mark>

* **Alan Adı** *(Zorunlu)*\
  Oluşturulan alanın sistemde ve ürün ekranlarında görünecek adıdır.
* **Açıklama** *(Opsiyonel)*\
  Alanının ne amaçla kullanıldığını açıklamak için kullanılır.
* **Alan Türü** *(Zorunlu)*\
  Alanının sistemde nasıl davranacağını belirler.\
  Alan türü değerleri:\
  ![](/files/JUQGCEkhNp3GDBbF4VBe)
* **Alan Değeri** *(Koşullu – Zorunlu)*\
  Yalnızca Alan Türü = Özellik veya Seçenek olduğunda görüntülenir.\
  Bu alan, alanın hangi değer setiyle çalışacağını belirler.
* **Liste Ayracı** *(Opsiyonel)*\
  Bu alanın ön yüzde ürün listeleme ekranlarında ayıraç olarak kullanılıp kullanılmayacağını belirler. Açık olduğunda, alan değeri farklı olan ürünler listelemede ayrı itemlar olarak gösterilebilir.

> Örnek:\
> iPhone 12 – Siyah / Beyaz / Mavi renkleri listelemede ayrı ürünler gibi gösterilebilir.

* **Kilitli** *(Opsiyonel)*\
  Alan kilitlendiğinde, ürün ekranlarında düzenlenemez hale gelir.
* **Sıralama** *(Opsiyonel)*\
  Alanların ürün ekranında hangi sırayla gösterileceğini belirler.\
  Sayısal bir değer alır. Küçük değerler üstte gösterilir.
* **Stil** *(Opsiyonel)*\
  Alan için ön yüzde veya arayüzde uygulanacak özel stil bilgisidir.\
  Gelişmiş kullanım senaryoları için opsiyoneldir.
  {% endcolumn %}

{% column %}

#### <mark style="background-color:purple;">2. Validasyon Bilgileri</mark>

* **Veri Tipi Eşleşsin**\
  Alan için tanımlanan veri tipi ile girilen değerin uyumlu olmasını zorunlu kılar.

> Örnek:\
> Sayı beklenen bir alana metin girilmesini engeller.

* **Zorunlu** *(Opsiyonel)*\
  Bu alan işaretlendiğinde, ürün veya varyant yayına alınmadan önce bu alanın doldurulması gerekir.
* **Minimum Aralık Değeri** *(Opsiyonel)*\
  Sayısal alanlar için girilebilecek en düşük değeri belirler.
* **Maksimum Aralık Değeri** *(Opsiyonel)*\
  Sayısal alanlar için girilebilecek en yüksek değeri belirler.

#### <mark style="background-color:purple;">3. Eşleştirme (Mapping) Bilgileri</mark>

Bu bölüm, oluşturulan alanın değerinin sistemde hangi nesneye ve o nesnenin hangi alanına yazılacağını belirler.\
Alan, Veri Tipi ve Nesne Alanı bir bütün olarak değerlendirilmelidir.

* **Alan** *(Opsiyonel)*\
  Verinin hangi yapı üzerinden saklanacağını belirtir.\
  Genellikle 'Meta Verileri' olarak gelir.
* **Veri Tipi** *(Opsiyonel)*

  Veri Tipi, girilen değerin sistemde hangi nesneye ait olduğunu belirtir.

*Veri tipi değerleri:*\
*\[ Ürün Dokümanı ] \[ Ürün Doküman Etiketi ] \[ Kategori ] \[ Kategori Boyutu ] \[ Kategori Filtresi ]* \
*\[ Kategori Filtre Seçeneği ] \[ Kategori Görseli ] \[ Kategori Ürünleri] \[ Kategori Özelliği ] \[ Kategori Etiketi ] \[ Kategori Tercümesi ] \[ Kategori Varyant Listesi ] \[ Marka ] \[ Marka Filtresi ] \[ Marka Filtre Seçeneği ] \[ Marka Görseli ] \[ Marka Ürünleri ] \[ Marka Özelliği ] \[ Marka Etiketi ] \[ Marka Tercümesi ] \[ Marka Varyant Listesi ] \[ Para Birimi ] \[ Para Birimi Tercümesi ] \[ Özel Liste Dokümanı ] \[ Özel Liste Doküman Görseli ] \[ Veri Akışı ] \[ Veri Akış Kategorisi ]* \
*\[ Veri Akış Özel Listesi ] \[ Veri Akış Satış Etkinliği ] \[ Veri Akış Markası ] \[ Veri Havuzu ] \[ Veri Havuzu Etiketi ] \[ Veri Havuzu Özelliği ] \[ Veri Havuzu Ögesi ] \[ Veri Havuzu Öge Etiketi ] \[ Veri Havuzu Öge Alan Değeri ] \[ Veri Şeması ] \[ Veri Şema Kategorisi ] \[ Veri Şema Alanı ]* \
*\[ Veri Şema Şablonu ] \[ Ambalaj ]* \
*\[ Ambalaj Boyutu ] \[ Fiyat ] \[ Fiyat Listesi ] \[ Satış Etkinliği ] \[ Satış Etkinlik Etiketi ] \[ Satış Etkinlik Özelliği ] \[ Satış Etkinlik Ögesi ] \[ Varyant ] \[ Varyant Etiketi ]* \
*\[ Varyant Özelliği ] \[ Varyant Tercümesi ] \[ Varyant Özellik Tercümesi ] \[ Varyant Seçenek Değeri ] \[ Garanti ]*

* **Nesne Alanı** *(Opsiyonel)*

  Seçilen veri tipinin içindeki hedef alanı belirtir.

  Örnek: Name, TaxRate, ParentId, OptionValues, IntegrationCode, ShortDescription, LongDescription, ProductId, Type, Unit, Link, Options

{% endcolumn %}
{% endcolumns %}

#### :arrow\_forward: <mark style="color:$info;">Alan Tipleri Nelerdir?</mark>

Veri şemasına alan eklerken seçilen **Alan Türü**, ilgili bilginin sistemde hangi yapı ile ilişkilendirileceğini belirler. Alan türünü, alanın ürün üzerindeki kullanım amacına göre seçmeniz önerilir.

<table><thead><tr><th width="160.55560302734375">Alan Türü</th><th>Açıklama</th></tr></thead><tbody><tr><td><strong>Özellik</strong></td><td>Fiyat veya stok değişimine neden olmayan ürün niteliklerini tutar. </td></tr><tr><td><strong>Seçenek</strong></td><td>Fiyat veya stokta farklılık yaratan varyant bilgilerini tutar. </td></tr><tr><td><strong>Kategori</strong></td><td>Ürünün kategori yapısı ile ilişkilendirilmesini sağlar.</td></tr><tr><td><strong>Marka</strong></td><td>Ürünün marka bilgisi ile eşleşmesini sağlar.</td></tr><tr><td><strong>Referanslar</strong></td><td>Ürünün diğer kayıtlarla ilişkilendirilmesini sağlar.</td></tr></tbody></table>

* [x] *Alan türü olarak <mark style="background-color:purple;">**Özellik**</mark> veya <mark style="background-color:purple;">**Seçenek**</mark> seçildiğinde;*\
  Yeni alan ekleme penceresinde <mark style="color:$info;">Alan Değeri</mark> alanı aktif hale gelir. Bu alanda, daha önce tanımladığınız özellik veya seçenek değerleri arasından seçim yapmanız gerekir.
* [x] *Alan türü <mark style="background-color:purple;">**Kategori**</mark>* *veya <mark style="background-color:purple;">**Marka**</mark>* *olarak seçildiğinde;*\
  Bu alanlar için ayrıca bir alan değeri seçimi yapılmaz. Bu bilgiler ürün yükleme sırasında Excel dosyasında, sistemde tanımlı tüm kategori ve marka değerleri arasından seçilerek girilir.
* [x] *Alan türü <mark style="background-color:purple;">**Referanslar**</mark>* *olarak seçildiğinde;*\
  Aynı pencerede yer alan eşleştirme bilgileri alanlarının doldurulması gerekir. Bu alanlar, girilen verinin ürün üzerinde hangi alana yazılacağını belirlemek için kullanılır.

&#x20;          Bu bölümde:\
&#x20;          **Alan**: Referans verinin hangi yapıdan alınacağını belirler (meta\
&#x20;          verileri)\
&#x20;          **Veri Tipi**: Değerin ürün bazında mı yoksa varyant bazında mı\
&#x20;          yönetileceğini belirler. Ürün seviyesinde sabit kalacak alanlar\
&#x20;          için <mark style="color:$info;">Ürün</mark>, varyantlara göre değişecek alanlar için <mark style="color:$info;">**Varyant**</mark>\
&#x20;            seçilmelidir.\
&#x20;          **Nesne Alanı**: Girilen değerin ürün üzerinde hangi alanı\
&#x20;          dolduracağını belirler. Örneğin kısa açıklama için\
&#x20;          <mark style="color:$info;">ShortDescription</mark>, uzun açıklama için <mark style="color:$info;">LongDescription</mark>, vergi \
&#x20;          oranı için <mark style="color:$info;">TaxRate</mark> seçilir.

{% hint style="success" %}
Doğru alan türünü seçmek, ürün verisinin sistem içinde doğru şekilde işlenmesi için önemlidir.
{% endhint %}

{% hint style="info" %}
:star:**Ekstra**

Özellik veya Seçenek için önceden tanımlanan değerler, Alan Değeri alanında aşağıdaki veri tiplerini destekler: *<mark style="color:purple;">Metin, Tam Sayı, Ondalık Sayı, Ölçü, Tekil Kod, Tek Satır Metin, Uzun Metin, Zengin Metin, Tekli Seçim, Çoklu Seçim, Liste, Var/Yok, Tarih, E-posta, Tel No, URL, Fiyat, Yüzde, Süre</mark>*. Bu sayede alan yapısını ihtiyaçlarınıza göre esnek şekilde özelleştirebilirsiniz.
{% endhint %}

#### :arrow\_forward: <mark style="color:$info;">Minimum önerilen alanlar nelerdir?</mark>

Ürünlerin katalogda doğru konumlanabilmesi ve temel seviyede yönetilebilmesi için veri şemasında bazı alanların tanımlanması önerilir. Minimum seviyede aşağıdaki yapı ile başlanması yeterlidir:

* **Marka (Marka)** — Ürünün doğru marka ile eşleşmesini ve filtrelenmesini sağlar.
* **Kategori (Kategori)** — Ürünün katalogda doğru konuma yerleşmesini sağlar.
* **Kısa Açıklama (Özellik)** — Listeleme ve özet alanlarında ürünün hızlı anlaşılmasını destekler.
* **Uzun Açıklama (Özellik)** — Ürün detay sayfasında zengin içerik sunulmasını sağlar.

İhtiyaç duyulması halinde veri modelinizi **Seçenek** (varyant oluşturan alanlar) ve **Referanslar** (ilişkili ürünler vb.) ile genişletebilirsiniz.

> **Not:** Veri şemasına minimum alan seti ile başlayıp kullanım ihtiyaçlarına göre yeni alanlar eklemeniz önerilir.

#### :arrow\_forward: <mark style="color:$info;">Zorunlu alan nasıl tanımlanır?</mark>

Bir alanı <mark style="background-color:purple;">zorunlu</mark> olarak işaretlediğinizde, ürün oluşturma ve import işlemleri sırasında bu alanın doldurulması gerekir. Bu sayede eksik veri girişi engellenir ve ürün verisi daha kontrollü ilerler.

Bir alanı zorunlu yapmak için:

1. Veri şeması detay sayfasında ilgili alanı ekleyin veya düzenleyin.
2. Açılan pencerede <mark style="background-color:purple;">**Zorunlu**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">seçeneğini aktif</mark> edin.
3. Değişiklikleri kaydedin.

Alan zorunlu olarak işaretlendiğinde, bu bilgi girilmeden ürün kaydedilemez veya import edilemez.

<div align="center" data-with-frame="true"><figure><img src="/files/qSSaHlgvusS5AJhKQ3MS" alt="" width="223"><figcaption></figcaption></figure></div>

{% hint style="info" %}
&#x20;Çok fazla alanı zorunlu yapmak, ürün yükleme sürecini zorlaştırabilir. Zorunlu alanları **minimum** seviyede tutmanız önerilir.
{% endhint %}

#### :arrow\_forward: <mark style="color:$info;">Şema oluşturulmadan neden kategori/havuz oluşturulamaz?</mark>

Veri şeması, ürün verisinin hangi alanlar üzerinden yönetileceğini belirleyen temel yapıdır. Kategori ve havuz yapıları, ürünleri bu şemaya göre organize eder ve işler.

* [x] <mark style="background-color:purple;">Kategori teknik olarak veri şeması olmadan oluşturulabilir; ancak bu kategori taslak durumda kalır ve havuz oluşturma adımında seçilemez.</mark> Bunun nedeni, havuz ve ürün yapılarının çalışabilmesi için kategoriye bağlı bir veri şemasının bulunmasının gerekli olmasıdır.

Veri şeması tanımlandığında kategori artık havuz oluşturma sürecinde kullanılabilir.

> **Not:** Bu bağımlılık, ürün verisinin eksik veya tutarsız bir yapı ile ilerlemesini önlemek amacıyla uygulanır.

#### :arrow\_forward: <mark style="color:$info;">Örnek Senaryo: Televizyon Ürünü için Veri Şeması Oluşturma</mark>

Televizyon kategorisindeki ürünlerinizi <mark style="background-color:purple;">belirli bir kural seti ile, tutarlı ve kontrollü</mark> bir yapıda yayınlamak istediğinizi düşünün.

Bu yapılandırmayı sağlayabilmek için ilk adım, televizyon ürünlerine özel bir veri şeması oluşturmaktır.

{% stepper %}
{% step %}
**Ayarlar > Katalog > Ürün Aileleri yolunu izleyin.**
{% endstep %}

{% step %}
**Yeni Veri Şeması Ekle butonuna tıklayın.**

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p>Açılan pencerede:<br><strong>Veri Şeması Türü:</strong> Ürün<br><strong>Şema Adı:</strong> Televizyon<br><strong>Eşleştirme Anahtarı:</strong> TV</p><p>Kaydet butonuna tıklayın. Veri şeması oluşturulur ve detay sayfasına yönlendirilirsiniz.</p></td><td data-object-fit="fill"><a href="/files/8mkBYQTmKPdfFKRcePy3">/files/8mkBYQTmKPdfFKRcePy3</a></td></tr></tbody></table>
{% endstep %}

{% step %}
**Alanları ekleyin.**<br>

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><ol><li>Veri şaması detay sayfası <strong>Temel Bilgiler</strong> alanı açık gelir.</li></ol></td><td data-object-fit="fill"><a href="/files/DpbO8IGucsjQ5ApyDI6x">/files/DpbO8IGucsjQ5ApyDI6x</a></td></tr><tr><td><ol start="2"><li>Veri şeması detay sayfası <strong>Veri Şeması Alanları</strong> açılır.<br><strong>Yeni Alan Ekle</strong> butonuna tıklanır.<br></li></ol></td><td data-object-fit="fill"><a href="/files/RKM9Uqw0LTQzw8eaueEp">/files/RKM9Uqw0LTQzw8eaueEp</a></td></tr><tr><td><p></p><ol start="3"><li><strong>Alan Adı:</strong> Marka<br><strong>Alan Türü:</strong> Marka<br><strong>Açıklama:</strong> Ürünün ait olduğu markayı seçiniz.<br><strong>Sıralama:</strong> 1<br><strong>Kilitli:</strong> Pasif<br><strong>Zorunlu:</strong> Aktif<br><strong>Veri Tipi:</strong> Marka</li></ol></td><td data-object-fit="contain"><a href="/files/svTcvqHnlQE6FubDEXcu">/files/svTcvqHnlQE6FubDEXcu</a></td></tr><tr><td><ol start="4"><li><p>Televizyon ürünlerim için gerekli <strong>alanları veri şemama ekledim</strong>. Bu alanlar sayesinde ürün bilgilerimi <strong>belirlediğim kural seti</strong> doğrultusunda yönetebilirim.</p><p>İhtiyaç duyduğum kadar alan ekledim, mevcut alanları düzenleyebilir ve istersem veri yapımı gereksinimlerime göre yeniden yapılandırabilirim.</p></li></ol></td><td data-object-fit="fill"><a href="/files/fyENvsn3mjWRzSAMvKrM">/files/fyENvsn3mjWRzSAMvKrM</a></td></tr></tbody></table>
{% endstep %}

{% step %}
:tada:**Veri şemanız başarıyla oluşturuldu.**

> **Not:** Oluşturduğunuz her veri şeması için sistem tarafından otomatik olarak bir havuz oluşturulur. Bu havuz, ilgili veri şemasına bağlı ürünlerin yönetileceği temel yapıyı temsil eder.
> {% endstep %}
> {% endstepper %}


# Özellik ve Seçenek nasıl tanımlanır?

Bu sayfada ürün özelliklerini ve seçeneklerini nasıl tanımlayacağınızı, aralarındaki farkı ve veri şemasına nasıl ekleyeceğinizi öğreneceksiniz.

### :rocket:<mark style="color:$primary;background-color:purple;">Özellik ve Seçenekleri Yapılandırın</mark>

Özellikler ve seçenekler, ürün kartının hangi bilgileri içereceğini ve bu bilgilerin sistemde nasıl yönetileceğini belirler. Doğru yapılandırıldığında, ürün verisi daha tutarlı ilerler ve varyant yönetimi daha kontrollü şekilde yapılır.

#### :arrow\_forward:<mark style="color:$info;">Özellik Nedir?</mark>

**Özellik**, ürünün teknik veya açıklayıcı niteliklerini tanımlamak için kullanılan veri alanıdır. Özellikler, ürün kartında gösterilen bilgileri oluşturur ve ürünün filtrelenmesini, karşılaştırılmasını ve detaylandırılmasını sağlar.

Özellikler fiyat veya stok değişikliğine neden olmaz; ürünün niteliğini tanımlar.

* <mark style="background-color:purple;">**Özellik Veri Tipi Nedir?**</mark>

Bir özellik oluşturulduktan sonra, bu özelliğin hangi formatta veri kabul edeceği belirlenir. Buna veri tipi denir.

```
Desteklenen veri tipleri: 
-Tekil Kod   -Tek Satır Metin   -Uzun Metin   -Zengin Metin   -Tekli Seçim  -Çoklu Seçim
-Liste   -Var/Yok   -Tarih   -E-posta   -Tel No   -URL   -Fiyat   -Yüzde   -Süre   -Ölçü
```

Veri tipi olarak **Tekli Seçim** veya **Çoklu Seçim** seçildiğinde, özellik için kullanılacak değerleri önceden tanımlamalısınız. Bu değerleri sistemde siz oluşturur ve ihtiyaçlarınıza göre istediğiniz kadar ekleyebilir veya düzenleyebilirsiniz.

> Televizyon örneğinden devam edelim, önce bir özellik tanımlayalım ve veri tipini 'çoklu seçim' olarak seçelim:
>
> * **Özellik:** Enerji Sınıfı
> * **Veri Tipi:** Çoklu Seçim
> * **Tanımlanan Değerler:** A, B, C, D, E, F
> *
>
> ```
> <div align="left" data-with-frame="true"><figure><img src="/files/pWk6xcnP0MOTNxHgDGW3" alt="" width="131"><figcaption></figcaption></figure></div>
> ```
>
> Bu sayede ürün oluşturma sırasında kullanıcı yalnızca tanımladığınız değerler arasından seçim yapabilir. Yeni değer girilemez; yalnızca mevcut seçenekler kullanılabilir.

Bu yöntemle veri girişini kontrol altında tutarsınız ve tutarlı bir ürün yapısı oluşturursunuz.

* <mark style="background-color:purple;">**Özellik Grubu Nedir?**</mark>

**Özellik grubu**, benzer özellikleri bir arada düzenlemek için kullanılır. Özellik grupları, PIM kullanıcısı olarak ürün verinizi daha düzenli yönetmenize yardımcı olur. İlgili özellikleri aynı başlık altında toplayarak hem ürün girişini hem de veri yönetimini kolaylaştırabilirsiniz.

> Örneğin televizyon ürünü için **Ekran Boyutu, Çözünürlük ve Panel Teknolojisi** gibi özellikleri oluşturduysanız, bu özellikleri **Ekran Özellikleri** adlı bir özellik grubu altında toplayın. Bu şekilde ilgili özellikleri aynı başlık altında düzenleyebilir ve ürün kartında daha düzenli bir yapı oluşturabilirsiniz.

#### :arrow\_forward:<mark style="color:$info;">Seçenek Nedir?</mark>

**Seçenek**, ürünün farklı versiyonlarını oluşturmak için kullanılan alanlardır. Genellikle fiyat veya stokta farklılık yaratan bilgiler seçenek olarak tanımlanır.

> Örneğin televizyon ürününde **Çözünürlük** bir seçenek olabilir. Bu seçenek, televizyonun hangi çözünürlükte sunulduğunu belirler ve kendine ait seçenek değerleri içerir, kendine ait seçenek değerleri vardır.

Bir seçenek oluştururken, seçeneğin hangi veri tipinde değer alacağını belirleyebilirsiniz.

Desteklenen veri tipleri şunlardır:

* [x] Metin, Tam Sayı, Ondalık Sayı, Ölçü

* <mark style="background-color:purple;">**Seçenek Değeri Nedir?**</mark>

**Seçenek değeri**, bir seçeneğe ait kullanılabilir değerleri ifade eder. Bir seçenek oluşturduktan sonra, o seçeneğe ait istediğiniz kadar seçenek değeri ekleyebilirsiniz.

> Örneğin **Çözünürlük** bir TV seçeneği ise, buna ait seçenek değerleri **4K**, **8K** gibi değerler olabilir. Ürün oluştururken kullanıcı bu değerler arasından seçim yapar.\
> Başka bir örnek olarak **Renk** seçeneğini düşünün. Bu seçeneğe ait değerler **Siyah**, **Mavi**, **Bebek Mavisi** gibi farklı renkler olabilir.

Seçenek değerlerini tamamen ihtiyaçlarınıza göre tanımlayabilirsiniz.

* <mark style="background-color:purple;">**Seçenek Değer Grubu Nedir?**</mark>

**Seçenek değer grubu**, benzer seçenek değerlerini bir arada düzenlemek için kullanılır. Çok sayıda seçenek değeri bulunan alanlarda değerleri daha düzenli yönetmenize yardımcı olur.

> Örneğin televizyon ürünü için **Renk** seçeneğini oluşturduğunuzu düşünün. Bu seçeneğe ait değerler **Gri, Gümüş, Antrasit, Beyaz, Siyah** gibi farklı tonlar olabilir. Bu değerlerden benzer gördüklerinizi örneğin gri+gümüş+antrasit üçlüsünü **Gri Tonları** adlı bir seçenek değer grubunda toplayabilirsiniz.

Seçenek değer grubu oluşturmak için:

1. **Ayarlar > Katalog > Seçenekler > Seçenek Değer Grupları** sayfasına gidin.
2. **Seçenek Değer Grubu Ekle** butonuna tıklayın.
3. Açılan pencerede **Seçenek Değer Grubu Adı** , **Görüntülenecek Ad** ve **Değer Grubu Kodu** alanlarını doldurun, kaydedin.
4.

```
<div align="left" data-with-frame="true"><figure><img src="/files/c20HnthD18AWn7uaoBqS" alt="" width="117"><figcaption></figcaption></figure></div>
```

5. Seçenek değerlerini oluşturduktan sonra ilgili değerin **detay sayfası**na gidin ve bu değeri oluşturduğunuz **seçenek değer grubuna** bağlayın.

Bu sayede benzer seçenek değerlerini aynı grup altında düzenleyebilirsiniz.

* <mark style="background-color:purple;">**Seçenek Grubu Nedir?**</mark>

**Seçenek grubu**, birden fazla seçeneği mantıksal olarak aynı başlık altında toplamak için kullanılır. Bu yapı özellikle çok sayıda seçenek bulunan ürünlerde yönetimi kolaylaştırır.

> Örneğin televizyon ürününde **Renk**, **Panel Teknolojisi,** **Çözünürlük, Dahili Wi-Fi** gibi birden fazla farklı seçenek oluşturduysanız, bu seçeneklerden renk, panel teknolojisi ve çözünürlüğü ekran özelliği olarak nitelendirebilir, **Ekran Özellikleri** adlı bir seçenek grubunda bir araya getirebilirsiniz.

Seçenek değer grubu oluşturmak için:

1. **Ayarlar > Katalog > Seçenekler > Seçenek Grupları** sayfasına gidin.
2. **Seçenek Grubu Ekle** butonuna tıklayın.
3. Açılan pencerede **Seçenek Grubu Adı, Görüntülenecek Ad** ve **Grubu Kodu** alanlarını doldurun, kaydedin.
4.

```
<div align="left" data-with-frame="true"><figure><img src="/files/ncoan2Zj1icXrKXsHcJa" alt="" width="116"><figcaption></figcaption></figure></div>
```

5. Seçenek grubu oluşturduktan sonra, ilgili seçeneğin detay sayfasına gidin ve **Seçenek Grubu** alanından oluşturduğunuz grubu seçerek seçeneği bu gruba bağlayın.

Bu şekilde televizyon ürününe ait varyant seçeneklerini düzenli bir yapı içinde yönetebilirsiniz.

#### :arrow\_forward:<mark style="color:$info;">Seçenek ve Özellik Aralarındaki Fark Nedir?</mark>

**Özellikler**, ürünün teknik veya açıklayıcı niteliklerini ifade eder. Ürünü tanımlar ancak fiyat veya stokta farklılık oluşturmaz.

**Seçenekler** ise ürünün farklı versiyonlarını oluşturmak için kullanılır. Genellikle fiyat veya stokta farklılık yaratan bilgiler seçenek olarak tanımlanır.

{% hint style="info" %}
Alan tanımlarken şu kuralı kullanabilirsiniz: Ürünün farklı bir versiyonunu oluşturuyorsa **seçenek**, yalnızca ürün bilgisini tanımlıyorsa **özellik** olarak tanımlayın.
{% endhint %}

> Örneğin televizyon ürünü için **Enerji Sınıfı**, **Garanti Süresi** veya **Model Yılı** gibi bilgiler genellikle **özellik** olarak tanımlanır. Bu bilgiler ürünü tanımlar ancak çoğu senaryoda farklı bir varyant oluşturmaz.
>
> Buna karşılık **Ekran Boyutu**, **Renk** veya **Çözünürlük** gibi alanlar genellikle **seçenek** olarak tanımlanır. Bu alanların farklı değerleri ürünün farklı versiyonlarını oluşturabilir ve fiyat veya stok bilgisini etkileyebilir.
>
> Ancak bu ayrım tamamen sizin ürün modelleme tercihinize bağlıdır. Örneğin bazı işletmeler için **Enerji Sınıfı** ürün fiyatını etkileyen bir varyant olabilir. Böyle bir durumda bu alanı **seçenek** olarak tanımlayabilirsiniz.

Lidia PIM’de ürün veri modelinizi iş ihtiyaçlarınıza göre esnek şekilde kurgulayabilir, hangi alanların **özellik** hangi alanların **seçenek** olacağına siz karar verebilirsiniz.

#### :arrow\_forward:<mark style="color:$info;">Özellik nasıl oluşturulur?</mark>

{% stepper %}
{% step %}
**Ayarlar > Katalog > Özellikler sayfasına gidin.**
{% endstep %}

{% step %}
**Özellik Ekle butonuna tıklayın.**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p>Açılan modalda:</p><ul><li><strong>Özellik Adı</strong> → Zorunlu</li><li><strong>Özellik Kodu</strong> → Zorunlu</li><li><strong>Özellik Grubu</strong> → Opsiyonel</li></ul><p>Bu alanlar doldurulduktan sonra <strong>Devam Et</strong> butonuna tıklayın.</p><p>Özellik oluşturulur ve detay sayfasına yönlendirilirsiniz.</p></td><td data-object-fit="fill"><a href="/files/ciW4DHJDgSXw2yQ7xIo6">/files/ciW4DHJDgSXw2yQ7xIo6</a></td></tr></tbody></table>
{% endstep %}

{% step %}
**Detay sayfasında ilgili özelleştirmeleri yapın.**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p></p><ul><li>Veri Tipi seçilir</li><li>Gerekirse özellik grubu bağlanır</li><li>Seçim tipindeyse değerler eklenir</li></ul><p>Kaydedin.</p></td><td data-object-fit="contain"><a href="/files/e7lG9p9JrXK2p091PQjw">/files/e7lG9p9JrXK2p091PQjw</a></td></tr></tbody></table>
{% endstep %}

{% step %}
🎉**Özellik başarıyla oluşturuldu.**
{% endstep %}
{% endstepper %}

#### :arrow\_forward:<mark style="color:$info;">Seçenek nasıl oluşturulur?</mark>

{% stepper %}
{% step %}
**Ayarlar > Katalog > Seçenekler > Seçenekler sayfasına gidin.**
{% endstep %}

{% step %}
**Seçenek Ekle butonuna tıklayın.**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p></p><p>Açılan <strong>Yeni Seçenek Ekle</strong> penceresinde aşağıdaki alanları doldurun:</p><ul><li><strong>Seçenek Grubu (Opsiyonel)</strong></li><li><strong>Seçenek Adı (Zorunlu)</strong></li><li><strong>Görüntülenecek Ad (Zorunlu)</strong></li><li><strong>Seçenek Kodu (Zorunlu)</strong></li><li><strong>Veri Tipi (Zorunlu)</strong><br><em>Metin</em>, <em>Tam Sayı</em>, <em>Ondalık Sayı</em> veya <em>Ölçü</em>.</li></ul><p>Alanları doldurduktan sonra <strong>Devam Et</strong> butonuna tıklayın.<br>Seçenek oluşturulur ve detay sayfasına yönlendirilirsiniz.</p></td><td data-object-fit="contain"><a href="/files/irKelHoRZDtV0V69hKMy">/files/irKelHoRZDtV0V69hKMy</a></td></tr></tbody></table>
{% endstep %}

{% step %}
**Detay sayfasında ilgili özelleştirmeleri yapın.**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p></p><ul><li>Veri Tipi seçilir, değiştirilir.</li><li>Gerekirse seçenek grubu bağlanır</li></ul></td><td data-object-fit="contain"><a href="/files/jLvYavsVVUQlUarLYCul">/files/jLvYavsVVUQlUarLYCul</a></td></tr></tbody></table>
{% endstep %}

{% step %}
**Detay sayfasında Seçenek Değerleri tab’ine gidin.**
{% endstep %}

{% step %}
**Değer Ekle butonuna tıklayın.**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p>Açılan pencerede aşağıdaki alanları doldurun:</p><ul><li><strong>Değer Adı (Zorunlu)</strong></li><li><strong>Değer Kodu (Zorunlu)</strong></li></ul><p>Alanları doldurduktan sonra <strong>Devam Et</strong> butonuna tıklayın.<br>Seçenek değeri oluşturulur ve ilgili seçeneğe eklenmiş olur.<br>İstenirse seçenek değer grubu bağlanır</p></td><td data-object-fit="contain"><a href="/files/NKPZOtVkQl6Ao9T1YRW3">/files/NKPZOtVkQl6Ao9T1YRW3</a></td></tr></tbody></table>
{% endstep %}

{% step %}
🎉**Seçenek başarıyla oluşturuldu.**
{% endstep %}
{% endstepper %}

#### :arrow\_forward:<mark style="color:$info;">Örnek Kullanım Senaryosu: Televizyon</mark>

Bir televizyon ürünü için ürün modelimizi oluştururken hem **özellikleri** hem de **seçenekleri** birlikte tanımlayalım.

Öncelikle televizyon ürününü tanımlayan **özellikleri** oluşturalım. Bu alanlar ürünün teknik bilgilerini tutar ve genellikle varyant oluşturmaz.

{% tabs %}
{% tab title="Enerji Sınıfı" %} <mark style="color:$primary;">**Enerji Sınıfı Özelliğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Özellikler** sayfasına gidin.

2. **Özellik Ekle** butonuna tıklayın.

3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Özellik Adı:** Enerji Sınıfı
   * **Özellik Kodu:** ENRJ-1
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/0xvOB6d18hl33eOa2QA2" alt="" width="235"><figcaption></figcaption></figure></div>
   ```

4. **Devam Et** butonuna tıklayın.

Özellik oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

5. **Veri Tipi** olarak **Çoklu Seçim** seçin.
6. **Değer Ekle** butonuna tıklayarak aşağıdaki değerleri oluşturun:
   * A
   * B
   * C
   * D

<div align="left" data-with-frame="true"><figure><img src="/files/QhOs76wnUzHFanlu2SCU" alt="" width="264"><figcaption></figcaption></figure></div>

:tada:Enerji sınıfı özelliği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Garanti Süresi" %} <mark style="color:$primary;">**Garanti Süresi Özelliğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Özellikler** sayfasına gidin.
2. **Özellik Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Özellik Adı:** Garanti Süresi (Ay)
   * **Özellik Kodu:** GRNT
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/IUmCuKjFf3dy9BbBGevM" alt="" width="233"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Özellik oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

5. **Veri Tipi** olarak **Tam Sayı** seçin.

<div align="left" data-with-frame="true"><figure><img src="/files/Zew5Djd5hqyU2VIDM8mT" alt="" width="335"><figcaption></figcaption></figure></div>

Garanti süresi özelliği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Model Yılı" %} <mark style="color:$primary;">**Model Yılı Özelliğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Özellikler** sayfasına gidin.
2. **Özellik Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Özellik Adı:** Model Yılı
   * **Özellik Kodu:** MDL
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/vIrMLihpln8N89SJSPKj" alt="" width="233"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Özellik oluşturulduktan sonra detay sayfasına yönlendirilirsiniz. Detay sayfasında:

5. **Veri Tipi** olarak **Tam Sayı** seçin.

<div align="left" data-with-frame="true"><figure><img src="/files/pc9CmB4PNXeZ2HUi8U9N" alt="" width="353"><figcaption></figcaption></figure></div>

Model yılı özelliği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Dahili Uydu Alıcı" %} <mark style="color:$primary;">**Dahili Uydu Alıcı Özelliğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Özellikler** sayfasına gidin.
2. **Özellik Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Özellik Adı:** Dahili Uydu Alıcı
   * **Özellik Kodu:** dahili\_uydu\_alici
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/iF4eDZfnsNTdVViBzeLN" alt="" width="230"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Özellik oluşturulduktan sonra detay sayfasına yönlendirilirsiniz. Detay sayfasında:

5. **Veri Tipi** olarak **Var/Yok** seçin.

<div align="left" data-with-frame="true"><figure><img src="/files/teqSI84bsySY4cdOjr1q" alt="" width="334"><figcaption></figcaption></figure></div>

Dahili uydu alıcı özelliği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}
{% endtabs %}

Şimdi ürünün farklı versiyonlarını oluşturmak için **seçenekleri** tanımlayalım. Bu alanlar ürünün varyantlarını oluşturur ve fiyat veya stok bilgisini etkileyebilir.

{% tabs %}
{% tab title="Ekran Boyutu" %} <mark style="color:$primary;">**Ekran Boyutu Seçeneğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Seçenekler > Seçenekler** sayfasına gidin.
2. **Seçenek Ekle** butonuna tıklayın.
3. Açılan **Yeni Seçenek Ekle** penceresinde aşağıdaki alanları doldurun:

   * **Seçenek Adı:** Ekran Boyutu (inç)              *(Zorunlu)*
   * **Görüntülenecek Ad:** Ekran Boyutu (inç)  *(Zorunlu)*
   * **Seçenek Kodu:** ekrn12                               *(Zorunlu)*
   * **Veri Tipi:** Ölçü                                             *(Zorunlu)*
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/w2SrTWOW6zMilkuR4cZB" alt="" width="233"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Seçenek oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

<div align="left" data-with-frame="true"><figure><img src="/files/RVaS4Mdfa420MLifXjxh" alt="" width="291"><figcaption></figcaption></figure></div>

5. **Seçenek Değerleri** tab’ine gidin.

6. **Değer Ekle** butonuna tıklayın.

7. Açılan **Yeni Değer** penceresinde aşağıdaki alanları doldurun:

   * **Değer Adı:** 75 inç           &#x20;
   * **Görüntülenecek Değer Adı:** 75 inç &#x20;
   * **Değer Kodu:** 75
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/zudrciNV4xNjarPgHV5S" alt="" width="232"><figcaption></figcaption></figure></div>
   ```

8. Tek tek aşağıdaki değerleri oluşturun:

* **55 inç**
* **65 inç**
* **75 inç**

:tada:Ekran Boyutu seçeneği ve değerleri oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Çözünürlük" %} <mark style="color:$primary;">**Çözünürlük Seçeneğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Seçenekler > Seçenekler** sayfasına gidin.
2. **Seçenek Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Seçenek Adı:** Çözünürlük              *(Zorunlu)*
   * **Görüntülenecek Ad:** Çözünürlük  *(Zorunlu)*
   * **Seçenek Kodu:** CZNRLK                *(Zorunlu)*
   * **Veri Tipi:** Metin                               *(Zorunlu)*
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/1dnF2AK6o1faxVCDkb0t" alt="" width="230"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Seçenek oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

<div align="left" data-with-frame="true"><figure><img src="/files/Vpvi63cTHuACjG52y44J" alt="" width="294"><figcaption></figcaption></figure></div>

5. **Seçenek Değerleri** tab’ine gidin.
6. **Değer Ekle** butonuna tıklayın.
7. Açılan **Yeni Değer** penceresinde aşağıdaki alanları doldurun:

   * **Değer Adı:** 4K         &#x20;
   * **Görüntülenecek Değer Adı:** 4K  &#x20;
   * **Değer Kodu:** 4K &#x20;
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/lagpiGPEgwT8NLpdgdPl" alt="" width="231"><figcaption></figcaption></figure></div>
   ```
8. Tek tek aşağıdaki değerleri oluşturun:
   * **4K**
   * **8K**

Çözünürlük seçeneği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Panel Teknolojisi" %} <mark style="color:$primary;">**Panel Teknolojisi Seçeneğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Seçenekler > Seçenekler** sayfasına gidin.
2. **Seçenek Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Seçenek Adı:** Panel Teknolojisi               *(Zorunlu)*
   * **Görüntülenecek Ad:** Panel Teknolojisi   *(Zorunlu)*
   * **Seçenek Kodu:** PNL-TKNLJ                    *(Zorunlu)*
   * **Veri Tipi:** Metin                                         *(Zorunlu)*
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/BE8uLmCMVKRYeSqnUg95" alt="" width="232"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Seçenek oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

<div align="left" data-with-frame="true"><figure><img src="/files/TYUHIo1m2d4fN7yyphwA" alt="" width="312"><figcaption></figcaption></figure></div>

5. **Seçenek Değerleri** tab’ine gidin.

6. **Değer Ekle** butonuna tıklayın.

7. Açılan **Yeni Değer** penceresinde aşağıdaki alanları doldurun:

   * **Değer Adı:** LED         &#x20;
   * **Görüntülenecek Değer Adı:** LED         &#x20;
   * **Değer Kodu:** LED           &#x20;
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/5wWUWqsRf7qpkncv2rc6" alt="" width="231"><figcaption></figcaption></figure></div>
   ```

8. Tek tek aşağıdaki değerleri oluşturun:
   * **LED**
   * **OLED**
   * **QLED**

Panel Teknolojisi seçeneği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}

{% tab title="Renk" %} <mark style="color:$primary;">**Renk Seçeneğini Oluşturma**</mark>

1. **Ayarlar > Katalog > Seçenekler > Seçenekler** sayfasına gidin.
2. **Seçenek Ekle** butonuna tıklayın.
3. Açılan pencerede aşağıdaki alanları doldurun:

   * **Seçenek Adı:** Renk              *(Zorunlu)*
   * **Görüntülenecek Ad:** Renk  *(Zorunlu)*
   * **Seçenek Kodu:** RENK          *(Zorunlu)*
   * **Veri Tipi:** Metin                     *(Zorunlu)*
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/xxJj1gPLGQId3uRMELPV" alt="" width="233"><figcaption></figcaption></figure></div>
   ```
4. **Devam Et** butonuna tıklayın.

Seçenek oluşturulduktan sonra detay sayfasına yönlendirilirsiniz.

<div align="left" data-with-frame="true"><figure><img src="/files/cM34gRuivhNpfHZN1uIt" alt="" width="255"><figcaption></figcaption></figure></div>

5. **Seçenek Değerleri** tab’ine gidin.
6. **Değer Ekle** butonuna tıklayın.
7. Açılan **Yeni Değer** penceresinde aşağıdaki alanları doldurun:

   * **Değer Adı:** Siyah         &#x20;
   * **Görüntülenecek Değer Adı:** LED         &#x20;
   * **Değer Kodu:** SYH
   *

   ```
   <div align="left" data-with-frame="true"><figure><img src="/files/2pVzHLzyVuEVySQQUejr" alt="" width="233"><figcaption></figcaption></figure></div>
   ```
8. Tek tek aşağıdaki değerleri oluşturun:

* **Siyah**
* **Gri**

Renk seçeneği oluşturulmuş olur, artık veri şemasına bağlayabilirsiniz.
{% endtab %}
{% endtabs %}

#### :arrow\_forward:<mark style="color:$info;">Özellikler ve seçenekler veri şemasına nasıl eklenir?</mark>

Özellikleri ve seçenekleri oluşturduktan sonra, bu alanları ürün veri modelinizde kullanabilmek için veri şemasına eklemelisiniz.

Bunun için:

{% stepper %}
{% step %}
**Ayarlar > Katalog > Ürün Aileleri** sayfasına gidin.
{% endstep %}

{% step %}
Özellik ve seçenekleri eklemek istediğiniz veri şemasını açın.
{% endstep %}

{% step %}
Veri şeması detay sayfasında **Veri Şeması Alanları** tab’ine gidin.
{% endstep %}

{% step %}
**Yeni Alan Ekle** butonuna tıklayın.

* Alan Adı (Zorunlu)\
  Veri şemasına eklemek istediğiniz alanın adını girin.
* Alan Türü (Zorunlu)\
  Eklemek istediğiniz alanın türünü seçin.
  * Özellik eklemek için    -> Özellik
  * Seçenek eklemek için -> Seçenek
* Alan Değeri (Zorunlu)\
  Alan Türü olarak **Özellik** veya **Seçenek** seçtiğinizde bu alan görünür.\
  Bu bölümden daha önce oluşturduğunuz özelliği veya seçeneği seçin.
  {% endstep %}

{% step %}
Alanları doldurduktan sonra Kaydet butonuna tıklayın.
{% endstep %}

{% step %}
Alan veri şemasına eklenir ve ürün oluşturma sırasında kullanılabilir hale gelir.

:tada:Artık veri şemamızı <mark style="background-color:purple;">kategoriye</mark> bağlayabilir, havuz oluşturma işlemine geçebiliriz.
{% endstep %}
{% endstepper %}

> Televizyon örneğimizden devam edelim ve veri şeması için oluşturduğunuz özellikleri veri şemasına ekleyelim.
>
> Öncelikle <mark style="background-color:purple;">**Televizyon veri şeması**</mark>**nın** detay sayfasına gidin ve **Yeni Alan Ekle** butonuna tıklayın. Açılan pencerede <mark style="background-color:purple;">**Alan Türü**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">olarak</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Özellik**</mark> seçin. Ardından Alan Değeri alanından daha önce oluşturduğunuz özelliklerden birini seçin, eklemeyi tamamlayın:
>
> * Enerji Sınıfı
> * Garanti Süresi
> * Model Yılı
> * Dahili Uydu Alıcı
>
> Aynı adımları izleyerek seçenekleri de veri şemasına ekleyebilirsiniz. Bunun için <mark style="background-color:purple;">**Alan Türü**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">olarak Seçenek</mark> seçin ve Alan Değeri alanından daha önce oluşturduğunuz seçenekleri ekleyin:
>
> * Ekran Boyutu
> * Çözünürlük
> * Panel Teknolojisi
> * Renk
> *
>
> ```
> <div align="left" data-with-frame="true"><figure><img src="/files/aKCKAsJISYGVdamyxxms" alt="" width="375"><figcaption></figcaption></figure></div>
> ```
>
> Bu şekilde televizyon ürünleri için tanımladığınız özellik ve seçenekleri veri şemasına ekleyebilir ve ürün modelinizde kullanabilirsiniz.


# Havuz nedir, nasıl yönetilir?

Bu sayfada havuzun ne olduğunu, ne amaçla kullanıldığını ve nasıl oluşturulduğunu ayrıca kategori, veri şeması ve havuz arasındaki ilişkiyi öğreneceksiniz.

### :rocket:<mark style="color:$primary;background-color:purple;">Havuz'ları Anlayın ve Yönetin</mark>

Önceki sayfalarda ürün [veri şemasını](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/veri-semasi-nasil-olusturulur) oluşturduk ve ürün modelimizi [özellikler ile seçenekleri](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/ozellik-ve-secenek-nasil-tanimlanir) tanımlayarak hazırladık. Şimdi bu veri modelini kullanarak ürünleri yöneteceğimiz yapıyı inceleyelim.

#### :arrow\_forward:<mark style="color:$info;">Havuz Nedir?</mark>

**Havuz**, ürünlerin sistemde ilk kez oluşturulduğu ve yönetildiği çalışma alanıdır. Ürünler bu alana yüklenir ve ürün bilgileri burada kontrol edilir.

Ürünler havuza <mark style="background-color:purple;">Excel dosyaları veya entegrasyonlar</mark> (örneğin SAP) aracılığıyla yüklenebilir.\
Her havuz, belirli bir <mark style="background-color:purple;">kategoriye</mark> bağlıdır ve o kategori için tanımlanan <mark style="background-color:purple;">**veri şemasını**</mark> kullanır. Bu sayede ürünler platformda tanımlanan standart veri yapısına uygun şekilde oluşturulur ve yönetilir.

Başka bir ifadeyle havuz, ürünlerin doğru veri modeli ile sisteme yüklenmesini sağlayan başlangıç noktasıdır.

#### :arrow\_forward:<mark style="color:$info;">Havuz ne amaçla kullanılır?</mark>

Ürünleri sisteme yüklerken havuzu kullanırsınız. Ürün verileri bu alan içinde oluşturulur, düzenlenir ve kontrol edilir.

Havuz sayesinde:

* <mark style="background-color:purple;">ürünler doğru kategori altında yönetilir</mark>
* <mark style="background-color:purple;">ürün verisi tanımlanan veri şemasına uygun ilerler</mark>
* <mark style="background-color:purple;">ürün yükleme ve yönetim süreçleri daha düzenli hale gelir</mark>

> Örneğin televizyon ürünleri için oluşturduğunuz **Televizyon** kategorisine bağlı bir havuz kullanarak, televizyon ürünlerinizi ilgili veri modeli ile sisteme yükleyebilirsiniz.&#x20;

{% hint style="info" %}
**Önemli**: Yeni bir veri şeması oluşturduğunuzda, sistem otomatik olarak aynı isimde bir havuz oluşturur. Bu havuz, ilgili veri şemasına bağlı ürünlerin yönetileceği alan olarak kullanılır.
{% endhint %}

#### :arrow\_forward:<mark style="color:$info;">Havuz Oluşturmak İçin Neden Kategori Gereklidir?</mark>

Havuz oluştururken bir kategori seçmeniz gerekir. Bunun nedeni, havuz'un hangi ürün tipini yöneteceğini bilmesi gerektiğidir.

Kategori aynı zamanda hangi veri şemasının kullanılacağını da belirler.

Her kategori, kendisine bağlı bir **veri şeması** ile çalışır. Bu veri şeması ürünlerin hangi alanları içereceğini ve ürün verisinin nasıl yapılandırılacağını tanımlar. Havuz oluşturulduğunda sistem, seçilen kategoriye bağlı veri şemasını kullanarak ürünlerin bu yapıya uygun şekilde oluşturulmasını sağlar.

Başka bir ifadeyle:

*<mark style="color:purple;">Veri Şeması → Kategori → Havuz → Ürün</mark>*

Bu ilişki sayesinde ürünler doğru veri modeli ile oluşturulur.

{% hint style="info" %}
Eğer henüz bir veri şeması oluşturmadıysanız, [**Veri Şeması Nasıl Oluşturulur?**](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/veri-semasi-nasil-olusturulur) sayfasındaki adımları takip edebilirsiniz.
{% endhint %}

***

{% hint style="info" icon="delete-right" %}
Kategori oluşturma adımına geçmeden önce, kategori yapısı için gerekli olan **kategori boyutunun** ne olduğunu ve nasıl tanımlandığını öğrenmeniz gerekir.
{% endhint %}

#### :arrow\_forward:<mark style="color:$info;">Kategori Boyutu Nedir?</mark>

Kategori boyutu, kategori yapınızı belirli bir amaca göre organize etmenizi sağlar. Aynı sistem içinde birden fazla kategori yapısı oluşturabilir ve bu yapıları farklı ihtiyaçlara göre ayrı ayrı yönetebilirsiniz.

Kategori boyutu oluşturmak için aşağıdaki adımları izleyin:

{% stepper %}
{% step %} <mark style="background-color:purple;">**Ayarlar > Katalog > Kategori Boyutları**</mark> **sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Boyut Ekle**</mark>**&#x20;butonuna tıklayın.**

Açılan pencerede aşağıdaki alanları doldurun:

* **Ad (Zorunlu)**
* **Kod (Zorunlu)**
* **Entegrasyon Kodu (Zorunlu)**
*

```
<div align="left" data-with-frame="true"><figure><img src="/files/JDrOBpWZ7XmH7k7LcBUu" alt="" width="237"><figcaption></figcaption></figure></div>
```

{% endstep %}

{% step %} <mark style="background-color:purple;">**Kaydet**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}
{% endstepper %}

Kategori boyutu oluşturulduktan sonra kategori tanımlama adımına geçebilirsiniz.

#### :arrow\_forward:<mark style="color:$info;">Kategori Nasıl Oluşturulur?</mark>

Kategori oluşturmak için aşağıdaki adımları izleyin:

{% stepper %}
{% step %} <mark style="background-color:purple;">**Katalog > Kategoriler**</mark>**&#x20;sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Kategori Ekle**</mark> **butonuna tıklayın.**

Açılan pencerede aşağıdaki alanları doldurun:

* **İsim (Zorunlu)**
* **Boyut (Zorunlu)**
* **Veri Şeması**&#x20;
* **Üst Kategori**
* **Kod (Zorunlu)**

> Kategorinizi hiyerarşik bir yapıda oluşturmak istiyorsanız, **Üst Kategori (Opsiyonel)** alanından kategoriyi bağlamak istediğiniz üst kategoriyi seçebilirsiniz.

> :warning:Aynı pencerede <mark style="background-color:purple;">**Veri Şeması**</mark> alanı da yer alır. Bu alan seçilmeden kategori kaydedilebilir ve kategori oluşturulabilir. Ancak bu durumda kategori *<mark style="background-color:purple;">**taslak**</mark>* statüsünde oluşturulur.
>
> ![](/files/yrP59dl4fi5xWZro3gE8)
>
> Yeni bir kategori oluştururken veri şeması seçmeniz önerilir. Bu sayede kategori doğrudan ilgili veri modeli ile ilişkilendirilmiş olur. \
> Eğer veri şeması seçmeden taslak bir kategori oluşturduysanız, <mark style="background-color:purple;">kategori detay sayfasına</mark> giderek daha sonra **veri şeması** bağlayabilirsiniz.
> {% endstep %}

{% step %}
🎉**Kategori başarıyla oluşturuldu.**
{% endstep %}
{% endstepper %}

#### :arrow\_forward:<mark style="color:$info;">Havuz Nasıl Oluşturulur?</mark>

Kategori oluşturma işlemini tamamladıktan sonra <mark style="background-color:purple;">havuz oluşturma</mark> adımına geçebilirsiniz.

Yeni bir havuz oluşturmak için aşağıdaki adımları izleyin:

{% stepper %}
{% step %} <mark style="background-color:purple;">**Katalog > Havuzlar**</mark>**&#x20;sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Ürün Ailesi Ekle**</mark> **butonuna tıklayın.**

Açılan pencerede sistemde tanımlı kategoriler, varsa alt kategorileriyle birlikte listelenir.

Yeni bir ürün ailesi oluşturmak ve içerisine ürün ekleyebilmek için bir kategori seçmeniz gerekir.
{% endstep %}

{% step %}
**Bir kategori seçtikten sonra&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
:tada:**Seçilen kategoriye bağlı olarak sistem, ürün eklemeye hazır&#x20;**<mark style="background-color:purple;">**boş bir havuz**</mark>**&#x20;oluşturur.**

Bu havuz içinde ürünlerinizi oluşturmaya veya yüklemeye başlayabilirsiniz.
{% endstep %}
{% endstepper %}

> Havuz oluşturma penceresinde listelenen kategorilerden herhangi biri bir veri şemasına bağlı değilse seçilemez. Bu durumda kategori adının yanında <mark style="background-color:purple;">**\[Veri şeması yok]**</mark> uyarısı görüntülenir. <mark style="color:purple;background-color:purple;">Havuz oluşturabilmek için önce ilgili kategoriye bir veri şeması bağlamanız gerekir.</mark>

#### :arrow\_forward:<mark style="color:$info;">Havuz Yönetimi Nasıl Yapılır?</mark>

Oluşturduğunuz bir havuzun içindeki ürünleri yönetmek için havuz detay sayfasına gitmeniz gerekir.

Bunun için Havuzlar sayfasında ilgili havuzu bulun ve <mark style="background-color:purple;">**Ürünleri Yönet**</mark> butonuna tıklayın. Bu işlem sizi havuzun detay sayfasına yönlendirir.

{% hint style="info" %}
**Önemli:** Yeni oluşturulan bir havuz başlangıçta **boş** olarak oluşturulur. İçinde ürün bulunmayan, boş havuzlar silinebilir. Ancak içinde ürün bulunan havuzlar silinemez.
{% endhint %}

Havuza ürün yükleme işlemi <mark style="background-color:purple;">**Excel dosyası**</mark> aracılığıyla gerçekleştirilir.

Yüklenen ürünler ilk olarak havuz detay sayfasındaki Tümü sekmesi altında listelenir. Bu aşamada ürünler sistemde oluşturulmuş olsa da henüz yayınlanmış sayılmaz.\
Ürünler, havuz içinde <mark style="background-color:purple;">yayınlanmayı bekleyen</mark> ürünler olarak tutulur.

Ürünleri yayınladıktan sonra ilgili ürünler havuz detay sayfasındaki <mark style="background-color:purple;">Yayındakiler</mark> sekmesi altında listelenmeye başlar.

**Havuz yaşam döngüsü:** *Ürün Yükleme → Havuz (Tümü) → Yayınlama → Yayındakiler*

{% hint style="info" %}
&#x20;**Not:** Havuzda listelenen ürünleri **dışa aktarabilirsiniz**. Yayınlanmış ürünler ve yayınlanmayı bekleyen ürünler ayrı ayrı dışa aktarılabilir.
{% endhint %}


# Medya ve Varlık yönetimi nasıl yapılır?

Bu sayfada medya varlıklarını nasıl yöneteceğinizi, görsel, dosya ve video yükleme işlemlerini nasıl gerçekleştireceğinizi ve yüklenen medyaları ürünlerle nasıl eşleştireceğinizi öğreneceksiniz.

### Ürünlerinizi medya varlıkları ile zenginleştirin

Medya yönetimi, ürün, kategori ve marka kayıtlarında kullanılacak görsel, dosya ve video varlıklarının merkezi olarak yönetilmesini sağlar. Doğru yapılandırıldığında içerikler daha düzenli ilerler, medya yönetimi kolaylaşır ve medya eşleştirmeleri daha kontrollü şekilde yapılır.

#### Medya yönetimi nedir?

Medya yönetimi, ürün, kategori ve marka kayıtlarında kullanılacak görsel, dosya ve videoları PIM içerisinde merkezi olarak yönetmenizi sağlar.

Medya Yönetimi alanı altında:

* **Medya Listesi**
* **Toplu Medya Yükle**
* **Görseller**
* **Dosyalar**
* **Videolar**
* **Silinen Kayıtlar**

başlıkları yer alır.

Bu alanlar sayesinde medya varlıklarını görüntüleyebilir, yeni medya yükleyebilir, toplu medya işlemleri gerçekleştirebilir ve silinen kayıtları yönetebilirsiniz. Medya Listesi alanı tüm medya kayıtlarını merkezi olarak görüntülemek ve yönetmek için kullanılırken, Toplu Medya Yükle alanı çok sayıda medya dosyasını aynı anda sisteme yüklemenizi sağlar. Görseller, Dosyalar ve Videolar alanları medya türlerine göre ayrı yönetim sunarken, Silinen Kayıtlar alanı silinen medya varlıklarını görüntülemek ve geri yüklemek için kullanılır.

Medya yönetimi özellikle ürün görsellerini düzenli tutmak, ürün kartlarını zenginleştirmek ve doğru medya varlığının doğru kayıtla eşleşmesini sağlamak için kullanılır.

#### Lidia PIM’e görsel, dosya ve video nasıl yüklenir?

Medya yükleme işlemlerini medya türlerine göre (görsel, dosya, video) ayrılmış dosya gezgini alanlarından gerçekleştirebilir veya toplu medya yükleme ekranını kullanabilirsiniz.

{% hint style="info" %}
Görseller, Dosyalar ve Videolar alanlarının tamamı **aynı dosya gezgini** yapısını kullanır.
{% endhint %}

* **Dosya Gezgini Yapısı**

<figure><img src="/files/zluV8BwBR5TaQ5r90loD" alt=""><figcaption></figcaption></figure>

Dosya gezgini ekranının üst bölümünde işlem butonları ve bir arama alanı yer alır. Alt bölüm ise iki ayrı alandan oluşur. Sol tarafta yalnızca klasör yapısı görüntülenirken, sağ tarafta klasör ve dosya içerikleri birlikte listelenir.

Sağ taraftaki listeleme alanında medya kayıtlarına ait isim, yetki bilgisi, değiştirilme tarihi, boyut ve tür bilgileri görüntülenir.

<div data-with-frame="true"><figure><img src="/files/o1knfYmHnzW3Vzj99ozE" alt=""><figcaption></figcaption></figure></div>

* <img src="/files/U5VZMsNQuwr1lpxNDRJL" alt="" data-size="line">Üst bölümde yer alan geri ve ileri ok ikonları klasör içinde gezinmenizi sağlar.
* <img src="/files/0dHq9qB15fb51atNlWZW" alt="" data-size="line"> Bu ikonların yanında yer alan klasör oluşturma butonu ile yeni klasör oluşturabilirsiniz. Butona tıkladıktan sonra yalnızca klasör ismini girmeniz yeterlidir. Oluşturulan klasörler hem sol taraftaki klasör alanında hem de sağ taraftaki listeleme alanında görüntülenir.
* <img src="/files/9SM3wbdmXIZ2d0bSYW81" alt="" data-size="line"> Yeni dosya ekleme ikonu, bilgisayarınızdan sisteme yeni medya yüklemek için kullanılır. Butona tıkladığınızda açılan pencere üzerinden dosyaları sürükle-bırak yöntemiyle yükleyebilir veya Dosya Seç butonunu kullanabilirsiniz.
* <img src="/files/Rjl6ODF6Hs99QTHF3GG7" alt="" data-size="line"> Yeniden adlandırma ikonu yalnızca seçilen dosya veya klasör üzerinde aktif olur ve ilgili medya kaydının adını değiştirmek için kullanılır.
* <img src="/files/s4Qpd9x5UoHB6hCiK0lQ" alt="" data-size="line"> Makas ikonu ise kesme işlemini gerçekleştirir ve yanındaki yapıştır butonu ile birlikte çalışır.
* <img src="/files/Hb3KNPMg4OSvgcUpnaFQ" alt="" data-size="line"> Yapıştır butonu yalnızca bir kesme işlemi yapıldıktan sonra aktif hale gelir.
* <img src="/files/9s5rDgeaPCZigxTCNJ2C" alt="" data-size="line"> Silme ikonu, dosya veya klasörleri silmek için kullanılır. Silinen medya kayıtları doğrudan kalıcı olarak silinmez ve Silinen Kayıtlar alanında 14 gün boyunca tutulur. İstenirse kullanıcı kayıtları bekletmeden kalıcı olarak da silebilir.\ <img src="/files/ffd5YnTPe0p44gwCleyj" alt="" data-size="original">
* <img src="/files/WgySX5PuVn3v2Ob7WEfR" alt="" data-size="line"> Göz ikonu medya varlıklarını önizlemek için kullanılır. İsterseniz önizleme alanını tam ekran olarak da görüntüleyebilirsiniz.
* <img src="/files/Aoh07zhaRio5y4nSKLxQ" alt="" data-size="line">/<img src="/files/3Q8fZfIvlwHOea6eMu3Y" alt="" data-size="line"> Listeleme ikonu ile medya kayıtlarını simge görünümü veya liste görünümü şeklinde görüntüleyebilirsiniz.

{% columns %}
{% column %}

<figure><img src="/files/a75Pf96L0Lut9cHqRIGM" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/BLeZMGx10UWwDPSdSVH7" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

* [ ] <img src="/files/ZHnZREHjjaqaPI2M1uwT" alt="" data-size="line"> Sıralama ikonu ise kayıtları ada, boyuta, tarihe, türe veya izin bilgilerine göre sıralamanızı sağlar. Ayrıca yalnızca klasörleri görüntüleyebilir veya ağaç görünümü üzerinden yeni ana klasörler oluşturabilirsiniz.
* [ ] <img src="/files/oyWXny3YF3BqkkISJT9p" alt="" data-size="line"> Ev ikonu yalnızca bir dosya veya klasör seçildiğinde aktif olur. Bu butona tıklandığında açılan pencerede: Yeni sekmede aç, Bağlantıyı kopyala, İndir seçenekleri görüntülenir.\
  \
  ![](/files/ALKBYzahCupJuRhRGRKG)
* [x] <mark style="color:$info;">**Görsel Nasıl Yüklenir?**</mark>

{% stepper %}
{% step %}
**Medya Yönetimi > Görseller** sayfasına gidin.
{% endstep %}

{% step %}
**Klasör oluşturma ikonuna tıklayın.**
{% endstep %}

{% step %}
**Klasör adını** **girin**.

<div align="left" data-with-frame="true"><figure><img src="/files/YlxPYMUljSvQwYBOCkrg" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Oluşturulan klasöre tıklayarak klasörü açın.**
{% endstep %}

{% step %}
**Dosya yükleme ikonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/3DhnBTMuDLG90uFRhkt9" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Bilgisayarınızdan yüklemek istediğiniz dosyaları seçin.**

Seçilen dosyalar dosya gezgini alanına yüklenmiş olur.
{% endstep %}
{% endstepper %}

> **Not:** Medya yükleme adımları Dosyalar ve Videolar alanları için de birebir aynı şekilde çalışır.

{% hint style="info" %}
Görseller dosya gezginine yüklenen medya varlıkları **ürün, kategori ve marka** kayıtlarında kullanılabilir.
{% endhint %}

#### Toplu medya yükleme işlemi nasıl yapılır?

Birden fazla medya varlığını aynı anda yüklemek için toplu medya yükleme özelliğini kullanabilirsiniz.

{% stepper %}
{% step %}
**Medya Yönetimi > Toplu Medya Yükle sayfasına gidin.**
{% endstep %}

{% step %}
**Açılan ekranda aşağıdaki medya türlerinden birini seçin:**

* Kategori Görseli
* Marka Görseli
* Ürün Görseli
* Doküman

<div align="left" data-with-frame="true"><figure><img src="/files/QL5kFnu3dwNixnstFluy" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Medya türünü seçtikten sonra ekranda açılan yükleme alanına dosyalarınızı sürükleyin veya bilgisayarınızdan seçin.**

Yüklenen dosyaların ekranda listelendiğini göreceksiniz.

![](/files/QZEpGCAYbyGkU8pfyg2S)
{% endstep %}

{% step %}
**Devam Et butonuna tıklayın.**

Bu işlem sonrasında ilk aşama olan Doküman Yükle adımı tamamlanır ve sistem sizi **Veriyi Kontrol Et** adımına yönlendirir.

<div align="left"><figure><img src="/files/oOCxn6psO08sDr5JXdtT" alt=""><figcaption></figcaption></figure></div>

Bu aşamada sistem medya boyutlarını ve yükleme kurallarını kontrol eder. Eğer görseller uygun boyutlarda değilse veya yükleme kurallarına uygun değilse işlem hata verir ve ilgili medya kayıtları içeri alınmaz.

{% hint style="info" %}
Hatalı medya kayıtları için aynı ekranda yer alan **Yeni Görsel Yükle** butonunu kullanarak tekrar yükleme yapabilirsiniz.

<img src="/files/sxKOHKLGtekzSudYVbPe" alt="" data-size="original">
{% endhint %}
{% endstep %}

{% step %}
**Validasyon işlemi başarılıysa Devam Et butonuna tıklayın.**

Son aşama olan **Tamamlandı** ekranına yönlendirilirsiniz.
{% endstep %}

{% step %}
**Medya Yönetimi butonuna tıklayarak dosya gezgini ekranına geri dönebilir ve yüklenen medya kayıtlarını kontrol edebilirsiniz.**
{% endstep %}
{% endstepper %}

#### Medya listesi ne işe yarar?

Medya listesi, Lidia PIM’e yüklenen tüm medya varlıklarını merkezi olarak görüntüleyebileceğiniz ve yönetebileceğiniz alandır.

Bu ekranda medya kayıtlarına ait isim, dosya türü, dosya uzantısı, etiket, kullanım alanı, oluşturulma tarihi ve durum bilgileri görüntülenir. Aynı ekran üzerinden medya kayıtlarını filtreleyebilir, detaylarını inceleyebilir, düzenleyebilir veya silebilirsiniz.

Medya listesi ekranında yer alan **Toplu Güncellemeler** butonu ile seçilen medya kayıtları üzerinde toplu işlemler gerçekleştirebilirsiniz.

Bu alan altında:

* Durum Güncelle, Etiket Ekle, Dokümanları Eşleştir

işlemleri yer alır.

Durum Güncelle işlemi ile seçilen medya kayıtlarının durum bilgileri toplu olarak güncellenebilir. Etiket Ekle işlemi medya kayıtlarını etiketlemek ve daha kolay filtrelemek için kullanılır. Dokümanları Eşleştir işlemi ise medya varlıklarını ilgili kayıtlarla ilişkilendirmek için kullanılır.

#### Yüklenen varlıklar ürünlerle nasıl eşleştirilir?

Medya eşleştirme işlemi, yüklenen medya varlıklarının ürün kayıtlarıyla ilişkilendirilmesini sağlar.

Bu işlem iki farklı şekilde gerçekleştirilebilir:<br>

:small\_orange\_diamond:**Resim Kodu ile Otomatik Eşleştirme**

Ürün oluştururken veya ürün bilgilerini düzenlerken yer alan **Görsel Kodu** alanına girilen değer ile sisteme yüklenen görsel adı aynıysa sistem ilgili görseli ürünle otomatik olarak eşleştirir.

**Örneğin** ürün üzerinde yer alan Resim Kodu değeri:

* TV\_RESIM

ise, sisteme yüklenen görsel adı da aynı şekilde TV\_RESIM olduğunda eşleştirme otomatik yapılır.

{% hint style="info" %}
Aynı ürüne birden fazla görsel eklemek istiyorsanız görsellerinizi Resim Kodu değerinin türev isimleriyle yükleyebilirsiniz. Örneğin: TV\_RESIM\_1, TV\_RESIM\_2...
{% endhint %}

:small\_orange\_diamond:**Medya Listesi Üzerinden Manuel Eşleştirme**

Medya listesi ekranı üzerinden de manuel eşleştirme yapılabilir.

1. **Medya Yönetimi > Medya Listesi** sayfasına gidin.
2. Eşleştirmek istediğiniz medya kayıtlarını seçin.
3. **Toplu Güncellemeler** butonuna tıklayın.
4. Açılan seçenekler içerisinden **Dokümanları Eşleştir** işlemini seçin.
5. Açılan kontrol penceresinde işlemi inceleyin.
6. **Onayla** butonuna tıklayarak eşleştirme işlemini tamamlayın.

> **Not:** Toplu Güncellemeler butonu yalnızca medya kaydı seçildiğinde aktif hale gelir.

#### Kategori, marka ve ürün medyası detay sayfasından nasıl yüklenir?

Medya varlıkları ürün, kategori ve marka kayıtlarının detay sayfaları üzerinden yönetilebilir.

:small\_orange\_diamond:<mark style="color:$info;">**Kategori Medyası Nasıl Eklenir?**</mark>

{% stepper %}
{% step %}
**Katalog > Kategoriler sayfasına gidin.**
{% endstep %}

{% step %}
**İlgili kategori detay sayfasını açın.**

Temel Bilgi sekmesi açık gelir.
{% endstep %}

{% step %}
**Görseller alanında yer alan Görsel Seçin butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/KS3b1qlOuOOOIVzMJKO3" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Açılan görsel dosya gezgini ekranından daha önce yüklediğiniz görseller arasından seçim yapın.**
{% endstep %}

{% step %}
**Ekle butonuna tıklayın.**

> İsterseniz aynı kategoriye birden fazla görsel ekleyebilirsiniz.

{% hint style="info" %}
Görseller eklendikten sonra ilgili görseli **Kapak Görseli** olarak işaretleyebilirsiniz. Kapak görseli, kategori için varsayılan ve öncelikli görüntülenecek görseli belirlemek için kullanılır.

<img src="/files/VM76MducXTKdK7Uka9hq" alt="" data-size="original">
{% endhint %}
{% endstep %}

{% step %}
**Kaydet butonuna tıklayın.**

> Dikkat!\
> Kaydet butonuna basmadan sayfadan çıkarsanız görsel ekleme işlemi tamamlanmaz.
> {% endstep %}
> {% endstepper %}

:small\_orange\_diamond:<mark style="color:$info;">**Marka Medyası Nasıl Eklenir?**</mark>

Marka medya yönetimi de kategori medya yönetimi ile aynı şekilde çalışır.

{% stepper %}
{% step %}
**Katalog > Markalar sayfasına gidin.**
{% endstep %}

{% step %}
**İlgili marka detay sayfasını açın.**

Temel Bilgi sekmesi açık gelir.
{% endstep %}

{% step %}
**Resim alanında yer alan Görsel Seçin butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/0KqIBfDQrPk7vqw5D8cP" alt="" width="372"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Açılan görsel dosya gezgini ekranından daha önce yüklediğiniz görseller arasından seçim yapın.**
{% endstep %}

{% step %}
**Ekle butonuna tıklayın.**

> İsterseniz aynı markaya birden fazla görsel ekleyebilirsiniz.

{% hint style="info" %}
Görseller eklendikten sonra ilgili görseli **Kapak Görseli** olarak işaretleyebilirsiniz. Kapak görseli, marka için varsayılan ve öncelikli görüntülenecek görseli belirlemek için kullanılır.

<img src="/files/JY6CNf1D1X4fffJgmQtA" alt="" data-size="original">
{% endhint %}
{% endstep %}

{% step %}
**Kaydet butonuna tıklayın.**

> Dikkat!\
> Kaydet butonuna basmadan sayfadan çıkarsanız görsel ekleme işlemi tamamlanmaz.
> {% endstep %}
> {% endstepper %}

:small\_orange\_diamond:<mark style="color:$info;">**Ürün Medyası Nasıl Eklenir?**</mark>

Bu bölümde, ürün detay sayfası üzerinden görsel ve doküman yönetiminin nasıl yapılacağı anlatılmaktadır.

{% stepper %}
{% step %}
**Katalog > Ürünler sayfasına gidin.**
{% endstep %}

{% step %}
**İlgili ürün detay sayfasını açın.**
{% endstep %}

{% step %}
**Medya Yönetimi sekmesine gidin.**

Bu alanda Görseller ve Dokümanlar olmak üzere iki ayrı medya alanı yer alır. Ürün yükleme sırasında eklediğiniz görselleri ve dokümanları bu ekran üzerinden görüntüleyebilirsiniz.

<div align="left" data-with-frame="true"><figure><img src="/files/6LszqL9zcOlbLZWAlkCL" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Yeni Görsel Ekle butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan görsel dosya gezgini ekranından daha önce yüklediğiniz görseller arasından seçim yapın.**
{% endstep %}

{% step %}
**Ekle butonuna tıklayın.**

Gerekirse ilgili görseli kapak görseli olarak işaretleyin.
{% endstep %}

{% step %}
**Kaydet butonuna tıklayın.**
{% endstep %}
{% endstepper %}

> Ürüne doküman eklemek için **Yeni Doküman Ekle** butonuna tıklayın. Açılan dosyalar dosya gezgini ekranından daha önce yüklediğiniz dokümanları seçin, Ekle butonuna tıklayın ve işlemi tamamlamak için **Kaydet** butonunu kullanın.

#### Silinen kayıtlar nerede tutulur ve nasıl yönetilir?

Silinen medya kayıtları doğrudan kalıcı olarak silinmez. Silinen kayıtlar, belirli bir süre boyunca **Silinen Kayıtlar** alanında tutulur.

Bu alandan silinen medya kayıtlarını görüntüleyebilir, geri yükleyebilir veya kalıcı olarak silebilirsiniz.

Silinen kayıtları yönetmek için:

1. **Medya Yönetimi > Silinen Kayıtlar** sayfasına gidin.
2. Silinen medya kaydını bulun.
3. Gerekirse **Geri Yükle** seçeneğini kullanın.
4. Kaydı tamamen kaldırmak istiyorsanız **Kalıcı Olarak Sil** işlemini seçin.

{% hint style="info" %}
**Dikkat!**

Silinen medya kayıtları 14 gün boyunca geri yüklenebilir. Süre dolduktan sonra kayıtlar sistem tarafından kalıcı olarak silinir.
{% endhint %}


# Ürün nasıl eklenir?

Önceki adımlarda ürün veri modelinizi ve havuzunuzu hazırladınız. Bu sayfada ürünlerinizi Excel kullanarak Lidia PIM’e nasıl yükleyeceğinizi öğreneceksiniz.

### :rocket:<mark style="color:$primary;background-color:purple;">Ürünlerinizi PIM'e Yükleyin</mark>

Ürün yükleme süreci, hazırladığınız veri modeline göre çalışır ve ürün bilgileri bu yapı üzerinden sisteme aktarılır. Excel şablonu, <mark style="background-color:purple;">veri şemasında tanımlanan alanlara göre</mark> oluşturulur ve yüklenen ürünler bu alanlara uygun şekilde sisteme işlenir. Bu sayede ürün verisi standart bir yapı içinde ilerler ve sistem tarafından doğru şekilde yönetilir.

#### :arrow\_forward:<mark style="color:$info;">Ürün Yükleme Öncesi Tamamlanması Gereken Adımlar</mark>

{% hint style="warning" %}
**Önemli**

Ürünlerinizi sisteme yüklemeden önce aşağıdaki yapıların hazır olduğundan emin olun. Eğer bu adımlardan herhangi biri henüz tamamlanmadıysa, ilgili dokümana giderek işlemi tamamlayabilirsiniz.
{% endhint %}

* [x] **1.Ürün veri şeması oluşturulmuş olmalıdır.**

> Veri şeması oluşturma adımlarını öğrenmek için → [Veri Şeması Nasıl Oluşturulur?](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/veri-semasi-nasil-olusturulur)

* [x] **2.Ürün özellikleri ve seçenekleri tanımlanmış olmalıdır.**

> Özellik ve seçenek tanımlama adımlarını öğrenmek için → [Özellik ve Seçenek nasıl tanımlanır?](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/ozellik-ve-secenek-nasil-tanimlanir)

* [x] **3.Tanımlanan özellik ve seçenekler veri şemasına eklenmiş olmalıdır.**

> Veri şeması alanlarını yapılandırma hakkında daha fazla bilgi için → [Özellikler ve seçenekler veri şemasına nasıl eklenir?](/products/lidia-pim/quick-start-guide/ozellik-ve-secenek-nasil-tanimlanir#ozellikler-ve-secenekler-veri-semasina-nasil-eklenir)

* [x] **4.Ürün kategorisi oluşturulmuş ve veri şeması kategoriye bağlanmış olmalıdır.**

> Kategori ve veri şeması ilişkisi hakkında detaylar için → [Kategori Nasıl Oluşturulur?](/products/lidia-pim/quick-start-guide/havuz-nedir-nasil-yonetilir#kategori-nasil-olusturulur)

* [x] **5.İlgili kategoriye bağlı bir havuz oluşturulmuş olmalıdır.**

> Havuz oluşturma adımlarını görmek için → [Havuzları Anlayın ve Yönetin](/products/lidia-pim/quick-start-guide/havuz-nedir-nasil-yonetilir#havuzlari-anlayin-ve-yonetin)

\
Tüm bu adımlar tamamlandıysa artık ürünlerinizi Excel kullanarak sisteme yüklemeye hazırsınız.

#### :arrow\_forward:<mark style="color:$info;">Excel Şablonu Nasıl İndirilir?</mark>

Lidia PIM’de ürünlerinizi Excel dosyası kullanarak sisteme ekleyebilirsiniz. Bu yöntem sayesinde ister tek bir ürün girebilir, ister çok sayıda ürünü aynı anda toplu olarak yükleyebilirsiniz. Ürün bilgileri, havuzun bağlı olduğu veri şemasına göre oluşturulan Excel şablonu üzerinden sisteme aktarılır.

{% stepper %}
{% step %}
**Katalog > Havuzlar sayfasına gidin.**
{% endstep %}

{% step %}
**Ürün yüklemek istediğiniz havuzu bulun ve&#x20;**<mark style="background-color:purple;">**Ürünleri Yönet**</mark>**&#x20;butonuna tıklayarak havuz detay sayfasını açın.**&#x20;

> **Not:** Daha önce ürün yüklenmemiş bir havuzda, detay sayfasında boş bir liste görünümü ile karşılaşırsınız. Eğer havuza daha önce ürün yüklenmişse, bu ürünler havuz detay sayfasında liste halinde görüntülenir.&#x20;
> {% endstep %}

{% step %}
**Ekranda yer alan&#x20;**<mark style="background-color:purple;">**İçeri Veri Aktar**</mark>**&#x20;butonuna tıklayın.**&#x20;
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**Taslak Şemayı İndir**</mark>**&#x20;seçeneğini görecekiniz.**

<div align="left" data-with-frame="true"><figure><img src="/files/aVmzzxEwYc3pCUbJwDDU" alt="" width="375"><figcaption></figcaption></figure></div>

Bu seçeneğe tıklayarak Excel şablonunu indirebilirsiniz.

> Her havuz için oluşturulan Excel şablonu kendine özeldir. Şablon, havuzu oluştururken seçtiğiniz veri şeması ve bu veri şemasına eklediğiniz alanlara göre otomatik olarak oluşturulur. Bu nedenle farklı havuzlar için indirilen Excel şablonları farklı alan kombinasyonları içerebilir.
> {% endstep %}
> {% endstepper %}

#### :arrow\_forward:<mark style="color:$info;">Excel Dosyası Nasıl Doldurulur?</mark>

İndirdiğiniz Excel dosyası, ürün bilgilerini sisteme yüklemek için doldurmanız gereken alanları içerir. Dosya içinde her alanın ne anlama geldiğini ve hangi alanların zorunlu olduğunu görebilirsiniz.&#x20;

İndirdiğiniz Excel dosyası iki sayfadan oluşur:

1. **Şablon Bilgileri**
2. **Ürünler**

Her iki sayfa da ürün yükleme sürecinde farklı bir amaçla kullanılır.

***

:star:**Şablon Bilgileri Sayfası**

Excel dosyasındaki ilk sayfa Şablon Bilgileri sayfasıdır. Bu sayfa, Excel dosyasında dolduracağınız tüm alanlar hakkında bilgi içerir.

Bu sayfada:

* Alan adları
* Alan açıklamaları
* Alanların zorunlu veya opsiyonel olup olmadığı

gösterilir.

Sistem tarafından otomatik oluşturulan alanlarda alan açıklamaları hazır olarak gelir. Eğer veri şeması oluştururken kendi alanlarınız için açıklama eklediyseniz (örneğin özellik, seçenek, marka veya kategori alanları), bu açıklamalar da Excel dosyasında görüntülenir.

<div align="center" data-with-frame="true"><figure><img src="/files/m2ZVa9evx72cJsqE4f1b" alt="" width="375"><figcaption></figcaption></figure></div>

> Televizyon örneği üzerinden ilerlediğimiz bu senaryoda **Marka** ve **Kategori** alanları için veri şeması oluşturulurken açıklama bilgisi eklenmiştir. Bu nedenle Excel dosyasında bu alanların **Alan Açıklaması** sütununun dolu olduğu görülür. Örneğe göz atmak için: [<mark style="color:$info;">Örnek Senaryo: Televizyon Ürünü için Veri Şeması Oluşturma</mark>](/products/lidia-pim/quick-start-guide/veri-semasi-nasil-olusturulur#ornek-senaryo-televizyon-urunu-icin-veri-semasi-olusturma)
>
> Bu alanlar haricinde açıklaması dolu olan diğer alanlar ise **sistem tarafından otomatik olarak oluşturulan ve açıklaması sistem tarafından eklenen alanlardır**.

{% hint style="danger" %}
Zorunlu alanlar **kırmızı renkle işaretlenir**.

Bu alanlar boş bırakılırsa ürün yükleme işlemi sırasında hata oluşur.
{% endhint %}

<i class="fa-arrow-turn-down-right" style="color:yellow;">:arrow-turn-down-right:</i> **Sistem Tarafından Eklenen Alanlar**

Excel dosyasında bazı alanlar <mark style="background-color:purple;">sistem tarafından otomatik</mark> olarak oluşturulur. Bu alanlar her havuz için standart olarak bulunur ve ürün yönetimi sürecinin doğru şekilde ilerlemesi için kullanılır.

<table><thead><tr><th valign="top">Zorunlu</th><th valign="top">Opsiyonel</th><th valign="top">Salt Okunur</th></tr></thead><tbody><tr><td valign="top"><p>Bu alanlardan aşağıdakiler <strong>zorunlu alanlardır</strong> ve ürün yükleme sırasında doldurulmaları gerekir:</p><p></p><ul><li><mark style="color:purple;">Ürün Adı</mark></li><li><mark style="color:purple;">Ürün Tekil Kodu</mark></li><li><mark style="color:purple;">Satıcı Eşya Kodu</mark></li><li><mark style="color:purple;">Grup Kodu</mark></li><li><mark style="color:purple;">Resim Kodu</mark></li><li><mark style="color:purple;">Ürün Durumu</mark></li><li><mark style="color:purple;">Havuz Durumu</mark></li></ul></td><td valign="top"><p>Bu alanlardan aşağıdakiler  <strong>opsiyoneldir</strong> ve ürünleri etiketlemek veya sınıflandırmak için kullanılabilir.</p><p></p><ul><li><mark style="color:purple;">Etiketler</mark></li><li><mark style="color:purple;">Rozetler</mark></li><li><mark style="color:purple;">Yönetsel Etiketler</mark></li><li><mark style="color:purple;">Diğer Etiketler</mark></li></ul></td><td valign="top"><p>Bu alanlardan aşağıdakiler  <strong>salt okunur</strong> yapıdadır ve kullanıcı tarafından düzenlenemez.</p><p></p><p></p><ul><li><mark style="color:purple;">Güncellenme Tarihi</mark></li><li><mark style="color:purple;">Oluşturulma Tarihi</mark></li></ul></td></tr></tbody></table>

***

:star:**Ürünler Sayfası**

Excel dosyasındaki ikinci sayfa Ürünler sayfasıdır. <mark style="background-color:purple;">Ürün bilgilerini gireceğiniz asıl sayfa</mark> burasıdır. Şablon Bilgileri sayfasında açıklamalarını gördüğünüz alanları, bu sayfada <mark style="background-color:purple;">ürün bazında</mark> doldurursunuz.

Ürünler sayfasında yer alan alanlar, ürün bilgilerini daha düzenli şekilde girebilmeniz için farklı başlıklar altında gruplanmıştır. Aşağıda bu başlıkların her birinin ne anlama geldiğini ve ürün girişinde nasıl kullanıldığını inceleyebilirsiniz.

* **Temel Bilgiler Alanları**

Temel Bilgiler alanı, ürünün sistemde tanımlanabilmesi için gerekli olan ana alanları içerir. Bu alanlar her havuz için sistem tarafından oluşturulur ve ürün kaydının oluşturulabilmesi için doldurulmaları gerekir.

Bu bölümde ***Ürün Adı, Ürün Tekil Kodu, Lidia Kodu, Satıcı Eşya Kodu, Grup Kodu ve Resim Kodu*** alanları yer alır.

Ürün Adı, Ürün Tekil Kodu, Satıcı Eşya Kodu, Grup Kodu ve Resim Kodu alanlarının doldurulması gerekir. <mark style="color:$info;background-color:purple;">**Lidia Kodu**</mark> ise Lidia PIM sistemi tarafından otomatik olarak oluşturulduğu için kullanıcı tarafından doldurulmaz ve boş bırakılması gerekir.

* **Kategori ve Marka Alanları**

Kategori ve marka alanları, ürünün hangi kategori altında yer aldığını ve hangi markaya ait olduğunu belirlemek için kullanılır. <mark style="background-color:purple;">**Bu alanlar Excel dosyasında yalnızca veri şemasını oluştururken ilgili alanları veri şemasına eklediyseniz görünür.**</mark>

Bu alanların zorunlu olup olmaması veri şemasına eklerken zorunlu seçeneğini aktif edip etmemenize bağlıdır. Eğer bu alanlar veri şemasında zorunlu olarak tanımlandıysa, Excel dosyasında da doldurulmaları gerekir. Boş bırakılması durumunda ürün yükleme sırasında sistem hata verecektir.

* [x] Kategori ve marka alanlarında veri girmek için hücreye tıkladığınızda, sistemde tanımlı olan değerler arasından seçim yapabileceğiniz bir **seçim listesi** görüntülenir. Bu sayede ürün bilgileri sistemde tanımlı kategori ve marka değerleri ile uyumlu şekilde girilir.

> Televizyon örneğinde veri şemasını oluştururken **Kategori** ve **Marka** alanlarını da veri şemasına eklemiştik. Bu nedenle televizyon havuzu için Excel şablonunu indirdiğinizde, kategori ve marka alanlarının Excel dosyasında otomatik olarak oluşturulduğunu görebilirsiniz. Bu alanlarda hücreye tıkladığınızda, sistemde tanımlı kategori ve marka değerleri arasından seçim yapabilirsiniz.

* **Özellik ve Seçenek Alanları**

Veri şemasına eklediğiniz özellikler ve seçenekler, Excel dosyasında otomatik olarak sütunlar halinde oluşturulur. Bu alanlar ürünün teknik özelliklerini ve varyant bilgilerini temsil eder.

Bu alanların zorunlu olup olmaması, veri şemasına eklerken zorunlu seçeneğini aktif edip etmemenize bağlıdır. Zorunlu olarak tanımlanan alanların Excel dosyasında boş bırakılması ürün yükleme sırasında hata oluşmasına neden olur.

Özellik ve seçenek alanlarında da hücreye tıkladığınızda daha önce sistemde tanımlanan değerleri seçebileceğiniz bir **seçim listesi** görüntülenir.

> Televizyon örneğinde daha önce **Enerji Sınıfı, Garanti Süresi ve Model Yılı** gibi alanları özellik olarak; **Ekran Boyutu, Çözünürlük ve Panel Teknolojisi** gibi alanları ise seçenek olarak tanımlamıştık. Bu nedenle televizyon havuzu için Excel şablonunu indirdiğinizde, veri şemasına eklediğiniz bu özellik ve seçenek alanlarının Excel dosyasında otomatik olarak oluşturulduğunu görebilirsiniz.

* **Diğer Bilgiler Alanı**

Excel dosyasında ayrıca Diğer Bilgiler başlığı altında sistem tarafından otomatik olarak oluşturulan bazı alanlar yer alır. Bu bölümde ***Etiketler, Rozetler, Yönetsel Etiketler ve Diğer Etiketler*** gibi alanlar bulunur. Bu alanların doldurulması zorunlu değildir ve ürünleri etiketlemek veya sınıflandırmak için kullanılabilir.

Aynı bölümde yer alan <mark style="background-color:purple;">**Ürün Durumu**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">ve</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Havuz Durumu**</mark> alanları ise ürünün sistemde nasıl kaydedileceğini belirleyen önemli alanlardır.

* [x] Ürün Durumu alanı ürünün aktif veya pasif olup olmadığını belirler. Bu alanda **1 değeri ürünün aktif**, **0 değeri ise ürünün pasif** olduğunu ifade eder.
* [x] Havuz Durumu alanı ise ürünün havuz içindeki durumunu belirler. Bu alanda **1 değeri aktif havuzu**, **0 değeri pasif havuzu**, **-99 değeri ise ürünün sistemden silinmesini** ifade eder.

<table><thead><tr><th width="158.5185546875">Ürün Durumu</th><th width="153.40740966796875">Havuz Durumu</th><th>Sonuç</th></tr></thead><tbody><tr><td>1</td><td>1</td><td>Ürün havuzda aktif ve yayınlanmaya hazır</td></tr><tr><td>1</td><td>0</td><td>Havuz pasif olduğu için ürün yüklenemez</td></tr><tr><td>0</td><td>1</td><td>Ürün pasif olarak havuza eklenir, yayınlanamaz</td></tr><tr><td>0</td><td>0</td><td>Havuz pasif olduğu için ürün yüklenemez</td></tr><tr><td>-</td><td>-99</td><td>Ürün sistemden silinir</td></tr></tbody></table>

#### :arrow\_forward:<mark style="color:$info;">Ürün Yükleme İşlemi Nasıl Yapılır?</mark>

Ürün ekleme süreci iki temel aşamadan oluşur. İlk aşamada ürün bilgileri Excel dosyası kullanılarak <mark style="background-color:purple;">havuza yüklenir</mark>. İkinci aşamada ise havuza eklenen bu ürünler <mark style="background-color:purple;">kontrol edilerek yayınlanır</mark>. Aşağıdaki adımlarda ürünleri havuza yükledikten sonra nasıl yayınlayacağınızı inceleyebilirsiniz.

#### <i class="fa-file-arrow-up">:file-arrow-up:</i> <mark style="color:$primary;">**Havuza ürün yükleme adımları**</mark>

{% stepper %}
{% step %} <mark style="background-color:purple;">**Katalog > Havuzlar**</mark>**&#x20;sayfasına gidin.**
{% endstep %}

{% step %}
**Ürün yüklemek istediğiniz havuzu bulun ve&#x20;**<mark style="background-color:purple;">**Ürünleri Yönet**</mark>**&#x20;butonuna tıklayarak havuz detay sayfasını açın.**

<a href="https://pim.lidiacommerce.com/metadata/data-pools" class="button primary">Ürünleri Yönet</a>
{% endstep %}

{% step %}
**Sayfanın üst bölümünde yer alan "**<mark style="background-color:purple;">**Veriyi İçe Aktar"**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**"Dosyayı yüklemek için tıklayın"**</mark>**&#x20;alanına tıklayın ve hazırladığınız dolu Excel dosyasını seçin.**

Bu alana yalnızca Excel formatında (.xlsx) dosya yükleyebilirsiniz.

Excel dosyasını yükleme işlemi üç adımda ilerler: *<mark style="color:purple;background-color:purple;">Yeni Excel Dokümanı Yükle → Veriyi Kontrol Et → Tamamlandı.</mark>*

<div align="left" data-with-frame="true"><figure><img src="/files/3N4LL4wcCVnuVi3n3ZKr" alt="" width="210"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Excel dosyası yüklendikten sonra&#x20;**<mark style="background-color:purple;">**Yeni Excel Dokümanı Yükle**</mark>**&#x20;adımı tamamlanır,&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın ve bir sonraki adıma geçin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Veriyi Kontrol Et**</mark>**&#x20;adımında sistem kontrolünden geçilir, ardından&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın ve içe aktarımı onaylama adımına geçin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**"İçe aktarımı onaylıyorum"**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/o02pc5JY6jXWabOUdZWg" alt="" width="155"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
:tada:**Havuza ürün aktarımı tamamlandı**
{% endstep %}
{% endstepper %}

***

Excel yükleme işlemi tamamlandığında ürünler havuza eklenir ve yayınlanmayı bekler. Bu ürünleri <mark style="background-color:purple;">havuz detay sayfasında Tümü sekmesi</mark> altında görebilirsiniz. Ürünleri canlıya almak için aşağıdaki adımları izleyin.

#### <i class="fa-arrow-down-to-square">:arrow-down-to-square:</i> <mark style="color:$primary;">**Havuzdaki Ürünleri Yayınlama Adımları**</mark>

{% stepper %}
{% step %}
**Havuz detay sayfasında&#x20;**<mark style="background-color:purple;">**Tümü**</mark>**&#x20;sekmesine gidin, Yayınlamak istediğiniz ürünleri veya tüm ürünleri seçin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Ürünleri Yayınla**</mark>**&#x20;butonuna tıklayın.**

Açılan pencerede aşağıdaki seçeneklerden birini seçin:

* **Yalnızca seçilen ürünleri yayınla**
* **Tüm ürün havuzunu yayınla**
  {% endstep %}

{% step %} <mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/u5dtuPRFZf8iSXuri4QL" alt="" width="234"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Açılan doğrulama penceresinde&#x20;**<mark style="background-color:purple;">**Tüm Ürünler Yayınlanabilir kontrolü**</mark>**&#x20;yapılır.**\
**Kontrol tamamlandıktan sonra&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/6l3OPCXlpH7wPFCEgQKp" alt="" width="234"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Yayınlamadan önce ürünleri inceleyerek kontrol edin.**

Bu ekranda ürünler **Yeni Ürünler**, **Güncellenen Ürünler**, **Yeni Varyantlar** ve **Güncellenen Varyantlar** başlıkları altında listelenir.

> <mark style="background-color:purple;">İlk kez yüklenen ürünler</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Yeni Ürünler**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">ve</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Yeni Varyantlar**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">altında görünür.</mark> Mevcut ürünlerde yapılan değişiklikler ise Güncellenen Ürünler ve Güncellenen Varyantlar başlıklarında gösterilir. Değiştirilen alanlar sarı renkle işaretlenir.
> {% endstep %}

{% step %} <mark style="background-color:purple;">**Onayla ve Yayına Al**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**Yayınla**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/Zrdk83tqeqQiePFTjM0U" alt="" width="236"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
:tada:**İlk ürününüzü PIM’e yüklediniz ve yayınladınız.**
{% endstep %}
{% endstepper %}

#### :arrow\_forward:<mark style="color:$info;">Olası Hatalar ve Çözüm Yolları</mark>

Ürün yükleme ve yayınlama süreçlerinde sistem bazı doğrulamalar yapar. Bu doğrulamalar, ürün verilerinin eksik veya hatalı şekilde sisteme eklenmesini engellemek için uygulanır.

* **Excel Yükleme Aşamasında Karşılaşılabilecek Hatalar**

Excel dosyası yüklenirken sistem *<mark style="color:$info;">Veriyi Kontrol Et</mark>* adımında dosyadaki verileri kontrol eder. Eğer Excel dosyasında hata bulunursa işlem tamamlanmaz ve uyarılar görüntülenir.

<div align="center" data-with-frame="true"><figure><img src="/files/TvnVLotuUcOSuYaMEbKI" alt="Aktarım Tamamlanamadı Uyarısı" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
**İçe aktarım tamamlanamadı!**\
Excel ile içeri veri aktarımı tamamlanamadı. Lütfen Excel dökümanını kontrol ederek tekrar deneyiniz.
{% endhint %}

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Lidia kodu alanının doldurulması**\
Lidia Kodu alanı sistem tarafından otomatik oluşturulur. Bu alanın kullanıcı tarafından doldurulması yükleme işlemi sırasında hataya neden olur.\
**Çözüm:** Excel dosyasındaki *<mark style="color:$info;">Lidia Kodu</mark>* alanını boş bırakın.

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Zorunlu alanların doldurulmaması**\
Veri şemasında zorunlu olarak tanımlanan alanların boş bırakılması ürün yükleme sırasında hataya neden olur.\
**Çözüm:** Excel dosyasında *<mark style="color:$info;">kırmızı ile işaretlenmiş zorunlu alanların tamamını</mark>* doldurun.

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Ürün görselinin eksik olması**\
Ürün görselleri tanımlanmadan ürünler yayınlama aşamasına geçemez.\
**Çözüm:** Ürüne ait görselleri sisteme yükleyin ve ilgili *<mark style="color:$info;">resim kodu</mark>* ile ürün kaydıyla eşleştirin.&#x20;

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Excel dışında bir dosya formatı yüklenmesi**\
Ürün yükleme işlemi yalnızca **.xlsx formatındaki Excel dosyaları** ile yapılabilir.\
**Çözüm:** Dosyanın *<mark style="color:$info;">Excel formatında (.xlsx)</mark>* olduğundan emin olun.

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Boş Excel dosyası yüklenmesi**\
Excel dosyasındaki ürün satırlarının doldurulmadan yüklenmesi işlemin başarısız olmasına neden olur.\
**Çözüm:** Doldurulmamış, *<mark style="color:$info;">boş Excel dosyası yüklemediğinizden</mark>* emin olun.

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Ürün durumunun aktif olmaması**\
Excel dolduruken ürün durumu Aktif (1) olarak ayarlanmadığında ürünler havuza yüklenir ancak yayınlanamaz.\
**Çözüm:** Excel dosyasında *<mark style="color:$info;">Ürün Durumu alanını 1 (Aktif)</mark>* olarak güncelleyin ve ürünleri tekrar yayınlamayı deneyin.

<i class="fa-circle-exclamation" style="color:$danger;">:circle-exclamation:</i> **Havuz durumunun aktif olmaması**\
Havuz Durumu Aktif (1) olarak ayarlanmadığında ürünler havuza yüklenemez.\
**Çözüm:** Excel dosyasında *<mark style="color:$info;">Havuz Durumu alanını 1 (Aktif)</mark>* olarak güncelleyin ve dosyayı tekrar yükleyin.

* **Ürün Yayınlama Aşamasında Karşılaşılabilecek Durumlar**

Ürünler havuza yüklendikten sonra yayınlama işlemi sırasında sistem ek doğrulamalar gerçekleştirir. Bu doğrulamalar sonucunda yayınlama işlemi tam başarılı, kısmi başarılı veya başarısız olabilir.\
Doğrulama sonucuna göre sistem üç farklı senaryo gösterebilir: tüm ürünlerin yayınlanabildiği durum, kısmi yayınlama durumu veya hiçbir ürünün yayınlanamadığı durum.

**1.Kısmi Yayınlama**

{% columns %}
{% column width="50%" %}
Bazı ürünler yayınlama gereksinimlerini karşılamıyorsa sistem Kısmi Yayınlama uyarısı gösterir. Bu ekranda:

* Yayınlanabilecek ürün sayısı
* Yayınlanamayacak ürün sayısı

ayrı ayrı gösterilir.

Yayınlanamayan ürünler için nedenler de listelenir. Örneğin:

* Ürün durumu aktif değildir
* Zorunlu içerik alanları eksiktir
* Zorunlu özellikler tanımlanmamıştır
  {% endcolumn %}

{% column width="50%" %}

<div align="left" data-with-frame="true"><figure><img src="/files/fEwYV8DggVvQCEjzPmbQ" alt="" width="233"><figcaption></figcaption></figure></div>

&#x20;                 **Kısmi Yayınlama**
{% endcolumn %}
{% endcolumns %}

**2.Hiçbir Ürün Yayınlanamaz**

{% columns %}
{% column %}
Eğer seçilen ürünlerin hiçbiri yayınlama gereksinimlerini karşılamıyorsa yayınlama işlemi engellenir.

Bu durumda sistem doğrulama sonuçlarını gösterir ve aşağıdaki aksiyonları önerir:

* Eksik ürün bilgilerini tamamlayın
* Ürün durumunu Aktif olarak güncelleyin
* Gerekli alanları doldurduktan sonra yayınlama işlemini tekrar deneyin

İlgili ürünleri incelemek için Ürünleri İncele seçeneğini kullanabilirsiniz.
{% endcolumn %}

{% column %}

<div align="left" data-with-frame="true"><figure><img src="/files/dBhZSbCwz81YcDrbz4Ux" alt="" width="235"><figcaption></figcaption></figure></div>

&#x20;     **Hiçbir Ürün Yayınlanamaz**
{% endcolumn %}
{% endcolumns %}

#### :arrow\_forward:<mark style="color:$info;">Import sonrası kontrol adımları</mark>

Ürün yükleme işlemi tamamlandıktan sonra ürünlerin havuza doğru şekilde eklendiğini ve başarıyla yayınlandığını kontrol etmeniz önerilir. Bu kontrol, ürünlerin sistemde doğru şekilde oluşturulduğunu doğrulamanıza yardımcı olur.

Yayınlama tamamlandıktan sonra ürünler havuz detay sayfasındaki hen *<mark style="color:$info;">Tümü</mark>* hem *<mark style="color:$info;">Yayındakiler</mark>* sekmesi altında listelenir. Excel dosyasında yer alan alan başlıkları, bu listeleme sayfasında da aynı şekilde görüntülenir.

* [x] Yayınlanan ürünler ayrıca PIM sol menüsünde yer alan **Katalog > Ürünler** ve **Katalog > Varyantlar** sayfalarında listelenmeye başlar. Buradan ürünlerinizi görüntüleyebilir ve yönetebilirsiniz.

#### :arrow\_forward: <mark style="color:$info;">Örnek Senaryo: Televizyon Ürünü Yayınlama</mark>

Önceki adımlarda televizyon ürünleri için bir [veri şeması oluşturduk,](/products/lidia-pim/quick-start-guide/veri-semasi-nasil-olusturulur#ornek-senaryo-televizyon-urunu-icin-veri-semasi-olusturma) gerekli [özellik ve seçenekleri tanımladık,](/products/lidia-pim/quick-start-guide/ozellik-ve-secenek-nasil-tanimlanir#ornek-kullanim-senaryosu-televizyon) bu alanları veri şemasına ekledik ve **televizyon kategorisine bağlı bir havuz oluşturduk**.

Şimdi bu veri modelini kullanarak televizyon ürünlerini **Excel ile havuza yükleyip yayınlama sürecini** inceleyelim.

{% stepper %}
{% step %}
**Katalog > Havuzlar sayfasına gidin.**

<div align="left" data-with-frame="true"><figure><img src="/files/yAkoAzS54pdg0pcKBg2T" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Televizyon havuzunu bulun ve&#x20;**<mark style="background-color:purple;">**Ürünleri Yönet**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Havuz detay sayfasında&#x20;**<mark style="background-color:purple;">**Veriyi İçe Aktar**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**Taslak Excel Şeması**</mark>**&#x20;seçeneğini tıklayarak Excel dosyasını indirin.**
{% endstep %}

{% step %}
**Excel dosyasını doldurun.**

<div align="left" data-with-frame="true"><figure><img src="/files/UYdt4YJyxdScOv7mM5wp" alt="" width="375"><figcaption></figcaption></figure></div>

<div align="left" data-with-frame="true"><figure><img src="/files/AkeMagIYS9CAP2yLvUYm" alt="" width="375"><figcaption></figcaption></figure></div>

> Excel dosyasındaki alanları televizyon ürününe ait bilgilerle doldurun. Özellik ve seçenek alanlarında, daha önce tanımladığınız değerler <mark style="background-color:purple;">seçim listesi (dropdown)</mark> olarak görünür ve yalnızca bu değerler seçilebilir.
> {% endstep %}

{% step %}
**Excel dosyasını havuza yükleyin.**

Hazırladığınız Excel dosyasını kaydedin. Ardından tekrar havuz detay sayfasında <mark style="background-color:purple;">Veriyi İçe Aktar</mark> butonuna tıklayın ve bu kez hazırladığınız dolu Excel dosyasını seçin.

<div align="left" data-with-frame="true"><figure><img src="/files/1XI0dDMIxhsunKZxBrMv" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Veriyi kontrol edin.**

Dosya yüklendikten sonra sistem verileri kontrol eder. Eğer dosyada hata yoksa ürünler listelenir ve işlem tamamlanmaya hazır hale gelir.

<div align="left" data-with-frame="true"><figure><img src="/files/UO6blisCP6JLdcMC2bar" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Kontrol adımı tamamlandıktan sonra&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan modalda** <mark style="background-color:purple;">**"İçe aktarımı onaylıyorum"**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/XE1YvkJmLDEjtewtCqzO" alt="" width="155"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Havuza ürün aktarımı tamamlandınız.**

<div align="left" data-with-frame="true"><figure><img src="/files/8MNY1bNQFRKiqWFQpLPL" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Havuz detay sayfasında&#x20;**<mark style="background-color:purple;">**Tümü sekmesinde**</mark>**&#x20;yayınlamak istediğiniz ürünleri veya tüm&#x20;**<mark style="background-color:purple;">**ürünleri seçin.**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/DihJgxup56zCVe4Smafr" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %} <mark style="background-color:purple;">**Ürünleri Yayınla**</mark>**&#x20;butonuna tıklayın.**

Açılan pencerede aşağıdaki seçeneklerden birini seçin:

* **Yalnızca seçilen ürünleri yayınla**
* **Tüm ürün havuzunu yayınla**

<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/TaS1pFQdp8SRE46BNvu8" alt="" width="234"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Açılan doğrulama penceresinde&#x20;**<mark style="background-color:purple;">**Tüm Ürünler Yayınlanabilir kontrolü**</mark>**&#x20;yapılır.**\
**Kontrol tamamlandıktan sonra&#x20;**<mark style="background-color:purple;">**Devam Et**</mark>**&#x20;butonuna tıklayın.**

<div align="left" data-with-frame="true"><figure><img src="/files/zP0VL3VQ0yr528YfMLWE" alt="" width="233"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Yayınlamadan önce ürünleri inceleyerek kontrol edin.**

<div align="left" data-with-frame="true"><figure><img src="/files/X9Ee0uYH9LZgFfZhTO1h" alt="" width="375"><figcaption></figcaption></figure></div>

> <mark style="background-color:purple;">İlk kez yüklenen ürünler</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Yeni Ürünler**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">ve</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**Yeni Varyantlar**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">altında görünür.</mark> Mevcut ürünlerde yapılan değişiklikler ise Güncellenen Ürünler ve Güncellenen Varyantlar başlıklarında gösterilir. Değiştirilen alanlar sarı renkle işaretlenir.

<mark style="background-color:purple;">**Onayla ve Yayına Al**</mark>**&#x20;butonuna tıklayın.**
{% endstep %}

{% step %}
**Açılan pencerede&#x20;**<mark style="background-color:purple;">**Yayınla**</mark>**&#x20;butonuna tıklayın**<mark style="background-color:purple;">**.**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/FppAptf347GANA6qp2tL" alt="" width="237"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
:tada:**Tebrikler, ilk ürününüzü PIM’e yüklediniz ve yayınladınız.**
{% endstep %}
{% endstepper %}


# Kullanıcı ve Rol nasıl tanımlanır?

Bu sayfada Lidia PIM’de kullanıcı ve rol tanımlama sürecini, kullanıcı ekleme adımlarını ve rol atamaları ile erişim yetkilerinin nasıl yönetildiğini öğreneceksiniz.

### :rocket:<mark style="color:$primary;background-color:purple;">Kullanıcı ve Rol Yetkilerini Yönetin</mark>

Lidia PIM’de kullanıcı yetkileri roller aracılığıyla yönetilir. Sistem içerisinde varsayılan olarak gelen roller bulunur ve ihtiyaçlarınıza göre yeni roller tanımlanabilir. Roller için erişilebilecek alanlar ile görüntüleme ve düzenleme yetkileri konfigüre edilebilir. Yeni kullanıcı oluştururken kullanıcıya bir rol atanarak sistemdeki erişim yetkileri belirlenir.

#### :arrow\_forward:<mark style="color:$info;">Rol nedir, ne işe yarar?</mark>

Rol, bir kullanıcının Lidia PIM içinde hangi ekranlara erişebileceğini ve hangi işlemleri yapabileceğini belirleyen yetki tanımıdır.

Kısaca, rol yapısı şu soruların cevabını verir:

* Kullanıcı hangi modülleri görebilir?
* Hangi sayfalara erişebilir?
* Hangi işlemleri yapabilir?
* Hangi işlemleri yapamaz?

{% hint style="info" %}
**Tüm kullanıcıların aynı yetkiye sahip olması gerekmez**

Ürün verisini yöneten bir kullanıcı ile yalnızca içerik kontrolü yapan bir kullanıcının erişim ihtiyacı farklı olabilir. Bu nedenle kullanıcılar, görevlerine uygun roller ile sisteme tanımlanır.
{% endhint %}

Lidia PIM içerisinde sistem tarafından tanımlı bazı <mark style="background-color:purple;">varsayılan roller</mark> bulunur. Bu roller, kullanıcıların sistemde hangi alanlara erişebileceğini ve bu alanlarda hangi yetkilere sahip olacağını belirler. Yetkiler temel olarak <mark style="background-color:purple;">**görüntüleme**</mark> ve <mark style="background-color:purple;">**düzenleme**</mark> olmak üzere iki seviyede tanımlanır.

* **Sistem tarafından tanımlı roller:**

<table><thead><tr><th width="244.44439697265625">Rol Adı</th><th width="436.266845703125">Rol Açıklaması</th></tr></thead><tbody><tr><td><mark style="color:purple;"><strong>Guest</strong></mark></td><td>Sisteme sınırlı erişimi olan kullanıcı rolüdür. Genellikle yalnızca belirli alanları görüntüleme yetkisine sahiptir ve düzenleme yetkisi bulunmaz.</td></tr><tr><td><mark style="color:purple;"><strong>OrganizationUser</strong></mark></td><td>Organizasyon içinde temel kullanıcı rolüdür. Yetkili olduğu modüllerde verileri görüntüleyebilir ve görev kapsamına göre sınırlı düzenleme işlemleri yapabilir.</td></tr><tr><td><mark style="color:purple;"><strong>OrganizationAdmin</strong></mark></td><td>Organizasyon seviyesinde yönetim yetkilerine sahip roldür. Kullanıcıları, rolleri ve organizasyon içindeki erişimleri yönetebilir.</td></tr><tr><td><mark style="color:purple;"><strong>OrganizationOwner</strong></mark></td><td>Organizasyonun en yüksek yetkili rolüdür. Organizasyon ayarlarını yönetebilir, kullanıcı ve rol yetkilerini düzenleyebilir ve tüm modüllere tam erişime sahiptir.</td></tr><tr><td><mark style="color:purple;"><strong>CustomerSuccess</strong></mark></td><td>Platform sağlayıcı ekipleri için kullanılan destek rolüdür. Müşteri organizasyonlarını inceleyebilir, sorun çözme ve destek süreçlerinde gerekli erişimlere sahiptir.</td></tr><tr><td><mark style="color:purple;"><strong>ApplicationAdmin</strong></mark></td><td>Uygulama veya platform seviyesinde yönetim yetkisine sahip roldür. Sistem konfigürasyonları, uygulama ayarları ve platform genelindeki yönetim işlemlerini gerçekleştirebilir.</td></tr></tbody></table>

* [x] Rol bazında hangi modüllerin görüntülenebileceği ve hangi alanların düzenlenebileceği ayrı ayrı belirlenebilir. Gerekli durumlarda, daha yüksek yetkilere sahip kullanıcılar bu rol yetkilerini konfigüre ederek erişim kapsamını güncelleyebilir.

#### :arrow\_forward:<mark style="color:$info;">Rol bazlı yetkiler nelerdir?</mark>

Yetkiler, Sistem altında hiyerarşik olarak yapılandırılır. Her kırılım için <mark style="color:purple;">Görüntüle</mark> ve <mark style="color:purple;">Düzenle</mark> yetkileri ayrı ayrı tanımlanabilir. Aşağıdaki yer alan alanlar için görüntülüme yada düzenleme yetkisi rol bazında konfigüre edilebilir.&#x20;

**System** → Tüm yetki yapısının en üst kırılımıdır.\
│\
├─**Settings** → Sistem ayarlarının yönetildiği ana alandır.\
│    ├─ **Authorization** → Kullanıcı ve rol yetkilerinin yönetildiği alandır.\
│    │     ├─ <mark style="color:$info;">**Authorized Users**</mark> → Sistem kullanıcılarının yönetildiği alandır.\
│    │     └─ <mark style="color:$info;">**Roles**</mark> → Roller ve rol yetkilerinin tanımlandığı alandır.\
│    ├─ **Contacts** → İletişim kayıtlarının yönetildiği alandır.\
│    ├─ **Catalog** → Ürün veri yapısına ait tanımların yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Data Schemas**</mark> → Veri şemalarının oluşturulduğu ve yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Collections**</mark> → Koleksiyonların yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Data Locks**</mark> → Veri kilitleme işlemlerinin yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Product Relations**</mark> → Ürün ilişkilerinin tanımlandığı alandır.\
│    │      ├─ <mark style="color:$info;">**Category Dimensions**</mark> → Kategori kırılımlarının yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Channels**</mark> → Kanal yapılarının tanımlandığı alandır.\
│    │      ├─ <mark style="color:$info;">**MetaData Tags**</mark> → Metadata etiketlerinin yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Properties**</mark> → Özelliklerin tanımlandığı ve yönetildiği alandır.\
│    │      └─ <mark style="color:$info;">**Options**</mark> → Seçenek yapılarının yönetildiği alandır.\
│    │            ├─ Properties → Seçeneklerle ilişkili özelliklerin yönetildiği alandır.\
│    │            ├─ Property Groups → Özellik gruplarının yönetildiği alandır.\
│    │            ├─ Options → Seçeneklerin tanımlandığı alandır.\
│    │            ├─ Option Groups → Seçenek gruplarının yönetildiği alandır.\
│    │            ├─ Option Values → Seçenek değerlerinin tanımlandığı alandır.\
│    │            └─ Option Value Groups → Seçenek değer gruplarının yönetildiği alandır.\
│    ├─  **Localization** → Lokalizasyon ayarlarının yönetildiği alandır.\
│    │      ├─ <mark style="color:$info;">**Languages**</mark> → Sistem dillerinin tanımlandığı alandır.\
│    │      ├─ <mark style="color:$info;">**Currencies**</mark> → Para birimlerinin yönetildiği alandır.\
│    │      └─ <mark style="color:$info;">**Measurement Units**</mark> → Ölçü birimlerinin tanımlandığı alandır.\
│    └─ **Configurations** → Sistem konfigürasyonlarının yönetildiği alandır.\
│\
├─**Notification Center** → Bildirim merkezi yönetim alanıdır.\
│    ├─ **Notifications** → Sistem bildirimlerinin görüntülendiği alandır.\
│    └─ **Settings** → Bildirim ayarlarının yapılandırıldığı alandır.\
│\
├─**My Organization** → Organizasyon ayarlarının yönetildiği alandır.\
│    ├─ **Details** → Organizasyon bilgilerinin görüntülendiği alandır.\
│    ├─ **Subscriptions** → Abonelik bilgilerinin yönetildiği alandır.\
│    └─ **Applications** → Organizasyona bağlı uygulamaların yönetildiği alandır.\
│\
├─**Catalog** → Organizasyon bazlı katalog yönetim alanıdır.\
│    ├─ **Data Pools** → Veri havuzlarının yönetildiği alandır.\
│    ├─ **Categories** → Kategori yapısının yönetildiği alandır.\
│    ├─ **Trademarks** → Marka bilgilerinin yönetildiği alandır.\
│    ├─ **Custom Lists** → Özel listelerin yönetildiği alandır.\
│    ├─ **Products** → Ürünlerin yönetildiği alandır.\
&#x20;     └─ **Variants** → Varyantların yönetildiği alandır.\
│\
├─ **Inventory** → Envanter ve fiyat yapılarının yönetildiği alandır.\
│    └─ **Price Lists** → Fiyat listelerinin yönetildiği alandır.\
│\
├ ─**Media Management** → Medya içeriklerinin yönetildiği alandır.\
│    ├─**Documents** → Dokümanların yönetildiği alandır.\
│    ├─ **Images** → Görsellerin yönetildiği alandır.\
│    ├─ **Files** → Dosyaların yönetildiği alandır.\
│    └─ **Videos** → Videoların yönetildiği alandır.\
│&#x20;\
├─ **Services** → Servis ve entegrasyon alanıdır.\
│     └─ **Feeds** → Veri akışlarının yönetildiği alandır.\
│&#x20;\
└─ **Reports** → Raporlama ve kayıt izleme alanıdır.\
&#x20;      └─  **Audit Logs** → Sistem işlem kayıtlarının görüntülendiği alandır.

#### :arrow\_forward:<mark style="color:$info;">Rol nasıl oluşturulur?</mark>

{% stepper %}
{% step %} <mark style="background-color:purple;">**Ayarlar > Yetkilendirme > Roller**</mark>**&#x20;sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Rol Ekle**</mark> **aksiyonunu seçin.**

Açılan modalda:

* **Rol adı** alanını doldurun *(zorunlu)*
* **Kullanıcılar** alanı isteğe bağlıdır, daha sonra eklenebilir
*

```
<div align="left" data-with-frame="true"><figure><img src="/files/6ZGJmJLCrw42FclLlFe0" alt="" width="234"><figcaption></figcaption></figure></div>
```

{% endstep %}

{% step %}
:tada:**Yeni rol tanımlandı.**

Rol oluşturulduktan sonra detay sayfası üzerinden yönetilebilir.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Önemli**&#x20;

Rol oluşturma ve yetki tanımlama işlemleri, kullanıcının sahip olduğu role bağlıdır. Örneğin, Guest rolüne sahip bir kullanıcı rol oluşturma veya yetki tanımlama işlemlerini gerçekleştiremez.
{% endhint %}

> **Rol detayında neler yapılır?**
>
> Rol oluşturulduktan sonra rol detay sayfası üzerinden yönetim yapılır.
>
> > * *<mark style="color:$info;">Kullanıcılar</mark>* sekmesinde bu role bağlı kullanıcılar görüntülenebilir ve <mark style="background-color:purple;">**Kullanıcılara rol tanımla**</mark> aksiyonu ile yeni kullanıcılar bu role eklenebilir.&#x20;
> > * *<mark style="color:$info;">Yetkiler</mark>* sekmesinde ise rolün sistemde hangi alanlara erişebileceği belirlenir; her modül için görüntüleme ve düzenleme yetkileri ayrı ayrı tanımlanabilir veya kaldırılabilir. Bu sayede rol bazlı erişim kapsamı merkezi ve kontrollü şekilde yönetilir.
>
> &#x20;

#### :arrow\_forward:<mark style="color:$info;">Yeni kullanıcı nasıl oluşturulur?</mark>

{% stepper %}
{% step %} <mark style="background-color:purple;">**Ayarlar > Yetkilendirme > Kullanıcılar**</mark> **sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Kullanıcı Ekle**</mark>**&#x20;butonuna tıklayın.**

Açılan modalda:

* **E-posta**, **Cep Telefonu** ve **Doğum Tarihi** alanlarını doldurun *(zorunludur)*
*

```
<div align="left" data-with-frame="true"><figure><img src="/files/0o1YRUYhRpMwV4qLbWPQ" alt="" width="237"><figcaption></figcaption></figure></div>
```

{% endstep %}

{% step %}
:tada:**Yeni kullanıcı oluşturdunuz.**
{% endstep %}
{% endstepper %}

> **Kullanıcı detayında neler yapılır?**
>
> Kullanıcı oluşturulduktan sonra detay sayfası üzerinden yönetilebilir.
>
> > * *<mark style="color:$info;">Temel Bilgiler</mark>* sekmesinden ad soyad, cep telefonu, doğum tarihi ve kimlik bilgisi gibi kullanıcı bilgilerini görüntüleyebilir ve kontrol edebilirsiniz. Gerekli durumlarda <mark style="background-color:purple;">**Şifre sıfırlama isteği gönder**</mark> aksiyonu ile kullanıcı için şifre yenileme süreci başlatabilirsiniz.
> > * *<mark style="color:$info;">Yetkiler</mark>* sekmesinde kullanıcıya ekstra rol atayabilirsiniz. Bir kullanıcıya birden fazla rol tanımlanabilir ve kullanıcının sistemdeki erişim yetkileri bu roller üzerinden belirlenir.

#### :arrow\_forward:<mark style="color:$info;">Kullanıcıya rol nasıl atanır?</mark>

Kullanıcıya rol atama işlemi birden fazla noktadan yapılabilir:

* **Kullanıcı üzerinden:** <mark style="background-color:purple;">Kullanıcı oluşturma sırasında</mark> veya kullanıcı detay sayfasındaki *<mark style="color:$info;background-color:purple;">Yetkiler</mark>* sekmesinden rol atanabilir.
* **Rol üzerinden:** <mark style="background-color:purple;">Rol oluşturma sırasında</mark> veya rol detay sayfasındaki *<mark style="color:$info;background-color:purple;">Kullanıcılar</mark>* sekmesinden kullanıcıya rol atanabilir.

{% hint style="warning" %}
:bangbang:Tüm bu yöntemlerde kullanıcıya bir veya birden fazla rol tanımlanabilir ve kullanıcının sistemdeki erişim yetkileri, atanmış rollerin birleşimi ile belirlenir.
{% endhint %}


# Dış sistemler için ürün aktarımı nasıl yapılır?

Bu sayfada Lidia PIM'de bulunan ürünlerinizi farklı platformlara aktarmak için akış oluşturmayı, akış ayarlarını yapılandırmayı ve alan eşleştirmelerini yapmayı öğreneceksiniz.

### :rocket:<mark style="color:$primary;background-color:purple;">Ürünlerinizi Dış Platformlara Hazırlayın</mark>

Akış yönetimi, Lidia PIM’deki ürün verilerini farklı platformların beklediği formatlarda hazırlamanızı sağlar. Bu sayede ürünlerinizi pazaryerleri, reklam platformları, entegrasyon servisleri veya diğer dış sistemlerle tek bir bağlantı üzerinden paylaşabilirsiniz.

Doğru yapılandırılmış bir akış, ürün bilgilerinin hedef platformun beklediği alan yapısına uygun şekilde aktarılmasını sağlar ve manuel veri hazırlama ihtiyacını ortadan kaldırır.

#### :arrow\_forward:<mark style="color:$info;">Akış Nedir, Ne Amaçla Kullanılır?</mark>

Akış, Lidia PIM'de bulunan ürün bilgilerinin belirli bir formatta dış sistemlere aktarılmasını sağlayan veri çıktısıdır.

Bir akış oluşturduğunuzda sistem, seçtiğiniz ürün bilgilerini belirlediğiniz alan yapısına göre hazırlar ve size benzersiz bir bağlantı (**URL**) oluşturur. Bu bağlantıyı ürün verilerini almak isteyen dış sistemlerle paylaşabilirsiniz. Dış sistem, bu URL üzerinden ürün adı, marka, kategori, fiyat, stok, teknik özellikler ve görseller gibi bilgileri belirlenen formatta alabilir.

> **Örneğin**, seramik ve yapı malzemeleri üreten bir firma, ürün kataloglarını sürekli e-posta ile göndermek yerine mimarlık ofisleriyle oluşturduğu akış bağlantısını paylaşabilir. Mimarlar bu bağlantı üzerinden güncel ürün bilgilerine, teknik özelliklere ve görsellere her zaman erişebilir. Ürün bilgilerinde bir güncelleme yapıldığında, akış üzerinden paylaşılan veriler de güncel hale gelir ve dosyaların yeniden gönderilmesine gerek kalmaz.
>
> \
> Bu sayede ürün verileri tek bir kaynaktan yönetilir ve farklı sistemlerle güncel ve tutarlı şekilde paylaşılabilir.

#### :arrow\_forward:<mark style="color:$info;">Hangi Akış Formatları Desteklenmektedir?</mark>

Lidia PIM'de akış oluştururken üç farklı yapılandırma seçeneği sunulur:

* **Google Shopping Formatı**
* **Lidia PIM Formatı**
* **Manuel Yapılandırma**

Seçtiğiniz format, ürün bilgilerinin hangi alanlarla ve hangi yapıda dış sisteme aktarılacağını belirler.

<div align="center" data-with-frame="true"><figure><img src="/files/tJzDdX3yubkUy126b3EO" alt="" width="254"><figcaption></figcaption></figure></div>

1. **Google Shopping Formatı**\
   ![](/files/hpIZes16umovJ33euOiY)<br>

   **Google Shopping** **Formatı**, Google Merchant Center'ın beklediği XML yapısına uygun olarak önceden hazırlanmış hazır bir akış şablonudur.

   Bu format seçildiğinde sistem, Google Shopping için gerekli XML yapısını ve temel alan eşleştirmelerini otomatik olarak oluşturur. Böylece kullanıcı, XML yapısını sıfırdan oluşturmak yerine hazır gelen yapı üzerinde ihtiyaç duyduğu düzenlemeleri yaparak akışı kısa sürede hazırlayabilir.

   Hazır şablon üç temel bölümden oluşur:

   * **rss** (Akışın kök grubu)
   * **channel** (Akış bilgilerini içeren grup)
   * **item** (Ürün bilgilerinin yer aldığı grup)

   \
   :small\_orange\_diamond:**RSS Grubu**

   Akışın en üst seviyesinde **rss** grubu yer alır ve varsayılan olarak **Tekrarlanmayan** türünde oluşturulur. Bunun nedeni, XML çıktısında **rss** etiketinin yalnızca bir kez oluşturulması gerektiğidir.

   RSS grubunda ayrıca **Öznitelikler & Varsayılan Değer** alanı hazır olarak gelir. Bu bölüm, XML etiketine eklenecek **Node Attribute (XML öznitelikleri)** ve varsayılan değerleri tanımlamak için kullanılır.

   Google Shopping hazır şablonunda aşağıdaki öznitelikler varsayılan olarak tanımlanmıştır:

   | Node Attribute | Değer Türü   | Varsayılan Değer                |
   | -------------- | ------------ | ------------------------------- |
   | `xmlns:g`      | Statik Değer | `http://base.google.com/ns/1.0` |
   | `version`      | Statik Değer | `2.0`                           |

   \
   Bu değerler Google Shopping XML standardına uygun olarak sistem tarafından otomatik eklenir.

   İhtiyaç duyulması halinde bu alanlar özelleştirilebilir. Örneğin;

   * [x] XML özniteliğinin adı değiştirilebilir.
   * [x] Statik değer yerine farklı bir değer kullanılabilir.
   * [x] Yeni XML öznitelikleri eklenebilir.
   * [x] Mevcut öznitelikler silinebilir.

   Burada kullanılan değerler **Lidia PIM'deki sistem alanlarından alınmaz**. Bunlar doğrudan XML yapısına eklenecek **statik değerlerdir** ve kullanıcı tarafından serbestçe düzenlenebilir.

   \
   :small\_orange\_diamond:**Channel Grubu**

   RSS grubunun altında **channel** grubu yer alır ve varsayılan olarak **Tekrarlanmayan** türünde oluşturulur.

   Bu grup, XML çıktısında yalnızca bir kez oluşturulur ve akışın ürün listesini barındıran üst kapsayıcı görevi görür.

   İhtiyaç halinde channel grubuna yeni alanlar veya alt gruplar eklenebilir.\
   \
   :small\_orange\_diamond:**Item Grubu**

   Channel grubunun altında **item** grubu bulunur ve varsayılan olarak **Ürün Listesi** türünde oluşturulur.

   Bu yapı sayesinde akışta bulunan her ürün için ayrı bir **item** etiketi oluşturulur. Ürün alanları bu grubun altında tanımlanır ve her ürün için otomatik olarak tekrar edilir.

   Hazır Google Shopping şablonunda ürün adı, açıklama, ürün bağlantısı, ana görsel, fiyat, marka, entegrasyon kodu ve Google Shopping tarafından kullanılan diğer temel alan eşleştirmeleri varsayılan olarak tanımlanmıştır. Kullanıcı isterse mevcut eşleştirmeleri düzenleyebilir, yeni alanlar ekleyebilir veya kullanılmayan alanları kaldırabilir.

{% hint style="info" %}
Tekrarlayan ürün gruplarında, örneğin **Ürün Listesi** seçildiğinde, sistem XML çıktısını otomatik olarak düzenler. Grup adı **item** ise XML içerisinde dış kapsayıcı (**Container**) **`<items>`**, her ürün kaydı ise tekil **`<item>`** etiketi olarak oluşturulur. Böylece akışta bulunan her ürün için ayrı bir **`<item>`** düğümü üretilir ve XML yapısı standartlara uygun şekilde hazırlanır.\
\
Varsayılan olarak oluşturulan "Kapsayıcı (Container)" ve "Tekil (Item)" etiketleri de özelleştirilebilir. Bu özellik sayesinde akış yapısını, veri aktarımı yapılacak dış sistemin beklediği XML yapısına uygun şekilde düzenleyebilirsiniz. Özelleştirme adımları [**Öznitelikler & Varsayılan Değer**](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/dis-sistemler-icin-urun-aktarimi-nasil-yapilir#oznitelikler-and-varsayilan-deger-nedir) bölümünde detaylı olarak açıklanmaktadır.
{% endhint %}

{% hint style="warning" %}
**🔒 Zorunlu Alan Koruması**\
Google Shopping entegrasyonu için gerekli zorunlu alanlar sistem tarafından korunur. Bu alanlar arayüzde kilitli olarak görüntülenir ve silinemez veya pasifleştirilemez.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/HDGxZFV038QOoUefk4go" alt=""><figcaption></figcaption></figure></div>

2. **Lidia PIM Formatı**\
   ![](/files/OETegC1bQ0u3KwERPKG8)\
   \
   **Lidia PIM Formatı**, Lidia PIM'de bulunan ürün verilerinin tamamını dış sistemlere aktarmak için hazırlanmış hazır bir akış şablonudur.

   Bu format seçildiğinde akış yapısı ve alan eşleştirmeleri sistem tarafından otomatik olarak oluşturulur. Tüm grup, alt grup ve alan yapıları varsayılan olarak tanımlanmış şekilde gelir. Kullanıcı, isterse hazır gelen yapıyı düzenleyebilir veya kendi ihtiyaçlarına göre özelleştirebilir.

   Hazır şablon aşağıdaki yapıyı içerir:

   * Akışın en üst seviyesinde **Tekrarlanmayan** türünde **test\_product\_feed** grubu oluşturulur.
   * Bu grubun altında **Ürün Listesi** yer alır ve akışa dahil edilen her ürün için ayrı bir **`<product>`** etiketi oluşturulur. Dış kapsayıcı (**Container**) etiketi ise **`<products>`** olarak oluşturulur.
   * Ürün grubunun altında **Varyant Listesi** hazır olarak bulunur. Her varyant için ayrı bir **`<variant>`** etiketi oluşturulurken dış kapsayıcı (**Container**) etiketi **`<variants>`** olarak oluşturulur.
   * **Varyant Listesi** içerisinde varsayılan olarak **Varyant Görsel Listesi**, **Varyant Doküman Listesi** ve **Varyant Seçenek Değeri Listesi** alt grupları bulunur. Bu gruplar kendi alan eşleştirmeleriyle birlikte hazır gelir.
   * Ürün grubu altında ayrıca **Ürün Görsel Listesi**, **Ürün Doküman Listesi**, **Ürün Kategori Listesi**, **Ürün Marka Listesi**, **Ürün Özellik Listesi** ve **Ürün Seçenek Listesi** varsayılan olarak oluşturulur. Bu grupların her biri, ilgili veri tipine ait sistem alanlarıyla birlikte hazır olarak tanımlanmıştır.
   * Hazır şablonda kullanılan varsayılan XML etiketleri aşağıdaki gibidir:
     * **`<products>` / `<product>`**
     * **`<variants>` / `<variant>`**
     * **`<pictures>` / `<picture>`**
     * **`<documents>` / `<document>`**
     * **`<categories>` / `<category>`**
     * **`<trademarks>` / `<trademark>`**
     * **`<properties>` / `<property>`**
     * **`<options>` / `<option>`**

   Bu yapı sayesinde ürünler, varyantlar ve bunlara bağlı tüm ilişkili veriler hiyerarşik olarak tek bir akış içerisinde dış sistemlere aktarılabilir.

{% hint style="info" icon="up-right-from-square" %}
Lidia PIM Formatı, grup ve alt grup yapısını hazır olarak oluşturur. Hazır şablonda kullanılan grup hiyerarşisi, alan eşleştirmeleri ve XML etiket yapıları [**Grup ve Alt Grup Yapısı**](https://docs.lidiacommerce.com/products/lidia-pim/quick-start-guide/dis-sistemler-icin-urun-aktarimi-nasil-yapilir#grup-ve-alt-grup-yapisi) bölümünde detaylı olarak açıklanmaktadır.
{% endhint %}

{% hint style="warning" %}
Bir ürünün tüm varyantlarını listelemek için ürün grubunun altında **Varyant Listesi** türünde bir alt grup bulunmalıdır. **Ürün** veya **Tekrarlanmayan** gruplar altına doğrudan eklenen tekil varyant alanları (örneğin **Varyant Kodu**, **Varyant Durumu**) tüm varyantları listelemez; yalnızca ilgili ürünün ilk varyantına ait bilgiyi döndürür. Bu nedenle Lidia PIM Formatı’nda hazır yapı, ürün grubunun altında **Varyant Listesi** yer alacak şekilde kurgulanmıştır.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/nyWNUExDoK2F8lc5DpP4" alt=""><figcaption></figcaption></figure></div>

3. **Manuel Yapılandırma**\
   \
   Manuel Yapılandırma seçildiğinde **Mapping Alanı** boş olarak oluşturulur. Bu yöntemde akışta hangi grup, alt grup ve alanların yer alacağı tamamen kullanıcı tarafından belirlenir.

   Hazır şablon kullanılmadığı için akış yapısını sıfırdan oluşturmanız gerekir. İlk olarak **Grup Ekle** butonunu kullanarak ana grup yapısını oluşturabilir, ardından bu grubun altında ihtiyaç duyduğunuz alt grupları ve alanları tanımlayabilirsiniz.

   Bu seçenek, hazır Lidia PIM veya Google Shopping şablonları yerine tamamen özelleştirilmiş bir akış oluşturmak isteyen kullanıcılar için uygundur.

<div data-with-frame="true"><figure><img src="/files/BY63BO6EIg0FiRYNvZVY" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Ekranın sağ tarafında bulunan **Önizleme** alanı, yaptığınız alan eşleştirmelerinin oluşturulacak akış çıktısına nasıl yansıyacağını anlık olarak gösterir. Böylece akışı kaydetmeden önce oluşacak çıktıyı kontrol edebilir ve gerekli düzenlemeleri yapabilirsiniz.
{% endhint %}

#### :arrow\_forward:<mark style="color:$info;">Yeni Akış Nasıl Oluşturulur?</mark>

{% stepper %}
{% step %} <mark style="background-color:purple;">**Servisler > Akışlar**</mark>**&#x20;sayfasına gidin.**
{% endstep %}

{% step %} <mark style="background-color:purple;">**Yeni Akış Ekle**</mark>**&#x20;butonuna tıklayın.**

Açılan modalda:

* **Akış Adı (Zorunlu)**
* **Akış Kodu (Zorunlu)**
* **Akış Formatı (Zorunlu)** — Lidia PIM , Google Shopping veya Boş eşleme formatlarından birini seçin.
*

```
<div align="left" data-with-frame="true"><figure><img src="/files/jXIlV4yQyELpxOsXln2M" alt="" width="131"><figcaption></figcaption></figure></div>
```

* **Devam Et** butonuna tıklayın.
  {% endstep %}

{% step %}
:tada:**Yeni akış oluşturuldu.**

Akış oluşturulduktan sonra sistem sizi akış detay sayfasına yönlendirir. Bu sayfada akış ayarlarını yapılandırabilir ve alan eşleştirme işlemlerini tamamlayabilirsiniz.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Önemli**&#x20;

Oluşturulan her akış için erişim yetkileri **Erişim Kontrolü** üzerinden yönetilebilir. Böylece akış bağlantısını yalnızca erişim izni bulunan kullanıcılar veya sistemler kullanabilir.
{% endhint %}

#### :arrow\_forward:<mark style="color:$info;">Akış Ayarları Nasıl Yapılır?</mark>

Akış oluşturulduktan sonra, akışın nasıl çalışacağını bu bölümden yönetebilirsiniz. Akışın erişim ayarlarını düzenleyebilir, çıktı davranışını özelleştirebilir, aktarılacak verileri filtreleyebilir ve alan eşleştirmelerini yapılandırabilirsiniz.

Bu işlemler sırasıyla **Temel Bilgiler**, **Akış Ayarları** ve **Formatlar ve Önizleme** bölümleri üzerinden gerçekleştirilir.

&#x20;:rocket: **Temel Bilgiler**

**Temel Bilgiler** bölümü, akışın kimlik bilgilerini, paylaşım bağlantılarını ve güvenlik ayarlarını yönetmek için kullanılır.

Bu bölümden;

* Akış adını ve akış kodunu güncelleyebilir,
* Akışın aktif veya pasif durumunu değiştirebilir,
* Akış URL'lerine erişim için erişim kontrolünü yönetebilir,
* JSON, XML ve CSV formatlarında oluşturulan paylaşım bağlantılarını görüntüleyebilir,
* Akışa erişecek sistemler için bir veya birden fazla erişim anahtarı oluşturabilir ve yönetebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/Ot4P5sgEWTabyhTlWCzq" alt="" width="563"><figcaption></figcaption></figure></div>

Sistem, oluşturduğunuz her akış için otomatik olarak **JSON**, **XML** ve **CSV** formatlarında paylaşım bağlantıları oluşturur.

* **JSON:** API entegrasyonları ve modern uygulamalar tarafından tercih edilen veri formatıdır.
* **XML:** XML tabanlı çalışan entegrasyonlar ve Google Shopping gibi platformlar için kullanılır.
* **CSV:** Excel, raporlama araçları ve tablo tabanlı veri aktarımı yapan sistemler için uygundur.

Her URL'nin yanında bulunan **Kopyala** butonu ile bağlantıyı tek tıklamayla panoya kopyalayabilir ve entegrasyon yapılacak sistemle paylaşabilirsiniz.

{% hint style="info" %}
**Info:** JSON, XML ve CSV bağlantılarının tamamı aynı akış verisini içerir. Fark yalnızca verinin dış sisteme sunulduğu çıktı formatıdır.
{% endhint %}

Aynı ekranda yer alan **Yeni Erişim Anahtarı Ekle** butonu ile akış bağlantısına erişim için kullanılacak anahtar değerler oluşturabilirsiniz. Erişim anahtarı, akış URL’inin yetkili sistemler tarafından güvenli şekilde kullanılmasını sağlar.

Bir akış için birden fazla erişim anahtarı tanımlayabilirsiniz. Böylece farklı dış sistemler veya iş ortakları için ayrı anahtarlar oluşturabilir, erişimleri birbirinden bağımsız şekilde yönetebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/j7flFZuKu7YsIbcOcKXB" alt="" width="563"><figcaption></figcaption></figure></div>

&#x20;:rocket: **Akış Ayarları**&#x20;

**Akış Ayarları** bölümü, oluşturulan akışın nasıl üretileceğini, hangi verilerin akışa dahil edileceğini (filtreleme seçenekleri) ve çıktı üzerinde uygulanacak veri işleme kurallarını belirlemek için kullanılır.

<mark style="background-color:blue;">**-Çıktı Ayarları**</mark>

Çıktı Ayarları bölümü, oluşturulacak akış dosyasının hangi kurallara göre üretileceğini belirler. Yapılan ayarlar, oluşturulan JSON, XML ve CSV çıktılarının tamamına uygulanır.

Bu bölümde aşağıdaki ayarlar yapılandırılabilir:

* **GZIP Sıkıştırma:**\
  GZIP Sıkıştırma seçeneği etkinleştirildiğinde oluşturulan çıktı dosyası GZIP algoritması kullanılarak sıkıştırılır. Büyük veri setlerinin daha **küçük boyutta** paylaşılması gerektiğinde bu seçenek kullanılabilir.

<div data-with-frame="true"><figure><img src="/files/QE4Ff0uU4UZObONfoqdL" alt="" width="309"><figcaption></figcaption></figure></div>

* **Boş Alan Yönetimi**\
  Bu bölüm, boş veya **null** değerlerin akış çıktısında nasıl işleneceğini belirler. **Boş Değerleri Hariç Tut** seçeneği etkinleştirildiğinde boş veya null değer içeren alanlar oluşturulan akış çıktısına dahil edilmez.

  <div data-with-frame="true"><figure><img src="/files/KGkmSTrsZVbuCDSwQCeY" alt="" width="313"><figcaption></figcaption></figure></div>
* **Boşluk Karakteri Yönetimi**\
  Bu bölüm, metin alanlarında bulunan gereksiz boşlukların otomatik olarak temizlenmesini sağlar. **Boşlukları Temizle** seçeneği etkinleştirildiğinde tüm metin değerlerinin başındaki ve sonundaki gereksiz boşluk karakterleri kaldırılır.<br>

  <div data-with-frame="true"><figure><img src="/files/YJW53DXlZyEpoRFSOdMK" alt="" width="364"><figcaption></figcaption></figure></div>
* **Önbellek Ayarları**\
  Akış çıktılarının önbelleğe alınmasını sağlar. **Önbellek Kullan** seçeneği etkinleştirildiğinde sistem oluşturulan akış çıktısını önbellekte saklar. Aynı akış tekrar talep edildiğinde çıktı yeniden oluşturulmak yerine önbellekten sunulur. Bu sayede API yanıt süreleri kısalır ve sistem performansı artırılır. **Önbellek Süresi (saniye)** alanından önbelleğin ne kadar süre geçerli olacağını belirleyebilirsiniz. Örneğin 3600 değeri, akış çıktısının 3600 saniye boyunca önbellekte tutulacağı anlamına gelir.<br>

<div data-with-frame="true"><figure><img src="/files/xcVWJyBGCeeCTZJ0foKF" alt="" width="375"><figcaption></figcaption></figure></div>

* **Tarih Formatı Yönetimi**\
  **A**kışta yer alan tarih ve saat bilgilerinin hangi biçimde dış sistemlere aktarılacağını belirlemek için kullanılır. Tarih formatı ve yerel format kültürü birlikte çalışır. Veri aktarımı yapılacak sistem belirli bir tarih standardı veya bölgesel biçimlendirme bekliyorsa, bu alanlardan uygun format ve kültür seçilerek akış çıktısı hedef sisteme uyumlu hale getirilebilir.

<div data-with-frame="true"><figure><img src="/files/AqVJTPG64u2UWVtIupMb" alt="" width="375"><figcaption></figcaption></figure></div>

* **Durum Bazlı Filtreleme**\
  Bu bölümde akışa dahil edilecek ürün ve varyant durumları belirlenir. **Ürün Durumları** ve **Varyant Durumları** için ayrı ayrı durum filtreleme uygulanabilir. Durum filtreleme kapalı olduğunda ilgili tüm durumlar akışa dahil edilir.

  Durum filtreleme etkinleştirildiğinde **Dahil Edilecek Durumlar** alanı aktif olur ve akışta yer almasını istediğiniz durumları seçmeniz gerekir. Yalnızca seçilen durumlara sahip ürün veya varyantlar akış çıktısına dahil edilir.

  <div align="center" data-with-frame="true"><figure><img src="/files/sxCAiTtdhXPjks9d47Jq" alt="" width="375"><figcaption></figcaption></figure></div>

<mark style="background-color:blue;">**-Filtreler**</mark>

Filtreler bölümü, akışa dahil edilecek verileri belirli kriterlere göre sınırlandırmanızı sağlar. Bu sayede yalnızca istediğiniz ürünler akışta yer alır.

Bu bölümde aşağıdaki filtreler kullanılabilir:

* Kategoriler
* Hariç Kategoriler
* Markalar
* Hariç Markalar
* Özel Listeler
* Ürün Özellikleri
* Varyant Özellikleri
* Seçenek Değerleri
* Ürün Etiketleri
* Hariç Ürün Etiketleri
* Varyant Etiketleri
* Hariç Varyant Etiketleri

Seçilen filtreler birlikte değerlendirilir ve yalnızca belirlenen kriterlere uyan kayıtlar akışa dahil edilir.

<mark style="background-color:blue;">**-Veri Paketi**</mark>

Veri Paketi bölümü, akışta hangi veri paketlerinin yer alacağını belirlemek için kullanılır.

Bu bölümde aşağıdaki alanlar yapılandırılabilir:

* Koleksiyonlar
* Kategori Boyutları

Seçilen veri paketleri, oluşturulan akış çıktısına dahil edilir.

#### :arrow\_forward:<mark style="color:$info;">Ürün Alanları Feed Alanları ile Nasıl Eşleştirilir?</mark>

Alan eşleştirme işlemleri **Formatlar ve Önizleme** sekmesinde gerçekleştirilir. Sayfanın üst kısmında yer alan **Kullanım Kuralları ve İpuçları** bölümü ise eşleştirme işlemi sırasında dikkat edilmesi gereken kurallar hakkında yönlendirici bilgiler sunar.

<div data-with-frame="true"><figure><img src="/files/JaNdFjjj16gp0auOf6XF" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/WwR7LS32UEl2tn688rZe" alt=""><figcaption></figcaption></figure></div>

#### :star: Alan eşleştirme işlemleri **Mapping Alanı** üzerinden gerçekleştirilir.

Bir akış oluştururken yalnızca hangi verilerin aktarılacağını değil, bu verilerin dış sistemde **hangi hiyerarşik yapı ile oluşturulacağını** da tanımlarsınız.

Bu yapı **Grup**, **Alt Grup** ve **Alan** bileşenlerinden oluşur.

Akış oluşturulurken önce veri yapısı oluşturulur, ardından bu yapının içerisine aktarılacak alanlar eklenir. Böylece dış sistemin beklediği XML veya JSON yapısı eksiksiz şekilde hazırlanmış olur.

> <mark style="background-color:purple;">**Grup aksiyonları**</mark><mark style="background-color:purple;">;</mark>\
> Akış çıktısının yapısını düzenlemek için kullanılır. Hazır şablon kullanıyorsanız bu alanlar çoğunlukla sistem tarafından önceden oluşturulmuş gelir. Kullanıcı olarak yalnızca ihtiyaç duyduğunuz alanları düzenleyebilir, yeni alan ekleyebilir veya gereksiz alanları kaldırabilirsiniz.
>
> Manuel yapılandırma kullanıyorsanız bu butonlarla akışın yapısını sıfırdan oluşturursunuz.\
> &#x20;<img src="/files/05RU9G9heQdm0cBViefF" alt="" data-size="line">**Alan Ekle** ile gruba yeni veri alanı ekleyebilir,\
> &#x20;<img src="/files/TpSHY7IJUMtFyPtmPYC8" alt="" data-size="line">**Alt Grup Ekle** ile iç içe grup yapısı oluşturabilir,\
> &#x20;<img src="/files/mWgexucn7LlwKf0QjcNl" alt="" data-size="line">**Öznitelikler ve Varsayılan Değerleri Yönet** alanından sabit değer veya XML özniteliği tanımlayabilir,\
> &#x20;<img src="/files/FtMXTvwFqi8KHW78wgeh" alt="" data-size="line"> **Sil** butonu ile kullanmak istemediğiniz grupları kaldırabilirsiniz.

#### Grup ve Alt Grup Yapısı

* #### **Grup Nedir?**

Grup, akışın en üst seviyedeki veri yapısını temsil eder. Her grup, oluşturulacak çıktıda bir düğüm (node) oluşturur ve altında yer alacak alt grupları veya alanları kapsar.

![](/files/Eaw4LgccX4r2XGhgeJzZ) **Grup Ekle** butonuna tıklayarak yeni bir grup oluşturabilirsiniz.&#x20;

Grup oluşturduktan sonra;

* grubun adını değiştirebilir,
* grubun koleksiyon tipini belirleyebilir,
* içerisine alan ekleyebilir,
* alt grup oluşturabilirsiniz.

Her grup oluşturulurken grubun nasıl davranacağını belirleyen bir **Koleksiyon Tipi** seçilir.\
Bu seçim, grubun XML veya JSON çıktısında kaç kez oluşturulacağını belirler.<br>

* **Tekrarlanmayan:** Grup yalnızca **bir kez** oluşturulur. Genellikle akışın genel yapısını oluşturan ve yalnızca tek bir kez bulunması gereken üst seviye gruplar için kullanılır. Örneğin; `rss, channel, feed, root`  gibi gruplar tekrarlanmayan olarak tanımlanır. Bu gruplar akışın iskeletini oluşturur ve içerisinde ürün listesi veya diğer alt gruplar yer alır.
* **Ürün Listesi:** Grup, akışa dahil edilen **her ürün için** bir kez oluşturulur. Örneğin akışta 100 ürün varsa bu grup 100 kez tekrarlanır ve her ürünün bilgileri ayrı ayrı yazılır.
* **Varyant Listesi:** Grup, akışa dahil edilen **her ürün varyantı için** oluşturulur. Örneğin bir tişörtün S, M ve L olmak üzere 3 varyantı varsa, varyant grubunda bu üç varyant ayrı ayrı listelenir.

\
Örneğin akış çıktısında grup adı **product** ise sistem aşağıdaki yapıyı oluşturur:

```
<products>
    <product>...</product>
    <product>...</product>
    <product>...</product>
</products>
```

{% hint style="info" %}
Burada **`<products>`** dış kapsayıcı (**Container**) etiketi, **`<product>`** ise her ürün için tekrar eden tekil (**Item**) etikettir.\
\
Tekrarlayan grup türlerinde (**Ürün Listesi** ve **Varyant Listesi**) dış kapsayıcı (**Container**) ve tekil (**Item**) etiketleri varsayılan olarak sistem tarafından oluşturulur. İhtiyaç duyulması halinde bu etiket adları da özelleştirilebilir. Bu yapı sayesinde akış, veri aktarımı yapılacak dış sistemin beklediği XML formatına uygun hale getirilebilir.<br>
{% endhint %}

* #### **Alt Grup Nedir?**

Alt grup, mevcut grubun altında farklı veri tiplerini hiyerarşik olarak organize etmek için kullanılır.

Ürünler tek başına yalnızca ürün bilgilerinden oluşmaz. Bir ürün; görsellere, dokümanlara, kategorilere, markaya, özelliklere, varyantlara sahip olabilir.

Bu ilişkili verilerin tamamı alt gruplar kullanılarak ürünün altında organize edilir.

:arrow\_right: Eğer oluşturulan grup **Tekrarlanmayan** türündeyse, bu grubun altına eklenecek **alt gruplar için** aşağıdaki türlerden biri seçilebilir:

* Tekrarlanmayan
* Ürün Listesi
* Varyant Listesi

<figure><img src="/files/QzuIIClUxv5SgiavofVX" alt=""><figcaption></figcaption></figure>

:arrow\_right: Eğer oluşturulan grup **Ürün Listesi**  türündeyse bu grubun altına eklenecek **alt gruplar için** aşağıdaki türlerden biri seçilebilir:

* Tekrarlanmayan
* Ürün Doküman Listesi
* Ürün Görsel Listesi
* Ürün Kategori Listesi
* Ürün Marka Listesi
* Ürün Özellik Listesi
* Ürün Listesi
* Varyant Listesi

<figure><img src="/files/lMHJnlJAarZuNUT5lqeS" alt=""><figcaption></figcaption></figure>

:arrow\_right:  Eğer oluşturulan grup **Varyant Listesi**  türündeyse bu grubun altına eklenecek **alt gruplar için** aşağıdaki türlerden biri seçilebilir:

* Tekrarlanmayan
* Ürün Doküman Listesi
* Ürün Görsel Listesi
* Ürün Kategori Listesi
* Ürün Marka Listesi
* Ürün Özellik Listesi
* Varyant Doküman Listesi
* Varyant Görsel Listesi
* Varyant Özellik Listesi
* Varyant Seçenek Değeri Listesi

<figure><img src="/files/D293QTKjoqDa3gbB2gIA" alt=""><figcaption></figcaption></figure>

* #### **Alan Nedir?**

Alan, akış çıktısında yer alacak tek bir veri bilgisini temsil eder. Bir grubun veya alt grubun içerisine eklenir ve Lidia PIM'deki bir sistem alanının dış sisteme hangi adla aktarılacağını belirler.

Her alan iki bölümden oluşur:

* **Sistem Alanı:** Lidia PIM'de bulunan ve aktarılacak veriyi temsil eder (örneğin Ürün Adı, Ürün Kodu veya Fiyat).
* **Çıktı Alanı:** Seçilen sistem alanının akış çıktısında hangi adla oluşturulacağını belirler.

Örneğin, sistem alanı olarak Ürün > Adı seçip çıktı alanı olarak title tanımlarsanız, ürün adı akış çıktısında title alanı olarak oluşturulur.

<img src="/files/i56sGX4U01kCMOZPNS2e" alt="" data-size="line">**Alan Ekle** butonuna tıklayarak yeni bir alan oluşturabilirsiniz. Açılan pencerede, sol tarafta Lidia PIM'deki sistem alanı, sağ tarafta ise bu alanın akış çıktısında kullanılacak adı tanımlanır.&#x20;

{% hint style="info" %}
Ekleyebileceğiniz sistem alanları, alanın bulunduğu grup veya alt grubun türüne göre değişir. Örneğin **Ürün Listesi** altında ürün alanları, **Varyant Listesi** altında varyant alanları, **Ürün Görsel Listesi** altında ise görsellere ait alanlar listelenir.
{% endhint %}

Alan eklerken yalnızca Lidia PIM'deki ürün, varyant veya diğer sistem alanlarını değil, "Özel Değerler" kullanarak sabit veya sistem tarafından üretilen değerleri de akışa ekleyebilirsiniz. Bu seçenek, belirli bir sistem alanına karşılık gelmeyen ancak akış çıktısında yer alması gereken değerler için kullanılır.

**Özel Değerler**

1. **Statik Değer:** Kullanıcı tarafından manuel olarak girilen sabit bir metin değeridir. Bu değer, akış oluşturulurken tüm kayıtlar için aynı şekilde çıktıya yazılır.
2. **Sistem Değeri:** Akış oluşturulurken sistem tarafından otomatik olarak üretilen bilgileri kullanmanızı sağlar.

   Bu seçenek kullanıldığında aşağıdaki sistem değerleri seçilebilir:

   * **Site Adı:** Akışın ait olduğu site bilgisini kullanır.
   * **Şu Anki Zaman:** Akışın oluşturulduğu anın tarih ve saat bilgisini kullanır.
   * **Domain:** Akışın yayınlandığı domain bilgisini kullanır.
   * **IP:** Akış isteğinin işlendiği sunucunun IP bilgisini kullanır.

   Bu değerler manuel olarak girilmez; akış oluşturulduğu anda sistem tarafından otomatik olarak üretilerek çıktıya eklenir.

{% hint style="info" %}
**Info:** Statik Değer ve Sistem Değeri yalnızca alan oluştururken değil, **Node Öznitelikleri (XML Attribute)** tanımlanırken de kullanılabilir. Bu sayede hem XML etiketlerinin içerisine hem de alan değerlerine sabit veya dinamik sistem bilgileri eklenebilir
{% endhint %}

* #### **Alan Türlerine Göre Kullanılabilecek Sistem Alanları Nelerdir?**

1. <mark style="background-color:blue;">**Ürün Listesi Alanları**</mark>

Ürün Listesi türündeki bir gruba alan eklemek için Alan Ekle butonuna tıklayın. Açılan pencerede sol taraftan Lidia PIM'deki sistem alanını seçin, sağ tarafta ise bu alanın akış çıktısında kullanılacak adını belirleyin.

<div data-with-frame="true"><figure><img src="/files/nJsDU38TmpROCeiheLyt" alt=""><figcaption></figcaption></figure></div>

**Ürün Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Ürün ID
* Ürün Adı
* Ürün Kodu
* Ürün Entegrasyon Kodu
* Ürün Kısa Açıklama
* Ürün Uzun Açıklama
* Ürün Ana Görsel Yolu
* Ürün Vergi Oranı
* Ürün Birimi
* Ürün Tipi
* Ürün Bağlantısı
* Ürün Güncellenme Tarihi
* Ürün Oluşturulma Tarihi
* Ürün Durumu
  {% endcolumn %}

{% column width="33.33333333333333%" %}

* Ürün > Kategori > Kategori ID
* Ürün > Kategori > Adı
* Ürün > Kategori > Kategori Tam Adı
* Ürün > Kategori > Kodu
* Ürün > Kategori > Entegrasyon Kodu
* Ürün > Kategori > Güncellenme Tarihi
* Ürün > Kategori > Oluşturulma Tarihi
* Ürün > Kategori > Durum
* Ürün > Marka > Marka ID
  {% endcolumn %}

{% column width="33.33333333333333%" %}

* Ürün > Marka > Adı
* Ürün > Marka > Kodu
* Ürün > Marka > Entegrasyon Kodu
* Ürün > Marka > Güncellenme Tarihi
* Ürün > Marka > Oluşturulma Tarihi
* Ürün > Marka > Durum
* Ürün > Envanter > Stok
* Ürün > Envanter > Fiyat
* Ürün > Envanter > Liste Fiyatı
* Ürün > Özellik
  {% endcolumn %}
  {% endcolumns %}

Ürün alanlarını tanımladıktan sonra, ihtiyaç duyduğunuz ilişkili verileri akışa dahil etmek için ilgili grubun içerisine yeni alt gruplar ekleyebilirsiniz.

Her alt grup belirli bir veri tipini temsil eder. Böylece ürün bilgileri, varyantlar, görseller, dokümanlar, kategoriler, markalar ve özellikler kendi yapıları içerisinde düzenli şekilde oluşturulur. Bu yaklaşım, akış çıktısının dış sistemlerin beklediği hiyerarşik yapıya uygun olmasını sağlar.

{% hint style="info" %}
Ürüne bağlı veriler, ayrı alt gruplar altında yapılandırılır. Bu sayede her veri tipi kendi alanlarıyla birlikte dış sisteme düzenli ve hiyerarşik olarak aktarılır.
{% endhint %}

2. <mark style="background-color:blue;">**Varyant Listesi Alanları**</mark>

Ürüne ait varyant bilgilerini akışa dahil etmek için Varyant Listesi alt grubunu oluşturun. Ardından Alan Ekle butonuna tıklayarak varyanta ait sistem alanlarını seçebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/7ZtRq3Vm08PI7UR2FqMr" alt=""><figcaption></figcaption></figure></div>

**Varyant Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Varyant ID
* Varyant Adı
* Varyant Kodu
* Varyant Entegrasyon Kodu
* Varyant Kısa Açıklama
* Varyant Uzun Açıklama
  {% endcolumn %}

{% column %}

* Varyant Ana Görsel Yolu
* Varyant Güncellenme Tarihi
* Varyant Oluşturulma Tarihi
* Varyant Durumu
* Varyant Seçenek Değeri
* Varyant Özelliği
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
Varyant altındaki görseller ve dokümanlar, ilgili varyantın benzersiz kodu ile eşleştirilerek otomatik filtrelenir ve sadece o varyanta özel olanlar listelenir.

Eğer varyanta özel görsel veya doküman bulunamazsa, sistem otomatik olarak ana ürünün görsellerini ve dokümanlarını listeler.
{% endhint %}

3. <mark style="background-color:blue;">**Ürün Doküman Listesi Alanları**</mark>

Ürüne ait doküman bilgilerini akışa dahil etmek için **Ürün Doküman Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak doküman alanlarını seçebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/81cWJS1dyCpM9am4fNzX" alt=""><figcaption></figcaption></figure></div>

**Ürün Doküman Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Doküman Yolu
* Doküman Adı
* Doküman Formatı
  {% endcolumn %}

{% column %}

* Güncellenme Tarihi
* Oluşturulma Tarihi
* Durum
  {% endcolumn %}
  {% endcolumns %}

4. <mark style="background-color:blue;">**Ürün Görsel Listesi Alanları**</mark>

Ürüne ait görsel bilgilerini akışa dahil etmek için **Ürün Görsel Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak görsel alanlarını seçebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/Lift2rSH7MlYRP1TKHnB" alt=""><figcaption></figcaption></figure></div>

**Ürün Görsel Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Görsel Yolu
* Görsel Formatı
* Görsel Adı
* Kapak Görseli mi
  {% endcolumn %}

{% column %}

* Alt Bilgisi (Alt Text)
* Güncellenme Tarihi
* Oluşturulma Tarihi
* Durum
  {% endcolumn %}
  {% endcolumns %}

5. <mark style="background-color:blue;">**Ürün Kategori Listesi Alanları**</mark>

Ürüne ait kategori bilgilerini akışa dahil etmek için **Ürün Kategori Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak kategori alanlarını seçebilirsiniz.

<figure><img src="/files/0uX2rGEOVi8iHd1XzuD3" alt=""><figcaption></figcaption></figure>

**Ürün Kategori Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Kategori ID
* Kategori Adı
* Kategori Tam Adı
* Kategori Kodu
  {% endcolumn %}

{% column %}

* Kategori Entegrasyon Kodu
* Güncellenme Tarihi
* Oluşturulma Tarihi
* Durum
  {% endcolumn %}
  {% endcolumns %}

6. <mark style="background-color:blue;">**Ürün Marka Listesi Alanları**</mark>

Ürüne ait marka bilgilerini akışa dahil etmek için **Ürün Marka Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak marka alanlarını seçebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/1yv8oSPuKL5S7ledPrIV" alt=""><figcaption></figcaption></figure></div>

**Ürün marka listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Marka ID
* Marka Adı
* Marka Kodu
* Marka Entegrasyon Kodu
  {% endcolumn %}

{% column %}

* Güncellenme Tarihi
* Oluşturulma Tarihi
* Durum
  {% endcolumn %}
  {% endcolumns %}

7. <mark style="background-color:blue;">**Ürün Özellik Listesi Alanları**</mark>

Ürüne ait özellik bilgilerini akışa dahil etmek için **Ürün Özellik Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak özellik alanlarını seçebilirsiniz.

<div data-with-frame="true"><figure><img src="/files/aPvRIwfwghRiAY0T1dpW" alt=""><figcaption></figcaption></figure></div>

**Ürün Özellik Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Anahtar
* Ad
* Değer
  {% endcolumn %}

{% column %}

* Güncellenme Tarihi
* Oluşturulma Tarihi
* Durum
  {% endcolumn %}
  {% endcolumns %}

8. <mark style="background-color:blue;">**Ürün Seçenek Listesi Alanları**</mark>

Ürüne ait seçenek bilgilerini akışa dahil etmek için **Ürün Seçenek Listesi** alt grubunu oluşturun. Ardından **Alan Ekle** butonuna tıklayarak seçenek alanlarını seçebilirsiniz.

<figure><img src="/files/gy4snfTEhpF63VKHZT1q" alt=""><figcaption></figcaption></figure>

**Ürün Seçenek Listesi** seçildiğinde **Alan Ekle** butonu ile aşağıdaki ürün alanları akışa eklenebilir:

{% columns %}
{% column %}

* Seçenek ID
* Seçenek Adı
* Seçenek Görünen Adı
* Seçenek Kodu
  {% endcolumn %}

{% column %}

* Seçenek Entegrasyon Kodu

* Güncellenme Tarihi

* Oluşturulma Tarihi

* Durum
  {% endcolumn %}
  {% endcolumns %}

* #### **Öznitelikler & Varsayılan Değer Nedir?**

Grup veya alan oluşturduktan sonra **Öznitelikler & Varsayılan Değer** <img src="/files/LXKWv38tvxs4mF7EfT0C" alt="" data-size="line">panelini kullanarak akış çıktısını daha esnek hale getirebilirsiniz.

Bu bölüm sayesinde XML etiketlerine öznitelik (attribute) ekleyebilir, varsayılan değerler tanımlayabilir, sistem değerlerini kullanabilir veya çıktı üretimi sırasında belirli değerleri dinamik olarak değiştirebilirsiniz.

Bu özellikler, özellikle dış sistemin belirli bir XML yapısı veya sabit değer beklediği entegrasyonlarda kullanılır.\
\
![](/files/bMTPxhNIKskKsXp60JaT)

* **Node Öznitelikleri:** XML etiketlerinin içerisine **attribute (öznitelik)** eklemek için kullanılır. Bazı dış sistemler, veriyi yalnızca etiketin içerisinde değil, etiketin özellikleri (attribute) olarak da bekleyebilir. Bu durumda Node Öznitelikleri kullanılarak ilgili XML yapısı oluşturulur.\
  \
  Örneğin aşağıdaki XML çıktısında;

  ```
  <rss version="2.0" xmlns:g="http://base.google.com/ns/1.0">
  ```

  * **rss** XML etiketidir.
  * **version** ve **xmlns:g** ise bu etikete ait **Node Öznitelikleri (XML Attribute)**'dır.

  Bu nedenle Google Shopping gibi bazı hazır formatlarda gerekli Node Öznitelikleri sistem tarafından varsayılan olarak eklenmiş şekilde gelir.<br>
* **Varsayılan Değer:** Alanın karşılığı Lidia PIM'de boş olduğunda kullanılacak değeri belirler.

  Örneğin ürünün kısa açıklaması bulunmuyorsa; "Açıklama Bulunamadı" değeri otomatik olarak yazdırılabilir.

{% hint style="info" %}
Varsayılan değerler yalnızca eşlenen kaynak alan boş olduğunda çıktıda görünür. Ayrıca Görsel, Doküman veya Seçenek gibi koleksiyon gruplarında, bir alan için öznitelik tanımlarken aynı koleksiyon ögesinin diğer alanlarını (örn: Görsel Yolu için Görsel Adı veya Formatı) öznitelik değeri olarak eşleyebilirsiniz. Sistem bu öznitelikleri her liste elemanı için dinamik olarak çözecektir.<br>
{% endhint %}

* **XML Etiket Adını Özelleştir:** Bu bölüm, oluşturulan grubun XML çıktısında kullanılacak etiket adlarını özelleştirmenizi sağlar. Böylece XML yapısı, veri aktarımı yapılacak dış sistemin beklediği etiket isimlerine göre uyarlanabilir. Gösterilen alanlar, grubun türüne göre farklılık gösterir.\
  \
  :small\_orange\_diamond:**Tekrarlanmayan Gruplar**\
  Grup türü **Tekrarlanmayan** ise yalnızca **Tekil (Item) Etiketi** alanı görüntülenir.

  Bu alan, XML çıktısında oluşturulacak etiket adını belirler. Örneğin grup için **rss** veya **channel** yerine farklı bir XML etiketi kullanılması gerekiyorsa bu alandan özelleştirilebilir.\
  \
  :small\_orange\_diamond:**Tekrarlayan Gruplar**\
  Grup türü **Ürün Listesi**, **Varyant Listesi** veya diğer tekrarlayan koleksiyon türlerinden biri olduğunda iki farklı alan görüntülenir:

  * **Kapsayıcı (Container) Etiketi:** Tüm kayıtları saran üst XML etiketini ifade eder.
  * **Tekil (Item) Etiketi:** Her kayıt için tekrar eden XML etiketini ifade eder.

  \
  Örneğin;

  **Kapsayıcı Etiketi:** `products`

  **Tekil Etiketi:** `product`\
  olarak tanımlandığında XML çıktısı aşağıdaki şekilde oluşturulur:

  ```
  <products>     <product>...</product>    <product>...</product></products>
  ```

  İstenirse bu adlar farklı sistemlerin beklediği yapıya göre özelleştirilebilir.

  Örneğin;

  * `<items>` / `<item>`
  * `<entries>` / `<entry>`
  * `<catalog>` / `<product>`

  gibi farklı XML yapıları oluşturulabilir.

{% hint style="warning" %}
XML etiket adlarını değiştirmek yalnızca oluşturulan XML çıktısını etkiler. Lidia PIM'deki veri yapısı veya alan eşleştirmeleri değişmez. Bu özellik, farklı entegrasyonların beklediği XML şemasına uyum sağlamak amacıyla sunulmuştur.
{% endhint %}

* #### **Alan Seviyesinde Öznitelikler & Varsayılan Değer Nasıl Yapılandırılır?**

Bir alan ekledikten sonra, ilgili alanın sağ tarafında bulunan <img src="/files/AXmGbFrQa9s0JZrIIZ64" alt="" data-size="line">**Öznitelik ve Varsayılan Değeri Yönet** butonuna tıklayarak yalnızca o alana özel ayarları yapılandırabilirsiniz.

* **Node Öznitelikleri:** İlgili alana XML öznitelikleri (attribute) eklemek için kullanılır.
* **Varsayılan Değer:** Kaynak alan boş olduğunda kullanılacak değeri tanımlar.
* **Kara Liste Değerleri:** Belirli alan değerlerinin akış çıktısında kullanılmasını engellemek için kullanılır. Bu alana eklenen değerlerle eşleşen kayıtlar, geçersiz veya istenmeyen değer olarak değerlendirilir ve çıktı oluşturulurken dikkate alınmaz.\
  \
  Örneğin; `0, Yok, -`   gibi değerler kara listeye eklenebilir.\
  \
  Bu özellik, dış sistem tarafından kabul edilmeyen veya anlamsız kabul edilen değerlerin akış çıktısına dahil edilmesini önlemek amacıyla kullanılabilir.<br>
* **Değer Değiştiriciler:** Değer Değiştiriciler, kaynak alandaki belirli değerlerin akış oluşturulurken farklı değerlerle değiştirilmesini sağlar. Bu özellik sayesinde Lidia PIM'deki veriyi değiştirmeden, yalnızca oluşturulan akış çıktısı üzerinde dönüşüm uygulanabilir. Örneğin;<br>

  | Kaynak Değer | Çıktı Değeri |
  | ------------ | ------------ |
  | `true`       | `main`       |
  | `false`      | `secondary`  |
  | `Aktif`      | `enabled`    |
  | `Pasif`      | `disabled`   |

  \
  Bu dönüşümler yalnızca akış oluşturulurken uygulanır ve Lidia PIM'de saklanan orijinal veriyi değiştirmez.

#### :arrow\_forward:<mark style="color:$info;">Akış Nasıl Çalıştırılır ve Dış Sistemlerle Nasıl Paylaşılır?</mark>

Akış ayarları ve alan eşleştirme işlemleri tamamlandıktan sonra akışınızı kullanabilirsiniz.

Akış çalıştırıldığında sistem, seçilen ürün verilerini belirlenen ayarlara göre hazırlar ve farklı çıktı formatlarında bağlantılar oluşturur. Lidia PIM’de akış çıktısı **JSON**, **XML** ve **CSV** formatlarında kullanılabilir.

Örnek bağlantı:

<div data-with-frame="true"><figure><img src="/files/2zZVwQ1u2lvJGOebqIsT" alt=""><figcaption></figcaption></figure></div>

Hedef sistem hangi formatı destekliyorsa ilgili bağlantıyı kopyalayarak platforma ekleyebilir veya entegrasyon süreçlerinde kullanabilirsiniz.

Örnek çıktı:

<div data-with-frame="true"><figure><img src="/files/QNs5VbQaeGTZxjczGRk9" alt=""><figcaption></figcaption></figure></div>


# PIM User Guide

Welcome to the **Lidia PIM User Guide**! This guide provides comprehensive documentation to help you navigate and utilize Lidia PIM efficiently. Whether you're a new user or an experienced administrator, you will find all the essential information here.

{% hint style="info" %}
**Tip:** Use the left menu to quickly jump to different sections of the guide. If you're new to Lidia PIM, start with the **Getting Started** section.
{% endhint %}

{% hint style="warning" %}
🔍 **Looking for something specific?** Use the search bar at the top to find exact topics faster!
{% endhint %}

| [**Getting Started**](/products/lidia-pim/pim-user-guide/getting-started)                             | Introduction                  | Introduction to Lidia PIM and its key functionalities.              |
| ----------------------------------------------------------------------------------------------------- | ----------------------------- | ------------------------------------------------------------------- |
|                                                                                                       | Homepage                      | Overview of the main dashboard and its components.                  |
|                                                                                                       | Left menu navigation          | Explanation of the primary navigation menu structure.               |
|                                                                                                       | Account information           | Managing user account details and preferences.                      |
|                                                                                                       | Organization details          | Configuring company information and metadata.                       |
| [**Settings**](/products/lidia-pim/pim-user-guide/settings)                                           | Authorization                 | Managing user roles, permissions, and access control in Lidia PIM.  |
|                                                                                                       | **Contacts**                  | Listing and managing users associated with the PIM system.          |
|                                                                                                       | **Catalog settings**          | Structuring and organizing product data for efficient management.   |
|                                                                                                       | **Channels**                  | Managing product data distribution across multiple sales platforms. |
|                                                                                                       | **Tags**                      | Assigning and managing labels for products, categories, and brands. |
|                                                                                                       | Localizations                 | Adapting product data for different languages and regions.          |
| [**Notifications**](/products/lidia-pim/pim-user-guide/notifications)                                 | Notification center           | Viewing and filtering alerts and system messages.                   |
|                                                                                                       | Notification setting          | Enabling and managing system notifications.                         |
| [**Organization**](/products/lidia-pim/pim-user-guide/organization)                                   | Organization details          | Managing company details and metadata.                              |
|                                                                                                       | Subscriptions                 | Viewing and managing subscription plans.                            |
|                                                                                                       | Lidia applications            | Integrating external applications with Lidia PIM.                   |
| [**Catalog**](/products/lidia-pim/pim-user-guide/catalog)                                             | Pools                         | Structuring and organizing pools.                                   |
|                                                                                                       | Categories                    | Structuring and organizing products into categories.                |
|                                                                                                       | Trademarks                    | Managing product brands and trademarks.                             |
|                                                                                                       | Product lists                 | Creating curated product lists.                                     |
|                                                                                                       | Products                      | Adding, editing, and managing product data.                         |
|                                                                                                       | Variants                      | Handling product variations (size, color, etc.).                    |
| [**Inventory**](/products/lidia-pim/pim-user-guide/inventory)                                         | Price lists                   | Defining and managing different pricing structures.                 |
| [**Digital Asset Management (DAM)**](/products/lidia-pim/pim-user-guide/digital-asset-management-dam) | Media list                    | Centralized repository for images, videos, and files.               |
|                                                                                                       | Bulk media upload             | Uploading multiple media files simultaneously.                      |
|                                                                                                       | Image & file management       | Organizing product media with metadata.                             |
| [**Feeds**](/products/lidia-pim/pim-user-guide/feeds)                                                 | Creating feeds                | Setting up product data feeds for external platforms.               |
|                                                                                                       | Feed filters & data selection | Customizing feeds based on categories and attributes.               |
|                                                                                                       | Data package configuration    | Defining the scope of exported product information.                 |
|                                                                                                       | Access control                | Managing security and access permissions for feeds.                 |
| [**Reporting**](/products/lidia-pim/pim-user-guide/reporting)                                         | Audit logs                    | Tracking system changes and user actions.                           |


# Getting Started

Getting Started

To begin, visit <https://pim.lidiacommerce.com/>. You will be greeted by the login screen, where you can log in using your assigned email and password.

Once logged in, you will be redirected to the homepage.

### Homepage

The homepage is the first screen encountered when logging into Lidia PIM. On this screen, management processes can be performed from the left menu, account information and organizations can be viewed, and the language can be changed.

The homepage consists of the following sections:

* **Catalog Data Quality**: Provides an overview of the quality of product data, highlighting missing or incomplete information that may require attention to ensure data accuracy and consistency.
* **Product Status**: Displays the current state of products within the system, including whether they are in draft, pending approval, published, or inactive. This section helps users track the progress of product information management.
* **Product Families**: Organizes products into predefined groups based on shared attributes and characteristics, enabling efficient management of similar product types.
* **Data Pools**: Represents collections of product data that can be processed, enriched, and published to various channels. This section helps manage product information before it is distributed.
* **Categories**: Defines the hierarchical structure of the product catalog, allowing products to be organized into logical groups based on industry standards or company-specific classifications.
* **Custom Lists**: Allows users to create and manage personalized product groupings based on specific criteria, enabling better segmentation and filtering of product data.
* **Trademarks**: Manages registered brand names and logos associated with products, ensuring accurate brand representation across various sales and marketing channels.
* **Channels and Feeds**: Handles the distribution of product data to external platforms such as e-commerce websites, marketplaces, and other third-party systems. Users can configure channels and set up feeds to automate data exports.

This structure provides users with a comprehensive view of their product information and its distribution, ensuring efficient and accurate product data management.

### Left Menu

The left menu contains sections for managing the PIM system.

<figure><img src="/files/Jhytetz2hKkfQugQZcj8" alt=""><figcaption><p>Left Menu</p></figcaption></figure>

### Left Menu Navigation

* [**Settings**](/products/lidia-pim/pim-user-guide/settings)\
  Access system preferences, user roles, and general configurations.
* [**Notification Center**](/products/lidia-pim/pim-user-guide/notifications)\
  View and manage system notifications, alerts, and updates.
* [**My Organization**](/products/lidia-pim/pim-user-guide/organization)\
  Manage organization details, user roles, and active subscriptions.
* [**Catalog**](/products/lidia-pim/pim-user-guide/catalog)\
  Browse and manage product data, categories, and attributes.
* [**Inventory Management**<br>](/products/lidia-pim/pim-user-guide/inventory)Monitor and control stock levels, warehouse details, and product availability.
* [**Media Management**](/products/lidia-pim/pim-user-guide/digital-asset-management-dam)\
  Upload, organize, and manage product images, videos, and digital assets.
* [**Services**](/products/lidia-pim/pim-user-guide/feeds)\
  Access additional features and integrations related to the PIM system.
* [**Reports**](/products/lidia-pim/pim-user-guide/reporting)\
  Generate and view analytics and performance reports.

## Account Information

To modify account details, organizations, or the language setting, click on the profile section in the top-right corner.

In the user information section, the following details can be updated:

* Profile picture
* First and last name
* Email address
* Phone number
* Password update

## Organization Details

Under organization details, users can:

* Update the organization name and description
* View active organization subscriptions
* Manage organization users (only users with the "Application Administrator" role can be created and updated)
* View existing Lidia applications (Console, Merchant Console, etc.)


# Settings

The **Settings** section contains pages where PIM users can configure and manage system-wide settings. These settings enable effective platform management and customization.

## **Authorization**

The **Authorization** section includes pages where user roles and permissions are defined and managed within the PIM system. It consists of two main categories:

* **Users**: The **Users** page displays a list of all registered users in the PIM system. Users can be viewed in detail, updated, deleted, and filtered based on their status.
* **Roles**: The **Roles** page lists predefined roles and the number of active users assigned to each role. New roles can be created, and existing roles, including admin roles, can be edited. Permissions for specific pages can also be adjusted, and inactive roles can be deleted.

## **Contacts**

The **Contacts** section allows listing and managing defined users within the PIM system. User details and access permissions can be modified from this section.

## **Catalog**

The **Catalog** menu includes pages used to organize, manage, and maintain product data.

* **Product Families**: The **Product Families** page is used to group products with similar characteristics. For example, an electronics store may create product families such as **"Phones"** or **"Computers"**.
* **Collections**: The **Collections** section allows users to view existing collections and create new ones.

### **Properties**

The **Properties** menu defines specific attributes for products, allowing for more detailed product descriptions. It is divided into two subsections:

* **Properties**: This page defines and manages product attributes such as **"128 GB Storage"** under **"Disk Capacity"**.
* **Property Groups**: **Property Groups** categorize similar properties, such as **"Technical Specifications"** or **"Dimensions,"** for better organization.

### **Options**

The **Options** menu manages additional product customizations and variations. It consists of three subsections:

* **Options**: The **Options** page defines product variations such as different colors or sizes.
* **Option Groups**: **Option Groups** categorize similar options, such as **"Colors"** or **"Sizes,"** for better management.
* **Option Value Groups**: **Option Value Groups** store possible values for a specific option. For example, the **"Colors"** group may contain values like **"Red,"** **"Blue,"** and **"Green."**

### **Data Locks**

The **Data Locks** page prevents accidental modifications of critical data, such as product information or pricing.

### **Product Relations**

**Product Relations** allow linking products to define different types of relationships, including:

* **Main and Sub-Product Relationship**
* **Related Product Relationship**
* **Accessory Product Relationship**

### **Category Dimensions**

**Category Dimensions** streamline product navigation within the PIM system by creating filters for product categories.

## **Channels**

In **PIM systems, Channels** define where product data is managed and made available for different sales platforms, marketplaces, e-commerce stores, retail locations, and social media platforms. **Channels** ensure that product data is correctly formatted, optimized, and distributed according to the specific requirements of each platform.

By using **Channels**, businesses can ensure that products are published with accurate and up-to-date information, improving customer experience and sales performance. **Channels** also enable product data tracking, updates, and reporting for each platform.

## **Tags**

**Tags** provide a centralized area where labels assigned to products, categories, brands, and lists are managed.

## **Localizations**

**Localization** refers to adapting products and services to specific markets or regions based on cultural, linguistic, and geographic factors. The **Localization** menu consists of four sections:

* **Multi-Language**: Languages can be centrally defined in the PIM system, allowing product data to be translated and managed in multiple languages.
* **Multi-Currencies**: Currency management ensures that product pricing lists are maintained in multiple currencies, with exchange rates managed centrally.
* **Units of Measures**: Measurement unit management allows products to have centrally managed dimensions and weight units, ensuring consistency across product data.


# Notifications

## **Notification Center in PIM System**

The **Notification Center** in the PIM system allows users to customize and manage notifications for various platform operations. Users can configure which updates they want to receive notifications for and view past notifications related to product data, catalog updates, and system changes.

***

### **Notifications Page**

The **Notifications** page provides an overview of all system notifications, helping users track updates and changes in real time. The key features of this page include:

* **Search and Filter Options**
  * Users can search for specific notifications by keywords.
  * Filters allow sorting notifications by **Notification Type** and **Date**.
* **Unread Notifications Toggle**
  * Users can choose to display only unread notifications for better focus.
* **Notification Entries**
  * Each notification includes details such as:
    * **Event Type** (e.g., "Custom list updated," "Data schema updated")
    * **User or System Action** (e.g., "Aysu Acar has updated the 'Minimalist Bathroom Furniture' custom list.")
    * **Date of Update**
* **Mark All as Read**
  * Users can mark all notifications as read to clear alerts.

<figure><img src="/files/1qg4PLURfMgyw0MIWz20" alt=""><figcaption></figcaption></figure>

***

### **Notification Settings Page**

The **Notification Settings** page enables users to select the types of notifications they wish to receive. The available notification categories include:

* **Catalog Notifications**
  * **Product and Variant Notifications**: Users can receive notifications when a product or variant is updated.
  * **Tag Updates**: Users can be notified when product tags are added, removed, or updated.
* **Data Schema Notifications**
  * Users are notified when a new data schema is added, updated, or removed.
* **Property Notifications**
  * Notifications are sent when a new property is added, updated, or removed.
* **Option Notifications**
  * Users receive updates when options or option values are added, removed, or modified.
* **Tag Notifications**
  * Users can enable notifications for when tags are added, updated, or removed.
* **Category Notifications**
  * Notifications for category additions, removals, or updates.
* **Trademark Notifications**
  * Users can receive alerts when trademarks are added, removed, or modified.
* **Custom List Notifications**
  * Users are notified when a new custom list is created, modified, or deleted.

The **Save Changes** button allows users to confirm their notification preferences.

<figure><img src="/files/aNqJP5ZnqyszezTn13SA" alt=""><figcaption><p>Settings</p></figcaption></figure>

This structured notification system ensures that users stay informed about critical updates while allowing them to customize their preferences for a streamlined experience.


# Organization

The **My Organization** section in the PIM system allows users to manage their organization’s details, subscriptions, and linked Lidia applications. This section ensures that companies can maintain control over their organization settings, manage access, and integrate essential applications.

***

## **Details Page**

The **Details** page displays key information about the organization, allowing administrators to manage its status and metadata. The fields available on this page include:

* **Status**
  * Indicates whether the organization is active or inactive.
* **Organization Domain**
  * Displays the domain name associated with the organization.
* **Organization Type**
  * Defines the type of organization (e.g., **Standard**).
* **Organization Code**
  * Displays a unique organization identifier (if applicable).
* **Company Name** *(Required)*
  * Specifies the official name of the company.
* **Description** *(Required)*
  * Provides a brief description of the company.

Users can **Save** any modifications or **Cancel** changes.

<figure><img src="/files/3rYMT8EbnADuBtP1qlqt" alt=""><figcaption><p>Organizastion Detail</p></figcaption></figure>

***

## **Subscriptions Page**

The **Subscriptions** page allows organizations to manage their active subscriptions within the PIM system. Key functionalities of this page include viewing **active and inactive** subscriptions.

This page ensures that organizations maintain proper access levels based on their subscription plan.

***

## **Lidia Applications Page**

The **Lidia Applications** page provides an overview of integrated Lidia applications available for the organization. Organizations can:

* **View available applications** that enhance their product information management.
* **Enable or disable integrations** with specific Lidia applications.
* **Manage API access** and credentials for connected applications.
* **Monitor application usage** and permissions.

This page ensures seamless integration between PIM and other essential Lidia Commerce tools.


# Catalog

The **Catalog** section within the PIM system is designed to **organize, manage, and structure** product data efficiently. It includes six key areas:

1. **Pools**
2. **Categories**
3. **Trademarks**
4. **Lists**
5. **Products**
6. **Variants**

Each of these sections plays a crucial role in structuring and maintaining product information.

***

### **Pools**

The **Pools** section allows users to create **product groups** by defining specific categories related to them. It serves as a structured **data repository** where products are classified based on their relevance.

* Pools can **group products by characteristics** such as **material type, product usage, or function.**
* Helps in **bulk management** and **categorization of large datasets.**
* Each pool can have **multiple associated categories.**
* Users can **view, update, and manage** product pools easily.

Example: A **"Bathroom Accessories"** pool might contain related categories like **mirrors, soap dispensers, and towel holders.**

### **Categories**

The **Categories** section enables users to classify products into **hierarchical groups** for better organization.

* Categories allow for **structuring products** based on **shared attributes.**
* Each category can contain **subcategories**, making navigation and filtering easier.
* Users can view details such as **total products, active status, and assigned subcategories.**
* Categories are essential for **product discoverability in e-commerce platforms.**

Example Category Structure:

* **Electronics**
  * Laptops
  * Mobile Phones
  * Televisions
* **Home & Living**
  * Furniture
  * Kitchen Appliances
  * Home Decor

Categories ensure that **products are well-organized and easy to find**, improving usability for both customers and administrators.

### **Trademarks**

The **Trademarks** section is responsible for managing **brands and manufacturers** associated with products.

* Each trademark (brand) can be assigned to **multiple products.**
* The system allows **creating, editing, and deleting** trademarks.
* Products under each trademark are **listed and categorized.**
* Sub-trademarks can be managed under parent brands.

Example:

* **Trademark: Apple**
  * Products: iPhones, MacBooks, iPads
* **Trademark: Samsung**
  * Products: Galaxy Phones, Smart TVs, Refrigerators

This section helps maintain **brand identity and consistency** across the product catalog.

### **Lists**

The **Lists** section is used for **custom product groupings** based on business needs.

* Users can create **custom lists** for **specific marketing campaigns, seasonal promotions, or internal tracking.**
* Lists can contain **selected products, categories, or variants.**
* Helps in efficiently managing **exclusive product collections** within the system.

Example Lists:

* **"Best Sellers"** – Featuring the top-selling products.
* **"Holiday Specials"** – Seasonal discounts and limited-time products.

This feature is useful for **e-commerce marketing and inventory planning.**

***

### **Products**

The **Products** section is where all **product information** is stored and managed.

* Users can **view, edit, and delete** products.
* Products can be assigned **categories, trademarks, prices, and media assets.**
* Allows bulk product imports and exports.
* Supports **product relationships** (e.g., **main product and accessories**).
* Each product has the following **main data sections**:
  * **Main Information**
  * **Variants**
  * **Properties**
  * **Related Products**
  * **Media Management**
  * **Pricing**

This section ensures that **products are structured and enriched with relevant data** for sales and marketing.

### **Variants**

The **Variants** section manages **product variations** such as **different sizes, colors, or materials**.

* Each product can have multiple **variants** grouped under it.
* Variants share **common attributes** with the main product but have **unique identifiers.**
* Useful for products that have **multiple configurations**.
* Supports **bulk updates** and filtering by trademark, category, and status.

Example:

* **Product: Running Shoes**
  * Variant 1: Size 9, Red
  * Variant 2: Size 10, Blue
  * Variant 3: Size 11, Black

The **Variants** section helps streamline **product customization and inventory management.**


# Inventory

The **Inventory Management** section in the PIM system provides tools to manage and organize product-related inventory details, including **price lists** and variant pricing.

***

### **Price Lists**

The **Price Lists** page displays all available pricing lists in the system and allows users to manage them efficiently.

* Users can **view, edit, and delete** price lists.
* Each price list contains **specific pricing details** for products and their variants.
* Pricing lists are **categorized with unique codes** for easy identification.
* Users can **filter, sort, and group** price lists based on various attributes.

#### **Key Features:**

* **List ID**: Unique identifier for each price list.
* **Name**: The descriptive name of the price list.
* **Code**: Short code representation of the price list.
* **Status**: Indicates if the price list is **active** or inactive.


# Digital Asset Management (DAM)

The **Digital Asset Management (DAM) module** in **Lidia PIM** provides a centralized system for **storing, organizing, and managing digital assets** such as **images, videos, documents, and product-related media**. It ensures seamless integration with **product data management**, allowing businesses to maintain a structured and accessible digital asset repository.

***

## **Key Features of Lidia PIM’s DAM System**

### **Centralized Asset Management**

The DAM system within **Lidia PIM** acts as a **single source of truth** for all digital assets. It supports:

* **Storage & Retrieval** of product-related media.
* **Categorization & Folder Structuring** for better asset organization.
* **Bulk Management Capabilities** for uploading and handling multiple assets at once.

### **Bulk Media Upload & Validation**

* Users can **upload multiple assets simultaneously**, reducing manual effort.
* Supports **image, video, document, and custom file formats**.
* **Validation mechanisms** ensure correct file types, dimensions, and quality.

### **Media Categories & Organization**

The DAM module in **Lidia PIM** segments digital assets into structured categories:\
**Product Media** – Images and videos associated with specific products.\
**Trademark Media** – Brand-related assets such as logos and branding materials.\
**Category Media** – Visuals linked to product categories.\
**Document Management** – PDFs, brochures, and technical files stored for reference.

This **categorization** allows for **quick retrieval and efficient media organization**.

***

### **Asset Metadata & Searchability**

* Digital assets are indexed with **metadata** such as **file type, size, labels, and associations**.
* Users can **search, filter, and sort** media files based on various attributes.
* **Batch actions** allow for bulk editing and management of media assets.

***

### **Folder-Based Organization & Structured Storage**

The DAM module supports **hierarchical folder structuring**, enabling:

* **Custom folders** for different product lines, brands, or content types.
* **Drag-and-drop functionality** for organizing files efficiently.
* **Role-based access management** for different teams handling assets.

### **File Management & Document Handling**

The **document storage system** within DAM allows businesses to:

* **Upload, track, and manage PDF files, datasheets, and manuals**.
* **Categorize documents based on usage**, such as **marketing materials, technical guides, and compliance documents**.
* **Filter and group** files by type, format, and assigned labels.

Documents are **easily accessible**, ensuring that product-related resources are well-maintained.

***

### **Image & Video Management**

* **Dedicated sections** for managing product images and promotional visuals.
* Supports **high-resolution images** for e-commerce and marketing use.
* **Batch upload & file structuring** for product photography.
* Enables **video file storage** for tutorials, advertisements, and demonstrations.


# Feeds

The **Feeds module** in Lidia PIM enables businesses to **distribute product data** to **third-party platforms** by creating **customizable data feeds**. Feeds act as a **bridge** between the PIM system and external systems such as **marketplaces, e-commerce platforms, ERP systems, and marketing tools**.

***

### **Feed Management Overview**

The **Feeds page** provides a centralized interface where users can:

* **Create, edit, and delete feeds** for external integrations.
* **View active and inactive feeds** along with their details.
* **Define feed URLs** for seamless data synchronization.
* **Monitor product counts associated with each feed.**

Each feed contains:\
**Feed Name** – The identifier for the feed.\
**URL** – The endpoint where the data is made available.\
**Format** – The data structure (e.g., JSON, XML).\
**Feed Code** – A unique code for the feed.\
**Product Count** – The number of products included in the feed.\
**Status** – Indicates whether the feed is active or inactive.

Users can add **new feeds** by clicking on the **"Add New Feed"** button

***

### **Feed Configuration & Customization**

When creating or editing a feed, users can define several key parameters:

#### **Basic Information**

* **Feed Status:** Set the feed as **Active or Inactive**.
* **Feed Code:** A unique identifier for the feed.
* **Feed Format:** The data format used for integration (e.g., JSON, XML).
* **Access Control:** Manage authorization and access settings for the feed.
* **Feed URL:** The endpoint for retrieving product data.

### **Filtering Data for Feeds**

Lidia PIM allows users to **customize the product data included in each feed** using **filtering options**. This ensures that **only relevant products** are exported to third-party systems.

#### **Available Filters:**

* **Categories:** Include only products from specific categories.
* **Brands:** Restrict the feed to selected brands.
* **Special Lists:** Add products from pre-defined custom lists.
* **Product Properties:** Include products with specific attributes (e.g., "Material: 100% Leather").
* **Variant Properties:** Define feeds based on product variations.
* **Option Values:** Filter products by options like **color, size, or configuration**.
* **Tags:** Select only products with specific labels or tags.

Negative filters can also be applied to **exclude** certain products from the feed.

***

### **Data Package & Collections**

The **Data Package** defines the **extent of product data** included in the feed. Users can:

* Choose **which collections** should be part of the feed.
* Include **category dimensions** to enhance product classification.

#### **How Feed Data is Generated:**

1. **The system applies the selected filters** to retrieve relevant product data.
2. **Products are enriched with their properties, options, and tags** unless they are excluded by filters.
3. **If collections are included, the system adds extra product attributes** based on the defined collections.

***

### **Authorization & Data Access**

Feeds in Lidia PIM can be protected using **access keys**, ensuring that **only authorized systems** can access the product data. Users can:

* **Generate new authorization keys** for secure data sharing.
* **Restrict access** to prevent unauthorized use.


# Reporting

The **Audit Report** page in **Lidia PIM** provides a comprehensive **log of system activities**, ensuring transparency and traceability for all actions performed within the platform. This feature is essential for **tracking changes, monitoring updates, and maintaining data integrity**.

***

## **Audit Logs Overview**

The **Audit Logs** section displays a **detailed history of system events**, allowing users to **track modifications and operations** performed on different data entities.

### **Key Data Points in Audit Logs:**

**Log ID** – A unique identifier for each audit entry.\
**Event Type** – Describes the nature of the action (e.g., **Update, Create, Delete, Other**).\
**Entity Type** – Specifies the category of data affected (e.g., **Data Pool, Product, Category**).\
**Entity ID** – The unique identifier of the modified data entity.\
**Message** – Provides a summary of the performed action.\
**Created Date** – The timestamp indicating when the action occurred.

These logs enable **administrators and auditors** to **review historical changes** and ensure **compliance with internal policies and external regulations**.

### **Features & Functionality**

* **Search & Filter Options**
  * Users can **filter logs based on event type, entity type, or specific entity IDs**.
  * Sorting capabilities allow logs to be **organized by date or event type**.
* **Grouping & Sorting**
  * Users can **drag and drop column headers** to group logs based on specific attributes.
  * This enhances **data visibility** and makes it easier to analyze related audit entries.
* **Log Details & Insights**
  * Each entry contains a **detailed message** describing the change.
  * Logs can be expanded to **view additional details about the modifications**.


# Turkish

Lidia Commerce ürün ailesine ait Lidia PIM ürününün Türkçe kılavuzudur.

Başlarken

Başlamak için <https://pim.lidiacommerce.com/> adresini ziyaret edin. Giriş ekranı ile karşılaşacaksınız. Size atanmış e-posta ve şifre ile giriş yapabilirsiniz.\
Giriş yaptıktan sonra ana sayfaya yönlendirileceksiniz.

### Ana Sayfa

Ana sayfa, Lidia PIM’e giriş yaptığınızda karşılaştığınız ilk ekrandır. Bu ekranda sol menüden yönetim işlemleri yapılabilir, hesap bilgileri ve organizasyonlar görüntülenebilir, ayrıca dil değiştirilebilir.

Ana sayfa aşağıdaki bölümlerden oluşur:

* **Katalog Veri Kalitesi**: Ürün verilerinin kalitesine genel bir bakış sunar ve eksik veya tamamlanmamış bilgileri vurgular. Bu sayede verilerin doğruluğu ve tutarlılığı sağlanabilir.
* **Ürün Durumu**: Sistemdeki ürünlerin mevcut durumunu gösterir. Ürünlerin taslak, onay bekliyor, yayınlanmış veya pasif olup olmadığını takip etmeye yardımcı olur.
* **Ürün Aileleri**: Ürünleri, ortak özelliklere ve kategorilere göre önceden tanımlanmış gruplara ayırır. Benzer ürün türlerini daha verimli yönetmeyi sağlar.
* **Veri Havuzları**: Ürün verilerinin işlenebileceği, zenginleştirilebileceği ve çeşitli kanallara yayınlanabileceği veri koleksiyonlarını temsil eder.
* **Kategoriler**: Ürün kataloğunun hiyerarşik yapısını belirler. Ürünlerin sektör standartlarına veya şirket içi sınıflandırmalara göre düzenlenmesini sağlar.
* **Özel Listeler**: Belirli kriterlere dayalı olarak kişiselleştirilmiş ürün grupları oluşturmayı ve yönetmeyi sağlar. Böylece ürün verilerinin daha iyi segmentasyonu ve filtrelenmesi mümkündür.
* **Markalar**: Ürünlerle ilişkili tescilli marka adlarını ve logoları yönetir. Bu, marka kimliğinin farklı satış ve pazarlama kanallarında doğru şekilde sunulmasını sağlar.
* **Kanallar ve Akışlar**: Ürün verilerinin e-ticaret siteleri, pazar yerleri ve diğer üçüncü taraf sistemlere aktarılmasını yönetir. Kullanıcılar kanalları yapılandırabilir ve veri akışlarını otomatikleştirmek için ayarlamalar yapabilir.

Bu yapı, kullanıcıların ürün bilgilerini ve dağıtım süreçlerini daha verimli yönetmesine yardımcı olur.

### Sol Menü

Sol menü, PIM sistemini yönetmek için kullanılan bölümleri içerir.

#### **Sol Menü Navigasyonu**

* **Ayarlar**: Sistem tercihlerini, kullanıcı rollerini ve genel yapılandırmaları yönetin.
* **Bildirim Merkezi**: Sistem bildirimlerini, uyarıları ve güncellemeleri görüntüleyin ve yönetin.
* **Organizasyonum**: Organizasyon detaylarını, kullanıcı rollerini ve aktif abonelikleri yönetin.
* **Katalog**: Ürün verilerini, kategorileri ve nitelikleri görüntüleyin ve yönetin.
* **Stok Yönetimi**: Stok seviyelerini, depo bilgilerini ve ürün bulunabilirliğini takip edin.
* **Medya Yönetimi**: Ürün görsellerini, videolarını ve dijital varlıkları yükleyin, organize edin ve yönetin.
* **Hizmetler**: PIM sistemiyle ilgili ek özelliklere ve entegrasyonlara erişin.
* **Raporlar**: Analiz ve performans raporlarını oluşturun ve görüntüleyin.

<figure><img src="/files/Jhytetz2hKkfQugQZcj8" alt=""><figcaption><p>Left Menu</p></figcaption></figure>

***

### **Hesap Bilgileri**

Hesap bilgilerini, organizasyon detaylarını veya dili değiştirmek için sağ üst köşedeki profil bölümüne tıklayın.

#### **Kullanıcı Bilgileri**

Aşağıdaki bilgiler güncellenebilir:

* Profil fotoğrafı
* Ad ve soyad
* E-posta adresi
* Telefon numarası
* Şifre güncelleme

#### **Organizasyon Bilgileri**

Organizasyon detayları altında kullanıcılar şunları yapabilir:

* Organizasyon adını ve açıklamasını güncelleme
* Aktif organizasyon aboneliklerini görüntüleme
* Organizasyon kullanıcılarını yönetme (Sadece "Uygulama Yöneticisi" rolüne sahip kullanıcılar yeni kullanıcı oluşturabilir ve mevcut kullanıcıları güncelleyebilir.)
* Mevcut Lidia uygulamalarını görüntüleme (Console, Merchant Console vb.)

Bu yapı sayesinde kullanıcılar hesap bilgilerini ve organizasyonlarını kolayca yönetebilirler.

## Ayarlar

Ayarlar bölümü, PIM kullanıcılarının sistem genelindeki ayarları yapılandırmasına ve yönetmesine olanak tanıyan sayfaları içerir. Bu ayarlar, platform yönetimini ve özelleştirmesini etkili bir şekilde sağlamaya yardımcı olur.

### **Yetkilendirme**

Yetkilendirme bölümü, PIM sisteminde kullanıcı rolleri ve izinlerinin tanımlandığı ve yönetildiği sayfalardan oluşur. İki ana kategoriye ayrılır:

* **Kullanıcılar**: Kullanıcılar sayfası, PIM sistemine kayıtlı tüm kullanıcıların listesini gösterir. Kullanıcılar detaylı olarak görüntülenebilir, güncellenebilir, silinebilir ve durumlarına göre filtrelenebilir.
* **Roller**: Roller sayfası, önceden tanımlanmış rolleri ve her role atanmış aktif kullanıcı sayısını listeler. Yeni roller oluşturulabilir, mevcut roller (yönetici rolleri dahil) düzenlenebilir. Belirli sayfalara ait izinler ayarlanabilir ve pasif roller silinebilir.

### **Kişiler**

Kişiler bölümü, PIM sisteminde tanımlanmış kullanıcıların listelenmesine ve yönetilmesine olanak tanır. Bu bölümden kullanıcı detayları ve erişim izinleri değiştirilebilir.

***

### **Katalog**

Katalog menüsü, ürün verilerini düzenlemek, yönetmek ve sürdürmek için kullanılan sayfaları içerir.

* **Ürün Aileleri**: Ürün Aileleri sayfası, benzer özelliklere sahip ürünleri gruplamak için kullanılır. Örneğin, bir elektronik mağazası "Telefonlar" veya "Bilgisayarlar" gibi ürün aileleri oluşturabilir.
* **Koleksiyonlar**: Koleksiyonlar bölümü, mevcut koleksiyonları görüntülemeye ve yeni koleksiyonlar oluşturmaya olanak tanır.

#### **Özellikler**

Özellikler menüsü, ürünler için belirli nitelikler tanımlayarak daha ayrıntılı ürün açıklamaları yapılmasını sağlar. İki alt bölüme ayrılır:

* **Özellikler**: Bu sayfa, "Disk Kapasitesi" altında "128 GB Depolama" gibi ürün özelliklerini tanımlamak ve yönetmek için kullanılır.
* **Özellik Grupları**: Benzer özellikleri "Teknik Özellikler" veya "Boyutlar" gibi kategorilere ayırarak daha iyi bir organizasyon sağlar.

***

#### **Seçenekler**

Seçenekler menüsü, ek ürün özelleştirmelerini ve varyasyonlarını yönetmek için kullanılır. Üç alt bölüme ayrılır:

* **Seçenekler**: Ürünlerin farklı renk veya beden gibi varyasyonlarını tanımlar.
* **Seçenek Grupları**: Benzer seçenekleri gruplandırarak (örneğin "Renkler" veya "Bedenler") daha kolay yönetim sağlar.
* **Seçenek Değer Grupları**: Belirli bir seçenek için olası değerleri saklar. Örneğin, "Renkler" grubu içinde "Kırmızı", "Mavi" ve "Yeşil" gibi değerler bulunur.

***

#### **Veri Kilitleme**

Veri Kilitleme sayfası, ürün bilgileri veya fiyatlandırma gibi kritik verilerin yanlışlıkla değiştirilmesini önler.

***

#### **Ürün İlişkileri**

Ürün İlişkileri, ürünler arasındaki bağlantıları tanımlamak için kullanılır. Farklı türde ilişkiler oluşturulabilir:

* **Ana ve Alt Ürün İlişkisi**
* **İlgili Ürün İlişkisi**
* **Aksesuar Ürün İlişkisi**

***

#### **Kategori Boyutları**

Kategori Boyutları, PIM sisteminde ürün kategorileri için filtreler oluşturarak ürünlerin daha iyi yönetilmesini sağlar.

***

### **Kanallar**

PIM sistemlerinde **Kanallar**, ürün verilerinin farklı satış platformları, pazar yerleri, e-ticaret siteleri, fiziksel mağazalar ve sosyal medya platformlarında nasıl yönetileceğini ve sunulacağını tanımlar.

Kanallar, ürün verilerinin her platformun özel gereksinimlerine göre doğru formatta, optimize edilmiş ve güncel bir şekilde dağıtılmasını sağlar.\
Bu sayede işletmeler:

* Ürünlerin doğru ve güncel bilgilerle yayınlanmasını sağlayarak müşteri deneyimini ve satış performansını artırabilir.
* Ürün verilerini her platform için takip edebilir, güncelleyebilir ve raporlayabilir.

***

### **Etiketler**

Etiketler, ürünlere, kategorilere, markalara ve listelere atanan etiketlerin yönetildiği merkezi bir alan sağlar.

***

### **Yerelleştirme**

Yerelleştirme, ürünlerin ve hizmetlerin kültürel, dilsel ve coğrafi faktörlere göre belirli pazarlara uyarlanmasını ifade eder. **Yerelleştirme menüsü** dört bölümden oluşur:

* **Çoklu Dil**: PIM sisteminde diller merkezi olarak tanımlanabilir, böylece ürün verileri birden fazla dilde çevrilebilir ve yönetilebilir.
* **Çoklu Para Birimi**: Para birimi yönetimi, ürün fiyatlandırma listelerinin birden fazla para biriminde tutulmasını sağlar ve döviz kurları merkezi olarak yönetilir.
* **Ölçü Birimleri**: Ölçü birimi yönetimi, ürünlerin boyut ve ağırlık gibi ölçümlerinin tutarlı bir şekilde yönetilmesini sağlar.

***

Bu yapı, kullanıcıların PIM sistemindeki ürün verilerini ve yönetim süreçlerini daha verimli ve düzenli bir şekilde kontrol etmelerine yardımcı olur.

## Bildirimler

PIM sistemindeki **Bildirim Merkezi**, kullanıcıların çeşitli platform işlemleri için bildirimleri özelleştirmesine ve yönetmesine olanak tanır. Kullanıcılar hangi güncellemeler için bildirim almak istediklerini yapılandırabilir ve ürün verileri, katalog güncellemeleri ve sistem değişiklikleriyle ilgili geçmiş bildirimleri görüntüleyebilirler.

***

### **Bildirimler Sayfası**

**Bildirimler Sayfası**, tüm sistem bildirimlerine genel bir bakış sunarak kullanıcıların güncellemeleri ve değişiklikleri gerçek zamanlı olarak takip etmelerini sağlar. Bu sayfanın temel özellikleri şunlardır:

#### **Arama ve Filtreleme Seçenekleri**

* Kullanıcılar belirli bildirimleri anahtar kelimelerle arayabilir.
* Filtreler sayesinde bildirimler **Bildirim Türü** ve **Tarih** bazında sıralanabilir.

#### **Okunmamış Bildirimler Filtreleme**

* Kullanıcılar sadece **okunmamış bildirimleri** görüntülemeyi seçerek önemli güncellemelere daha iyi odaklanabilirler.

### **Bildirim Kayıtları**

Her bildirim aşağıdaki detayları içerir:

* **Olay Türü** (Örn: "Özel liste güncellendi", "Veri şeması güncellendi")
* **Kullanıcı veya Sistem İşlemi** (Örn: *"Aysu Acar, 'Minimalist Banyo Mobilyası' özel listesini güncelledi."*)
* **Güncelleme Tarihi**

**Tümünü Okundu Olarak İşaretle**

* Kullanıcılar tüm bildirimleri **okundu olarak işaretleyerek** bildirim ekranını temizleyebilirler.

### **Bildirim Ayarları Sayfası**

**Bildirim Ayarları Sayfası**, kullanıcıların hangi tür bildirimleri almak istediklerini seçmelerini sağlar. Mevcut bildirim kategorileri şunlardır:

**Katalog Bildirimleri**

* **Ürün ve Varyant Bildirimleri**: Bir ürün veya varyant güncellendiğinde bildirim alınmasını sağlar.
* **Etiket Güncellemeleri**: Ürün etiketleri eklendiğinde, kaldırıldığında veya güncellendiğinde bildirim gönderilir.

**Veri Şeması Bildirimleri**

* Yeni bir **veri şeması eklendiğinde, güncellendiğinde veya kaldırıldığında** kullanıcılar bilgilendirilir.

**Özellik Bildirimleri**

* Yeni bir **özellik** eklendiğinde, güncellendiğinde veya kaldırıldığında bildirim alınır.

**Seçenek Bildirimleri**

* **Seçenekler veya seçenek değerleri eklendiğinde, kaldırıldığında veya değiştirildiğinde** bildirim gönderilir.

**Etiket Bildirimleri**

* **Etiketler eklendiğinde, güncellendiğinde veya kaldırıldığında** bildirim alınır.

**Kategori Bildirimleri**

* **Kategori ekleme, kaldırma veya güncelleme işlemleri** için bildirimler etkinleştirilebilir.

**Marka Bildirimleri**

* **Yeni marka eklendiğinde, kaldırıldığında veya güncellendiğinde** bildirim alınabilir.

**Özel Liste Bildirimleri**

* Yeni bir **özel liste oluşturulduğunda, değiştirildiğinde veya silindiğinde** kullanıcılar bilgilendirilir.

**Değişiklikleri Kaydet**

* Kullanıcılar tercih ettikleri bildirim ayarlarını **Kaydet** düğmesi ile onaylayabilirler.

Bu yapılandırılmış **bildirim sistemi**, kullanıcıların kritik güncellemeler hakkında bilgilendirilmesini sağlarken, bildirim tercihlerini özelleştirmelerine de olanak tanır. Böylece kullanıcılar gereksiz bildirimlerden kaçınarak yalnızca önemli güncellemelere odaklanabilirler.

## Organizasyon

PIM sistemindeki **Organizasyonum** bölümü, kullanıcıların organizasyonlarına ait detayları, abonelikleri ve bağlı Lidia uygulamalarını yönetmelerine olanak tanır. Bu bölüm, şirketlerin organizasyon ayarlarını kontrol altında tutmalarını, erişimi yönetmelerini ve gerekli uygulamaları entegre etmelerini sağlar.

### **Detaylar Sayfası**

**Detaylar** sayfası, organizasyona ait temel bilgileri görüntüler ve yöneticilerin durumunu ve meta verilerini yönetmesine imkan tanır. Bu sayfadaki alanlar şunlardır:

* **Durum**\
  Organizasyonun aktif veya pasif olup olmadığını gösterir.
* **Organizasyon Alan Adı**\
  Organizasyona ait alan adını görüntüler.
* **Organizasyon Türü**\
  Organizasyonun türünü tanımlar (ör. Standart).
* **Organizasyon Kodu**\
  Organizasyona ait benzersiz bir kimlik kodunu gösterir (varsa).
* **Şirket Adı (Zorunlu)**\
  Şirketin resmi adını belirtir.
* **Açıklama (Zorunlu)**\
  Şirket hakkında kısa bir açıklama sağlar.

Kullanıcılar, yapılan değişiklikleri **Kaydet** veya **İptal** edebilirler.

### **Abonelikler Sayfası**

**Abonelikler** sayfası, organizasyonların PIM sistemindeki aktif aboneliklerini yönetmelerine olanak tanır. Bu sayfadaki temel işlevler şunlardır:

* Aktif ve pasif abonelikleri görüntüleme
* Organizasyonların, abonelik planlarına göre uygun erişim seviyelerini korumasını sağlama

### **Lidia Uygulamaları Sayfası**

**Lidia Uygulamaları** sayfası, organizasyonun entegre edebileceği Lidia uygulamalarının genel bir görünümünü sunar. Organizasyonlar şunları yapabilir:

* Ürün bilgi yönetimini geliştiren mevcut uygulamaları görüntüleme
* Belirli Lidia uygulamalarıyla entegrasyonları etkinleştirme veya devre dışı bırakma
* Bağlı uygulamalar için API erişimini ve kimlik bilgilerini yönetme
* Uygulama kullanımını ve izinlerini izleme

Bu sayfa, PIM ile diğer önemli **Lidia Commerce** araçları arasındaki entegrasyonun sorunsuz çalışmasını sağlar.

## Katalog

PIM sistemindeki **Katalog** bölümü, ürün verilerini düzenlemek, yönetmek ve yapılandırmak için tasarlanmıştır. Altı ana alan içerir:

* **Havuzlar (Pools)**
* **Kategoriler (Categories)**
* **Markalar (Trademarks)**
* **Listeler (Lists)**
* **Ürünler (Products)**
* **Varyantlar (Variants)**

Bu bölümlerin her biri, ürün bilgilerini yapılandırma ve yönetme sürecinde kritik bir rol oynar.

***

### **Havuzlar (Pools)**

**Havuzlar** bölümü, belirli kategorilere bağlı ürün grupları oluşturmayı sağlar. Yapılandırılmış bir veri deposu işlevi görerek, ürünlerin ilgili olduğu alanlara göre sınıflandırılmasına yardımcı olur.

* Ürünleri malzeme türü, kullanım amacı veya fonksiyonuna göre gruplandırabilir.
* Büyük veri kümelerini toplu yönetmeyi ve kategorize etmeyi kolaylaştırır.
* Her havuz birden fazla kategori ile ilişkilendirilebilir.
* Kullanıcılar, ürün havuzlarını görüntüleyebilir, güncelleyebilir ve yönetebilir.

**Örnek:**\
*Banyo Aksesuarları* havuzu, aynalar, sabunluklar ve havluluklar gibi ilgili kategorileri içerebilir.

***

### **Kategoriler (Categories)**

**Kategoriler** bölümü, ürünlerin hiyerarşik gruplar halinde sınıflandırılmasını sağlar ve organizasyonu kolaylaştırır.

* Ürünler, ortak özelliklere dayalı olarak yapılandırılabilir.
* Her kategori, alt kategoriler içerebilir, bu da gezinmeyi ve filtrelemeyi kolaylaştırır.
* Kullanıcılar toplam ürün sayısını, aktif durumunu ve atanmış alt kategorileri görüntüleyebilir.
* E-ticaret platformlarında ürün keşfedilebilirliğini artırır.

**Örnek Kategori Yapısı:**

* **Elektronik**
  * Dizüstü Bilgisayarlar
  * Cep Telefonları
  * Televizyonlar
* **Ev & Yaşam**
  * Mobilya
  * Mutfak Aletleri
  * Ev Dekorasyonu

Bu yapı, ürünlerin iyi organize edilmesini ve hem müşteriler hem de yöneticiler için kolay bulunmasını sağlar.

***

### **Markalar (Trademarks)**

**Markalar** bölümü, ürünlerle ilişkili markaları ve üreticileri yönetmek için kullanılır.

* Her marka, birden fazla ürüne atanabilir.
* Sistem; marka oluşturma, düzenleme ve silme işlemlerini destekler.
* Her markanın altındaki ürünler listelenebilir ve kategorize edilebilir.
* Alt markalar, ana markalar altında yönetilebilir.

**Örnek:**

* **Marka:** Apple
  * **Ürünler:** iPhone, MacBook, iPad
* **Marka:** Samsung
  * **Ürünler:** Galaxy Telefonlar, Akıllı TV’ler, Buzdolapları

Bu bölüm, marka kimliğini ve tutarlılığını ürün kataloğunda korumaya yardımcı olur.

***

### **Listeler (Lists)**

**Listeler** bölümü, işletme ihtiyaçlarına göre özel ürün grupları oluşturmayı sağlar.

* Kullanıcılar, pazarlama kampanyaları, sezonluk promosyonlar veya iç takip için özel listeler oluşturabilir.
* Listeler; belirli ürünleri, kategorileri veya varyantları içerebilir.
* Özel koleksiyonların sistem içinde etkin yönetilmesine yardımcı olur.

**Örnek Listeler:**

* **"En Çok Satanlar"** – En çok satılan ürünler listesi.
* **"Yılbaşı Özel"** – Sezonluk indirimler ve sınırlı süreli ürünler.

Bu özellik, e-ticaret pazarlaması ve stok planlaması için oldukça faydalıdır.

***

### **Ürünler (Products)**

**Ürünler** bölümü, tüm ürün bilgilerini saklamak ve yönetmek için kullanılan ana bölümdür.

* Kullanıcılar ürünleri görüntüleyebilir, düzenleyebilir ve silebilir.
* Ürünler; kategorilere, markalara, fiyatlara ve medya varlıklarına atanabilir.
* Toplu ürün içe/dışa aktarma işlemleri desteklenir.
* Ürün ilişkileri (ana ürün ve aksesuarlar) tanımlanabilir.

Her ürün şu ana veri bölümlerini içerir:

* **Ana Bilgiler**
* **Varyantlar**
* **Özellikler**
* **İlgili Ürünler**
* **Medya Yönetimi**
* **Fiyatlandırma**

Bu bölüm, ürünlerin satış ve pazarlama için yapılandırılmasını ve zenginleştirilmesini sağlar.

***

### **Varyantlar (Variants)**

**Varyantlar** bölümü, farklı beden, renk veya malzeme seçeneklerine sahip ürünleri yönetmek için kullanılır.

* Her ürün, altında birden fazla varyanta sahip olabilir.
* Varyantlar, ana ürünle ortak özellikler paylaşır ancak benzersiz kimliklere sahiptir.
* Farklı konfigürasyonlara sahip ürünler için kullanışlıdır.
* Marka, kategori ve duruma göre toplu güncelleme ve filtreleme desteklenir.

**Örnek:**

* **Ürün:** Koşu Ayakkabısı
  * **Varyant 1:** Beden 42, Kırmızı
  * **Varyant 2:** Beden 43, Mavi
  * **Varyant 3:** Beden 44, Siyah

Bu bölüm, ürün özelleştirmelerini ve stok yönetimini kolaylaştırır.

## Envanter

PIM sistemindeki **Envanter Yönetimi** bölümü, ürünle ilgili envanter detaylarını yönetmek ve organize etmek için gerekli araçları sağlar. Bu bölüm, özellikle **fiyat listeleri** ve **varyant fiyatlandırmaları** gibi konuları kapsar.

***

### **Fiyat Listeleri (Price Lists)**

**Fiyat Listeleri** sayfası, sistemde bulunan tüm fiyat listelerini görüntülemeyi ve yönetmeyi sağlar.

* Kullanıcılar fiyat listelerini görüntüleyebilir, düzenleyebilir ve silebilir.
* Her fiyat listesi, belirli ürünlerin ve varyantlarının fiyatlandırma detaylarını içerir.
* Fiyat listeleri, kolay tanımlama için benzersiz kodlarla kategorize edilir.
* Kullanıcılar, fiyat listelerini çeşitli özelliklere göre filtreleyebilir, sıralayabilir ve gruplayabilir.

**Ana Özellikler:**

* **Liste Kimliği (List ID):** Her fiyat listesi için benzersiz bir tanımlayıcı.
* **Ad (Name):** Fiyat listesinin açıklayıcı adı.
* **Kod (Code):** Fiyat listesinin kısa kod temsili.
* **Durum (Status):** Fiyat listesinin aktif veya pasif olduğunu gösterir.

Bu sayfa, fiyatlandırma stratejilerinin etkili bir şekilde yönetilmesini ve güncellenmesini sağlar.

## Medya Yönetimi

### **Merkezi Varlık Yönetimi**

Lidia PIM’in DAM sistemi, tüm dijital varlıklar için **tek bir doğruluk kaynağı** olarak işlev görür. Sağladığı temel özellikler:

* **Ürünle ilgili medya dosyalarının saklanması ve alınması**
* **Kategori ve klasör yapılandırması ile düzenli varlık yönetimi**
* **Toplu yönetim yetenekleri** sayesinde birden fazla dosyanın aynı anda yüklenmesi ve işlenmesi

***

### **Toplu Medya Yükleme & Doğrulama**

* Kullanıcılar **birden fazla varlığı aynı anda yükleyebilir**, böylece manuel işlemler azalır.
* **Resim, video, belge ve özel dosya formatları desteklenir.**
* **Dosya doğrulama mekanizmaları**, doğru dosya türlerini, boyutları ve kaliteleri kontrol ederek geçersiz yüklemeleri önler.

### **Medya Kategorileri & Organizasyon**

Lidia PIM’in DAM modülü, dijital varlıkları belirli kategorilere ayırarak düzenler:

* **Ürün Medyası:** Belirli ürünlerle ilişkili resimler ve videolar
* **Marka Medyası:** Logolar ve marka kimliğiyle ilgili varlıklar
* **Kategori Medyası:** Ürün kategorilerine bağlı görseller
* **Belge Yönetimi:** Kataloglar, PDF broşürler ve teknik dosyalar

Bu kategorilendirme, varlıkların **hızlı erişimini ve verimli yönetimini** sağlar.

***

### **Varlık Meta Verileri & Arama Kolaylığı**

* Dijital varlıklar; **dosya türü, boyutu, etiketler ve ilişkili ürünler** gibi meta verilerle indekslenir.
* Kullanıcılar, medya dosyalarını **arama, filtreleme ve sıralama** seçenekleriyle kolayca yönetebilir.
* **Toplu işlem yetenekleri**, birden fazla medya dosyasının aynı anda düzenlenmesini ve yönetilmesini sağlar.

***

### **Klasör Bazlı Organizasyon & Yapılandırılmış Depolama**

DAM modülü, **hiyerarşik klasör yapılandırmasını** destekleyerek şu avantajları sunar:

* **Özel klasörler**, farklı **ürün serileri, markalar veya içerik türleri** için oluşturulabilir.
* **Sürükle & bırak (Drag-and-drop) desteği**, dosyaları hızlı bir şekilde düzenlemeye olanak tanır.
* **Rol bazlı erişim yönetimi**, farklı ekiplerin medya varlıklarını güvenli bir şekilde yönetmesini sağlar.

### **Dosya Yönetimi & Belge Takibi**

DAM modülünün belge yönetimi sistemi, işletmelerin şu işlemleri yapmasını sağlar:

* **PDF dosyaları, teknik belgeler ve kullanım kılavuzları** yükleme, izleme ve yönetme
* Belgeleri **pazarlama materyalleri, teknik rehberler ve uyumluluk belgeleri** gibi kategorilere ayırma
* Dosyaları **tür, format ve atanmış etiketlere** göre filtreleme ve gruplama

Bu sayede ürünle ilgili tüm dokümanlar **kolay erişilebilir ve düzenli** bir şekilde saklanır.

***

### **Resim & Video Yönetimi**

* Ürün görselleri ve promosyon içeriklerini yönetmek için **özel bölümler**
* **E-ticaret ve pazarlama için yüksek çözünürlüklü görsel desteği**
* **Toplu yükleme & dosya yapılandırma** özellikleri ile ürün fotoğraflarının hızlı yönetimi
* **Eğitim videoları, reklamlar ve tanıtım içerikleri için video dosya depolama**

Bu sistem, **ürün medya yönetimini kolaylaştırarak** markaların görsel varlıklarını etkin bir şekilde kullanmasına yardımcı olur.

## Akışlar

Lidia PIM’deki **Feeds** (Akışlar) modülü, işletmelerin **ürün verilerini üçüncü taraf platformlara dağıtmasını** sağlayarak, **pazaryerleri, e-ticaret platformları, ERP sistemleri ve pazarlama araçları** gibi harici sistemlerle entegrasyon kurmalarına olanak tanır.

***

### **Feed Yönetimi Genel Görünümü**

**Feeds** sayfası, kullanıcıların tüm veri akışlarını tek bir merkezi arayüzden yönetmesini sağlar. Kullanıcılar şunları yapabilir:

* Harici sistemlerle entegrasyon için **yeni feed’ler oluşturabilir, düzenleyebilir ve silebilir**.
* **Aktif ve pasif feed’leri** detaylarıyla birlikte görüntüleyebilir.
* **Feed URL’lerini tanımlayarak** veri senkronizasyonunu kolaylaştırabilir.
* **Her feed’e bağlı ürün sayılarını** izleyebilir.

Her feed şu temel bilgileri içerir:

* **Feed Adı:** Feed’in tanımlayıcı ismi.
* **URL:** Verinin yayınlandığı uç nokta.
* **Format:** Veri formatı (örn. JSON, XML).
* **Feed Kodu:** Feed için benzersiz bir kod.
* **Ürün Sayısı:** Feed’e dahil edilen ürünlerin toplam sayısı.
* **Durum:** Feed’in aktif veya pasif olduğunu belirtir.

Kullanıcılar **"Yeni Feed Ekle"** butonuna tıklayarak yeni bir feed oluşturabilirler.

### **Feed Yapılandırması & Özelleştirme**

Bir feed oluştururken veya düzenlerken, kullanıcılar aşağıdaki temel parametreleri belirleyebilir:

#### **Temel Bilgiler**

* **Feed Durumu:** Feed’in **aktif** veya **pasif** olup olmadığını ayarlama.
* **Feed Kodu:** Feed’e özel benzersiz bir kimlik.
* **Feed Formatı:** JSON, XML gibi kullanılacak veri formatını belirleme.
* **Erişim Kontrolü:** Feed için **yetkilendirme ve erişim ayarlarını** yönetme.
* **Feed URL:** Ürün verilerinin alındığı uç nokta.

### **Feed’ler İçin Veri Filtreleme**

Lidia PIM, her feed’de hangi ürünlerin yer alacağını belirlemek için **özelleştirilmiş filtreleme seçenekleri** sunar. Böylece yalnızca **ilgili ürünlerin harici sistemlere aktarılması** sağlanır.

#### **Mevcut Filtreler:**

* **Kategoriler:** Belirli kategorilere ait ürünleri içeren feed’ler oluşturma.
* **Markalar:** Seçili markalarla sınırlı feed’ler oluşturma.
* **Özel Listeler:** Önceden tanımlanmış özel listelerdeki ürünleri feed’e dahil etme.
* **Ürün Özellikleri:** Belirli özelliklere sahip ürünleri dahil etme (örn. **Malzeme: %100 Deri**).
* **Varyant Özellikleri:** Ürün varyantlarına göre feed oluşturma.
* **Seçenek Değerleri:** Renk, beden veya yapılandırma gibi seçeneklere göre filtreleme.
* **Etiketler (Tags):** Belirli etiketlere sahip ürünleri seçme.

**Negatif filtreler** de uygulanabilir; böylece belirli ürünler feed’e **dahil edilmez**.

Bu sistem, **özelleştirilmiş ve hedeflenmiş veri akışları oluşturmayı**, entegrasyonları yönetmeyi ve ürün verilerinin etkin dağıtımını sağlar.

## Raporlar

Lidia PIM’deki **Denetim Raporu** sayfası, sistemde gerçekleştirilen tüm işlemleri kapsayan **kapsamlı bir günlük kaydı (audit log)** sağlar. Bu özellik, **şeffaflık ve izlenebilirlik** sunarak değişiklikleri takip etmek, güncellemeleri izlemek ve veri bütünlüğünü korumak için kritik öneme sahiptir.

***

### **Denetim Günlükleri Genel Görünümü**

**Denetim Günlükleri** bölümü, sistemde gerçekleşen olayların ayrıntılı bir geçmişini görüntüleyerek farklı veri varlıkları üzerinde yapılan değişiklikleri takip etme imkanı sunar.

### **Denetim Günlüklerindeki Temel Veri Noktaları:**

* **Log Kimliği (Log ID):** Her denetim kaydı için benzersiz bir tanımlayıcı.
* **Olay Türü (Event Type):** Yapılan işlemin türünü belirtir (örn. **Güncelleme, Oluşturma, Silme, Diğer**).
* **Varlık Türü (Entity Type):** Etkilenen veri kategorisini gösterir (örn. **Veri Havuzu, Ürün, Kategori**).
* **Varlık Kimliği (Entity ID):** Değiştirilen veri varlığının benzersiz kimliği.
* **Mesaj (Message):** Gerçekleştirilen işlemin özetini sunar.
* **Oluşturulma Tarihi (Created Date):** İşlemin gerçekleştiği tarih ve saat damgası.

Bu günlükler, **yöneticilerin ve denetçilerin sistemde yapılan geçmiş değişiklikleri incelemesini** ve **iç politikalar ile dış düzenlemelere uyumluluğun sağlanmasını** mümkün kılar.

### **Özellikler & İşlevsellik**

#### **Arama & Filtreleme Seçenekleri**

* Kullanıcılar günlükleri **olay türüne, varlık türüne veya belirli varlık kimliklerine** göre filtreleyebilir.
* **Sıralama seçenekleri**, günlüklerin **tarih veya olay türüne göre organize edilmesini** sağlar.

#### **Gruplama & Sıralama**

* Kullanıcılar, **sütun başlıklarını sürükleyip bırakarak** günlükleri belirli özelliklere göre gruplandırabilir.
* Bu özellik, **ilgili denetim kayıtlarını analiz etmeyi ve veri görünürlüğünü artırmayı** kolaylaştırır.

#### **Log Detayları & Analiz**

* Her giriş, yapılan değişiklikler hakkında ayrıntılı bir mesaj içerir.
* Günlük kayıtları genişletilerek **değişikliklere dair ek detaylar görüntülenebilir**.

Bu sayfa, **sistem yönetimini ve güvenlik takibini** kolaylaştırarak Lidia PIM platformunun **güvenli, uyumlu ve izlenebilir bir şekilde çalışmasını** sağlar.


# Lidia Rating & Reviews

## **Overview**

The Lidia Ratings & Reviews feature empowers customers to share feedback on products and services, helping businesses build trust, enhance transparency, and drive purchasing decisions. Integrated within the Lidia digital commerce platform, this tool provides robust capabilities for collecting, managing, and displaying customer ratings and reviews across sales channels.

## **Key Features**

### **Customer Ratings and Reviews Submission**

* **Rating System**: Customers can provide a star rating (e.g., 1 to 5 stars) for each product they purchase, giving a quick visual indicator of product satisfaction.
* **Review Text**: Customers can add detailed written feedback, sharing their experiences, likes, dislikes, and suggestions, which assists other potential buyers in decision-making.
* **Media Uploads**: Allows customers to attach photos or videos to their reviews, adding valuable context and authenticity.
* **Anonymous Posting**: Optional anonymous posting for customers who wish to provide feedback without revealing their identity.

### **Review Moderation**

* **Automated Filters**: Built-in moderation tools filter out inappropriate content, including offensive language and spam, ensuring review quality.
* **Manual Approval**: Option for administrators to manually review and approve comments before they are posted, ensuring only authentic, relevant reviews are published.
* **Flagging System**: Customers and moderators can flag reviews for investigation, enabling quicker response to inappropriate or misleading content.

### **Review and Rating Display**

* **Average Rating Calculation**: The platform automatically calculates and displays average ratings, giving customers an overall score for each product.
* **Sort and Filter Options**: Allows customers to sort reviews by rating, date, or helpfulness, and filter by specific ratings (e.g., only 5-star or 1-star reviews).
* **Highlight Verified Purchases**: Tags reviews from verified purchases to add credibility and build customer confidence in the review system.

### **Analytics and Reporting**

* **Sentiment Analysis**: Uses analytics to assess customer sentiment across reviews, providing insights into product reception and potential areas for improvement.
* **Performance Metrics**: Tracks metrics like average ratings per product, review frequency, and customer engagement, which are essential for assessing product performance and customer satisfaction.
* **Customer Insights**: Identifies trends in customer feedback, such as frequently mentioned features or issues, helping inform product improvements and marketing strategies.

### **Multi-Channel Integration**

* **Unified Ratings & Reviews Display**: Ensures ratings and reviews are consistently displayed across all channels, including web, mobile apps, and third-party integrations.
* **Real-Time Updates**: Reviews and ratings sync in real-time, so new feedback is available instantly across all touchpoints.
* **Omnichannel Feedback Collection**: Collects feedback from all sales channels, consolidating it into a single view for easy management and response.

## **Getting Started with Ratings & Reviews**

1. **Setup and Configuration**
   * Enable the Ratings & Reviews feature through the Lidia Console, and configure the star rating system, review guidelines, and moderation rules.
   * Customize display settings for each sales channel to ensure a consistent look and feel across platforms.
2. **Moderation and Quality Control**
   * Define moderation criteria, including language filters and manual approval rules, to ensure review authenticity and relevance.
   * Set up notifications for flagged reviews, enabling moderators to respond quickly and maintain the platform’s credibility.
3. **Encouraging Customer Participation**
   * **Automated Review Requests**: After a purchase, send customers automated prompts via email or app notifications, encouraging them to leave a review.
   * **Incentivize Reviews**: Offer incentives, such as discounts or loyalty points, for verified reviews, boosting engagement without influencing review content.

## **Analytics and Reporting**

* **Review Dashboard**: View comprehensive metrics on reviews, such as average product ratings, frequency of reviews, and top-reviewed products.
* **Customer Sentiment Analysis**: Utilize sentiment analysis tools to identify positive and negative trends, helping inform customer service and product development.
* **Custom Reports**: Generate custom reports to track review volume, rating distribution, and other critical metrics over time, enabling data-driven decisions.


# Lidia Promotion Engine

## **Overview**

The Lidia Promotion Engine is an advanced tool built to enhance the marketing capabilities of digital commerce platforms. With support for multiple campaign and coupon types, it enables businesses to increase sales, engage customers, and improve loyalty through customizable and targeted promotions. This promotion engine is also equipped with real-time analytics, multi-channel deployment, and seamless integration capabilities.

## **Key Features**

### **Highly Customizable and Flexible Promotions**

#### **Dynamic Rule Engine**:

The dynamic rule engine in the Promotion Engine provides extensive flexibility in defining and managing promotions. Businesses can set targeted conditions for different types of campaigns, ensuring promotions reach the right customers at the right time.

#### **Active Campaign Types**:

* **Membership Campaigns**: Targeted promotions for new and existing members, encouraging sign-ups and rewarding loyalty.
* **Purchase Campaigns**: Discounts or rewards applied at the point of purchase to incentivize buying and upselling.
* **Post-Sales Campaigns**: Offers or benefits provided after a sale to encourage repeat purchases or positive reviews.
* **Promotional Campaigns**: General awareness campaigns, such as holiday sales or product launches, designed to boost visibility and traffic.

#### **Active Coupon Types**

* **Gift Certificates**: Value-based certificates that can be used as currency on the platform for future purchases.
* **Discount Coupons**: Coupons that provide a percentage or fixed discount on eligible purchases, applicable at checkout.

#### **Real-Time Analytics and Reporting**

* **Performance Monitoring**: Track campaign impact with metrics such as sales uplift, conversion rate improvements, and coupon usage.
* **ROI Analysis**: Assess the return on investment for each campaign by comparing the costs of discounts or rewards to generated revenue.
* **Engagement Insights**: Identify which campaigns and coupons drive the highest engagement among different customer segments.

#### **Seamless Integration with Existing E-commerce Platforms**

* **Easy Integration**: Designed to integrate seamlessly with any e-commerce platform, the Promotion Engine supports API-based connections, ensuring smooth operation with minimal setup.
* **Modular Design**: Allows businesses to activate only the features they need, providing a scalable and cost-effective solution.

#### **Multi-Channel Deployment**

* **Cross-Channel Support**: Deploy promotions across various sales channels, including online stores, mobile apps, and physical stores if applicable.
* **Data Synchronization**: Ensures uniform promotion distribution across channels for a consistent customer experience.
* **Omnichannel Capabilities**: Provides customers with the same promotional experience regardless of the channel they use, enhancing satisfaction and retention.

## **Creating and Managing Promotions**

1. **Define Campaign Objectives**:
   * Identify the type of campaign, whether for membership, purchase, post-sales engagement, or general promotion, and establish the goals for each.
2. **Configure Rules and Eligibility**:
   * Use the dynamic rule engine to set conditions such as customer eligibility, product restrictions, and usage limits.
   * Select specific channels for promotion deployment to align with customer preferences.
3. **Set Up Coupons**:
   * Define the type of coupon, either as a **Gift Certificate** or **Discount Coupon**, and assign value or discount details.
   * Apply any additional terms, such as minimum purchase requirements or validity periods.
4. **Launch and Monitor**:
   * Deploy the campaign across selected channels and use real-time analytics to track its performance, making adjustments as needed for optimization.

## **Analytics and Reporting**

* **Dashboard Overview**: Access a high-level summary of active campaigns, tracking metrics like total sales impact, coupon usage, and engagement rates.
* **Segment Analysis**: Review how different customer segments respond to membership, purchase, post-sales, and promotional campaigns to optimize targeting.
* **Custom Reports**: Export and customize reports to align with business needs, providing insights for strategic planning.

## **Use Cases**

1. **Membership Drive with Discounts**:
   * Offer a **Discount Coupon** to encourage new sign-ups or reward loyal members, enhancing customer acquisition and retention.
2. **Gift Certificate with Purchase Campaign**:
   * Provide **Gift Certificates** for purchases over a specific amount, motivating customers to spend more.
3. **Post-Sales Engagement Campaign**:
   * Send a discount coupon to customers after a purchase to encourage repeat sales and build loyalty.

## **Technical Support and Resources**

* **Documentation**: Comprehensive API and setup documentation for easy integration and troubleshooting.
* **Customer Support**: Ongoing support from Lidia for implementation and maintenance.
* **Training and Onboarding**: Training resources and sessions to help teams maximize the potential of the Promotion Engine.


# Lidia Console

## Overview

Lidia Console is a centralized administration interface designed for managing digital commerce operations efficiently. It serves as the core control panel for businesses to manage products, orders, customers, inventory, and various operational functions across different commerce models (B2B, B2C, and Marketplace). Built with an intuitive user interface and flexible tools, Lidia Console streamlines daily administrative tasks while supporting scalability for businesses of all sizes.

***

## Key Features

{% hint style="info" %}
If you would like to get more detailed information about the features, please follow the [link](/components/lidia-console/features).
{% endhint %}

#### 1. **User Roles and Permissions**

Lidia Console allows for the creation and management of user roles with granular permissions. Administrators can assign specific access rights based on roles, ensuring that sensitive information is protected and tasks are delegated appropriately. This role-based access control enables secure and efficient collaboration across teams.

* **Customizable Roles**: Create roles based on business needs (e.g., Admin, Sales Manager, Inventory Manager).
* **Permissions Management**: Control access to various features like catalog management, order processing, or customer data.

#### 2. **Order Management**

Lidia Console provides a comprehensive order management system that allows businesses to handle orders from placement to delivery. Users can track the status of orders, process returns, and manage payments, all from a single interface.

* **Order Tracking**: Monitor the lifecycle of orders from initiation to completion.
* **Return & Refund Management**: Simplify return and refund processes to ensure customer satisfaction.
* **Automated Notifications**: Keep customers updated on their order status through integrated notifications.

#### 3. **Inventory Management**

The inventory management tools in Lidia Console allow for real-time tracking of stock levels, preventing stockouts or overstock situations. Businesses can manage inventory across multiple locations or merchants, ensuring accurate and efficient logistics.

* **Real-Time Inventory Tracking**: View and manage stock levels across various locations.
* **Bulk Inventory Uploads**: Import inventory data from other systems via CSV or integration tools like Excel.
* **Low Stock Alerts**: Set alerts for low inventory levels to avoid stockouts.

#### 4. **Customer Management**

Lidia Console features a customer management module that provides a 360-degree view of customer data, including purchase history, contact information, and customer interactions. This feature enhances the ability to manage after-sales services and provides insights into customer behavior.

* **Customer Profiles**: Maintain detailed profiles with order history and contact information.
* **Customer Support**: Integrate with customer service systems to manage inquiries, complaints, and returns.
* **Loyalty Programs**: Support customer engagement with integrated loyalty programs and personalized offers.

#### 5. **Promotions and Discounts**

Easily create, manage, and track promotions and discounts using Lidia Console. The platform allows for setting specific discount rules based on products, customer segments, or seasonal campaigns.

* **Promotion Engine**: Define rules for discounts, offers, and seasonal promotions.
* **Campaign Management**: Schedule and track campaigns to assess performance.
* **Coupon Code Management**: Generate and manage unique coupon codes for specific marketing initiatives.

#### 6. **Analytics and Reporting**

Lidia Console includes built-in analytics and reporting tools that provide valuable insights into business performance. Customizable reports give visibility into sales, customer behavior, inventory turnover, and order efficiency, helping businesses make data-driven decisions.

* **Sales Reports**: View detailed reports on product sales, order volumes, and revenue.
* **Customer Insights**: Analyze customer purchasing patterns and behaviors.
* **Custom Reports**: Generate custom reports based on specific KPIs, such as inventory levels, delivery times, or customer retention rates.

***

## Integration Capabilities

Lidia Console integrates seamlessly with various third-party systems, including payment gateways, logistics providers, ERP, and CRM systems, providing a smooth flow of information across business applications.

* **Payment Integrations**: Connect with multiple payment providers to manage transactions securely.
* **Logistics Integrations**: Link with logistics providers to streamline order fulfillment and delivery.
* **ERP/CRM Connectivity**: Sync data with ERP systems for real-time inventory and financial reporting.

***

## Advanced Features

### **Catalog Management**

The catalog management feature allows users to create, update, and maintain product listings, ensuring that all product information is accurate and up-to-date. Users can import product data from systems like Lidia PIM or external databases.

* **Bulk Product Uploads**: Import product listings in bulk using CSV or API integrations.
* **Product Categorization**: Organize products into categories for better user navigation.
* **SEO Optimization**: Customize metadata for product pages to improve search engine visibility.

### **Content Management System (CMS)**

Lidia Console includes a CMS module that allows non-technical users to manage and update website content, including banners, product descriptions, and blog posts.

* **Drag-and-Drop Editor**: Easily create and modify content with a user-friendly editor.
* **Content Scheduling**: Schedule content updates for campaigns and seasonal promotions.
* **Multilingual Support**: Manage content in multiple languages for global reach.

***

### User Interface

Lidia Console is designed with an intuitive and user-friendly interface. Key tasks are easily accessible, and the platform provides a seamless experience for users across different departments, whether they are managing inventory, processing orders, or analyzing sales performance.

* **Dashboard**: A customizable overview of key metrics, including sales, inventory, and customer data.
* **Search and Filtering**: Advanced search and filtering tools to quickly locate orders, products, or customers.
* **Mobile Access**: Fully responsive interface for managing operations on mobile devices.

***

## Training and Support

Lidia Console includes extensive documentation and user training to ensure a smooth onboarding process. Dedicated support teams are available to assist with setup, customization, and ongoing usage.

* **Onboarding Support**: Get started with detailed tutorials and step-by-step guides.
* **Comprehensive Documentation**: Access user manuals and API documentation for advanced integrations.
* **Customer Support**: Dedicated support team for troubleshooting and assistance.

***

## Conclusion

Lidia Console is a robust and flexible administration tool that provides businesses with everything they need to manage their digital commerce operations efficiently. Its powerful features, combined with seamless integration and user-friendly interface, make it the ideal solution for businesses looking to scale their e-commerce operations across different models and industries.


# Lidia Console User Guide

Welcome to the Lidia Console User Guide. This documentation is designed to help you use the full capabilities of the Lidia Marketplace Console efficiently and effectively. Throughout the guide, you will explore the platform’s core building blocks, management interfaces, and operational workflows step by step—covering everything from daily operations to advanced administrative configurations.&#x20;

Whether you are a first-time user or an experienced administrator managing the platform, this guide aims to help you get the most out of your Lidia Console experience.

{% hint style="info" %}
**Tip:** If you're new to Lidia Console, start with the **Getting Started** section.
{% endhint %}

<table><thead><tr><th width="153.66668701171875"></th><th width="157"></th><th></th></tr></thead><tbody><tr><td><a href="/pages/Gh7O0ICkSRcCEaZimBqC"><strong>Getting Started</strong></a></td><td></td><td><ul><li>Dashboard</li></ul></td></tr><tr><td><a href="/pages/CK1FhWCR0WBWpL0P7UqF"><strong>Settings</strong></a></td><td><strong>Authorization</strong></td><td><ul><li>Users</li><li>Roles</li></ul></td></tr><tr><td></td><td><strong>Legal</strong></td><td><ul><li>Liables</li><li>Consent Documents</li></ul></td></tr><tr><td></td><td><strong>Payment</strong></td><td><ul><li>Payment Channels</li><li>Payment Institutions</li><li>Payment Instruments Groups</li><li>Payment Instruments </li><li>Payment Options</li><li>BIN Codes</li><li>Payment Rules</li></ul></td></tr><tr><td></td><td><strong>Logistics</strong></td><td><ul><li>Providers</li><li>Profiles</li><li>Rules</li></ul></td></tr><tr><td></td><td><strong>Commercial</strong></td><td><ul><li>Organization Rules</li></ul></td></tr><tr><td></td><td><strong>Catalog</strong></td><td><ul><li>Data Schemas</li><li>Product Relations</li><li>Data Locks</li><li>Properties</li><li>Options</li></ul></td></tr><tr><td></td><td><strong>Tags</strong></td><td><ul><li>Catalog Tags</li><li>Content Tags</li><li>Customer Tags </li></ul></td></tr><tr><td></td><td><strong>Extensions</strong></td><td><ul><li>Extensions</li></ul></td></tr><tr><td><a href="/pages/7mbIVqxy3BImNMCM0iz0"><strong>Notification Center</strong> </a></td><td></td><td><ul><li>Notifications</li><li>Notification Settings</li></ul></td></tr><tr><td><a href="/pages/ENHdwCJ4DGsimgrEY0Ca"><strong>Sellers</strong></a></td><td></td><td><ul><li>Networks</li><li>Seller List</li></ul></td></tr><tr><td><a href="/pages/Xj2vEyZQ3gxTzCCpr503"><strong>Customers</strong></a></td><td></td><td><ul><li>Customers</li><li>Consents</li><li>Reference Codes</li></ul></td></tr><tr><td><a href="/pages/h1pyevvthJlVDWuTFKjF"><strong>Product Management</strong></a></td><td></td><td><ul><li>Pools</li><li>Categories</li><li>Trademarks</li><li>Special Lists</li><li>Products</li><li>Variants</li></ul></td></tr><tr><td><a href="/pages/iYwZJmsQZ6qahpk3W1uM"><strong>Inventory</strong></a></td><td></td><td><ul><li>Warehouses</li><li>Inventories</li></ul></td></tr><tr><td><a href="/pages/cYih6SNs79FGavkDRBzp"><strong>Content</strong></a></td><td></td><td><ul><li>Templates</li><li>Pages</li><li>Redirects</li><li>Menus</li><li>Storefronts</li><li>Blocks</li><li>Content Objects</li></ul></td></tr><tr><td><a href="/pages/wvupgRQddo08JMy85Ryj"><strong>Media</strong></a></td><td></td><td><ul><li>Media List</li><li>Import Documents</li><li>Images</li><li>Files</li><li>Videos</li></ul></td></tr><tr><td><a href="/pages/3dEFBkuDxLWMZMB0c4WV"><strong>Goal Management</strong></a></td><td></td><td><ul><li>Goals</li></ul></td></tr><tr><td><a href="/pages/RGaT8ViknWEZhwMEDEr9"><strong>Campaign Management</strong></a></td><td></td><td><ul><li>Promotions</li><li>Coupons</li></ul></td></tr><tr><td><a href="/pages/b7LC1UWYLIGwNSrOOClw"><strong>Sales</strong></a></td><td></td><td><ul><li>Orders</li></ul></td></tr><tr><td><a href="/pages/cTGpnIz1e7fylbTJexXs"><strong>Logistic</strong></a></td><td></td><td><ul><li>Deliveries</li></ul></td></tr><tr><td><a href="/pages/ysFABIsrnS8ojVLeW8ta"><strong>Invoice Center</strong></a></td><td></td><td><ul><li>Invoices</li></ul></td></tr><tr><td><a href="/pages/SCaQ1gQwlrR0yQEUyxnt"><strong>Finance</strong></a></td><td></td><td><ul><li>Payments</li></ul></td></tr><tr><td><a href="/pages/EaKdSLUSnupYLxkU9ILl"><strong>After Sales</strong></a></td><td></td><td><ul><li>Returns</li><li>Cancellations</li></ul></td></tr><tr><td><a href="/pages/XRBdjLQkKyQkmITekr9o"><strong>Solution Center</strong></a></td><td></td><td><ul><li>Cases</li><li>Case Type</li></ul></td></tr><tr><td><a href="/pages/Dbh3NUQIsT66Zh95KX0N"><strong>Social Features</strong></a></td><td></td><td><ul><li>User Lists</li><li>Ratings and Reviews</li></ul></td></tr><tr><td><a href="/pages/8tzJ5hRtgeifBOkszvm7"><strong>Operational Tasks</strong></a></td><td></td><td><ul><li>Cache Management</li></ul></td></tr><tr><td><a href="/pages/DhYCwNrC8zFg2sKs3VBf"><strong>Reports</strong></a></td><td></td><td><ul><li>Sales Reports</li><li>Operational Reports</li><li>Cost Reports</li><li>Marketing Reports</li><li>Withholding Tax Declaration Reports</li></ul></td></tr><tr><td><a href="/pages/76gyB6WXfGFwVW6amsOa"><strong>Audit Reports</strong></a></td><td></td><td><ul><li>Transaction Logs</li></ul></td></tr></tbody></table>


# Getting Started

### **HomePage**

The Home Page is the first screen you encounter when you log in to the Lidia Console. From this screen, you can access all platform management processes, configure system settings, and monitor your notifications. While operational and administrative actions are performed through the modules listed in the left navigation menu, the top-right area allows you to switch language preferences, view system notifications, access and manage personal and organization-related account information, or securely log out of the platform.

* #### Left Menu Navigation

<figure><img src="/files/7O8hXxCGkR6WFsK5b0ZW" alt=""><figcaption></figcaption></figure>

[**Settings**](/components/lidia-console/lidia-console-user-guide/settings)\
Provides access to system preferences, core configurations, user roles, and overall platform settings.

[**Notification Center**](/components/lidia-console/lidia-console-user-guide/notifications)\
Allows you to view and manage system notifications, alerts, and updates.

[**Sellers**](/components/lidia-console/lidia-console-user-guide/sellers)\
Enables you to review seller applications submitted from the storefront, perform approval or rejection actions, and manage marketplace sellers and business partners.

[**Customers**](/components/lidia-console/lidia-console-user-guide/customers)\
Allows you to view registered customers, manage membership permissions, create new customer records, and maintain reference information.

[**Catalog**](/components/lidia-console/lidia-console-user-guide/product-management)\
Used to manage all products, brands, categories, variants, product pools, and product listings included in or offered for sale on the platform.

[**Inventory**](/components/lidia-console/lidia-console-user-guide/inventory)\
Provides an overview of all inventory data across the platform and allows inventory management.

[**Content Managenet**](/components/lidia-console/lidia-console-user-guide/content-management)\
A content management area where interface orchestrations and experience sets are defined and associated with appropriate templates across the platform.

[**Media**](/components/lidia-console/lidia-console-user-guide/media)\
Used to upload and manage all product-related images, videos, and files.

[**Goal Management**](/components/lidia-console/lidia-console-user-guide/goal-management)\
Allows you to define and track internal organizational goals and constraints.

[**Campaign Management**](/components/lidia-console/lidia-console-user-guide/campaign-management)\
Used to view existing campaigns and create new campaigns and coupon definitions.

[**Sales**](/components/lidia-console/lidia-console-user-guide/sales)\
Allows you to track and manage completed orders.

[**Logistics**](/components/lidia-console/lidia-console-user-guide/logistics)\
Used to track delivery and shipment processes related to orders.

[**Invoice Center**](/components/lidia-console/lidia-console-user-guide/invoice-center)\
Allows you to monitor invoices generated for completed orders.

[**Finance**](/components/lidia-console/lidia-console-user-guide/finance)\
Provides tracking and management of payments and financial transactions.

[**After-Sales**](/components/lidia-console/lidia-console-user-guide/after-sales)\
Used to manage and track order cancellation and return processes.

[**Solution Center**](/components/lidia-console/lidia-console-user-guide/solution-center)\
Allows you to track customer requests, complaints, and support tickets.

[**Social Capabilities**](/components/lidia-console/lidia-console-user-guide/social-features)\
Used to monitor customer feedback and engagement.

[**Operational Tasks**](/components/lidia-console/lidia-console-user-guide/operational-tasks)\
Used to manage technical and supportive processes related to platform operations.

[**Reports**](/components/lidia-console/lidia-console-user-guide/reports)\
Provides access to reports related to sales, operations, and cost data.

[**Audit Reports**](/components/lidia-console/lidia-console-user-guide/audit-reports)\
Allows tracking of system activity logs and transaction records at the organizational level.

[**Lidia App Store**](broken://pages/BM7i4vEz5KVBGN4G3fgE)

* #### Account Information

By clicking the profile area located in the upper-right corner, you can access the **Account Information** page. This section allows you to view and update both user- and organization-level information.

#### **User Information**

In the User Information section, the following details can be updated:

* Profile image
* First and last name
* Email address
* Phone number
* Password update

<figure><img src="/files/HqgSDP3KfzqbUF5Zkj3g" alt=""><figcaption></figcaption></figure>

* #### Organization Details

In the Organization Details section, the following actions can be performed:

Edit company information\
(Company name, company type, integration code, tax office, tax number, trade registry number, and address details)

View and update organization users

Assign new authorized users based on appropriate roles


# Settings

The Settings section is where the necessary configurations are defined to allow users to manage system-wide pages and capabilities. The configurations made in this section are referenced by all other.

## Authorization

The Authorization section includes the pages where user roles and permissions are defined and managed within the Lidia Console. In the Lidia Marketplace system, authorization is designed around a role-based approach rather than a user-based structure. This model enables centralized control and management of users’ access levels and permitted actions through assigned roles. The Authorization section consists of two main areas: Roles and Users.

* ### **Roles**

  Under the Roles section, the predefined roles provided by Lidia are displayed under **Lidia Roles**. These roles are configured to cover the platform’s standard usage scenarios. In addition, new roles can be created based on organization-specific needs, the created roles can be deleted, and users assigned to a role can be viewed through the role detail screen. For each role, permissions can be configured across all modules and capabilities available in the system.

  Roles can be configured with the following permission levels:

  * View permission
  * Edit permission
  * Both view and edit permissions

  Roles created later represent customized permission sets tailored to the specific needs of the project and the organization. These roles are referenced across the system to enforce authorization consistently.
* ### **Users**

  Under the Users section, a list of all registered users in the system is displayed. From this list, you can view each user’s first and last name, email address, assigned roles, system registration date, and user status (Active / Passive). By using the **Create New User** button located in the upper-right corner, a new member can be created by entering the following information:

  <figure><img src="/files/iC172HgqgnZJeSHP7tFa" alt=""><figcaption></figcaption></figure>

  \
  By accessing an individual user’s detail page, you can view basic user information such as first and last name, email address, phone number, and date of birth, as well as role and permission details.

{% hint style="success" %}
Depending on the permissions assigned to the user, this information and the assigned roles can be edited.
{% endhint %}

## Legal

The Legal section is the area where the organization’s legal obligations, documentation, and responsible institution information are centrally managed within the Lidia Console. This section ensures that legal content published on the platform is managed in an up-to-date, traceable, and versioned manner.

* ### **Consent Documents**

  When accessing the Legal Documents section, a document list is displayed containing the document ID, name, publisher, document code, version information, validity date, and active/passive status. In this area, legal documents such as KVKK texts, preliminary information forms, and similar documents can be uploaded, and uploaded documents can be versioned through this section.

<figure><img src="/files/7lbKqTd5TXHBTHSOCi6m" alt=""><figcaption></figcaption></figure>

Through document versioning, it is possible to perform checks in later stages, such as identifying who approved or did not approve specific versions of a document. From the Basic Information area on the document detail screen, the document content can be accessed and edited. Additionally, the complete version history of the document can be viewed through the Version History section on the detail screen.

* ### **Liables**

  Under the liables section, a list is displayed containing the name, address, and country information of the institution or institutions responsible for the management of the Lidia Console. By navigating to the details of a record, the institution’s basic information and the list of legal documents published by that institution can be accessed.

  Using the button located in the upper-right corner of the screen, a new data controller can be added.

## Payments

The Payments section is where the payment options, methods, and rules to be used on the platform are defined. Users’ preferred payment methods are configured through this section. During the payment collection process on the frontend, Lidia Collectors reference these definitions to verify whether the relevant payment method is defined in the system, as well as to check installment options and transaction conditions.

* ### **Payment Channels**

  Through the Payment Channels tab, a new payment channel can be added and all payment channels defined in the system can be listed. Each payment channel is a core component that determines how the payment flow operates and under which conditions it can be used.

  When accessing the detail screen of a payment channel, four main sections are displayed. The channel name and channel code are shown in the **Basic Information** section. Installment options related to the payment channel, interest rates applied to installments, active or passive status information, editing actions, and adding new installment options are managed through the **Options** section.

  Integration details and integration processes related to the payment channel are available in the **Integration Info** section. Payment transactions related to completed orders, including transaction amounts, transaction dates, and transaction types, can be reviewed in the **Transactions** section.

{% hint style="info" %}
![](/files/7fWqXv3cGqy7hCrBIVxt)<br>

When adding a new payment channel, you may either select from the known providers available in the system or define a new provider from scratch.
{% endhint %}

* ### **Payment Institutions**

  The Payment Institutions section is where the payment institutions to be used on the platform are defined and managed. Through this section, new payment institutions can be added, existing institutions can be listed, and removed when necessary.

  When accessing the detail screen of a payment institution, the institution’s basic information, related payment instruments, BIN codes, and payment channels are displayed. In the **Basic Information** section, the payment institution name, display name, and institution code are managed.

  In the **Payment Instruments** section, payment instruments associated with the relevant payment institution can be added, existing associations can be removed, or updated. In the **BIN Codes** section, BIN codes belonging to the institution can be listed and new BIN codes can be added.
* ### **Payment Instruments and Instrument Groups**

  The Payment Instruments section is where payment instruments belonging to a specific bank or payment provider are listed and defined. A new payment instrument can be added through this section. During the payment instrument creation process, the payment instrument name, code, associated instrument group, institution information, and instrument type are entered to complete the definition. From the detail page of a listed payment instrument, basic information, the BIN code list, and payment options can be viewed and edited.

  The Instrument Groups section allows different variations or structures of the same payment instrument to be grouped under a single group. Through this section, new payment instrument groups can be defined, existing groups can be viewed, and filtering operations can be performed.
* ### **Payment Options**

  The Payment Options section allows you to view and filter which payment institution offers which payment instrument and which installment options. Payment options can be listed based on payment institution, payment instrument, and installment details. When accessing the detail screen of any listed payment option, a description area containing basic information and a separate area containing technical parameters are displayed. \
  \
  Using the **Import Data** button located in the upper-right corner of the listing page, new payment option lists can be added to the system. During this process, the table should be prepared using the Excel template provided by the Lidia Console and uploaded accordingly. With the **Export Data** button in the same area, either selected fields from the list or the entire dataset can be exported in Excel format.

<figure><img src="/files/yhKOOCXL637sBzwHwWQR" alt=""><figcaption></figcaption></figure>

* ### **BIN Codes**

  The BIN Codes section is where BIN codes defined in the system are listed and their active or passive statuses are reviewed.
* ### **Payment Rules**

  The Payment Rules screen is where rule-based configurations for product payment transactions are defined. Through this screen, payment type and installment count rules can be created based on criteria such as category, brand, seller, price, and down payment amount.

## Logistics

The Logistics section is where delivery processes on the platform are managed and configured. Through this section, contracted service providers are defined and managed, delivery profiles are created, and custom delivery rules can be configured based on specific requirements. Logistics settings form the core structure that supports accurate and seamless order fulfillment.

* ### **Service Providers**

  The Service Providers section is the area where all contracted shipping companies and the shipping services they offer are managed. In this section, you can access the services provided by each shipping provider through labels such as standard shipping, bulky cargo, and next-day delivery. When accessing the detail screen of a service provider, the **Basic Information**, **Integration Information**, and **Service Information** sections are displayed.

  In the Basic Information section, the provider name and code can be edited. In the Integration Information section, the pricing interface URL, authorization interface URL, and API key information can be managed. In the Service Information section, a new service identity can be added by selecting a service type from the available options, and a price list can be uploaded for the defined service identity. During the price list upload process, the sample Excel template provided by the Lidia Console can be downloaded, edited as needed, and then uploaded to successfully complete the process.

  Thanks to these uploaded price lists, the system calculates estimated shipping costs at the moment products are prepared to be listed for sale on the platform and generates a shipping fee accordingly. This fee is later compared with the actual shipping cost, and this comparison is referenced in the calculation of settlement amounts.

<figure><img src="/files/WCwzFWpBdJn0JPvl1wHG" alt=""><figcaption></figcaption></figure>

* ### **Profiles**

  The Profiles section is where marketplace-recommended delivery profiles are managed and custom delivery profiles can be created. In this area, prioritization for small cargo and bulky cargo can be easily configured using the drag-and-drop method.
* ### **Rules**

  The Rules section is the area where delivery processes can be customized based on predefined rules. Under this section, service provider matching can be configured according to criteria such as category, weight, volumetric weight, city, district, and distance.

## Commercial

The Commercial section is where organizational commercial rules are defined and managed. In this section, existing rules are listed, viewed, and can be exported in Excel format when needed. When adding a new rule, the commission rule name, priority, and validity date are defined.

The created rule set can be configured based on criteria such as category, brand, product, seller, variant, and payment instrument. This allows commercial operations to be managed in a flexible and controlled manner according to organizational requirements.

<figure><img src="/files/972imTKhNYcojrOQAnwB" alt=""><figcaption></figcaption></figure>

## Catalog

The Catalog section is where the full scope of product data to be offered for sale or included in the product assortment is defined. In this section, the product data space, constraints, locks, and rules are configured, and the conditions under which products are included in the system are determined. Category-based fields and attributes are also managed to ensure product information is created in a consistent and controlled manner.

This area allows you to build the catalog architecture within the system and define an organization-specific product structure end to end. Through the Catalog, the product data space can be designed, data relationships can be established, and a solid foundation for product management can be created.

* ### **Data Schemas**

  The Data Schemas section is where you define under which data schema the products to be uploaded to the system will be structured. From this page, you can view all your data schemas and create new ones. By navigating to the details of any data schema, new fields can be added through the **Data Schema Fields** section.

  During the field creation process, field names can be customized as needed. Field names such as short description, brand, category, color, weight, volumetric weight, and tax rate can be defined. The field types for these fields are selected from options such as attribute, option, category reference, brand reference, image source, and document source.

  In addition, validation and mapping information can be defined for each field to configure which information is mandatory during product entry and which rules must be met for products under the related schema to be accepted into the system. This allows product data entry standards to be controlled in an organization-specific manner. These configurations can also be managed by uploading custom documents under the **Documents** section.
* ### **Product Relationships**

  The Product Relationships section is where logical and functional relationships between products are defined within the system. In this section, the name and description of product relationships are created to ensure that relationship types are defined with a standardized structure across the platform. At this stage, only the basic definition of the relationship is configured; the products or product variants to which the relationship applies are defined later through the product and variant detail screens. This structure allows different relationship scenarios, such as cross-sell, alternative products, or complementary products, to be managed flexibly.
* ### **Data Locks**

  The Data Locks section is used to ensure that certain information cannot be modified in a marketplace environment. These locks are not limited to the product creation process; they can also be applied during product data transfers from different platforms into the system. The source and target of where the lock is applied can be configured as needed.

  Through this section, data locks can be defined while importing product data from external sources, while editing product data within the Lidia Console, or while sending product data through flows, channels, services, or feeds. This ensures that critical product information remains protected from unauthorized or unintended changes.

  When adding a new data lock, the process requires defining the lock title, lock type, the source to which the lock will be applied, the lock scope, the related object type, the locked field, and a description.

{% hint style="success" %}
This is an advanced feature that covers data locking not only during product flows but also at the product data level.
{% endhint %}

* ### **Properties**

  The Properties section is where product characteristics are centrally defined and managed. When creating a new property in this section, basic information such as the property name, the property group it belongs to, and the data type it supports are defined. The selected data type determines which values the property can take and how it can be used across products.

  All product properties defined in the system can be viewed on the listing page. From this page, existing properties can be edited, updated, or deleted when necessary. Centralized property management ensures that product data is created in a consistent structure and contributes to more effective filtering, search, and product comparison functionalities.

  Properties are associated with **Property Groups** to create a more structured and meaningful organization. Under the Property Groups section, new property groups can be defined and existing groups can be listed. When navigating to the detail page of a property group, the list of property values associated with that group can be accessed. This relationship allows properties to be categorized and managed more efficiently, making the overall product data structure easier to control.
* ### **Options**

  The Options section is where options, option groups, and the values associated with these options are centrally managed within the scope of product properties. This section is one of the core building blocks for creating product variants and standardizing product data.

  **The Options page** is where all options defined in the system are listed. Through this page, new options can be created, existing options can be viewed, and edits can be made. Options form the basis of variant structures used on products and are managed by being associated with relevant option groups.

  Under the **Option Groups** section, multiple options are grouped under meaningful structures. This allows options to be categorized, creating a more organized and manageable structure. In this section, new option groups can be defined, existing groups can be listed, and options associated with a group can be viewed through the group detail page.

  **The Option Values page** is where each option value defined in the system is listed individually and can be edited. This section helps maintain the consistency of values used across products and prevents duplicate data entry.

  In the **Option Value Groups** section, option values are organized under logical groups. Through these groups, related option values can be viewed and managed together. New value groups can be created from this section, and associated values can be accessed through the group detail page.

  The Options section enables options and values to be managed in a reusable, controlled, and scalable structure, contributing to a more organized and sustainable product data architecture.

{% hint style="info" %}
**Properties** are fields where descriptive information about a product is entered, such as Processor Type, Screen Size, or Color. These fields describe the product and typically do not affect the price.

**Options** represent product variants and usually affect the price. They are user-selectable fields that create variations, such as Memory Capacity or Color Options.
{% endhint %}

## Tags

The Tags section is where tags to be used across the system are defined and managed. Tags are used to provide classification, differentiation, and ease of management across products, categories, brands, documents, or system-related processes.

When adding a new tag, the first step is to select the **tag type**. The tag type determines how the tag will be used within the system and how it will behave in the user interface. During tag type selection, descriptions for each tag type are displayed on the screen, and the appropriate tag type is selected accordingly.

The tag types available in the system are as follows:

<figure><img src="/files/TktQDtRDqui07ax2aR8v" alt=""><figcaption></figcaption></figure>

After selecting the tag type, the tag creation process is completed by entering the tag name, tag text, and tag code. The created tags can be used across relevant areas of the system and managed according to requirements.

## Extensions


# Notifications

The Lidia Marketplace Console Notification Center is the area where notifications related to all actions performed on the platform are tracked and where users are informed about real-time updates. Notifications can be filtered by notification type and date. Users can mark all notifications as read to clear existing alerts. They may also choose to view only unread notifications if desired.

When a notification is clicked, the user is redirected to the relevant Console page associated with the notification’s category. For example, when the “A new order has been created” notification is selected, the user is redirected to the related order detail page under the Orders page within the Sales section in the left navigation menu, based on the corresponding order number.

<figure><img src="/files/jxmFpAYW6ZfcYxjzFpIQ" alt=""><figcaption></figcaption></figure>

### **Notification Settings**

The Notification Settings page is where users can customize which actions they want to receive notifications for. After customization, users will receive notifications only for the selected action types. Notification preferences are personal and are managed independently of the organization.

Notification preferences are grouped under the following main categories:

#### **Organization Notifications**

* [x] A new merchant has been added

#### **Order Notifications**

* [x] A new order has been created
* [x] Order status has been updated
* [x] Order has been canceled
* [x] A new return request has been created

#### **Delivery Notifications**

* [x] A new delivery has been created
* [x] Delivery status has been updated
* [x] Delivery address has been updated

#### **Inventory Notifications**

* [x] There are products with low stock
* [x] There are products that are out of stock

#### **Marketing Notifications**

* [x] A new coupon has been created
* [x] A new campaign has been created

{% hint style="success" %}
This structured notification system allows users to stay informed about critical updates while enabling them to customize their notification preferences for a cleaner and more focused experience.
{% endhint %}


# Sellers

The Sellers section is where all sellers, business partners, and dealers defined in your marketplace system are centrally managed. Through this section, existing sellers and dealers can be listed, marketplace statuses can be monitored, and seller-related operational information can be viewed. In addition, new sellers who apply through the onboarding process can be displayed and evaluated in this area.

Each seller’s application and profile information can be reviewed in detail, and approval or rejection actions can be performed for applications. Furthermore, depending on organizational needs, new seller and dealer additions can also be carried out manually through the system. The Sellers section supports the end-to-end management of the seller and dealer lifecycle, contributing to the controlled and sustainable operation of marketplace processes.<br>

* ### **Seller List**

  When the Seller List page is opened, there are two main sections: **Sellers** and **Applications**. Under the Sellers section, the names, ID numbers, and active/passive statuses of all sellers defined in the system are listed in the initial view. By clicking the Details button next to each seller, you can access a total of 13 different screens containing detailed information about the selected seller. The seller can be removed from the system using the delete button located on the same row.

  The **Import Data** button located in the upper-right section of the Sellers page is used for bulk seller creation. Through this button, the sample Excel template provided by the Lidia Console can be downloaded. After editing this file by entering the required basic seller information and uploading it back to the system, sellers can be added to the list in bulk. This method is particularly used to reduce manual data entry during high-volume seller onboarding processes.

  Using the **Export Data** button, an Excel file containing the basic information of all listed sellers or selected sellers can be exported. This operation can be used for reporting, analysis, archiving, or data sharing with other systems.&#x20;

{% hint style="info" %}
The **Add New Seller** button located next to the Export Data button is accessible on both the Sellers and Applications screens.
{% endhint %}

### **Add New Seller**

When the Add New Seller button is clicked, basic information such as the seller name, company type ( individual company, sole proprietorship, joint-stock/limited company ) ,  product catalog type  ( physical, digital, physical and digital) and page URL address is requested. After entering this information, the onboarding process continues with the next steps. If the process is exited before completion, the seller is considered to be created in draft status, and the seller status is displayed as *Draft* in the list.

The onboarding process consists of the following steps:

* Authorized Information
* Company Information
* Store and Operation Information
* Company Documents
* Preview and Approval

Once all steps are completed, the seller application is listed in the system with a Approved or Rejected status.

* ### **Applications**

  Under the Applications section on the Seller List page, sellers who have applied through the onboarding process are listed. In this list, columns display the organization name, role, application owner, application date, and application status. This area is used for evaluating new seller applications and tracking the onboarding process.

### **Seller Detail Screens**

Within the Sellers section of the Lidia Console, the Seller List page allows you to navigate to each seller’s detail screens to track seller-related information. By clicking the Details button for a seller, multiple detail screens associated with that seller are displayed. These screens enable end-to-end monitoring of the seller’s store status, performance, company information, and operational structures.

***

#### **1. Store Dashboard**

The Store Dashboard is the main screen where the overall status and performance of the seller’s store are summarized. In this area, store name, store code, associated organization, active and published status, and application details are displayed in the summary panel at the top.

Below this section, the **first look** area displays the store rating, total earnings, number of active products, number of active categories, and a sales chart. From the store rating panel, access to the store evaluation report is provided, while the total earnings panel and sales chart allow navigation to the store sales reports.

Under the **Store Performance** section, key performance metrics are displayed, including total order count, average order value, order fulfillment rate, average delivery time, return rate, and number of pending orders. From the total orders, order fulfillment rate, and pending orders sections, users can navigate to the Orders page under the [Sales](/components/lidia-console/lidia-console-user-guide/sales) section in the left menu to view all orders associated with the store.

***

#### **2. Main İnfo Screen**

The Main İnfo screen is where store and company details related to the seller are displayed and managed. On this screen, store status information (such as active, passive, draft, ready to publish, deleted, or frozen) and store-related details such as the store name can be accessed.

**Company information** including company type, tax office, tax number, and trade registry number, as well as detailed **address information**, are also available on this screen. At the bottom of the page, the **Warehouse Information** section displays the warehouses used by the store for return processing and product shipment operations. The addresses and types of return warehouses and outbound warehouses used for product shipments are listed here. Multiple warehouses can be added, and they can be set as default based on their operational purpose.

***

#### **3. Filter Management**

The Filter Management section is where the filters that will be displayed with priority on listing pages are defined in order to improve the user experience. Through this section, filters that help users find products more quickly and easily can be configured.

Lidia Console provides the following main filter categories during the filter configuration process:

* Categories
* Trademarks
* Price Range
* Properties
* Options
* Tags

From the options under these categories, the ones suitable for your store can be selected to create customized filter sets. The created filter sets can be configured according to store needs, and the order of the filters within each set can be customized as desired.

***

#### **4. Page Management**

The Page Management section is where the seller’s store page displayed on the marketplace is created and customized. In this section, the seller’s display name on the marketplace, page template, tags, and similar fields are configured to design the store page.

From the **Add Section** area located at the bottom of the page, ready-made sections, blocks, and basic components provided by the Lidia Console can be added to the page. This structure allows flexible and manageable page layouts to be created without the need for coding.

Within the Sections area, general content structures can be defined. For example, four-card homepage layouts, monthly deals sections, campaign showcases, or featured content areas can be created. When adding a section, a basic component is first selected from the list. These basic components include paragraph, button, simple list, divider, video, image, showcase, and advanced list.

By combining the selected basic components, page sections are created and can be positioned on the store page in the desired order. This structure enables sellers to customize their store pages in line with their brand identity and marketing needs.

***

#### **5. SEO Management**

The SEO Management section is where search engine optimization settings for the seller’s store page are configured. Through this area, SEO-related information such as page titles, meta descriptions, keywords, and URL structures can be defined to improve the visibility of the store in search engines. Proper configuration of these settings helps increase organic traffic and enhances the discoverability of the store page.

***

#### **6. Slug Addresses**

The Page Addresses section is where the address = URL configurations of the store page are listed and managed. Through this page, different store addresses are displayed together with their priority, language/region, and status information. Page addresses are used to ensure proper routing and access management in stores with multi-language or multi-market structures.

***

#### **7. Authorized Persons**

The Authorized Persons section is where users associated with the seller and their access permissions are managed. In this section, the username, email address, assigned role, and access status of authorized persons are displayed. The permission levels of seller-related users are controlled through this screen to ensure operational security and proper task distribution.

Through this area, new authorized persons can be defined, and updates can be made to the roles or access statuses of existing users. The Authorized Persons section aims to centrally manage seller-based user access.

***

#### **8. Products**

The Products section is where the seller’s products are listed and basic product information is displayed. On this page, products are listed under the columns Product Name, Barcode, Seller Unique Code, Commission Rate, Product Trademark, Product Category, Stock and Price. This structure allows the seller’s product portfolio, stock status, and pricing information to be monitored from a single screen.

The Products section aims to facilitate seller-based product tracking and enable quick analysis of basic product performance information.

***

#### **9. Orders**

The Orders section is where the seller’s orders are listed and order processes are tracked. Through this section, order statuses, order dates, and total amounts are displayed, enabling operational tracking of orders. The Orders section contributes to monitoring seller performance and managing order processes effectively.

***

#### **10. Accurals**

The Accurals section is where the seller’s financial earnings and payment processes are tracked in detail. This screen displays period-based revenues, deductions, and net payout amounts for the seller in a summarized manner.

In the summary area at the top of the page, the **Total Progress Payment** (TRY) represents the net amount to be paid to the seller at the end of the period and is calculated by taking sales, returns, commissions, and other expenses into account. The **Sales Amount** shows the gross total of sales made within a specific period. **Pending Payments** include amounts that have been processed but not yet transferred to the seller, while **Past Payments** represent the total of completed payments made to the seller in previous periods.

In addition, this section displays the **Cargo interruption**, which represents the costs reflected to the seller for logistics services used in orders, the **Withholding Tax Amount**, calculated at a rate of 1% on the sales amount excluding VAT, and **Other Interruptions**, which include additional deduction items such as commissions, discounts, and penalties.

At the bottom of the page, a list presents detailed payout information by period. This list includes Payout Period, Estimated Payment Date, Payout Amount, Deduction Amount, Net Payout Amount, and Status information. The list can be filtered by criteria such as date, minimum–maximum amount, and status to easily access relevant payout records.

***

#### **11. Services / Features**

The Services / Features section is where additional services and features provided specifically for the seller are listed. Through this section, the types of services that the seller can benefit from are displayed.

***

#### **12. Access**

The Access section is a management area designed to allow platform administrators to access the seller panel, [Lidia Merchant Console](/components/lidia-merchant-console), in a controlled and traceable manner. Through the **“Connect to Seller Panel”** button on this page, direct access to the relevant seller’s Merchant Console screen can be provided. This access is used for providing seller support, reviewing configurations, and quickly investigating operational issues.

After access to the seller panel is established, all actions performed are recorded by the system. In the **Transaction Records** section located at the bottom of the page, details such as the user who accessed the panel, the connection date and time, and the types of actions performed are listed in detail. This structure increases transparency in authorization processes, ensures traceability of actions, and supports operational security.

***

#### **13. Settings**

The Settings section is where operational rules and restrictions related to the seller are managed. This section consists of four main headings: Delivery Settings, Inventory Settings, Order Settings, and Payment Settings. The configurations made here define the seller’s operational capabilities and limitations on the marketplace.

* **Delivery Settings**

In the Delivery Settings section, the delivery methods through which the seller can fulfill orders are defined. In this area, the appropriate options for the seller can be selected from the following:

* [ ] Delivery using courier companies contracted by the marketplace
* [ ] Delivery using courier companies contracted by the merchant
* [ ] Use of the merchant’s own delivery method
* [ ] Allowing the merchant to modify product weight information during the delivery creation stage only for shipments made with courier companies contracted by the marketplace

- **Inventory Settings**

The Inventory Settings section is where restrictions related to the seller’s product and stock management permissions are defined. Through this section, the following limitations can be applied:

* [ ] Restricting the merchant’s ability to add products
* [ ] Allowing the merchant to add products only under specified categories
* [ ] Allowing the merchant to add products only under specified brands
* [ ] Restricting the merchant’s ability to enter stock
* [ ] Restricting the merchant’s ability to set prices

These settings enable product and stock management to be carried out in a more controlled structure.

* **Order Settings**

In the Order Settings section, restrictions regarding the regions in which the seller can sell are defined. In this area, the following authorizations can be configured:

* [ ] Allowing the merchant to select countries
* [ ] Allowing the merchant to select provinces
* [ ] Allowing the merchant to select districts

In addition, requiring the merchant to approve the sales agreement can also be configured from this section.

* **Payment Settings**

In the Payment Settings section, the seller’s maturity periods and payout cycles are defined on a daily basis. Existing payment accounts can be viewed in this area; if needed, a new payment account can be added or existing payment account information can be updated. This structure ensures that payments to the seller are managed in a regular and controlled manner.

### Networks&#x20;

The Networks section, located under the Sellers heading in the left navigation menu, is where dealerships and regional partners that your company has contracted with are managed. This section is designed to centrally track and manage business partners that operate under agreements with your organization, distinct from sellers that directly sell on the marketplace.

From this page, all business partners defined in the system can be listed. Using the **Import Data** button located in the upper-right area, the sample Excel template provided by the Lidia Console can be downloaded. After making the necessary edits in this document, it can be uploaded back to the system to perform bulk dealer creation. This method helps reduce manual effort, especially when onboarding a large number of business partners.

With the **Export Data** button, an Excel file containing the basic information of the listed business partners can be downloaded. This export can be used for reporting, analysis, archiving, or sharing data with other systems. The **Add New Dealer** button allows business partners to be added manually on an individual basis.

When navigating to the detail page of any listed business partner, configurations can be managed under the following sections:

* Main Info
* Page Management
* SEO Management
* Slug Addresses
* Authorized Persons
* Orders
* Services&#x20;
* Settings

This structure enables operational, content-related, and administrative information related to business partners to be controlled from a single centralized location. The Business Partners section allows the company to manage its dealer and partner network in a scalable, traceable, and controlled manner.


# Customers

Regardless of whether they have made a purchase or not, every individual who has created a registration on the platform is considered a customer. The Customers section is the area where all users registered on the platform are centrally managed. Through this section, customers can be listed, their basic information can be viewed, order and payment histories can be tracked, campaigns and coupons they have benefited from can be reviewed, the permissions they granted during registration can be viewed, and referral code definitions can be created.

The Customers module is designed to monitor customer behavior, enable customer segmentation, and support end-to-end analysis of the customer experience.

## **Customer Management**

When entering the Customer Management page, users are first presented with the Customer List screen. On this screen, all customers registered in the system are listed, and for each customer, name and email address, segment information, order count, total order amount, membership date, and active/passive status can be viewed in a single overview. A new customer can also be manually created in the system using the **Add New Customer** button located in the upper-right corner of the page.

### **Customer Details**

When navigating to the customer detail screen, a total of eight main sections are available where customer information and behaviors can be monitored. In the summary area located at the top of these sections, key indicators such as the customer’s name, membership date, last visit date, last order date, total number of orders, total amount spent, and current wallet balance are displayed in real time. This summary area provides a quick overview of customer behavior and facilitates navigation to detailed sections.

#### **1. Basic Information**

This screen displays the basic information entered by the customer during registration. Details such as first and last name, gender, email address, phone number, and account activity status can be viewed and edited depending on user authorization.

#### **2. Addresses**

The Addresses screen is where customer address information is managed. In this section, Delivery Addresses, Corporate Invoice Addresses, and Individual Invoice Addresses are displayed in separate areas. Existing addresses can be edited, or new addresses can be added.

#### **3. Orders**

On the Orders screen, the customer’s entire order history is listed. For each order, information such as order number, product quantity, order date, order amount, payment method used, and order status is displayed. The order list can be filtered by date, order status (Draft, Pending Delivery, New, In Progress, Prepared, Invoiced, In Delivery Process, Delivered, Completed, Not Delivered, Returned, Cancelled, Expired), and request type (cancellation, return). When clicking on the details of any listed order, the user is redirected to the relevant order detail screen under **Sales > Orders** in the left menu.

{% hint style="info" %}
**Note:** This section is explained in detail in the Orders section. To review: [*Orders*](/components/lidia-console/features/order-management).
{% endhint %}

#### **4. Payments**

On the Payments screen, all payment transactions related to the customer are listed. For each payment, information such as transaction code, transaction date, payment method used, instrument group, service provider, and institution is displayed. When clicking on the details of any payment, the user is redirected to the relevant payment detail page under **Finance > Payments** in the left menu.

{% hint style="info" %}
**Note:** This section is explained in detail in the Payments section. To review: [*Payments*](/components/lidia-console/lidia-console-user-guide/finance).
{% endhint %}

#### **5. Campaigns**

On the Campaigns screen, the campaigns that the customer has benefited from are listed. Each campaign is displayed with information such as campaign name, campaign type, and start–end dates. The campaign list can be filtered based on campaign status and discount type (Membership, Promotion, Purchase, After-Sales). When clicking on a campaign detail, the user is redirected to the **Campaign Management > Campaigns** page in the left menu.

{% hint style="info" %}
**Note:** This section is explained in detail in the Campaigns section. To review: [*Campaigns*](/components/lidia-console/lidia-console-user-guide/campaign-management).
{% endhint %}

#### **6. Coupons**

On the Coupons screen, the coupons used by the customer in their orders are listed. This list includes information such as coupon name, coupon type, discount type, discount amount, usage limit, and expiration date. When navigating to the details of any listed coupon, the user is redirected to the **Campaign Management > Coupons** page in the left menu.

{% hint style="info" %}
**Note:** This section is explained in detail in the Coupons section. To review: [*Coupons*](/components/lidia-console/lidia-console-user-guide/campaign-management).
{% endhint %}

***

#### **7. Permissions**

The Permissions screen is where all permissions approved by the customer during marketplace login and usage processes are displayed and managed. On this screen, the customer’s accepted legal permissions, notification permissions, and other mandatory or approval-based preferences can be monitored in detail. Permissions can be filtered and analyzed based on their current status. The permission contents displayed in this section are sourced from the documents uploaded under **Settings > Legal Documents** and referenced by the system. This structure ensures that customer permissions are managed centrally, traceably, and in compliance with legal requirements.

***

#### **8. Logs**

On the Logs screen, the customer’s order and payment logs are listed separately along with date and IP address information. This area is used for tracking customer activities and supporting auditing processes.

## **Permissions**

When the Permissions page is accessed, all customer permissions are displayed on a single screen, listed according to customer ID numbers. This screen allows centralized monitoring of the legal, notification, and other permission types approved by customers and enables quick review of permission statuses.

## **Reference Codes**

A reference code is an identifier used to track where users or transactions originate from and to apply source-specific rules or benefits.\
The Reference Codes screen is the area where reference codes to be used on the platform are defined and managed. Through this screen, new reference codes can be created and a list of all reference codes defined in the system can be viewed. Reference codes can be defined according to different usage types such as platform-based, seller-based, or user-based.

When navigating to the details of any reference code, the Dashboard screen opens first. In the summary panel displayed on this screen, the creation date of the reference code, the start date, and the planned end date are shown. Through the 'stop refferal code validity' and 'expire refferal code'  buttons located in the same area, the active status of the code can be managed. In the side summary panel, statistics such as the usage count of the reference code and access and usage percentages are presented. At the bottom of the Home page, there is a usage detail chart that can be customized based on the selected date range, allowing the performance of the reference code to be visually monitored.

Another section available on the reference code detail screen is the Conditions and Rewards page. Through this page, the conditions under which the reference code will be valid can be defined. By creating role-based, seller-based, or user-based rules, the scope of use and the benefits provided by the reference code can be configured.

On the final section of the detail screen, the General Settings page, the basic configurations of the reference code are managed. In this area, the reference code name, reference code type, usage limit, and validity dates can be viewed and updated when necessary. This structure ensures that the lifecycle of reference codes is fully controlled end to end.


# Product Management

The Product Management section is the main management area that enables all products uploaded by sellers on the marketplace to be created and managed under a single catalog structure, within the rules defined by the platform. Since the system operates with a single catalog logic, sellers can upload products only through the category structures and data schemas determined by the platform. Thanks to this approach, all product data is collected within a standardized, consistent, and centralized data tree; category confusion, field incompatibilities, and data inconsistencies are prevented.

Within this section, operations such as defining the fields and criteria that sellers will use during product uploads, creating categories and category sets, managing product pools, defining brands, and structuring product–variant relationships are carried out. The Product Management area functions as the central structure that determines which category a product belongs to, which mandatory fields it must be uploaded with, how the variant structure is established, and how the product is represented across the marketplace. In this way, product entry processes on the seller side are kept under control, while listing, operational, and reporting processes proceed on a consistent data structure.

## **Pools**

Pools are structures created by the Console administrator to ensure that sellers upload their products in accordance with defined standards and the correct data structure on the platform. Pools are the area where products are initially created and controlled within the system. Products can be uploaded to this area via SAP integration or through Excel files.

Each pool is created based on a specific category and a data schema linked to that category. On the Pools screen, a new pool (product family) is defined using the Add New Product Family button located in the top right corner. In order to create a new product family and add products to it, selecting a category or subcategory from the list is mandatory. The selected category must be associated with a data schema defined in the system.

If a data schema has not yet been created for the relevant category, a data schema must first be defined and then linked to that category. The data schema definition process is carried out via the [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **> Catalog > Product Families** page. On this page, under the Data Schema Fields heading, the required attributes, options, and other field definitions for the relevant product family are configured. These field definitions are created as combinations that differentiate and customize data schemas from one another. Data schemas play a critical role in category creation and in defining product standards.

After all prerequisites are completed and pools are created, the defined product families are listed under the Manage Your Pool List heading. Each product family is displayed together with the total number of products it contains, the categories it is associated with, and its active/passive status. For active product families, if there are products that have not yet passed approval, the label “*X Products Pending Approval*” is displayed. Additionally, each product family includes a Manage Products button. If the number of products contained in a product family is 0, the Delete Product Family button becomes active alongside the Manage Products button.

When the Manage Products button is clicked, four separate pages are displayed under the heading “*View Products in the XXX Pool.*” These pages are Pending Approval, Approved, Rejected, and Published. The number of products on each page is shown next to the page title.

The products listed on these pages are displayed in a comprehensive table consisting of the following columns:

-Basic Information (product name, unique product code, Lidia code, seller item code, group code, image code),\
-Category Information,\
-Brand Information,\
-Options,\
-Attributes,\
-Other Information (short description, tax rate, product status, pool status, creation date).

On the Pending Approval page, Approve / Reject buttons are available for each product. Products can be approved or rejected individually or in bulk. During the rejection process, one of the system-provided rejection reasons must be selected. These rejection reasons include:

* [x] Missing description
* [x] Image not appropriate
* [x] Incorrect product name
* [x] Missing / incorrect category information
* [x] Incorrect volumetric weight information
* [x] Missing / incorrect color information
* [x] Incorrect pool
* [x] Uploaded category not defined under the brand
* [x] Product name and color information mismatch
* [x] Missing / incorrect VAT rate
* [x] Other

When a product is rejected, it is returned to the seller together with the selected rejection reason.

The tools located in the top right corner of the product management screen allow products within the pool to be filtered by seller, enable selected or all listed products to be exported to Excel format, and allow bulk row deletion via the Bulk Updates button. These features enable product management and approval processes to be carried out efficiently from a single center, while ensuring that data control is scalable and operationally sustainable.

## **Categories**

As mentioned earlier, each pool is based on a specific category and a data schema associated with that category. A category is a hierarchical structure in which products are logically grouped within the marketplace. A properly designed category structure ensures that products are listed in the correct place, filtering and search results function accurately, sellers fill in the correct fields when adding products, and business rules such as campaigns and commissions can be managed on a product group basis.

On the Categories page, a new category can be defined using the Add Category button located in the top-right corner. During this process, the category name is entered, the category is mandatorily matched with a data schema, and optionally a parent category can be selected to create a hierarchical structure. Associating a category with a data schema is mandatory. Within the data schema, attributes and options defined in the system are grouped.

* **Attribute**: Represents the defining characteristic of a product.
* **Option**: Represents the values that affect a product’s variants and pricing.

Attributes are defined under [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **> Catalog > Attributes**, and options are defined under [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **> Catalog > Options**.

Added categories are listed hierarchically under the Manage Categories section. In this list, the category name, the number of products in the category, the total number of products under parent categories, and the category status are displayed. When navigating to the details of any category, users are presented with a total of eight different sections related to category management.

* #### **Basic Information**

This section contains the core descriptive information of the category. The category name, category code, integration code, associated data schema, parent category, uploaded visuals (such as a cover image), short and long descriptions, and tag fields are displayed here. All fields can be filled in and existing information can be edited.

* #### **Attributes**

Under the Attributes section, predefined attributes and their associated options can be added to the category using the Add New Attribute button. This area is critical for defining how products under the category will be listed and filtered.

* #### **Product Management**

This page lists all products offered for sale under the selected category, including their images, product names, and product codes. When clicking on the details of any listed product, the user is redirected to the relevant product detail page under Product Management > Products in the Console’s left-hand menu.

* #### **Custom Sorting**

On the Custom Sorting page, products under the category are displayed based on the selected layout type (expanded view, 2-column, 3-column, 4-column, or 5-column view). The order in which products appear on the marketplace can be manually adjusted using drag-and-drop. To change the order of multiple products at once, the **CTRL** key can be used to make multiple selections.

* #### **Filter Management**

The Filter Management page is used to configure category-based filters to improve user experience. Filters can be created based on categories, brands, price ranges, attributes, options, and tags. The order of selected filters can be adjusted to determine which filters appear at the top in the marketplace interface.

* #### **Page Management**

The Page Management section includes the page name, template, page code, and tag information for the category. Using the Add Section button at the bottom of the page, sections, blocks, and core elements can be added to customize the category page. This structure allows category pages to be managed flexibly in terms of visuals and content.

* #### **SEO**

On the SEO page, the category’s meta title, meta description, and URL information can be configured. This area contributes to improved search engine indexing of category pages and helps increase organic traffic.

* #### **Slugs**

Under the Slugs section, the slug information for the category is displayed. This area is used to track and manage category URL structures when needed.

## **Trademarks**

The Trademarks section is the area where the brands associated with products offered for sale on the marketplace, and any existing sub-brand structures, are centrally managed. Through this section, all brands in the system can be defined, edited, ordered, and consistently associated with category and product structures from a single location. Trademark management plays a critical role in ensuring accurate product listings, a reliable filtering experience, the proper organization of category pages, and the healthy operation of campaign setups.

A new trademark can be added to the system using the Add New Trademark button located in the top-right corner of the Trademarks page. During the trademark creation process, the brand name is entered, an optional parent brand is selected if applicable, and a page address (slug) for the brand is defined. This structure allows parent brand–sub-brand relationships to be configured hierarchically. Next to the Add New Trademark button, the Export Data button enables all brands listed in the table to be exported in Excel format; this feature provides convenience for reporting, archiving, and data control processes.

Trademark ordering is not an area that is available by default to all users within the Console. This capability is a feature that can be provided and configured by Lidia management when needed. When the brand ordering feature is activated, the priority order in which brands are listed on the marketplace can be managed, and brand showcase strategies can be shaped accordingly.

Trademarks listed in the table can be deleted; additionally, when navigating to the detail screen of any brand, access to the same eight detail pages explained under the Categories section (Basic Information, Features, Product Management, Custom Ordering, Filter Management, Page Management, SEO, and Page Addresses) is also available through this area.

With this structure, brands are handled in an integrated manner with category, product, filtering, and page management processes, enabling the creation of a consistent, scalable, and manageable brand architecture across the marketplace.

## **Special Lists**

Special Lists are a management area that enables specific product, category, brand, or variant groups to be brought together and presented in line with a particular theme, period, or business objective within the marketplace. This structure allows the creation of special showcase pages such as Year-End Deals, Best Sellers, New Arrivals, and March Campaigns. Through special lists, products can be prioritized independently of the standard category structure, providing users with a more guided and focused shopping experience.

Using the Add New List button located in the top-right corner of the Special Lists page, a new special list can be created by entering a list name and page address. All lists created in this way are displayed under the Special List Management section. When navigating to the detail page of any listed special list, users are presented with a total of eight main sections where the list configuration is managed.

In the first section, Basic Information, fields such as list name, list code, short description, long description, images, and tags are available. This area allows viewing and editing of the core content information of the list. These details define how the list will be presented on the marketplace and which content it will be associated with.

In the second section, List Items, the elements that make up the content of the list are managed. Using the Add New Item button, a single item can be added to the list by selecting a product, category, variant, or brand. During this process, a priority order and active/passive status are defined for each item. Next to the Add New Item button, the Bulk Add Item button allows users to download a sample Excel document provided by the Console, make the necessary edits, and upload it back to the system to add items in bulk. During bulk upload, if the list already contains items, the newly uploaded data replaces the existing items, and only the newly added items are saved.

Using the Export Data button located next to the Bulk Add Item button, selected items or all items within the list can be exported in Excel format. This feature provides convenience for reporting and archiving list content.

For each item listed, information such as priority order, item type, and item name is displayed. By clicking on any item, the content name can be selected and an image can be added. Listed items can be removed from the list when needed or toggled between active and passive states to control their visibility on the marketplace.

The remaining sections on the special list detail screen are Features, Documents, Filter Management, Page Management, SEO, and Page Addresses. These sections function exactly the same as the corresponding structures described in the Categories section. Through these areas, the page structure, filtering options, content components, and SEO settings related to special lists can be managed in detail.

With this structure, special lists become a key component of marketing, showcase, and campaign strategies, enabling products to be presented flexibly and in a controlled manner based on specific scenarios.

## **Products**

The Products section is the area where all products uploaded to the system by sellers are centrally tracked and managed. Products can be added to the system manually via the seller interface, through SAP integration, or by using Excel files. This section ensures that all products available on the marketplace are kept under control in terms of status, content accuracy, and structural consistency.

On the Products screen, main product images, product name, associated brand, associated category, number of variants, product code, and product status are displayed in a single list view. Using the Export Data button located in the top-right corner of the page, selected products or the entire product list can be exported in Excel format. This feature provides convenience for reporting, auditing, and inventory control processes.

When navigating to the detail page of any listed product, a comprehensive detail screen opens where all product-related configurations are managed. This screen consists of multiple sections, each dedicated to a different aspect of product management.

* **Basic Information**\
  The Basic Information section includes the product name, product code, brand, category, tax rate, short description, long description, and tags. All fields except the product code can be edited. This section defines the core descriptive content of the product and the textual information presented to customers on the marketplace.
* **Variants**\
  In the Variants section, all variants associated with the product are listed together with their variant codes. Existing variants can be deleted from this area. Clicking on the details of any variant redirects the user to the corresponding variant detail page under **Product Management > Variants** in the Console left menu. This structure ensures consistent and centralized management of product–variant relationships.
* **Attributes**

  Under the Attributes section, new attributes can be added to the product or its variants from the attributes previously defined in the system. Existing attributes can also be removed when no longer needed. This section is used to manage the technical and distinguishing characteristics of the product.
* **Related Products**

  The Related Products section is used to manage relationships between products. By clicking the Add New Product Relationship button, a relationship type is selected from those previously defined under  [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **> Catalog > Product Relationships**. One or more related products are then selected and linked to the product. This structure supports scenarios such as similar products, complementary products, or alternative product recommendations.
* **Media Management**

  The Media Management section is where product images and documents are managed. Product images can be viewed, reordered, their statuses updated, and one image can be selected as the cover image. Using the Add New Image button, image files can be selected via the file explorer and added to the storefront.\
  Similarly, documents can be added using the Add New Document button. Uploaded documents can be viewed, reordered, and their statuses updated as needed.
* **Page Management, SEO, and Page Addresses**

  The Page Management, SEO, and Page Addresses sections are used to manage the product’s page structure, content components, and search engine visibility on the marketplace. These sections operate with the same logic and functionality as those used in category and special list management.
* **Inventory**

  The final section, Inventory, displays the commercial information related to the product. This includes the seller (merchant) offering the product, variation value, price, and stock information. Inventory data is a critical part of product management for monitoring availability and managing sales readiness.

  With this structure, the Products section brings together content, variant, relationship, media, and inventory management in a single center, providing a consistent, controlled, and scalable product management process across the marketplace.

## **Variants**

In the Lidia Commerce infrastructure, the concepts of product and variant are clearly separated.\
A product represents the main record offered for sale in the system and contains the top-level information shared by all variants. At the product level, information such as product name, brand, category, short and long descriptions, tax rate, and tags is defined. These details are considered common and valid for all variants associated with the product.

A variant represents the sale-specific sub-breakdowns of a product. Variable attributes such as color, size, dimensions, or capacity are managed at the variant level. In Lidia, critical commercial information such as stock, price, barcode, and sales status is defined per variant. This structure allows multiple variants under a single product to be managed independently, enabling more flexible and accurate stock and pricing control. In summary, in Lidia, a product is a single main record, while variants are N individual sales units belonging to that product.

* #### Variants Page

The Variants page is the central area where all variants in the system are listed and managed. On this page, the following information is displayed for each variant in a single list:\
Product image\
Variant name\
Associated brand\
Associated category\
Variant code

This listing structure is designed for fast control and operational tracking, especially in large product catalogs.

Using the filtering tools provided on the page, variants can be filtered by:

* Brand
* Category
* Seller
* Defined attributes in the system (e.g., color, capacity)
* Defined options (e.g., size, dimensions)

This filtering structure enables quick access to the correct variant, particularly in catalogs with a high number of variants.

* #### **Variant Detail Screen**

When navigating to the detail page of any listed variant, a detailed management screen opens where all configurations related to the variant can be managed. This screen follows the same logic as product management but is detailed specifically at the variant level.

On the **Basic Information** page, fields such as variant name, variant code, associated product code, color information, short description, long description, and tags are displayed. These fields define how the variant is identified and presented on the marketplace.

The other pages available on the variant detail screen are as follows:

* **Attributes:** Used to manage attributes defined specifically for the variant. Technical or distinguishing details that differ from the product level are configured here.
* **Related Variants:** Allows relationships to be established between variants. Alternative or complementary variant scenarios are managed in this section.
* **Media Management:** Used to manage images and documents related to the variant. Image ordering, cover image selection, and status updates are handled here.
* **Page Management:** Used to manage the page structure and content components of the variant on the marketplace.
* **SEO:** Enables variant-level search engine optimization by configuring meta title, meta description, and URL settings.
* **Slugs:** Used to manage the slugs where the variant is published.
* **Inventory:** Contains pricing, stock, seller (merchant), and variation value information related to the variant. All commercial data that directly affects sales is controlled from this page.


# Inventory

The Inventory section is the area where all products with defined price and stock information in the system are centrally tracked. Through this section, the product inventory of all sellers operating on the marketplace can be monitored, and warehouse definitions required for sellers to create deliveries using marketplace-contracted logistics providers can be managed. The Inventory module enables stock, pricing, and operational statuses of products to be controlled under a single structure.

The Inventory section consists of two main headings: **Warehouses** and **Inventory**.

* ### **Warehouses**

On the Warehouses page, a list of all warehouses defined by sellers is displayed. As previously mentioned in the seller detail screens under the [Sellers](/components/lidia-console/lidia-console-user-guide/sellers) section in the Console left menu, warehouse definitions are made at the bottom of the Basic Information section for each seller. The primary purpose of defining warehouses is to ensure that the system knows from which outbound warehouse the goods will be shipped, in accordance with the general rules created by shipping profiles.

On this page, a new warehouse can be defined using the **Add New Warehouse** button located in the upper-right corner by entering the warehouse name, warehouse code, and warehouse status information. In addition, the name, code, and status information of listed warehouses can be updated, and warehouses can be deleted when necessary. This structure allows sellers’ logistics processes to be managed in a more controlled and traceable manner.

* ### **Inventories**

On the Inventories page, all products in the system are displayed in a single, consolidated list. This list allows users to track the overall status of the marketplace product inventory. The inventory table includes the following columns:

Product Name, Barcode Code, Seller Unique Code, Trade Name, Store, Brand, Categories, Product Type, Group Code, Stock Status, Price, Commission Rate, and Active/Passive status.

All columns in the list are filterable, making it easy to analyze products based on different criteria. By clicking on any product listed under the Product Name column, the user is redirected to the Variants page under the [Catalog](/components/lidia-console/lidia-console-user-guide/product-management) section in the Console left menu, where detailed information about the selected product can be accessed.

Using the **Export Data to Excel** button located in the upper-right corner of the Inventory page, selected rows from the table or the entire inventory dataset can be exported as an Excel document. This feature enables easy sharing of inventory data for reporting, analysis, and operational tracking purposes.


# Content Management

Content section is the central area where the page structures, visual areas, and user-facing content within the marketplace are managed. Under this heading, the platform’s interface, navigation structure, and showcase layouts can be customized, configured according to different scenarios, and managed through dynamic content controls. Thanks to content management, page layouts, redirects, and visual components can be controlled without the need for technical development, supporting both user experience and operational flexibility.

## **Templates**

In the marketplace system, Templates are predefined structures that enable product and content information to be created with a standard visual and structural layout. Templates under the Content section are designed to ensure that, especially in PDP areas, headings, text fields, and content blocks are presented with the same visual hierarchy and layout logic. This structure provides consistency across the platform and prevents manual and unstructured content creation.

A new template can be created using the Add Template button located in the top-right corner of the Template Management page. During the template creation process, the template type and template name must first be defined. The template type is selected from the options provided by the system: Section, Showcase, Showcase Page, Special List, and Block. During the creation process, the system checks whether the template complies with the rule set of the selected type, and the creation is completed once compliance is confirmed.

All created templates are listed on the Template Management page. When navigating to the details of any template, the user is presented with the Template Type, Template Name, Description, Category, Cover Image, Preview Image, and the main Template Content area where configuration is performed. These fields allow the basic template information to be viewed and edited.

In the Lidia Console, the Template Content area is empty by default. This area is populated only within the structure provided by the selected template type before content is created. Templates do not offer a free-form structure; each template operates with a specific content and layout logic aligned with its intended use.

Within this scope, the Console administrator:

* Creates the template content in accordance with the template types provided by Lidia
* May request the preparation or modification of template content from the Lidia Admin when needed

Templates predefine:

* [x] Which fields the content will consist of
* [x] In which layout these fields will be displayed on the page
* [x] Within which template type the content will be used

Thanks to this structure, content is created with a standard layout, visual and structural consistency is maintained, and content management is handled centrally.

Lidia provides 5 different template types for use in content management. Each template type is designed for a different usage scenario:\
**Section**\
Used to create a separate content area within a page. It allows content to be grouped within a specific layout.\
**Showcase**\
Used to prominently display content, campaigns, or visuals that need to stand out.\
**Showcase Page**\
Used for independent, full-page content created with a showcase logic.\
**Special List**\
Allows multiple items with the same structure to be displayed as a list with a defined ordering logic.\
**Block**\
Used to create small, modular, and reusable content areas within a page.

## **Pages**

Pages is the area where all static and dynamic content presented to users on the marketplace is structured and managed. Through this section, controlled, consistent, and reusable page structures can be created for different content types such as categories, brands, campaigns, stores, or special lists. Page management standardizes both the user experience and content operations by ensuring that content is presented in the correct context, with the correct template and layout.

* **Creating a Page**

A new page can be added to the system using the Create New Page button located in the top-right corner of the Page Management screen. When creating a new page, the page characteristic must first be selected. The page characteristic defines the purpose of the page and the type of content it represents. This field can be one of the following options:\
Standard,Category,Brand,Store,Campaign,Special List,Topic.

After selecting the page characteristic, the page is created by entering the Page Name, Page Code, and Location information. The selected page characteristic directly affects the template and structure used by the page.

* #### **Page Detail**

When navigating to the details of any created page, the user is presented with 4 main sections where the page configuration is managed.

* **Basic Information**

The Basic Information section contains the main definitions of the page. This section includes:

Page name,Page template,Page code,Tags

Since the page characteristic is selected during page creation, the page template field is automatically populated according to the selected characteristic.

* Standard → `generic`
* Category → `category`
* Brand → `trademark`
* Store → `store`
* Campaign → `promotion`
* Special List → `customList`
* Topic → `topic`

This mapping ensures that each page type is created only with the template appropriate to its purpose and that structural consistency is maintained. On the right side of the Page Detail screen, a prototype preview of the created page is displayed. This area allows a quick visual preview of the page’s current structure.

* **Page Structure**

The Page Structure section is the main area where the content layout and components of the page are managed. This area is not a free-form design editor; content is created using predefined content building blocks provided by Lidia Console. This approach ensures that page designs remain consistent and sustainable.

Using the Add Section area, the following General Content Structures can be added to the page:

* -Paragraph  \
  -Basic List  \
  -Button  \
  -Divider  \
  -Video  \
  -Image  \
  -Two-Row Image  \
  -Spacer  \
  -Heading  \
  -Showcase  \
  -Advanced List

Each of these structures is designed to address a specific content need on the page. Content building blocks can be used individually or combined to create blocks. Through the use of blocks:

* Multiple content elements are grouped under a single structure
* Page layout becomes more readable and organized
* The same structure can be reused across different pages

This structure both accelerates content creation and ensures visual and structural consistency across pages.

* **SEO**

In the SEO section, meta title, meta description, and other search engine optimization settings related to the page are configured. This area supports proper indexing of the page by search engines and helps increase organic visibility.

* **Slug**&#x20;

The Slug section displays and manages the page’s URL structure. This field represents the page’s access address on the marketplace and is directly related to SEO.

## **Redirects**

The Redirects section is the area used to centrally manage URL changes on the marketplace. This structure aims to ensure that users and search engines are directed to the correct pages for moved pages, updated content, or URLs that are no longer in use. In this way, both user experience is preserved and potential SEO issues such as broken links and traffic loss are prevented.

Using the Add Redirect button located in the upper right corner of the Redirects page, a new redirect can be defined. During this process, a redirect is created by entering the Old URL and New URL information. The defined redirects are listed with the Old URL, New URL, Redirect Code, and Status columns. The redirect code indicates which HTTP redirect type is used for the relevant URL redirect, while the status information shows whether the redirect is active or inactive.

For scenarios that require bulk operations, the page includes an Import button. With this button, multiple redirects can be added at once by uploading a file prepared in Excel format. Similarly, by using the Export All button, all redirects defined in the system can be exported in Excel format. This feature provides operational convenience for documenting, backing up, and sharing redirect records with different teams.

The Redirects section is a critical management area that supports the smooth publishing of changes made in content management, SEO activities, and page configurations.

## **Menus**

Menus are the core navigation structures that enable users to move easily and quickly between pages within the marketplace. Positioned in fixed areas such as the header and footer, menus operate independently of page content and direct users to relevant pages or links through menu items. This structure aims to provide a consistent and clear user experience across the platform.

Using the Add New Menu button located in the top-right corner of the Menus page, a new menu can be created in the system. During the menu creation process, the menu name is entered and the active/passive status of the menu is defined. Once completed, the menu appears in the menu list and becomes available for editing.

When navigating to the detail view of a menu, the user is presented with the menu name and the area where menu items are managed. In this section, new menu items can be added, existing items can be updated or deleted, and the order of items can be rearranged. The ordering of menu items determines the priority in which they are displayed to users on the marketplace.

When adding a new menu item, the item type is selected first. Item types may include category, brand, product, custom list, content, or custom link. After selecting the item type, the corresponding target is defined and the link behavior is configured. The link can be set to open on the same page or in a new browser tab. Additionally, label information can be added to the menu item, and a visual can be assigned if desired.

Thanks to this flexible structure, menus provide a powerful control area for both content management and user experience. Menu structures support the platform’s information architecture while enabling users to reach the content they are looking for in the fewest possible steps, creating a cohesive and efficient navigation experience across the marketplace.

## **Storefronts**

Storefronts are special page structures within the marketplace that enable specific content to be highlighted in a controlled and attention-grabbing manner. Unlike product listing or category pages, showcases are designed to present selected content—such as campaigns, collections, brands, or seasonal themes—under a single scenario. This structure helps users reach the content the platform aims to highlight more quickly and provides a smooth, guided browsing experience.

A new showcase can be created using the Add New Showcase button located in the top-right corner of the screen. During the showcase creation process, a showcase name is first entered, followed by the selection of a showcase template. The templates provided by the system include No Template, Category Detail Banner, Homepage Showcase, and Category Showcase. The selected template determines how the showcase will be structured and displayed on the marketplace.

When navigating to the detail screen of any created showcase, two main sections are presented. The first section, Basic Information, displays the showcase name and allows management of the showcase’s general identifying information. The second section, Showcase Pages, is where the content structure of the showcase is created and managed. Within this section, new pages can be added to the showcase using the Add Page button.

During the page-adding process, the type of the showcase page is selected. The system offers three different showcase page types: Image Showcase Type, Video Showcase Type, and Template Showcase Type. The image showcase type is used for showcase content built around visuals, while the video showcase type is preferred for scenarios where video-based storytelling is emphasized. The template showcase type enables the creation of more standardized and controlled showcase pages using predefined template structures.

With this structure, showcases become a key component of campaign management, content highlighting, and marketing strategies. While ensuring that the main marketplace flow remains uninterrupted, showcases allow selected content to be brought to the forefront and enable users to access relevant content more quickly through clear and effective guidance.


# Media

The Media section is the central area where all images, documents, videos, and other files used across the marketplace and console are managed. Through this section, media files used in content, products, pages, or showcases can be viewed, edited, their statuses managed, and their usage areas controlled from a single location. Media management plays a critical role in maintaining content consistency, ensuring reusability of assets, and providing operational control.

## **Media List**

The Media List is the main area where all documents in the system are listed, displayed, and tracked. Documents in this area may include binary files, string files, images, videos, and audio files in various formats. The system supports a wide range of file extensions; examples include `.zip`, `.xml`, `.mp4`, `.webp`, `.xlsx`, `.dwg`, `.woff`, `.tif`, `.3gp`, `.7z`, among others.

In the list view, each media item is displayed together with its preview image, media name, file type, file extension, usage area, creation date, and status. Clicking on the thumbnail preview of any document enlarges the image, allowing a quick visual preview.

When navigating to the details of a media item, users are first presented with the Basic Information page. This page includes the uploaded document, media name, media type, file extension, media size, media URL, and media status. These details allow users to quickly review the technical properties of the file and its current status within the system.

Another key section on the media detail screen is the Usage Area section. The Usage Area indicates which content or data structures within the system a media file is used in or can be used in. In this section, users can manage the areas where the media is associated, the related usage codes, and the active or passive status of those areas. This structure enables controlled reuse of the same media across multiple contents and makes it easier to track media relationships.

At the top right of the Media List page, the Export Data button allows selected media items or the entire list to be exported in Excel format. This feature is useful for reporting and inventory tracking. Next to the Export Data button, the Bulk Update button becomes active when one or more media items are selected from the list.

Within Bulk Update operations, users can perform bulk status updates (such as active, passive, ready for publish, draft), apply bulk tag additions, and perform document matching. Through document matching, selected media items are grouped under the same usage area. Additionally, using the Download Selections option, users can download the original uploaded versions of the selected documents.

The search bar on the Media List screen allows filtering by media name, and additional filtering options are available for file type and file extension. This structure enables efficient and controlled management of large-scale media archives.

## **Import Documents**

The Import Documents screen is a management area that allows a large number of images or documents to be uploaded to the system in a single operation. The upload process consists of the steps **Upload Document → Validate Data → Completed**, and each stage progresses in a controlled manner. With this structure, category, brand, and product images as well as document files can be added to the system quickly and securely in compliance with defined standards.

There are four main template types available on the upload screen:

* **Category Image** (2000×2000 px)
* **Brand Image** (2000×2000 px)
* **Product Image** (2000×2000 px)
* **Document**

To upload documents, first select the relevant document type, then add the files you want to upload in the area that opens. After the files are added, you can proceed to the next step using the Continue button.

The next step is the Validate Data stage. On this screen, all uploaded files are automatically checked according to system rules. If any media within the uploaded bulk data does not meet the required conditions in terms of format, size, or content, the system displays a warning and requests that the relevant rows be corrected.

* Supported formats for images: \
  `.jpg`, `.jpeg`, `.png`, `.gif`, `.bmp`, `.jfif`, `.webp`, `.rar`, `.zip`
* Supported formats for documents:\
  &#x20;`.rar`, `.zip`, `.3dmax`, `.3ds`, `.step`, `.stp`, `.dwg`, `.pdf`

At this stage, the Show Only Invalid Rows button simplifies the editing process by listing only the files with errors. If there are no errors in the uploaded data, the message “Your bulk data has been uploaded successfully without errors!” is displayed on the screen, and the Continue option becomes active.

In the final Confirmation step, the upload process is completed and all files are added to the system without issues. Additionally, if needed, additional files can be added during the data validation stage. This structure ensures that the bulk document upload process is managed in a controlled, traceable, and error-resistant manner.

## **Image Management**

This area represents a structure generally referred to as Centralized Media Management (MAM / DAM-like structure). All images used within the marketplace are managed from a single central location under this section.

Image Management provides a folder-based structure that works similarly to a file explorer on a computer. Images are stored under specific folders and managed in an organized manner through these folders.

This structure allows:

* Images to be stored centrally and reused
* Order and hierarchy to be maintained through folders
* Read and write permissions to be controlled
* Image types and update information to be tracked

The Image Management area aims to ensure that all images used across the platform are managed in a structured, controlled, and sustainable way.

## **File Management**

File Management is the area where all documents used within the marketplace are stored and managed in a centralized structure. Similar to image management, it operates with a folder-based structure and provides a file-explorer-like experience.

Through File Management:

* Files such as PDFs, Excel documents, images, and similar formats can be uploaded
* Files can be organized under folders
* File type, size, and update information can be viewed
* Associations between files and different content or data types can be managed

This structure enables centralized control of documents, supports reuse, and ensures a standardized file management process across the platform.

## **Video Management**

Video Management is the area where all videos used within the marketplace are stored and managed in a centralized structure. Similar to image and file management, it operates with a folder-based structure, allowing videos to be organized efficiently.

Through Video Management:

* Video files can be uploaded to the system
* Videos can be organized under folders
* Video type, size, and update information can be viewed
* Associations between videos and different content or data types can be managed

This structure ensures centralized control of video assets, supports reuse, and enables consistent video management across the platform.


# Goal Management

The Goal Management section is the area where operational goals to be applied to sellers—especially logistics-focused goals—are defined and managed in line with the strategies you determine for your marketplace platform. Through this section, seller performance can be guided based on specific criteria, and improvements in operational processes can be supported. Defined goals can be applied on a category-based or seller-based level, providing a flexible targeting structure.

### **Goals**

A new goal can be defined using the **New Goal** button located in the upper-right corner of the Goals page. During the goal creation process, information such as the goal name, goal type (logistics), goal subtype (for example, order delivery to carrier time), goal date range, goal day selection, and goal duration definition (based on hours, days, or time intervals) is entered. Based on this information, a new goal is created in the system.

All defined goals are displayed as a list on the Goals page. This list is filterable, and by using the **Bulk Update** button, the status of selected goals can be updated collectively as active or passive. Users can remove goals from the system using the **Delete** button when necessary.

* ### **Goal Details**

When navigating to the details of any listed goal, two main sections are displayed: **Basic Information** and **Goal Scope**. On the Basic Information page, all details entered during goal creation are displayed, and these details can be edited if needed.

The Goal Scope page is used to determine where the defined goal will be applied. The goal can be applied on a category-based or seller-based level. When category-based application is selected, a selection must be made from all categories and subcategories previously defined in the system. When seller-based application is selected, the options **all sellers** or **specific sellers** are presented. If the specific sellers option is chosen, the names of the sellers to whom the goal will be applied must be entered to complete the targeting.

Through this structure, logistics goals can be applied in a controlled and measurable manner across the entire marketplace or specifically for certain sellers and categories.


# Campaign Management

The Campaign Management section is the area where campaigns and coupons are centrally defined, managed, and tracked on the marketplace platform. Through this section, different campaign and coupon structures can be created to support sales, increase customer engagement, and manage marketing setups. In addition, access to past campaigns and coupons enables retrospective analysis, allowing campaign performance to be evaluated and future marketing strategies to be planned more effectively based on the insights obtained. The Campaign Management module allows marketing activities to be carried out in a controlled, measurable, and sustainable manner.

This section essentially consists of two main headings: **Campaigns** and **Coupons**.

{% hint style="info" %}
*Campaigns* operate based on a specific trigger point. This trigger may occur in different scenarios such as user registration, cart creation, the purchase process, or post-sale actions.\
*Coupons*, on the other hand, are not tied to a flow or scenario; they have a condition-based reward mechanism.
{% endhint %}

### **Promotions**

The Promotions section is the area where campaigns suitable for different marketing scenarios on the marketplace are created, managed, and their performance is tracked. This area enables the design of promotions aimed at different business objectives such as customer acquisition, sales growth, and post-sales incentives.

When entering the Promotions page, a new promotion can be created via the Add New Promotion button located in the upper right corner of the screen. During the campaign creation process, a campaign name is entered and the promotion type is determined based on its intended use. Membership campaigns target users who are members of the platform or who meet specific membership criteria. Promotional campaigns are used to acquire new users or to highlight specific products and services. Purchase campaigns include discounts and benefits designed to encourage users to make purchases. Post-sales campaigns are designed to support customer satisfaction and repeat purchases after an order has been completed.

At this stage, the campaign start and end dates, the campaign scenario (creating a custom campaign or creating a predefined campaign), and a selection from predefined campaigns are also required. When the option to create a custom campaign is selected, the predefined campaigns field is not displayed.

All created promotions are listed under the All tab on the Campaigns page. In this list, the campaign name, priority order, campaign type, date information, and campaign status (active, passive, suspended, test, blocked) are displayed on a single screen. For all or selected campaigns in the list, campaign statuses can be updated in bulk using the Bulk Update button located in the upper right corner.

The Promotions page is also divided into subheadings as Live, Not Live, and Expired. Campaigns that are actively applied are listed under the Live tab, campaigns with a passive status are listed under the Not Live tab, and campaigns whose validity period has ended are listed under the Expired tab.

When entering the detail screen of any listed promotion, a total of 10 main pages that enable actions on the promotion are displayed. From the promotion detail screen, the promotion can be duplicated or deleted.

The pages available on the promotion detail screen and their main functions are as follows:

* **Summary and Performance:** The promotion creation date, start date, and planned end date are displayed. The Pause Promotion Validity and End Promotion Validity buttons in this area allow management of the campaign status. Side panels display the promotion audience, reach and usage rates, as well as revenue and cost information generated by the campaign. At the bottom of the page, a usage detail chart is presented based on the selected date range.
* **Audience:** Used to determine who the campaign will be applied to. The audience type can be selected as Everyone, Fixed Audience, or Custom Audience. When a fixed audience is selected, specific users can be imported by downloading the sample Excel file provided by the Console. In the custom audience option, a dynamic audience can be created by adding criteria such as user ID, email, age, gender, city, district, and segment using AND/OR logic.
* **Conditions and Rewards:** This page defines under which conditions the campaign will be valid and what rewards it will provide. Conditions can be created for fields such as category, brand, merchant, product, variant, product group, cart amount, and payment channel. The campaign can be configured to apply to the entire cart, specific products, or only to users who meet the conditions. Percentage-based or fixed-amount discounts, coupon definitions, and segment associations can be configured.
* **Restrictions:** This page is used to define restrictions such as whether the campaign can be combined with other campaigns, per-user usage limits, total campaign usage limits, and maximum discount amounts per order.
* **Settings:** Basic campaign information can be viewed and edited. In the lower section of the page, the campaign content can be enriched by adding a short description, long description, campaign tag, and small and large images.
* **Cost Settings:** A target cost amount can be defined for the campaign, and the campaign usage can be automatically stopped when this cost is reached. The cost type can be selected as marketplace, seller, or shared.
* **Properties:** This page allows predefined attributes in the system to be added to the campaign, enabling campaigns to be associated with additional properties for reporting and classification purposes.
* **Page Management:** A dedicated page can be created for the campaign. In this area, the page name, template, tags, and page code can be configured. Using the **Add Section** area at the bottom of the page, the page can be further customized with sections, blocks, and basic element components provided by the Console.
* **SEO:** Search engine optimization is enabled by defining the meta title, meta description, and URL for the campaign page.
* **Slugs:** Addresses and priority orders related to the campaign page are defined in this area. This structure is used to determine through which URL and with what priority the campaign page will be published within the platform.

### **Coupons**&#x20;

The Coupons section is the area where coupons and gift vouchers created to encourage users to shop on the marketplace, increase sales, and support campaign strategies are defined, managed, and their performance is tracked. This section enables both instant promotions and long-term incentive mechanisms to be managed in a controlled manner. It also allows access to previously created coupons, enabling retrospective analysis and evaluation.

When you enter the Coupons page, a new coupon can be created via the Add New Coupon button located in the top-right corner of the screen. During the coupon creation process, the coupon name is entered first, and the coupon type is selected. The coupon type can be defined as either a **Coupon** or a **Gift Voucher**. Gift vouchers are generally used to provide balance-like benefits for purposes such as customer satisfaction, post-refund compensation, or special user groups. Then, by entering the coupon’s validity start and end dates, the coupon creation process is completed.

All created coupons are listed under the All tab on the Coupons page. In this list, the coupon name, coupon type, discount type (percentage or fixed), discount amount, usage/limit information, and expiration date are displayed on a single screen. The Coupons page is also divided into two sub-tabs: Inactive and Expired. Coupons with a passive status are listed under the Inactive tab, while coupons whose expiration date has passed are listed under the Expired tab. This structure facilitates access to past coupons and supports analysis and reporting processes.

When the detail screen of any listed coupon is opened, a total of five main pages are available to manage the coupon.

* On the **Dashboard**, the coupon’s creation date, start date, and planned end date are displayed. The coupon status can be managed using the Pause Coupon Validity and End Coupon Validity buttons on this screen. The side panel displays the number of coupon codes, reach and usage percentages, as well as revenue and cost information generated from the coupon. At the bottom of the page, a coupon usage detail chart is presented based on the selected date range.
* On the **Conditions and Rewards** page, the conditions under which the coupon is valid and the rewards it provides are defined. Conditions can be created for fields such as category, brand, special list, seller, variant, cart amount, and per-user usage limit. The discount type to be applied can be configured as either a fixed amount or a percentage.

{% hint style="success" %}
*In campaigns*, the reward granted to the user can vary, such as a coupon, discount, bonus points, special payment options, or similar benefits.\
*In coupons*, the reward is limited to a fixed amount or percentage-based discount.
{% endhint %}

* The **Coupon Codes** page is where coupon codes are managed. On this page, coupon codes are listed and can be added using two methods: Add Single Coupon Code and Add Bulk Coupon Codes. With the single coupon code option, a single code can be created by entering the code, user information, and the active/passive status of the code. When selecting the bulk coupon code option, two methods are available: uploading coupon codes in bulk via an Excel file or generating coupon codes automatically by the system. If continuing with the Excel method, the sample Excel document provided by the Console should be downloaded, edited accordingly, and uploaded back to the system. If continuing with system-generated codes, information such as the number of coupon codes to be created, the character length of the codes, and preferences for letter and number usage must be entered. Coupon codes can consist of letters, numbers, or both. Additionally, using the Export Data button on the Coupon Codes page, all listed coupon codes can be exported as an Excel document.
* On the **General Settings** page, the basic information of the coupon can be viewed and edited. The coupon usage type is selected here as limited or unlimited. In the lower section of the page, the coupon content can be enriched by adding a short description, tags, and small and large images.
* On the **Cost Settings** page, a target cost amount can be defined for the coupon. When the specified target cost is reached, coupon usage can be automatically stopped. The cost type can be selected as marketplace, seller, or shared.


# Sales

The Sales section is the central area where all orders that have taken place on the marketplace are tracked and analyzed end to end. Through this section, it is possible to view in detail which customer made a purchase, from which store, on which date, and for what amount. Order statuses, included products, payment information, and delivery processes can be monitored from this area, enabling both real-time and historical tracking of sales operations.

## **Orders**

The Orders page is located under the Sales module and is the area where all orders created on the platform are listed in detail, filtered, and tracked on an individual order basis. This page enables monitoring each step of the order lifecycle and allows intervention when necessary.From this list, you can export the selected orders or all orders to an Excel file using the Export Data button located in the upper-right corner of the screen, allowing you to document the order data.

When you enter the Orders page, the summary panel located at the top of the screen displays key metrics that allow you to quickly review the overall situation. In this area, the Number of Orders, Number of Ordered Products, Number of Canceled / Returned Orders, Number of Approved Orders, and Number of Delivered / Completed Orders are shown respectively. The purpose of this summary panel is to enable you to evaluate the general status of order operations at a glance and to facilitate daily operational control.

Below the summary panel, the main table lists all orders in the system. This list consists of the columns Order ID, Reference No, Customer Name (including the customer’s email and phone number information), Total Amount, Tags, Order Date, and Order Status. Thanks to the filtering tools provided on the listing screen, you can analyze your orders in detail and manage your operational workload effectively. With the filtering options, orders can be narrowed down by the selected date range, minimum–maximum order amount, order status, and organizational breakdowns. Order status–based filtering options include pending delivery, new order, order in process, prepared order, invoiced orders, delivered orders, completed orders, expired orders, canceled orders, returned orders, and undeliverable orders. In addition, orders can also be filtered by sellers, dealers, user type (guest or registered user), predefined tags in the system, and orders with invoice requests only.

You can export selected orders or all orders in the list to Excel format using the Export Data button located at the top right of the page and document your order data. This feature provides operational convenience for use cases such as reporting, archiving, and data sharing with different teams.

### **Order Detail**

When you navigate to the detail of any order listed, the order’s date and time information along with the order tags assigned to the order are displayed at the top of the page under the Order Detail heading with the #XXXX ID number. An order may have more than one tag. Order tags are used to differentiate orders from one another, facilitate order tracking, and standardize operational classification. From this screen, you can add new tags to the order or remove existing ones.

**1) Summary Template**

The first template displayed on the order detail screen is the Summary section. This area presents the most critical order information in a single view. Within the summary template, the customer’s full name, email or phone number (displayed based on the method selected by the customer during registration), order date and time, order amount (TRY), order number (copyable), order reference number (copyable), and order status are shown. This template serves as a reference point to verify the core identity details of the order and to quickly initiate operational processes.

**2) Customer Information Template**

Located on the right side of the summary template, the Customer Information template displays detailed information about the customer who placed the order. This area includes the customer’s full name, Guest User / Registered User status, and email/phone details. In the row below, delivery information is shown, including the Contact Number and Delivery Address. Using the Update Delivery Address button, the delivery address can be changed; any update made here applies only to the relevant order.

Following the customer template, the Individual Invoice Address and then the Platform Information section are displayed. The Platform Information section enables monitoring of the customer’s overall behavior on the platform and presents metrics such as Membership Date, Last Order Date, Total Order Amount, Total Order Count, and Total Cancellation/Return Request Count. This area supports operational decision-making by allowing a quick evaluation of the customer’s history.

**3) Notes Section**

Below the customer information template, the Notes section is located. By adding notes to orders, you can record important details related to the order, ensure information continuity within the team, and prevent the loss of critical information. Notes are visible only to users who have access to this page, and multiple notes can be added for the same order. This area is generally used for internal operational notes, exceptional case records, or customer communication notes.

**4) Order Activity Template**

Located below the Notes section, the Order Activity template lists all steps that occur from the moment the customer adds the product to the cart until the order is completed, together with date and time information, in chronological order. This section is critical for verifying the steps experienced during the order process and for performing root cause analysis in case of potential issues.

The listed core steps are displayed under the following headings:

* Entered the order process
* Payment preference selected
* Invoice address selected
* Payment successfully completed
* Order process completed
* Order status updated
* Order shipped
* Order delivered

The steps displayed vary depending on the current status of the order; for example, for orders with a status of new, the process is typically visible up to the “Order process completed” step, whereas for orders with a status of in delivery process, the steps may be displayed up to the “Order shipped” stage.

**5) Order Account Breakdown Template**

The Order Account Breakdown template, located below the summary template, presents the revenue and cost items of the order in an itemized and accounted manner with detailed sub-breakdowns. This area allows you to analyze the financial impact of the order, platform costs, and seller shares in a single consolidated view.

**Revenue Table**

* Product Price
* Installment Difference
* Shipping Fee
* Total Revenue

**Cost Table**

* **Internal Costs**
  * Platform Cost
  * Payment Provider Cost
  * Shipping Cost
  * Seller Share
  * Withholding Tax Deduction
  * Refund Amount
  * Cancellation Amount
  * Marketplace Coupon Cost
  * Seller Coupon Cost
  * Marketplace Campaign Cost
  * Seller Campaign Cost
  * Loyalty Points Cost
* **External Costs**
  * External Coupon Cost
  * External Loyalty Points Cost

At the end of the template, the **Total Cost** information is displayed, completing the comprehensive financial summary of the order.

**6) Order Content Template**

The Order Content template, located below the Order Account Breakdown template, displays the operational progress and delivery stages of the products included in the order. In this area, seller information, product name, quantity, barcode number, and delivery stages of the ordered product(s) are listed. Delivery stages are displayed with different steps depending on the order status.

If the order status is **new**, the delivery stages are displayed as follows:\
-New\
-To be prepared\
-To be shipped\
-To be delivered

If the order status is **processing**, the delivery stages progress as follows: \
-Processing\
-To be prepared\
-To be shipped\
-To be delivered

Products that move past the new stage and are taken into processing can be removed from the order at this stage using the Cancel Product button.

When the order status is **prepared**, the delivery stages appear as follows:\
-Processing\
-Prepared\
-To be shipped\
-To be delivered

For products that move from the to be prepared stage to the prepared stage, the preparation date and time are displayed. In the next stage, to be shipped, the planned shipment date is shown.

If the order status is **in delivery process**, the stages are listed as follows:\
-Processing\
-Prepared\
-Delivery created\
-To be delivered

At this stage, delivery type, carrier provider, and delivery code information are displayed. By clicking the View Delivery Process button, you can open the delivery detail screen and access delivery code, shipment tracking number, recipient, and sender information. Using the View in Detail button at the bottom of the page, you are redirected to the [**Logistics**](/components/lidia-console/lidia-console-user-guide/logistics) **> Deliveries** page located in the Console side menu. In addition, at this stage, you can change the delivery status or cancel the delivery using the Intervene Delivery button. All actions performed are logged with your user information; the intervention type may be updating the delivery status or canceling the delivery, and an intervention reason can also be entered.

When the order status is **completed**, along with the information that the products have been delivered, the following details are displayed:

* Delivery type
* Carrier company that performed the delivery
* Order completion duration
* Seller’s average order completion time

Using the Create Request button located under this information, you can select products and enter a return reason to create a return request. If a return is created using a marketplace-contracted carrier, the system provides a return code. In the request creation area, View Seller Performance and Account Breakdown buttons are also available. The account breakdown button displays a detailed, product-based financial summary of the customer’s purchase; this area can be considered a smaller-scale version of the Order Account Breakdown template explained above.

For an order with a created return request, the return reason, the user who made the update, and the update date are displayed. The View Request Details button redirects you to the [**After Sales**](/components/lidia-console/lidia-console-user-guide/after-sales) **> Returns** page in the Console side menu and displays the return details of the relevant order. Additionally, using the Send Return Code to Customer button, the return code of the related delivery can be sent to the customer’s email address.

**7) Invoice Information Template**

The Invoice Information template, located below the Order Content template, is not displayed at every stage of the order. This template generally becomes visible after the order reaches the delivery process stage and a delivery code is created. In this area, the invoice uploaded by the seller who fulfilled the order is listed with the following information: Invoice Type, Invoice Number, Invoice Issue Date, and Order Reference Number. You can access the issued invoice for the order by using the View Invoice button. Additionally, the Invoice Center button within the template redirects you to the [**Invoice Center**](/components/lidia-console/lidia-console-user-guide/invoice-center) **> Invoices** page located in the Console side menu. If the seller has not yet uploaded an invoice, the Request Invoice Upload button can be used to notify the seller and enable tracking of the invoicing process.

**8) Payment Information Template**

The Payment Information template is generally located below the Invoice Information template; if the invoice template is not displayed, it may appear under the Order Content template. In this area, Payment Method, Installment Information, Payer, and Paid Amount are displayed. If the payment was made in installments, the installment plan is listed in detail; the payment flow can be tracked through Installments, Status (paid/unpaid), Payment Date, Amount Due, and Remaining Amount information.


# Logistics

The Logistics section is the central area where all delivery processes across the marketplace are monitored and analyzed end to end. Through this section, it is possible to track in detail which deliveries belong to which orders, which seller shipped them, which cargo company was used, and on which date and from which location the shipment was made. At the same time, information such as the customer associated with the delivery, delivery address, city–district details, the product contents of the shipment, and the current delivery status can be viewed within a single unified structure.

The Logistics module aims to provide transparency, ensure operational visibility, and enable the monitoring of delivery performance. In this way, marketplace administrators can centrally track delivery processes, identify potential delays or issues at an early stage, and carry out reporting and analysis activities in a reliable and structured manner.

## Deliveries

The Deliveries page is a section under the Logistics module where all marketplace deliveries are listed in detail and can be filtered. Through this page, key delivery information is displayed, the current stage of each delivery can be monitored, and the overall status of delivery processes can be followed from an operational perspective.

When this page is accessed, users are presented with a comprehensive list containing operational information related to deliveries. The list includes the following columns respectively: Order Date, Sender Name, Reference No, Courier Company, Tracking Code, Delivery Code, Shipment Date, Delivery Date to Recipient, Recipient, City / District, Delivery Content, and Order Status. This structure allows all key details of each delivery to be monitored from a single screen.

Using the Export Data button located in the upper right corner of the page, deliveries listed on the screen—either selected ones or the entire list—can be exported in Excel format. This feature provides operational convenience for reporting, archiving, or sharing delivery data with different teams.

Each delivery listed on the Deliveries page includes two action buttons. The first button directs the user to the Delivery Detail page of the related delivery. The second button opens a modal window that allows quick access to key information about the delivery’s shipping process. This modal particularly presents the Delivery Code, Shipment Tracking Number, Recipient, and Sender information in a summarized view. At the bottom of the modal, the View Details button is available, which redirects the user to the same delivery detail page opened by the first button, enabling quick navigation between screens.

The Delivery No represents the internal system record of the delivery, whereas the Shipment Tracking No is used to track the physical movements of the shipment on the courier company’s side. The shipment tracking number can be queried via the courier company’s website or integration, allowing the logistics process to be monitored through this identifier.

When navigating to the delivery detail page, the upper section displays the courier company performing the delivery along with the delivery code. If the seller has selected the option to deliver the shipment personally, a delivery number is not generated and this field remains empty. Once the delivery is integrated with the courier company, a Track Shipment button appears in the upper right corner of the screen. This button directs the user to the shipment inquiry page of the relevant courier company.

The first main section on the delivery detail page is the Summary Template. This template displays the customer name, order date, delivery amount (TRY), order number, order reference number, and delivery status. Delivery status may be shown in different states such as delivery code created, handed over to the sender, in delivery process, or delivered. This section enables quick assessment of the current state of the delivery.

Below the summary template, the Delivery Information template presents the recipient’s name and address along with the sender’s name and address. This information clearly shows from where and to where the delivery is being routed.

The next section, the Delivery Content template, displays details of the products included in the shipment. This area lists product name, quantity, product price, applied discount amount, and total amount. In this way, both the financial and product-based contents of the delivery can be viewed on a single screen.

On the right side of the delivery detail page, the Delivery Movements template is displayed. This section presents the main logistics events provided by the courier company step by step in chronological order. Each movement is shown together with location and date–time information. Examples include Shipment Collected, Shipment Loaded onto Vehicle, and Shipment Unloaded from Vehicle. This structure allows users to clearly track the current stage of the delivery process and analyze delivery performance.

This comprehensive structure enables delivery processes on the marketplace to be monitored in a transparent, traceable, and analyzable manner.


# Invoice Center

The Invoice Center is the area where invoices uploaded by sellers after completed transactions on the marketplace are centrally displayed, reviewed, and managed. Through this section, the accuracy of uploaded invoices is checked, approval or rejection processes are carried out, and invoices can be re-evaluated when necessary. Additionally, as a Console admin, you can manually upload invoices on behalf of sellers from this area. The Invoice Center serves as a critical control point that supports transparent, traceable, and compliant management of financial processes.

## Invoices

The Invoices page is the main screen under the Invoice Center where all invoice records are listed. On this page, invoices are grouped under four main headings: All, which lists all invoices in the system; Pending Invoices, which shows invoices awaiting approval or rejection; Approved Invoices, which includes accepted invoices; and Rejected Invoices, which displays invoices that have been rejected. This structure allows invoice statuses to be tracked quickly and clearly.

Using the Export Data button located in the upper right corner of the page, selected invoices or all invoices in the relevant lists can be exported in Excel format. This feature facilitates reporting, archiving, and data sharing for accounting processes. Next to this button, the Add Invoice button allows manual invoice entry. During the invoice upload process, the invoice number, invoice party, invoice date, invoice type, invoice scope, and return code information are entered, and the process is completed by uploading the invoice document in PDF format.

On the All screen of the Invoices page, all uploaded invoices are listed on a row basis. The list displays the user who uploaded the invoice, the invoice party indicating who issued the invoice to whom, the invoice type, the related transaction (order, delivery, or return), the invoice date, and the invoice status. The list can be filtered by invoice type (individual or corporate), invoice scope (order, delivery, return), invoice party, and invoice status. Invoice party options include:\
Seller → Platform, Seller → Buyer, Platform → Seller, Platform → Buyer, Buyer → Seller, and Buyer → Platform.\
Invoice statuses are represented as pending, approved, valid, or rejected.

For invoices with a pending status, Approve / Reject actions are available next to the detail button. At this stage, the invoice can be approved or rejected by selecting a rejection reason. Rejection reasons are chosen from predefined options such as incorrect party selection, incorrect invoice type or scope, or an invalid file. For invoices with approved or rejected status, a Re-evaluate button is available in the detail view. This allows an approved invoice to be rejected by selecting a rejection reason or a previously rejected invoice to be re-evaluated and accepted. For invoices with a valid status, a Re-upload Invoice button is displayed, enabling the information entered during the invoice upload process to be edited.

By clicking the detail button for any listed invoice, the uploaded e-invoice document can be accessed directly in PDF format. This structure ensures that invoice processes are managed end to end under full control, enabling effective auditing and financial verification processes.


# Finance

The Finance section is the central area where all payment transactions carried out on the marketplace are monitored, analyzed, and verified. Through this section, it is possible to track end-to-end which order a payment belongs to, which customer made the payment, the payment amount, the payment method used, and the date on which the payment was completed. The Finance module strengthens both operational and financial control by clearly displaying the order–payment matching. At the same time, it provides a reference structure for identifying, reporting, and, when necessary, technically analyzing issues that may occur in payment flows.

## Payments

The Payments page is the main screen under the Finance module where all payment transactions that have occurred in the system are listed. Each payment record displayed on this page is shown as directly matched with the order to which it belongs. When the order number of any listed payment is clicked, the user is automatically redirected to the [**Sales**](/components/lidia-console/lidia-console-user-guide/sales) **> Orders** page located in the Console left menu and can access the relevant order’s detail screen. This structure enables quick and consistent review of the relationship between payments and orders.

In the list presented on the Payments page, the following information is displayed in columns: the customer’s first and last name, email address, payment amount, masked card number for card payments, payment method, payment date, and payment status. Payment statuses are categorized as Unknown Transactions, Completed Transactions, Redirected Transactions, Expired Transactions, Failed Transactions, Rejected Transactions, and Pending Transactions. Thanks to the filtering tools available on the listing screen, payments can be filtered and analyzed based on payment status, a specified minimum–maximum amount range, and other operational criteria.

When navigating to the details of any payment listed, the user is first presented with the Summary Template. This area contains the most essential information related to the payment transaction. The summary template displays the transaction code, transaction amount , transaction type, the card information used (masked), and the transaction date. This template serves as a reference point for quickly verifying the identity and validation details of the payment.

Below the summary template is the Details Template, which is designed for technical review purposes. The Details template presents a response model structured in JSON format and contains technical status information returned by the system or the payment provider during the payment process. This area displays technical messages such as the transaction status (successful or failed), error codes, and related error descriptions. The information shown is generally intended to inform about integration issues, missing or incorrect parameters, or business rule violations. The Details area particularly supports technical and operations teams in quickly identifying the root cause of issues encountered during the payment process. This section is for informational purposes only and contains system messages that do not require direct user action.

With this structure, the Finance and Payments module enables payment processes to be managed in a transparent, traceable, and auditable manner from both operational and technical perspectives.


# After-Sales

The After Sales section is the central area where cancellation and return requests related to orders placed on the marketplace are managed and tracked. All cancellation and return requests created by customers or operational processes are collected under this module. Through this section, requests can be monitored end-to-end, evaluated by being associated with the relevant orders and deliveries, and after-sales processes can be managed in a controlled, transparent, and traceable manner.

## **Returns**

The Returns section is the central area where all orders with an initiated return request on the marketplace are listed, reviewed, and managed. Under this heading, return requests initiated by customers or sellers can be tracked end to end, and the status of each request can be viewed in detail. This section enables return processes to be managed in a transparent, traceable, and controlled manner.

On the Returns page, all orders with an open return request are displayed in a list format. For each request, the return request number, the related order amount (in TL), and the date the return request was created are shown. The list can be filtered by date, by request status, and by the minimum–maximum TL range of the order amount. Return request statuses are classified as New, In Progress, Completed, Accepted, Withdrawn, and Rejected. This filtering structure allows operational teams to easily distinguish between ongoing and completed return processes.

When you navigate to the details of any listed request, the #XXXXX Request Detail header appears at the top of the page, displaying summary information related to the return request. First, the Summary Template is shown. This template includes the customer’s full name, phone number and email address, the order date and time, the order amount, the related seller store information, the order number, and the order reference number. By clicking on the seller store name, you are redirected to the relevant seller’s store screen within the Seller List page under the [Sellers](/components/lidia-console/lidia-console-user-guide/sellers) section in the Console’s left menu.

Below the summary template is the Request Information template. This area displays the request ID, the party that initiated the process (buyer or seller), the request status, the transaction amount, the request type, sub-reason, and description fields in detail. These details clearly define the reason for the return request and its scope.

Under the Request Information template, the Products Related to the Request template is displayed. The content of this area varies depending on the status of the return request.

* When the request status is New, this template shows only the relevant product or products, quantity information, and amount details.
* When the request status is In Progress, information indicating that a shipment code has been created, along with the date–time details and the carrier name, is displayed. At this stage, the sender must confirm receipt of the products. If the products have not yet been received by the seller, a warning stating “The sender has not yet confirmed receipt of the products” appears on the screen. At this point, the Console admin has the authority to approve or reject return requests for the selected product or products.
* When the request status is Completed, the template displays confirmation information indicating that the request has been approved, along with the date and time, shipment type, approval reason, and description details.
* When the request status is Rejected, the template shows the “Request rejected” information together with the rejection date and time, rejection reason, and description details.

On the right side of the return request detail screen, the Request Movements template is displayed. This template presents the lifecycle of the return request step by step in chronological order. All actions taken throughout the process are recorded here. A sample request flow consists of the steps Process Started, Process Updated, Approved, and Completed. This structure makes it easy to track the current stage of the return process and review all actions taken previously.

The Returns section plays a critical role in ensuring the smooth execution of after-sales operations, maintaining customer satisfaction, and managing return processes under a standardized structure.

## **Cancellations**

The Cancellations section is the area where orders with cancellation requests created on the marketplace are listed and their processes are tracked. On this page, information such as request ID, cancellation request number, order amount (TL), request date, and request status is displayed. The listing screen can be filtered by date, request status, and the minimum–maximum order amount range.

Cancellation requests are tracked under statuses such as New, In Progress, Completed, Accepted, Withdrawn, and Rejected. The detail screen and process management of cancellation requests follow the same workflow and template structure defined in the Returns section. Therefore, for detailed review and management steps of cancellation requests, the **Returns** section can be referenced.


# Solution Center

The Solution Center is the central area where requests and feedback created by users, sellers, or the system within the marketplace are collected, categorized, and tracked in a unified structure. Through this section, it is possible to monitor what each request is related to, the type of request created, and its current status from a single screen. In addition, by managing request types, it becomes possible to control which topics users can create requests for and through which channels. The Solution Center plays a critical role in terms of operational visibility, feedback management, and process standardization.

This section consists of two main headings: **Cases** and **Case Types**.

### **Cases**

The Cases page is the area where all requests and feedback created within the system are listed and monitored. On this page, each request is displayed in a single list together with its request number and creation date. This enables time-based tracking of requests and analysis of operational workload.

Using the Export Data button located at the top right of the page, either selected requests or all listed requests can be exported in Excel format. This feature can be used for reporting, archiving, and sharing with different teams.

When navigating to the detail view of any listed request, the basic information of the user who created the request is displayed. This information includes the user’s first and last name, email address, and phone number. This structure clarifies the relationship between the request and the user, supporting quick responses and accurate communication.

### **Case Type**

The Case Type page is used to define and manage the topics and categories under which requests can be created within the system. This area ensures that requests are collected under a standardized structure and handled by the appropriate teams.

By using the Add New Case Type button located at the top right of the page, a new request type can be created. During the request type creation process, the relevant communication type is selected to configure the request. The communication types defined in the system are grouped under the following headings:

* **ORDER:**\
  Requests related to orders, such as order cancel request, order refund request, and order address change request.
* **PAYMENT:**\
  Requests related to payment and invoicing, such as order invoice request.
* **COMMUNICATION:**\
  General communication requests such as support and help request, partnership request, and general information request.
* **FEEDBACK:**\
  User feedback and complaints such as feedback and suggestion, and complaint and issue reporting.

When navigating to the detail view of any listed communication type on the Case Type page, information such as request type, request name, description, and request status is displayed. These fields can be edited to update existing request types or to deactivate them when necessary. This allows control over which request types are actively used and presented to users within the system.


# Social Features

Social Features is the area where social capabilities aimed at increasing user interaction and enriching the customer experience across the marketplace are managed. Under this section, shopping lists and collections created by customers, product reviews and ratings, as well as evaluations of the sellers they have shopped from, are monitored from a single center. The Social Features section supports tracking user behavior, analyzing customer feedback, and continuously improving the overall platform experience.

### **User Lists**

The User Lists section is the area that allows the management and display of the custom lists created by customers during their shopping experience on the marketplace through a single screen. Customers create these lists via the marketplace interface, and each list is displayed in the console with a unique list ID and the custom list name defined by the customer.

These custom lists may include products that customers have selected to purchase later, lists consisting of liked or favorite products, or any personalized collections created by freely adding products according to their preferences. In this way, customers can organize their shopping journey based on their own needs and track products more easily.

User Lists can be managed not only by customers but also by Console administrators. Using the Add New List button located in the upper-right corner of the page, a console admin can manually create a custom list in the system by entering the list name and list code. This capability supports the creation of special lists for campaign, segmentation, or operational purposes.

Various management actions can be performed on the created lists. The console admin can delete lists, navigate to the list detail page to edit basic information such as the list name and list code, and view the products added to the list by the customer. Additionally, products can be removed from the list or new products can be added to the list by the admin when necessary. With this structure, user lists serve as an effective tool that both enriches the customer experience and provides flexibility from a platform management perspective.

### Ratings and Reviews&#x20;

The Ratings and Reviews section is the central area where evaluations made by customers after their shopping experiences are collected and managed. Through this section, feedback provided about products, order processes, and sellers can be monitored within a single structure, customer satisfaction can be analyzed, and maintaining overall quality standards across the platform is supported. Customer reviews are categorized according to defined criteria and addressed in detail under the relevant subheadings.

* #### **Product Reviews**

The Product Reviews page is the area where customer reviews and ratings for products are reviewed through the admin approval process. When entering the page, product reviews that have been submitted by customers and are awaiting admin approval are first listed under the Review Requests heading. In this list, product information, seller information, and review details are displayed, and each request includes a Finalize Request button. Through this button, the review detail screen opens, where the customer’s star rating (out of 5), written comment, and the review’s date and time are shown. From this screen, the admin can approve the review or reject it by selecting an appropriate rejection reason. Approved or rejected reviews are listed under the Product Reviews section, and each review includes a status label along with a Re-evaluate button. This allows a previously approved review to be rejected or a rejected review to be moved to an approved status. Reviews listed under this section are synchronized live to the marketplace, and the lists can be exported in Excel format using the Export Data button located at the top right of the page.

* #### **Order Reviews**

The Order Reviews page is the area where customer ratings and comments regarding completed orders are managed. When entering the page, order reviews that have been submitted by customers and are awaiting admin approval are listed under the Review Requests heading. The screen structure, workflow, and review process on this page operate in the same way as product reviews. The admin can review the order-related feedback, approve the review, or reject it by specifying a rejection reason. Additionally, previously approved or rejected reviews can be reprocessed through the Re-evaluate button. Approved order reviews are published on the marketplace, making the customer experience visible.

* #### **Seller Reviews**

The Seller Reviews page is the area where ratings and comments given by customers to sellers they have shopped from are reviewed and managed. On this page, seller reviews that have been submitted by customers and are awaiting the admin approval process are listed under the Review Requests heading. The screen structure and review workflow are identical to those of product and order reviews. The admin can review the rating and comment given to the seller, approve the review to publish it on the marketplace, or reject it by specifying a rejection reason. Previously finalized reviews can be taken back into the review process using the Re-evaluate button. Approved seller reviews enable transparent monitoring of seller performance and support a sense of reliability across the marketplace.


# Operational Tasks

The Operational Tasks section is the area where background processes that support the technical and operational continuity of the platform are managed. This section is designed to maintain system performance, ensure data consistency, and enable quick responses to instant or periodic operational needs. Especially after high traffic, data updates, or system-level changes, the tools that support the platform’s operation with up-to-date and accurate data are provided under this heading.

***

### **Cache Management**

The Cache Management page is the central area where you can monitor and manage the cache structures used in the system. On this page, the total data counts of the caches created across the platform are displayed, providing an overall view of the current cache status. Caches are used to improve system performance, reduce page load times, and enable faster access to frequently used data.

Through this area, all cache data can be cleared in bulk when needed. Bulk clearing is generally preferred after changes to prices, stock, campaigns, content, or configurations to ensure that the system regenerates the most up-to-date data. In addition, by accessing cache detail screens, it is also possible to selectively delete cache records belonging only to specific data groups. This allows relevant data to be refreshed without affecting the entire system.

The Cache Management section plays a critical role in operational control, troubleshooting, and ensuring that changes made in the system are accurately reflected in the user interface. With this structure, Console admins can manage platform performance in a controlled and secure manner.


# Reports

The Reports section is a centralized reporting area designed to measure, analyze, and support decision-making processes for all commercial and operational activities carried out on the marketplace. Through this section, sales performance, operational processes, cost structures, campaign effectiveness, and legal reporting requirements can be comprehensively monitored. Reports provide managers, operations teams, and finance teams with the ability to evaluate the current state of the platform using numerical data and to take strategic actions.

Under the Reports heading, there are five main sub-sections: **Sales Reports**, **Operations Reports**, **Cost Reports**, **Campaign Reports**, and **Withholding Tax Declaration Reports**. All of these reports are structured to offer a consistent user experience. On each report screen, the Export Data button located in the upper-right corner allows the displayed report data to be exported in Excel format. This feature facilitates archiving reports, sharing them with different teams, and using them for further analysis.

### **Sales Report**

The Sales Report section is the main reporting area where all sales realized on the marketplace can be analyzed both in summary and in detail. Under this heading, the user is first presented with a graph showing sales amount and number of products sold on a date basis. Using the date range filter on the graph, the desired period can be selected, and once a filter is applied, the order list displayed below is filtered simultaneously. This synchronized structure enables sales performance for a specific period to be evaluated both visually and in tabular form together, helping to quickly analyze periodic trends as well as increases or decreases.

Directly below the graph, a comprehensive and detailed order list related to sales is displayed. Through this list, for each order, it is possible to view in a single screen: the order reference number, line code, customer information (including the customer’s total number of orders to date, email address, and phone number), the merchant to which the order belongs, the category and brand of the product, the purchased product name and quantity, the province and district breakdown of the order address, the invoice type, and the logistics details indicating which shipping company the order was or will be shipped with.

In addition, the sales report presents revenue items such as order shipment status, payment status, shipping revenue, product revenue, and maturity difference revenue; direct cost items such as product costs and payment provider costs; and indirect cost items such as shipping, platform, and marketing costs in detail. The report also includes the date on which the order was realized, any cancellation or return costs if applicable, loyalty points used, and the current order status. In this way, an end-to-end profitability analysis can be performed for each individual order.

When the details of any order row listed are selected, the user is automatically redirected to the relevant order detail page under [**Sales**](/components/lidia-console/lidia-console-user-guide/sales) **> Orders** in the Console left menu. The information displayed on the order detail screen, the available actions, and the operational workflows are explained in detail under the Orders section within the [Sales](/components/lidia-console/lidia-console-user-guide/sales) heading. This redirection enables a seamless transition from reporting to operations, allowing analysis and action processes to be managed without interruption.

### **Operational Reports**

Operational Reports offer a visual structure similar to sales reports, but differ in purpose and focus. The primary objective of this report is to enable analysis of orders based on operational flow, product-level movements, and process performance rather than financial outcomes.

Under this section, users are first presented with a date-based chart displaying sales amount and number of products sold. The desired date range can be selected directly on the chart to apply filtering. Based on the selected date range, both the chart and the list displayed immediately below it are updated synchronously. This structure allows operational intensity within a specific period to be evaluated simultaneously through both visual and tabular views. Although structurally similar to the sales report, the chart in operational reports is designed to track process volume and product movements rather than order performance.

In the comprehensive list displayed beneath the chart, the following fields are presented on a single screen: reference number, barcode, customer full name, total order count, email information, merchant and trade name, current account code, category, brand, product code, product name and quantity, order address (city/district), invoice type, shipping company, shipment status, payment status, shipping and product revenues, product, platform, and marketing costs, transaction date, product cancellation and return costs, loyalty points, external costs, and order status. These fields enable end-to-end evaluation of the operational and logistics aspects of orders.

The key distinction between operational reports and sales reports lies in the absence of a fixed order number at the center of the analysis. While sales reports typically structure listings around order numbers and order lines, operational reports emphasize product, merchant, category, logistics, and cost breakdowns. As a result, operational reports more clearly reveal product movements within the system independent of individual orders, highlight where operational intensity occurs, and identify the operational costs generated at different stages.

### **Cost Reports**

Cost Reports is a reporting area that enables detailed analysis of cost items related to transactions carried out on the platform. Like other reporting pages, this report is structured with a chart section at the top and a detailed listing area at the bottom. While the chart area allows for a quick view of overall trends, the main analysis is performed through the listing area.

In this report, the listing is based on Delivery ID. For each delivery, the associated order, the seller who fulfilled it, and all financial breakdowns related to the delivery are displayed in a single row. The list includes total delivery amount, product cost, delivery fee, commission amount, installment difference, shipping cost, platform and other operational costs, as well as cancellation–return costs and loyalty point costs, if any. This structure enables the cost impact of each delivery on both the platform and the seller to be examined in a detailed and comparable manner.

The primary purpose of Cost Reports is to make cost items generated throughout delivery and order processes visible on a per-item basis. Through this report, the costs created by each delivery on the platform and seller sides can be clearly tracked, supporting effective control of operational costs.

When any row in the list is clicked, the user is directed to the relevant order detail screen under Sales > Orders in the Console left menu. This allows direct linkage between cost data and order details, enabling end-to-end analysis.

### **Campaign Report**

The Campaign Report is located under the Marketing section within the Reports heading and follows a structure similar to other reporting screens, consisting of a chart in the upper section and a detailed list in the lower section. While the chart area allows for a quick view of the overall impact of campaigns, detailed analysis is carried out through the listing area.

In this report, the listing progresses based on the reference number. For each reference number, product barcode, customer and seller information, product category and brand details, address, invoice, and shipment information are displayed. One of the key fields that distinguishes the campaign report from other reports is the Audience Type; this field allows clear tracking of which target audience the campaign was applied to. In addition, campaign type, product cost, any cancellation–return costs, loyalty point usage, and status information are also shown. This structure enables the performance and impact of campaigns to be evaluated on a product, customer, and audience basis.

### **Withholding Tax Declaration Reports**

Withholding Tax Declaration Reports are a reporting area provided to track withholding tax calculations related to sales transactions on the platform in compliance with legal regulations and to support declaration processes. Unlike other reports, this report does not include charts; it is structured entirely around summary and detail lists focused on declaration and accounting. The purpose is to present the amounts subject to withholding tax on a periodic basis in a clear, traceable, and auditable manner.

Under the Summary Reports heading, the list consists of the following columns: Period, Sender, VAT-Included Sales Amount, VAT-Excluded Sales Amount, Withholding Tax Rate, and Description. This view aims to present, at a summary level, which sales belonging to which seller or sender are subject to withholding tax, at what rate, and what the tax base amounts are for the relevant period. In this way, period-based withholding tax liabilities can be quickly reviewed and compared prior to declaration.

On the Detail Reports page, the focus shifts to the collection aspect of withholding tax calculations. This section includes the fields Period, Total Collected Amount, and Description. Detail reports enable tracking of the total amounts collected from sales subject to withholding tax on a periodic basis and help ensure consistency between accounting records and declaration processes.


# Audit Reports

Audit Reports are a reporting area designed to ensure the traceability and transparency of all critical actions performed on the platform. This section enables user activities to be logged, reviewed retrospectively, and operational processes to be auditable. It serves as a key reference point for system security, internal control mechanisms, and regulatory compliance.

### **Transaction Logs**

The Transaction Logs page is the area within audit reports where all user actions performed on the platform are listed in detail. When this page is accessed, under the Audit Logs heading, the first and last names of users, IP addresses, date and time of the action, and the type of action performed by users who have logged into the system or made any changes are displayed on a single screen.

The primary purpose of this section is to make it visible that all activities within the operational system are recorded and to provide access to reports of these activities when needed. Configuration changes, updates, and other critical actions performed in the Console can be monitored here. This allows authorized users to review past actions retrospectively, identify the source of potential issues or unauthorized activities, and manage audit processes in a reliable and effective manner.


# Features

The feature guides provide in-depth information about the features, including their practical uses, advantages for businesses, and real-world applications.

{% hint style="warning" %}
This information can be valuable for individuals such as **business owners**, **product owners**, or **developers**.
{% endhint %}

Lidia Console is an essential component of the Lidia digital commerce suites, designed to provide a comprehensive management interface for administrators. Here are its key features:

1. [**User Roles and Permissions**:](/components/lidia-console/features/user-roles-and-permissions) Lidia Console supports defining various user roles and permissions, allowing different levels of access for team members, ensuring secure and structured management of operations​.
2. [**Order Management**](/components/lidia-console/features/order-management): It offers robust **order management** tools, enabling businesses to track orders, process returns, and manage order fulfillment efficiently​​.
3. [**Inventory Management**](/components/lidia-merchant-console/features/customer-management): Lidia Console includes **inventory management** capabilities, allowing administrators and merchants to track stock levels and manage inventory in real time​​.
4. [**Customer Management**](/components/lidia-console/features/customer-management): Lidia Console features a **customer management** system, which helps businesses handle customer data, track order history, and manage after-sales services​​.
5. [**Promotions and Discounts**](/components/lidia-console/features/promotions-and-discounts): It also includes tools to manage **promotions and discounts**, enabling businesses to create and track various promotional offers​.
6. [**Analytics & Reporting**](/components/lidia-console/features/analytics-and-reporting): Lidia Console provides comprehensive **analytics and reporting** features, giving businesses insights into sales performance, customer behavior, and operational efficiency​.

These features make Lidia Console a vital tool for running efficient, scalable digital commerce operations across various business models like B2B, B2C, and marketplace environments.


# User Roles & Permissions

## 1. **Role-Based Access Control (RBAC)**

This feature allows administrators to assign different access levels to users based on their roles within the organization. It ensures that team members only have access to the tools, data, and features they need to perform their job. Key aspects of RBAC include:

* **Predefined Roles**: Common roles like Admin, Editor, and Viewer come with predefined permissions that map to standard team functions.
  * **Admin**: Full access, including user management, settings, and reporting.
  * **Editor**: Can modify content, manage products, and make operational changes but without administrative privileges.
  * **Viewer**: Read-only access, suitable for stakeholders who need insights but should not alter any data or settings.
* **Permission Layers**: Access can be segmented into different layers such as product management, sales, content, or customer data, ensuring specific users are limited to the areas relevant to them.

## **2. Customizable User Roles**

Customizable roles allow organizations to tailor the permissions structure to their unique workflows. For example, you can create a role like “Logistics Manager” with specific permissions tied to managing inventory, shipments, and supplier relations. Features include:

* **Granular Permission Settings**: Define permissions for viewing, editing, or deleting items. For instance, a user can be allowed to view orders but not modify them.
* **Custom Workflows**: Roles can be designed around specific business processes, such as allowing access to the product catalog but restricting access to financial or customer data.
* **Role Templates**: Save custom roles as templates to be applied across multiple teams or projects, speeding up user onboarding.

## **3. Audit Trail**

The audit trail feature ensures accountability and transparency by tracking every action made within the platform. This means administrators can:

* **Track Changes**: View a record of actions taken by each user, including edits to products, changes to settings, or modifications to permissions.
* **User Accountability**: Identify who made specific changes and when they were made, helping ensure responsible use of the system.
* **Comprehensive Logs**: Logs can be filtered by user, date, or specific actions (e.g., product updates or order management), providing a detailed view for compliance and security purposes.
* **Security and Compliance**: The audit trail also serves as a vital tool for regulatory compliance, ensuring the business can demonstrate secure and controlled access to sensitive data.


# Order Management

## 1. **Real-Time Tracking**

This feature allows businesses to **monitor the status of all orders** from the moment they are placed to when they are delivered. Users can track every step in the order lifecycle, including:

* Order placement
* Payment processing
* Inventory checks
* Shipment status
* Final delivery

With **real-time updates**, businesses gain full visibility into each order's progress, reducing the likelihood of errors and ensuring timely resolution of any issues. It also provides **transparency for customers**, improving their experience by keeping them informed about the location and status of their purchases.

## 2. **Order Fulfillment**

The **Order Fulfillment** feature is designed to **simplify and automate the process of fulfilling orders** by integrating directly with various **shipping and logistics providers**. This feature helps:

* Automatically generate shipping labels
* Select optimal shipping providers based on location, speed, or cost
* Track shipments through integrated logistics services
* Ensure timely dispatch and delivery

By streamlining the fulfillment process, businesses reduce manual effort, minimize errors, and improve delivery times, leading to enhanced customer satisfaction.

## 3. **Returns and Cancellations**

The **Returns and Cancellations** feature allows businesses to **handle returns, order cancellations, and refunds** efficiently. It automates key steps like:

* Processing customer return requests
* Approving refunds
* Restocking returned items to inventory
* Cancelling orders before shipment

Integration with payment gateways ensures that refunds are processed quickly and accurately, providing a **hassle-free experience for both businesses and customers**. This feature helps reduce operational costs and ensures customers are more likely to trust and return to the platform.

Each of these features is designed to **optimize order management**, reduce errors, and enhance both operational efficiency and the overall customer experience.


# Inventory Management

## 1. **Stock Management**

This feature enables businesses to **monitor and manage inventory levels** in real-time. It allows users to:

* Track **stock levels** for all products
* Receive **low-stock alerts** to prevent shortages
* Set automatic **restocking schedules** based on demand forecasts or thresholds

By keeping a close eye on inventory, businesses can ensure that popular items are always available, minimize the risk of stockouts, and optimize their inventory holding costs. This also helps in **preventing overstocking** by setting limits for each product, thereby ensuring a balanced stock level.

## 2. **Batch Processing**

The **Batch Processing** feature allows users to **make bulk updates** to product listings and inventory data with just a few steps. Key functionalities include:

* Uploading and editing **multiple product entries** at once
* Updating **pricing, stock levels, and product details** in bulk
* Streamlining product listing management by using familiar tools such as spreadsheets

This feature saves time and reduces manual errors, especially when businesses need to manage large product catalogs or make frequent updates across multiple listings.

## 3. **Warehouse Integration**

The **Warehouse Integration** feature provides a seamless connection between the platform and external warehouses. It ensures **accurate stock counts and product availability** by:

* Syncing inventory data between the platform and **warehouse management systems**
* Providing **real-time visibility** of stock levels across multiple locations
* Ensuring that stock availability reflects actual warehouse data, reducing the risk of overselling

This integration leads to better **order fulfillment** efficiency, optimized warehouse operations, and improved customer satisfaction by ensuring accurate delivery expectations.

####


# Customer Management

## 1. **Customer Profiles**

The **Customer Profiles** feature provides businesses with a **comprehensive view** of each customer’s activity and preferences. It includes:

* **Purchase history**: Track all past orders and transactions.
* **Feedback and reviews**: Access customer reviews and ratings for products or services.
* **Personal preferences**: View customer preferences based on their browsing, purchases, and interaction patterns.

This detailed information allows businesses to **personalize marketing** efforts, provide better customer service, and create targeted offers that align with customer interests.

## 2. **Segmentation Tools**

**Segmentation Tools** allow businesses to **categorize customers** into different groups based on specific criteria, such as:

* **Demographics**: Age, gender, location, etc.
* **Purchase behavior**: Frequency of purchases, average order value, or product preferences.
* **Engagement levels**: Customers who frequently interact with marketing emails or campaigns.

These segments enable businesses to run **targeted marketing campaigns** and **personalized communication**, improving customer engagement and retention. Segmentation helps to maximize the effectiveness of marketing efforts by delivering the right message to the right audience.

## 3. **Communication Management**

The **Communication Management** feature streamlines all customer interactions through **integrated messaging tools**, including:

* **Email campaigns**: Send targeted emails to individual customers or specific segments.
* **Customer support interactions**: Manage support requests and queries within the platform.
* **Automated notifications**: Set up automatic messages for order confirmations, shipping updates, and other customer touchpoints.

By managing communication in one centralized place, businesses can ensure **consistent and efficient engagement**, improving customer satisfaction and fostering stronger relationships.


# Promotions & Discounts

Lidia Console offers robust tools for managing promotions and discounts, ensuring that businesses can create effective strategies to attract and retain customers. The features include Coupon Management, Personalized Offers, and Promotion Analytics, which provide comprehensive control over promotional activities.

## **1. Coupon Management**

* **Create Coupons:** Administrators can easily create discount coupons for specific products, categories, or the entire cart. These coupons can be percentage-based or fixed-amount discounts and have customizable conditions such as expiration dates, usage limits, and customer eligibility.
* **Manage Coupons:** Lidia Console simplifies the management of existing coupons by allowing users to edit, activate, or deactivate them as needed. This feature ensures flexibility in adjusting ongoing promotional strategies.
* **Track Performance:** Businesses can monitor how coupons are performing by tracking their usage frequency and effectiveness. This allows for real-time adjustments to promotion campaigns based on customer response.

## **2. Personalized Offers**

* **Target Specific Segments:** Lidia Console allows businesses to create customized offers for particular customer segments based on purchase history, location, or behavior. This ensures that promotions are relevant and appealing to each customer group.
* **Dynamic Personalization:** Leveraging customer data, the system can generate offers that dynamically adjust based on real-time interactions, boosting engagement and conversion rates.
* **Offer Control:** Administrators have full control over how and when offers are displayed, ensuring precise targeting for maximum impact.

## **3. Promotion Analytics**

* **Detailed Reporting:** The analytics tools within Lidia Console provide in-depth reports on promotional campaigns, tracking metrics such as conversion rates, coupon redemption, and sales generated from specific offers.
* **Data-Driven Insights:** Businesses can use these insights to measure the success of their campaigns and refine future promotional strategies based on customer behavior and campaign performance.
* **Customizable Dashboards:** Users can configure dashboards to display the most relevant data points, allowing for easy monitoring of key promotional metrics.

***


# Analytics & Reporting

Lidia Console provides comprehensive **Analytics & Reporting** tools that empower businesses to make data-driven decisions. The system includes **Sales Analytics**, **Customer Insights**, and **Inventory Reports**, each offering detailed, real-time data to enhance operational efficiency and strategic planning.

## **1. Sales Analytics**

* **Track Sales Performance:** Lidia Console's real-time reporting dashboards allow businesses to monitor sales performance dynamically. This includes tracking key metrics such as revenue, units sold, average order value, and sales by category or product.
* **Customizable Dashboards:** Users can tailor the dashboard views to focus on the most relevant data, ensuring quick access to essential sales metrics. Filters can be applied to break down sales by region, time period, or channel.
* **Historical Comparisons:** Easily compare current sales data with previous periods to identify trends, seasonality effects, or the impact of promotional activities.

## **2. Customer Insights**

* **Behavior Analysis:** Lidia Console offers deep insights into customer behavior, including purchase patterns, browsing habits, and product preferences. This helps businesses understand what drives customer engagement and retention.
* **Segmentation and Targeting:** By analyzing customer demographics, purchasing frequency, and average spend, businesses can segment their customer base to target future marketing efforts more effectively.
* **Campaign Optimization:** Customer insights also help optimize promotional and marketing campaigns by identifying which customer groups respond best to specific offers, allowing for more personalized marketing strategies.

## **3. Inventory Reports**

* **Track Inventory Turnover:** Detailed inventory reports show how quickly products are being sold, helping businesses measure stock turnover and plan restocking more effectively.
* **Stock Level Monitoring:** Lidia Console provides real-time visibility into stock levels across all products and warehouses, ensuring that businesses can avoid stockouts or overstocking.
* **Restocking Alerts:** Based on sales velocity and turnover rates, the system can generate restocking recommendations, enabling timely inventory replenishment to meet customer demand.


# Lidia Merchant Console

## Overview

Lidia Merchant Console is a specialized management tool designed for merchants operating within digital commerce platforms powered by Lidia Suites, such as online marketplaces. This console offers a comprehensive interface for merchants to manage their inventory, orders, payments, and customer interactions. It provides merchants with the autonomy and flexibility they need to handle their day-to-day operations efficiently while integrating seamlessly with the broader marketplace or e-commerce system.

***

## Key Features

#### 1. **Inventory Management**

Lidia Merchant Console provides robust tools for managing inventory across various product categories and locations. Merchants can easily update stock levels, monitor inventory movements, and set alerts for low-stock items.

* **Real-Time Stock Updates**: Merchants can adjust inventory in real time, ensuring accurate stock levels are displayed on the storefront.
* **Bulk Inventory Uploads**: Upload product data and stock levels in bulk via CSV or API, simplifying the process of managing large inventories.
* **Stock Alerts**: Set automatic notifications for low-stock items, enabling timely restocking.

#### 2. **Order Management**

The order management system within Lidia Merchant Console enables merchants to track and process incoming orders efficiently. It covers the full lifecycle of an order, from order placement to shipping and returns.

* **Order Tracking**: View and manage all orders from a centralized dashboard, with status updates (e.g., processing, shipped, delivered).
* **Shipping and Fulfillment**: Manage shipping operations by integrating with logistics providers or handling deliveries manually.
* **Returns and Refunds**: Process returns and refunds with built-in tools to ensure smooth after-sales operations and customer satisfaction.

#### 3. **Catalog Management**

Merchants can manage their product listings with ease through the catalog management feature. This includes adding new products, editing existing listings, and optimizing product descriptions for SEO.

* **Product Listings**: Create and edit product information, including images, descriptions, and pricing.
* **Category Management**: Organize products into relevant categories for easy navigation and discovery by customers.
* **Product Variants**: Manage product variations such as size, color, and model with flexible options to enhance the customer shopping experience.

#### 4. **Payment and Payout Management**

Lidia Merchant Console simplifies payment processes by integrating with multiple payment gateways. Merchants can track payments, view transaction history, and manage their payouts from the platform.

* **Payment Tracking**: Monitor payment statuses for completed and pending transactions.
* **Automated Payouts**: Once orders are fulfilled, merchants receive payouts through the platform's automated payout system, which accounts for any commission fees.
* **Financial Reporting**: Access detailed reports of transactions, commissions, and payouts for accounting and financial planning purposes.

#### 5. **Customer Management**

Merchants can access customer data related to their transactions and orders, allowing them to offer better customer support and enhance overall customer satisfaction.

* **Customer Profiles**: View detailed profiles of customers, including order history and contact information.
* **Order Communication**: Communicate directly with customers regarding orders, shipping, and support inquiries.
* **Customer Support Integration**: Link with customer service systems for handling complaints, inquiries, or after-sales service.

#### 6. **Promotions and Discounts**

Merchants can create promotions and apply discounts to their products, boosting visibility and increasing sales during specific periods or events.

* **Discount Codes**: Generate unique coupon codes that can be applied to specific products or across the entire store.
* **Promotional Campaigns**: Schedule and manage sales campaigns, providing customers with special offers like buy-one-get-one or percentage discounts.
* **Visibility Boost**: Promotions help increase the visibility of products on the marketplace or e-commerce platform, driving more traffic to the merchant's storefront.

#### 7. **Analytics and Reporting**

Lidia Merchant Console provides merchants with access to advanced analytics and reporting tools to track business performance, sales, and customer behavior.

* **Sales Reports**: Track sales performance over time, with options to filter by date, product category, and order status.
* **Customer Insights**: Analyze customer purchasing behavior, including repeat purchases, average order value, and demographics.
* **Inventory Turnover**: Monitor how quickly inventory is moving and identify slow-moving products that may need discounts or promotions.
* **Custom Reports**: Generate customized reports based on specific business KPIs, helping merchants make informed decisions.

***

## Integration Capabilities

Lidia Merchant Console is designed to integrate seamlessly with various external systems, ensuring that merchants can manage their operations holistically. From payment gateways to logistics providers, the console supports a wide range of third-party integrations.

* **Payment Gateway Integration**: Connect with multiple payment providers to handle secure transactions across different currencies and regions.
* **Logistics Integration**: Integrate with logistics providers for shipping and fulfillment, allowing real-time tracking and delivery updates.
* **ERP/CRM Systems**: Sync product and customer data with enterprise resource planning (ERP) and customer relationship management (CRM) systems for unified business operations.

***

## Advanced Features

### **Merchant Dashboard**

The merchant dashboard provides a real-time overview of the most important metrics, including sales figures, order statuses, inventory levels, and customer interactions. It serves as the main entry point for merchants to access all relevant business information at a glance.

* **Customizable Widgets**: Personalize the dashboard to display specific metrics such as daily sales, pending orders, or top-selling products.
* **Quick Access**: Get instant access to key features like inventory updates, order processing, and customer inquiries.

### **Multi-Channel Support**

For merchants operating across multiple channels, Lidia Merchant Console supports the management of products and sales across these platforms from a single interface. This feature is especially useful for those selling on both an online marketplace and their own e-commerce site.

* **Centralized Management**: Manage inventory, orders, and promotions across multiple channels from one location.
* **Channel-Specific Promotions**: Tailor promotions and pricing strategies for different sales channels.

### **Shipping and Logistics**

Lidia Merchant Console integrates with logistics providers, enabling merchants to manage shipping directly from the platform. Merchants can print shipping labels, track deliveries, and automate returns processes.

* **Shipping Label Generation**: Generate shipping labels directly within the console for quick and efficient order fulfillment.
* **Delivery Tracking**: Monitor the progress of shipments through integrated logistics services.
* **Returns Management**: Handle return requests and track the status of returns for full visibility and control over after-sales processes.

***

## User Interface

Lidia Merchant Console is designed with a clean, user-friendly interface to make managing commerce operations as intuitive as possible. Even merchants with limited technical skills can easily navigate the platform and perform essential tasks.

{% hint style="info" %}
Please follow the [link ](/components/lidia-merchant-console/merchant-console-user-guide)to access detailed navigation and user guide.
{% endhint %}

* **Navigation**: The sidebar navigation gives merchants quick access to key areas like orders, inventory, and promotions.
* **Search and Filters**: Powerful search and filtering tools help merchants quickly locate products, orders, or customers.
* **Mobile Optimization**: The console is fully responsive, allowing merchants to manage their operations on mobile devices, ensuring flexibility and on-the-go access.

***

## Training and Support

Lidia Merchant Console comes with extensive training resources and dedicated support to help merchants get the most out of the platform.

* **Onboarding and Training**: Step-by-step tutorials and training sessions are available to assist new merchants in setting up their operations.
* **Documentation**: Comprehensive user manuals and API documentation are available for advanced users and developers.
* **Customer Support**: Dedicated support is available to assist with technical issues, integrations, or general platform questions.

***

## Conclusion

Lidia Merchant Console is an all-in-one tool designed to empower merchants with full control over their commerce operations. With powerful inventory, order, and customer management capabilities, along with seamless integration options, Lidia Merchant Console makes it easy for merchants to manage their day-to-day business tasks efficiently. Whether you are a small merchant or part of a large multi-vendor marketplace, Lidia Merchant Console offers the scalability and flexibility needed to grow your business.


# Merchant Console User Guide

Welcome to the Lidia Merchant Console User Guide.\
This documentation has been prepared to help you use all the capabilities of the Lidia Merchant Console efficiently and effectively.Throughout this guide, you will step by step explore how to manage your panel as a seller, product and content management, sales and delivery processes, your earnings, and status reports.

Whether you are a seller using the platform for the first time or an experienced e-commerce professional, this guide aims to help you get the most out of your Lidia Merchant Console experience.

{% hint style="info" %}
**Tip:** If you're new to Lidia Merchant Console, start with the **Getting Started** section.
{% endhint %}

<table><thead><tr><th width="198.33331298828125"></th><th></th></tr></thead><tbody><tr><td><a href="/pages/w8Pk1zt6nBiuVvcpHb95"><strong>Getting Started</strong></a></td><td><ul><li>Dashboard</li></ul></td></tr><tr><td><a href="/pages/PhR6Q9SQGHFxw3Mpv4JS"><strong>Store Management</strong></a></td><td><ul><li>Store Details</li><li>Merchant Users</li></ul></td></tr><tr><td><a href="/pages/2y2qMGPlFFgytuRN0WMu"><strong>Product Management</strong></a></td><td><ul><li>Pool List</li><li>Price/Stock List</li><li>Quick Product Insert</li><li>My Products</li></ul></td></tr><tr><td><a href="/pages/uNdEt7k2MbAo38g40qRw"><strong>Sales Management</strong></a></td><td><ul><li>Order Management</li><li>Delivery Management</li><li>Delivery Profile</li><li>Demand Management</li></ul></td></tr><tr><td><a href="/pages/d8a6FQfNDvUmW3DZxfAc"><strong>Invoice Center</strong></a></td><td><ul><li>Invoices</li></ul></td></tr><tr><td><a href="/pages/79eSKlH3WquSvPtKVOq6"><strong>Finance Management</strong></a></td><td><ul><li>Accruals</li></ul></td></tr><tr><td><a href="/pages/i06ivXqEwsrtN2aJZGTr"><strong>Goal Management</strong></a></td><td><ul><li>Goals</li></ul></td></tr><tr><td><a href="/pages/byQdoEZi9v1lQbCpP3mM"><strong>Media Management</strong></a></td><td><ul><li>Image Management</li><li>Bulk Upload</li></ul></td></tr><tr><td><a href="/pages/t7kACQ8uFnfUTIc6oIp0"><strong>Reports</strong></a></td><td><ul><li>Sales Reports</li><li>Cancel/Return Reports</li><li>Product Reports</li><li>Witholding Tax Reports</li></ul></td></tr></tbody></table>


# Getting Started

## **Home Page**

The Home Page is the first screen you encounter when you log in to the Lidia Merchant Console. From this screen, you can access core operational processes such as product management, sales and delivery management, invoice and earnings tracking, and monitor your revenue, overall business performance, as well as sales and inventory summaries from a single central view.

Operational and administrative tasks are carried out through the modules listed in the left navigation menu. The statistical tables, KPI cards, and summary views presented on the main screen allow you to quickly assess your business status and performance at a glance.

In the top-right section of the screen, you can change language preferences, access personal and organizational account information, and securely log out of the platform.

* ### **Left Menu Navigation**

<figure><img src="/files/EshJxWgg3LIt8bsoHi2Q" alt=""><figcaption></figcaption></figure>

[**Store Management**](/components/lidia-merchant-console/merchant-console-user-guide/store-management)**:** The store status, basic definitions, and store-related configurations are controlled through this module.

[**Product Management**](/components/lidia-merchant-console/merchant-console-user-guide/product-management)**:** This is the module where the seller creates, updates, and manages their products.

[**Sales Management**](/components/lidia-merchant-console/merchant-console-user-guide/sales-management)**:** This section is used to manage order statuses, delivery steps, and sales-related operational processes.

[**Invoice Center**](/components/lidia-merchant-console/merchant-console-user-guide/invoice-center/invoices)**:** This is the area where invoice processes related to sales are managed.

[**Finance Management**](/components/lidia-merchant-console/merchant-console-user-guide/finanace-management)**:** This module is used to track earnings, payment statuses, and financial summaries.

[**Goal Management**](/components/lidia-merchant-console/merchant-console-user-guide/goal-management/goals)**:** The goals defined by the system are monitored through this module.

[**Media Management**](/components/lidia-merchant-console/merchant-console-user-guide/media-management)**:** This is the area where visual and media files related to products and the store are managed.

[**Reports**](/components/lidia-merchant-console/merchant-console-user-guide/reports)**:** This section provides reports that allow the seller to analyze sales, performance, and operational data.

* ### **Summary and Statistical Templates**

The summary and statistical templates displayed on the home page enable sellers to monitor their business performance in a quick and comprehensive manner. All displayed values are updated in real time based on the date selection filter available on the screen.

<figure><img src="/files/TLaWDseBQeGQF3IYKWah" alt=""><figcaption></figcaption></figure>

General Statistics Results

* [x] **Total Earnings**\
  Displays the total revenue earned within the selected date range; this value can be viewed on a daily, weekly, monthly, yearly, or custom date range basis using the date filter.
* [x] **Total Number of Orders**\
  Shows the total number of orders received within the selected date range, and the Orders link below this value redirects the user to the [Order Management](/components/lidia-merchant-console/features/order-management) page located in the Merchant Console left navigation menu.
* [x] **Number of Products Sold**\
  Displays the total number of products sold, and the Sales Report link below this value provides access to [sales reports](/components/lidia-merchant-console/merchant-console-user-guide/reports/sales-reports) under the Reports section in the Merchant Console left navigation menu.
* [x] **Total Active Product** \
  Indicates the total number of active products available for sale, and the My Products link below this value redirects the user to the [My Products](/components/lidia-merchant-console/merchant-console-user-guide/product-management/my-products) page under the Product Management section in the Merchant Console left navigation menu.
* [x] **Total Number of Returns**\
  Shows the total number of returns created within the selected date range, and the Sales Management link below this value redirects the user to the [Demand Management](/components/lidia-merchant-console/merchant-console-user-guide/sales-management/demand-management) page located in the Merchant Console left navigation menu.
* [x] **Return Rate**\
  Displays the ratio of completed returns to total sales, and similarly, the Sales Management link below this value redirects the user to the [Demand Management](/components/lidia-merchant-console/merchant-console-user-guide/sales-management/demand-management) page for detailed review.

{% hint style="success" %}
All KPI cards displayed under the General Statistics Results section are presented together with the **weekly change amount** for the last one-week period.
{% endhint %}

* ### **Sales Performance**

This template allows you to view your earnings from sales in a graphical format. Based on the selected date range, you can monitor revenue changes and analyze your sales performance over time.

* ### **Sales and Inventory Summaries**

This template consists of five main sections that summarize your sales and inventory status, enabling you to quickly evaluate your operational performance.

<figure><img src="/files/csxfgxxTx7APnX45wCAQ" alt=""><figcaption></figcaption></figure>

* [x] **Categories**\
  Displays how many different categories your product portfolio consists of. It allows you to check whether there have been any changes in the number of categories (added or removed) over the last week. Additionally, the **top 5 best-selling categories** and the number of products within each category are displayed.
* [x] **Order Status Summary**\
  Shows the percentage distribution of Pending Orders, Shipped Orders, and Delivered Orders. Using the View All option located in the top-right corner, you are redirected to the [Orders](/components/lidia-merchant-console/features/order-management) page in the left navigation menu.
* [x] **Best Selling Products**\
  Lists the products that have been sold the most since the day your store account was created on the platform, along with their sales quantities.
* [x] **Products with Low Stock** \
  Lists products with low or depleted stock levels according to their stock status, along with quantity information. Using the Price/Stock Actions option in the top-right corner, you are redirected to the [My Products ](/components/lidia-merchant-console/merchant-console-user-guide/product-management/my-products)page in the left navigation menu.
* [x] **Top Returned Items**\
  Lists the products most frequently returned by customers, along with their return quantities.

- ### **Account Information**

You can access the Account Information page by clicking the profile area located in the top-right corner. This page allows you to view and update information at both the user and organization levels, within the scope of your authorization.

***

#### **User Information**

In the User Information section, the personal details associated with your account can be updated through the following fields:

* Profile picture
* First and last name
* Email address
* Phone number
* Password update

#### **Organization Details**

In the Organization Details section, the following store and company-related configurations can be managed:

* **Store Information**\
  Store status and store name information can be viewed and updated.
* **Company Information**\
  Company name, company type, tax office, tax number, trade registry number, and MERSİS number are available in this section.
* **Address Information**\
  Province and district, neighborhood, street, building number, phone number, email address, and website information are managed in this section.&#x20;


# Store Management

The Store Management area is the main configuration section where sellers using the Lidia Merchant Console manage their store’s core definitions, operational settings, and integration details. Through this section, you can update your store information, define warehouse and delivery structures, view integration access details, and manage fundamental settings related to inventory and order processes.

The core framework of the configurations in this area is defined through the **Lidia Marketplace Console**; the **Lidia Merchant Console** serves as the layer where these centralized definitions are applied, displayed, and actively used in seller-specific operational processes.

Store Management is a centralized area that contains critical configurations required for seller operations to run accurately, consistently, and without interruption.


# Store Details

The Store Details page is a configuration area that allows you to manage your store’s core identity information, contact details, operational definitions, and system integrations from a single central location. Through this page, you can view the structure defined for your store on the platform, verify the information required for operational processes to function correctly, and update it when necessary.

The Store Details page consists of four main tabs: Basic Information, Address Information, Integration Information, and Settings.

#### **Basic Information**

The Basic Information tab contains the official and financial definitions of your store on the platform.

* **Store Name**\
  This is the name of your store displayed to customers on the platform and is used as a reference in order, reporting, and communication processes.
* **Current Title**\
  This is the official company name used in financial and accounting processes and serves as the basis for invoicing and earnings settlement operations.
* **Tax Office**\
  Indicates the tax office your company is affiliated with and is used for legal reporting processes.
* **Tax Number**\
  This is the unique tax identification number of your company and is mandatory for invoicing and legal compliance processes.
* **IBAN**\
  This is the bank account information to which earnings from sales are transferred and is used for payout processes.

#### **Address Information**

The Address Information tab contains communication and logistics-related details associated with your store and operations.

This section includes:\
-Province and district information\
-Full address\
-Phone number\
-Email address

* **Warehouse Information**

The Warehouse Information section under Address Information is where your logistics operations are managed. In this section, you can add warehouses to the system, edit them, and define them as default delivery dispatch points or return locations.

For each warehouse, the following information is defined:

* *Warehouse Name:* The name used to distinguish the warehouse and reference it in operational processes.
* *Warehouse Type:* Indicates the purpose for which the warehouse is used:
  * [x] **Delivery Dispatch Warehouse:** The warehouse from which orders are shipped to customers.
  * [x] **Receiving Warehouse:** The warehouse where customer returns are received.
  * [x] **Dispatch and Receiving Warehouse:** A warehouse where both shipment and return processes are managed together.
* *Warehouse Responsible Person:* Indicates the person responsible for warehouse operations.
* *Phone Number and Email Address:* Used for operational communication related to the warehouse.
* *Warehouse Address:* Specifies the physical location of the warehouse and is used as a reference in delivery and return routing.

You can add multiple warehouses to the system and configure them according to your operational needs.

#### **Integration Information**

The Integration Information tab contains details that enable your store to communicate securely and technically with the Lidia Marketplace infrastructure.

The following information displayed in this section:\
-ID\
-Access Key

is used for authentication and authorization in system integrations. These credentials ensure that product, stock, price, and order data are synchronized accurately and securely between your store and the platform.

#### **Settings**

The Settings tab is where operational constraints and rules related to your store are defined.

* **Inventory Settings**\
  Allows you to define restrictions based on product, category, brand, stock, and price. These settings ensure that products offered for sale are managed within defined rules.
* **Order Settings**\
  Allows you to define restrictions by country, province, and district for deliveries. This enables control over the regions where orders can be accepted.


# Merchant Users

The Merchant Users page is the area where users with access to the Merchant Console are listed. In this section, all users who have system access on behalf of your store are displayed.

<figure><img src="/files/FwTgK8o2b7QlH88a190A" alt=""><figcaption></figcaption></figure>

All user definition and configuration processes displayed in this section, including roles and authorizations, are carried out through the Lidia Marketplace Console. The Merchant Console serves as the layer where these definitions are applied and displayed; user creation, role assignment, or role modification actions cannot be performed through this area.

{% hint style="info" %}
When user creation, user management, or permission changes are required, these actions must be performed via **Lidia Marketplace Console →** [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **→ Authorization → Users**. In the Merchant Console, users are displayed only, and operational processes are carried out based on existing definitions.
{% endhint %}

On the user detail screen of any user, the following information can be viewed:\
![](/files/B0pY1Lc141AeClLa8YCY)

These fields are view-only and cannot be edited.\
Only the phone number field is editable.


# Product Management

The Product Management section is the area within the Lidia Merchant Console where sellers create, manage, and prepare their products for sale in accordance with platform standards. Through this section, you can define your product data according to the correct category structure, add products not only by creating them from scratch but also by selecting from products that already exist in the catalog, quickly upload your products to the system through bulk uploads, and prepare them for go-live by tracking approval and publishing processes.

Additionally, sellers can manage product pricing and stock information through this area, and maintain their operational processes by monitoring the current status of products available for sale.


# Pool List

In Lidia, product upload processes operate based on the Product Pool concept. Pools are structures created to ensure that sellers upload their products in compliance with the data structure and standards defined on the platform. Pools can be created from both the Marketplace Console and the Merchant Console.

Sellers can perform product upload operations through the Merchant Console using the following methods:

* **Bulk upload via Excel files**
* **Data transfer via SAP integration**

The Pool List page is the main workspace where product family creation, schema download, product upload, data validation, and approval/publishing processes are managed end to end.<br>

<figure><img src="/files/ozz9s3EqUG27fR1qo3Km" alt=""><figcaption></figcaption></figure>

***

#### 1) Creating a Product Family

When you enter the Pool List page, the process is initiated using the Add New Product Family button located in the top-right corner of the screen. Creating a product family is the mandatory first step to ensure products are uploaded with the correct schema.

Steps:

1. Click the Add New Product Family button.
2. Select a category to create a product family.
3. The category schema configured in the Marketplace Console is displayed.
4. By selecting from the defined categories and subcategories in the system, you create your product family.

<figure><img src="/files/BvSt5IrOfgSsKFCUeDU8" alt=""><figcaption></figcaption></figure>

This structure is designed based on a **single catalog** approach. A product family contains category-specific options and properties, as well as the mandatory / optional status of these fields. This approach eliminates the need to redefine the same fields for each product upload, allowing products to be added to a predefined standard structure, accelerating the process and reducing manual repetition.

#### 2) Product Family List and the “Manage Products” Area

All created product families are listed under the Product Families section on the Pool List page. The following information is displayed for each product family:

* ID
* Product family name
* Related category(ies)
* Product family status

The Manage Products button next to each product family is the primary area where product upload and data management actions are performed.

#### 3) Downloading the Data Schema (Excel Template)

After clicking the Manage Products button, the product upload process is initiated using the Import Data button located in the top-right section of the screen.

At this step:

1. The **Excel data schema** appropriate for the selected product family is downloaded.
2. The Excel template provided for each product family is different.

These differences arise from category-specific attribute and option fields, as well as the mandatory / optional definitions of these fields.

<figure><img src="/files/a3jJjGsa3dczLED2941g" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The fields defined for each product family and their mandatory statuses are configured by the Marketplace Console admin via\
**Marketplace Console →** [**Settings**](/components/lidia-console/lidia-console-user-guide/settings) **→ Catalog → Product Families**.\
Sellers using the Merchant Console do not have permission to modify these fields.
{% endhint %}

#### 4) Excel Template Structure and Data Entry

The downloaded Excel file consists of two main sheets:

* **Template Information**\
  This sheet contains descriptions of the fields that must be completed for the relevant product family, including the purpose of each field, whether it is mandatory or optional, and example values.
* **Products**\
  This is the main sheet where product data is entered and includes the following main sections:
  * Basic Information
  * Category Information
  * Brand Information
  * Options
  * Properties
  * Other Information

Using this sheet, bulk product upload can be performed by entering data for multiple products.

#### 5) Excel Upload and Onboarding Steps

After completing the Excel template, the file is uploaded to the system using the file selection tool. The upload process consists of the following onboarding steps:

**Upload Excel Document -> Validate Data -> Completed**

Once these steps are successfully completed, the product upload process is finalized.

#### 6) Pool Statuses and Product Flow

Uploaded products are managed under specific statuses before going live. The following tabs are displayed on the Pool List screen, each showing the number of products under the relevant status:

<figure><img src="/files/438ZXjLoLASPlVPcNCVG" alt=""><figcaption></figcaption></figure>

The process flows as follows:

* [x] **All**\
  All products entered via Excel are initially listed in this tab in a table format.
* [x] **Not Submitted for Approval**\
  Products that have not yet been submitted to the Marketplace admin are listed here. Selected products can be sent to the approval process using the Submit Selected Products for Approval button.
* [x] **Pending Approval**\
  Products submitted to the Marketplace admin for go-live approval are listed in this tab. The Marketplace admin views these products via\
  **Marketplace Console →** [**Product Management** ](/components/lidia-console/lidia-console-user-guide/product-management)**→ Pools**.
* [x] **Approved / Rejected**\
  The Marketplace admin:

- Uses the Approve action to move products to the Approved tab in both the Merchant Console and Marketplace Console.
- Uses the Reject action to move products to the Rejected tab in both consoles.

* [x] **Published**\
  Approved products are published by the Marketplace Console admin. Once published, these products are listed under the Published tab in both the Merchant Console and Marketplace Console.

#### 7) Exporting Data

Throughout the entire process, products listed in pools can be exported in Excel format using the Export Data button when needed. This feature can be used for reporting, validation, and archiving purposes.


# Price/Stock List

The Price / Stock Management page is the area where sellers centrally manage the stock, pricing, and sales availability of products and variants in their inventory. This page is used to ensure that products remain available for sale, are listed with accurate pricing, and that operational disruptions caused by stock depletion are prevented.

Through this screen, sellers can view the products in their inventory and update critical price and stock fields instantly and dynamically. In addition, as a seller, you can filter the listed inventory by brand and category to more easily and quickly display products, simplifying management for large product volumes.

Using the Import Data button located in the top-right corner of the screen, price and stock data can be uploaded in bulk by selecting the relevant Excel file for the category. This method provides fast and error-free updates, especially for sellers with large product volumes.

<figure><img src="/files/uCWAb2J2ePwnHLfmJcSI" alt=""><figcaption></figcaption></figure>

On this page, the following information is displayed in a table format for each product variant in the inventory:

* **Product Name:** The name of the product displayed to customers on the platform and used to identify the product.
* **Barcode:** A unique identifier for the product, used for product matching and stock tracking.
* **Seller Item Code:** A reference code used by the seller to identify the product within their internal systems.
* **Group Code:** A code used to associate variants of the same product (e.g., size, color).
* **Brand:** Indicates the brand to which the product belongs and is used in reporting and filtering processes.
* **Categories:** Indicates the product’s position within the platform’s category hierarchy.
* **Variation:** Displays variant information such as color, size, or dimensions.
* **Inventory Label:** A status indicator assigned by the system based on the product’s stock condition and used for operational alerts.
* **Stock Status:** Displays the current stock quantity and the product’s availability for sale.
* **List Price:** The base selling price of the product before any campaign or discount is applied.
* **Sale Price:** The effective selling price shown to customers after discounts or campaigns are applied.

Among these fields, Inventory Label, Stock Status, List Price, and Sale Price are critical and **dynamic fields** that can be updated instantly through the Merchant Console. Changes made to these fields have a direct impact on product availability and pricing.

* #### Stock Alerts and  Indicators

If there are products with low or depleted stock levels among the listed items, the system provides alert notifications to inform the seller.

* [x] **Low-stock products** are highlighted with a **yellow line** in the table.
* [x] **Out-of-stock products** are highlighted with a **red line**.

These visual indicators enable sellers to take quick action and help prevent sales losses caused by stock shortages.

<figure><img src="/files/TFl9pIFMTPDmj3vnURbX" alt=""><figcaption></figcaption></figure>

All inventory data listed on the Price / Stock Management page can be exported in Excel format using the Export Data button. This feature can be used for reporting, auditing, archiving, and data sharing with external systems.


# Quick Product Insert

The Quick Product Insert page is a feature that allows sellers to quickly and efficiently add products that already exist in the platform catalog to their own inventory. This page is designed to eliminate repetitive product data entry, shorten product onboarding time, reduce operational workload, and accelerate the go-live process.

Through this screen, sellers can create new SKUs for their stores by using products that have already been uploaded to the platform and are in a sale-ready state, by defining only stock and pricing information. This structure provides a significant operational advantage, especially for sellers working with large catalogs and requiring rapid product publishing.

The products listed on this page are all sale-ready catalog products available on the platform. Each product is presented with the following information to enable quick selection and comparison:

-Product Name\
-Small product preview image\
-Barcode\
-Brand\
-Category\
-Variation information\
-Tax Rate

These details help sellers quickly identify the correct product and minimize the risk of incorrect product selection.

* #### Add Product from Catalog

The Add Product from Catalog section is used when there is a product in the system that is identical to the product you plan to sell. Instead of re-entering all product data, you can add the product to your inventory by defining only the following information:

* **Seller Item Code**
* **Stock**
* **List Price (₺)**
* **Sale Price (₺)**

<figure><img src="/files/yeqv3MHFwasNpXK71xE6" alt=""><figcaption></figcaption></figure>

As a result of this process, a new SKU specific to your store is created, and the product becomes ready for sale.

Sellers can filter the listed products by brand and category to quickly access the products they are looking for. This filtering capability significantly improves usability, especially when working with large product catalogs, and makes the product insertion process more efficient.




---

[Next Page](/llms-full.txt/1)

