Premise
This article helps you understand how to work massively on products in Poleepo via the Catalogs section, clarifying the difference between Master Data and Publications and when to use a CSV file.
It is designed for both those who are using Poleepo for the first time and for experienced users who want a quick and consistent reference.
What you will find here
What are Catalogs?
Difference between Product and Publication (MP Product)
When to use a CSV
CSV File Requirements and Best Practices
Recommended procedure: export → edit → save → import
Most common use cases
Note on variants (Parent SKU / Child SKU)
1. What are the Catalogs on Poleepo?
The Catalogs section allows you to create and update product information in bulk (multiple products at once), avoiding manual changes product by product.
In Catalogs you will work on two distinct levels:
Personal data (Product)
Publications (MP Product)
Note: Understanding this distinction is key to operating the platform correctly.
2. Difference between Registry and Publication
2.1 Product Data – the “heart” of the product
The product master file contains the main information about the product within Poleepo. You can think of it as the "heart" or central part of the product.
Examples of information typically managed in the master data:
Product Name
SKU (product/variant identifier)
EAN/GTIN (if applicable)
Base price and VAT
Stock (availability)
Description and contents
Images
Attributes and characteristics
Variant Management (Parent SKU / Child SKU)
In practice: if you want to update what you see in the product sheet "at the top" in Poleepo, you are working on the Master Data.
2.2 Publication (MP Product) – offering the product on a channel
Publishing represents the way that product is offered on a specific channel (e.g., Amazon, ManoMano, Shopify, etc.). You can think of it as an "extension" of the product: it changes depending on the channel.
Examples of information typically managed in publications:
Channel-optimized title and content (when applicable)
Category and attributes required by the marketplace
Publication status (active/inactive/error)
Channel-specific fields (vary from channel to channel)
In practice: if you want to intervene in areas related to publishing on a specific channel, you are working on Publications.
3. When to use a CSV file
A CSV file is the fastest way to create or update information in bulk. It's useful when you need to apply changes to many products or when you want to import data from a management system.
Examples of using CSV:
Create new products
Creating products with variants
Update prices, VAT and stock levels
Update descriptions, titles, images, and attributes
Update channel-specific fields (via Publications)
4. What is a CSV file (quick explanation)
CSV stands for "Comma Separated Values." It's a text file organized into rows and columns:
Each row = one product (or one variant)
Each column = one field (e.g. SKU, price, description)
Separators:
In Poleepo, the use of the "|" (pipe) separator is recommended. However, the ";" (semicolon) and tabs are also supported, depending on the configuration and file.
5. File requirements and best practices
To avoid import errors, make sure the file:
Both in .csv format
Be encoded in UTF-8
Use a consistent separator throughout the file
Contains clear and duplicate-free headers (column names)
Does not contain formulas (paste values)
Do not alter key identifiers (e.g. SKU) if you are updating existing products
Warning: Changing the SKU or structure of your exported file may create duplicates or prevent the correct products from being updated.
6. Recommended procedure (the safest)
The recommended flow is always this:
Step 1 — Export
Export products from Poleepo (Registers or Publications depending on what you need to modify).
Step 2 — Edit
Open the file, change only the necessary fields, and paste values (not formulas).
Step 3 — Save
Save as CSV UTF-8 and make sure the separator is the expected one.
Step 4 — Import
Upload the file to Catalogs → Personal Data or Catalogs → Publications and start processing.
7. Quick Guide: Which section should I use?
Use this rule of thumb:
Do you want to edit product data in Poleepo? → Product Data
Want to edit data for a specific channel? → Publications
Common examples:
Update base price / VAT / stock → Master data
Update name, description, main images → Personal data
Update channel-specific name, description, and images → Posts
Update fields required by Amazon / ManoMano / other marketplaces → Publications
8. Note on variants (parent SKU / child SKU)
If your catalog contains variants, it's essential to respect the relationship between parent SKUs and child SKUs. In many cases:
Parent SKU = main product (model)
Child SKU = variant (size/color, etc.)
When updating via CSV, always verify that the rows are consistent with the expected variant structure, otherwise the import may fail or create unexpected results.