ManoMano

ManoMano is an online retailer specialising in DIY and gardening products. Originally based in France, it soon expanded to other parts of Europe and is now available in France, Belgium, Spain, Italy, the United Kingdom and Germany.

Open beta test phase

The ManoMano integration is currently in a closed beta.

1. Becoming a seller on ManoMano

First, apply to become a seller on ManoMano in order to offer your items on ManoMano. Afterwards, you will receive your ManoMano API key and a set of Contract IDs. These credentials are required for the setup in PlentyONE.

2. Frequency of data exchange

After you have set up ManoMano in PlentyONE, data is exchanged with the sales channel in the intervals described in Table 1.

Table 1. Frequency of data exchange
Data	Interval
Item export	daily
Offer export	every 15 minutes
Stock synchronisation	every 15 minutes
Price synchronisation	every 15 minutes
Order import	every 15 minutes

3. Setting up the data exchange

In order for the interface to successfully carry out the different data exchange routines for ManoMano, at least the settings in the following table are required.

Table 2. Mandatory settings for ManoMano
Settings section	Settings
Item export
Basic settings for the sales channel in the menu Sales Channels » Accounts	An account for ManoMano is created and activated. The API key for ManoMano is entered and saved. The Sales channel is selected. The Contract ID is entered. The account is activated.
Catalogue settings	A product catalogue is created. All mandatory fields have been mapped. The product catalogue is activated.
Listing settings	A product listing is created. The product listing is activated.
Variation settings	The variation is saved. The order referrer is saved.
Offer export
Basic settings for the sales channel in the menu Sales Channels » Accounts	An account for ManoMano is created. The API key for ManoMano is entered and saved. The Sales channel is selected. The Contract ID for the specific sales channel is entered. The Offer export cron is activated. The account is activated.
Catalogue settings	An offer catalogue is created. All mandatory fields have been mapped. The offer catalogue is activated.
Listing settings	An offer listing is created. The offer listing is activated.
Variation settings	The variation is saved. The order referrer is saved.
Order import
Basic settings for the sales channel in the menu Sales Channels » Accounts	An account for ManoMano is created and activated. The API key is entered and saved. The sales channel is selected. The Contract ID is entered. The order import cron is activated.

4. Workflow of an ManoMano order

Your items are listed on ManoMano.
Customers place an order on ManoMano.
The incomplete order is imported into PlentyONE.
→ At this point, the invoice and delivery address for the order are still missing and the order has not yet been paid for.
The order must be accepted or rejected via Flow.
If the order is accepted, customers make their payment to ManoMano.
With the payment confirmation, the invoice and delivery address on the order are updated in PlentyONE.
→ The order is complete.
The order is shipped.
The shipping confirmation must be sent to ManoMano by Flow.
Cancellations, returns and refunds are sent via Flow. For cancellations and refunds you need to select a reason.
Refunds can be accepted or refused via Flow.

Note: You cannot partially refund orders on ManoMano. Only full refunds are possible.

5. Setting up ManoMano in PlentyONE

First, create an account and carry out the basic settings to set up the sales channel in PlentyONE. To do so, proceed as described below.

5.1. Creating an account

In the Sales Channels » Accounts menu, create an account for ManoMano.

Creating an account:

Open the Sales Channels » Accounts menu.
Click on Create account ().
→ The window Create account opens.
Select ManoMano from the drop-down list Platform.
Select the Client (Shop) from the drop-down list.
Enter a name for the account.
Click on CREATE.
→ The account for ManoMano is created.

5.2. Account overview

In the Sales Channels » Accounts menu, you can create your ManoMano account. In addition, you can find an overview of the account here.

Table 3 contains an overview of the accounts in the Sales Channels » Accounts menu.

Table 3. Accounts in the Sales Channels » Accounts menu.

Setting

Explanation

bigtop_updates Connection

Connection status of the account.
Accounts can have the following connection statuses:

Connected (bigtop_updates) = The account is connected to the sales channel.
Disconnected (signal_disconnected) = The account is not connected to the sales channel.
Note: If the account is Disconnected, this may be due to missing or incorrect basic settings for the sales channel.

Name

Account name.

More

Click here to display more actions.

Account settings

Open the account settings.

Errors

Open errors for Product listings oder Offer listings. The number of errors for the product listings or offer listings for this account is shown in brackets.

Product listings

Open the overview of product listings for this account.

Activate account

Activate the account.

Delete account

Delete the account.

Listings online

Hover over Listings online to see the number of product listings and offer listings that are listed on sales channels for this account.

Errors

Hover over Errors to see the number of errors that occurred for product listings and offer listings.

5.3. Carrying out the channel settings for ManoMano

Next, carry out the channel settings for ManoMano.

Carrying out the channel settings for ManoMano:

Open the Sales Channels » Accounts menu.
Click on the tile for ManoMano.
→ The tab Channel settings opens.
Carry out the settings. Pay attention to the explanations given in Table 4.
Note: You can only configure the settings in the General, Contract IDs and Data exchange sections once you have correctly entered the client API key correctly and saved the settings.
Save () the settings.

Table 4. Channel settings for the sales channel ManoMano

Setting

Explanation

API credentials

Client API key

Enter the Client API key that you received from ManoMano.

You cannot access the other settings until you have entered and saved a Client API key in this section.

ManoMano Contract ID

Enter the general Contract ID that you received from ManoMano.

General

Sales Channels

Select the sales channel(s) on which you want to sell your products.

Unique properties of ManoMano sales channels

ManoMano uses unique sales channels for different combinations of:

order fulfillment types, i.e. fulfillment by ManoMano (MF) or not by ManoMano (NMF),
customer classes, i.e. either Business-to-Business (B2B) or Business-to-Consumer (B2C), and
countries in which ManoMano operates.

Each sales channel requires its own separate Contract ID in addition to the general Contract ID. Only select the sales channels for which you have corresponding Contract IDs.

Example: You want to sell your items to business customers on ManoMano Italy, with ManoMano handling fulfillment. To set this up in PlentyONE, you have to select the sales channel that matches this specific sales scenario, i.e. 187.03 ManoMano MF b2b IT.

Contract IDs

[Any selected sales channels]

Enter the matching Contract ID for each sales channel you selected in the previous section.

Note: While a contract ID is entered into a Plenty system the "price" and "stock" values of offer listings associated with that contract ID are "frozen". In other words, they cannot be edited by sources other than the Plenty system until the contract ID is removed from the system.

Data exchange

Order import

Activate this option to automatically import ManoMano orders into PlentyONE every 15 minutes.

Offer export cron

Activate this option to automatically export offers to ManoMano every 15 minutes.

Map shipping profiles

Add mapping ()

Click Add mapping () to create mappings for shipping profiles.
First, select the PlentyONE shipping profile from the drop-down list. Then select the Sales channel for which you want to create the mapping and an available Manomano carrier.
Note: You must create at least one mapping per sales channel.

5.4. Modifying the account settings

In the Account settings tab, you can adjust the account’s name.

Carrying out account settings:

Open the Sales Channels » Accounts menu.
Open the account for ManoMano.
Open the settings Account settings tab.
Enter the name.
Save () the settings.

5.5. Activating the account

In the Sales Channels » Accounts menu, activate the account to enable the data exchange with ManoMano.

Activating the account for ManoMano:

Open the Sales Channels » Accounts menu.
Click More () in the tile for ManoMano.
→ A drop-down list with further options appears.
Select the Activate account () option from the drop-down list.
→ The account is activated and data can be exchanged with ManoMano.

5.6. Activating the order referrer

Go to Setup » Orders » Order referrer to activate the order referrer. This ensures that orders are assigned to the correct sales channel.

What is an order referrer?

An order referrer tags an order with the sales channel on which the order was generated. Sales channels can be e.g. your online shop or markets on which you sell your items. Each sales channel has an individual order referrer. Some order referrers are available by default in your PlentyONE system. Further order referrers are added e.g. if you install a new plugin. For further information about the order referrer, see the page Order referrer of the PlentyONE manual.

Activating the order referrer for ManoMano:

Go to Setup » Orders » Order referrer.
Click Search ().
In the list, navigate to the option ManoMano with the ID 187.00.
On the right of the referrer’s line, click on Edit ().
→ The window Edit referrer opens.
Activate the option Visible in selection ().
Click on Save ().
→ The referrer is active.

Note: If you want to sell your items on ManoMano, then the parent referrer for ManoMano must be activated (187.00 ManoMano). Additionally, you have to activate the referrers that correspond to the ManoMano sales channels you want to use to sell your items.

Overview of all available order referrers for ManoMano

Table 5. Order referrers for ManoMano
Referrer name	Country platform	Customer class
187.00 ManoMano	This is the parent referrer for ManoMano. It is always required.
187.01 ManoMano MF b2b DE	ManoMano Germany	Business to Business
187.02 ManoMano MF b2b FR	ManoMano France	Business to Business
187.03 ManoMano MF b2b IT	ManoMano Italy	Business to Business
187.04 ManoMano MF b2b ES	ManoMano Spain	Business to Business
187.05 ManoMano MF b2c DE	ManoMano Germany	Business to Consumer
187.06 ManoMano MF b2c FR	ManoMano France	Business to Consumer
187.07 ManoMano MF b2c IT	ManoMano Italy	Business to Consumer
187.08 ManoMano MF b2c ES	ManoMano Spain	Business to Consumer
187.09 ManoMano NMF b2b DE	ManoMano Germany	Business to Business
187.10 ManoMano NMF b2b FR	ManoMano France	Business to Business
187.11 ManoMano NMF b2b GB	ManoMano Great Britain	Business to Business
187.12 ManoMano NMF b2b IT	ManoMano Italy	Business to Business
187.13 ManoMano NMF b2b ES	ManoMano Spain	Business to Business
187.14 ManoMano NMF b2c DE	ManoMano Germany	Business to Consumer
187.15 ManoMano NMF b2c FR	ManoMano France	Business to Consumer
187.16 ManoMano NMF b2c GB	ManoMano Great Britain	Business to Consumer
187.17 ManoMano NMF b2c IT	ManoMano Italy	Business to Consumer
187.18 ManoMano NMF b2c ES	ManoMano Spain	Business to Consumer

Example: You want to sell your items to business customers on ManoMano Italy, with ManoMano handling fulfillment. In order to set this up in PlentyONE you have to first activate the parent referrer for ManoMano (187.00 ManoMano). Then, activate the referrer that is required for your specific sales stuation (in this case 187.03 ManoMano MF b2b IT).

6. Exporting product data

Item data is exported to ManoMano using catalogues. Go to Data » Catalogues to create catalogues for ManoMano.

What is a catalogue?

Catalogues are used to export data from your PlentyONE system. There are two different catalogue formats:

Marketplace formats are used to export item data to markets.
Standard formats are used to export data from your PlentyONE system into a file.

Catalogues with marketplace formats allow you to tailor your item information exactly to the needs of the market. Because here, you assign a suitable PlentyONE data field to each of the data fields of the market. When your variation data is exported to the market, the market’s data fields are then filled with the correct PlentyONE data.

Is this your first time working with catalogues? Then read up on the basic concept of catalogues first.

6.1. Creating a product catalogue

Product data is exported to ManoMano using catalogues. To export your items to ManoMano, create a product catalogue in the Data » Catalogues menu. Afterwards, link the ManoMano data fields with item data saved in PlentyONE in the catalogue.
If you have activated the product catalogue, the account, the listing and the variations, the product data is automatically exported to ManoMano once a day.

Note: You need to set up a separate catalogue for each product category you want to sell on ManoMano.

Creating a catalogue:

Go to Data » Catalogues.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option ManoMano Products.
In the drop-down list Export type, select the option Listing.
In the drop-down list Category, select the ManoMano category.
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.

Other catalogue settings

Other catalogue settings are optional. Once you carried out the settings described on this page, your catalogue is automatically exported to ManoMano Products. That means you can ignore the catalogue settings for Format settings, Export settings and Download settings.

The Format settings, Export settings, and Download settings allow you to create a file with the variation data contained in the catalogue. However, this file does not contain information about whether the data export to ManoMano Products was successful.

Do not change the format in the catalogue’s Format settings. To ensure that the export to the sales channel works, all required settings are already configured when you create a catalogue. If you change the settings, errors might occur during the export.

6.1.1. Mapping data fields in the catalogue

After you have created a catalogue, map the ManoMano data fields to item data saved in PlentyONE. This chapter describes how you map data fields and what particularities apply for item exports to ManoMano.

The market expects product data that cannot be saved in the PlentyONE item menu? Then create a property for this data. Link this property with your variations. The actual values are saved as property values for this property. Is this your first time working with properties? Then read up on the principles of properties first.

Getting to know the catalogue menu for marketplace formats

Availability	Explanation
Navigation	When you open a catalogue, the view Mapping is shown. On the very left is the navigation. Switch to other views of the catalogue. Open the catalogue settings. Use filters that limit the data that is exported. Go back to the list of catalogues. Create a new catalogue.
Toolbar	The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.
Marketplace data field	To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱). *Tip:* Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions ().
PlentyONE data fields	On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Availability

Explanation

Navigation

When you open a catalogue, the view Mapping is shown. On the very left is the navigation.

Switch to other views of the catalogue.
Open the catalogue settings.
Use filters that limit the data that is exported.
Go back to the list of catalogues.
Create a new catalogue.

Toolbar

The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.

Marketplace data field

To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱).
Tip: Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions ().

PlentyONE data fields

On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Mapping catalogue fields:

Go to Data » Catalogues.
Click on the catalogue.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.
Map suitable PlentyONE data fields to the market data fields.
For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.
- Simple 1:1 mapping
- Simple 1:1 mapping with properties
- Complex 1:1 mapping
- 1:1 mapping with fallback data fields
- 1:n mapping
- Own value mapping
- Mapping with mathematical calculations
Save () the catalogue.
→ The mappings are saved.

Simple 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. If no suitable setting exists in PlentyONE. you can map a property instead.

As such, simple 1:1 mappings allow you to:

I want to fill this marketplace data field with the data from this PlentyONE setting.
If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.

Example: Sales price and RRP for Otto Market

This gif shows you how to map the marketplace data fields Sales price and RRP for Otto Market to PlentyONE data fields:

Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

Reminder: In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. However, what can you do if PlentyONE does not offer a suitable data field? Then it’s the properties' moment to shine. Properties allow you to save any kind of information in your properties.

Is this your first time working with properties? Then read up on the principles of properties first.

Creating a property:

Create a property with the necessary values.
Tip: Find out how to do that here.

Creating a simple 1:1 mapping with properties:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
Click on Confirm.
→ The property is mapped to the marketplace data field.

Complex 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

Like with the simple 1:1 mappings, you map a PlentyONE setting or property to a marketplace data field. Complex mappings are necessary whenever a marketplace data field has more than one possible value. Instead of mapping data fields, for complex mappings you map individual values of these data fields. For example, you cannot simply map the PlentyONE data field Shipping profile to the marketplace data field Shipping method. Why? The market cannot know which of your shipping profiles in PlentyONE corresponds to which of their shipping methods.

Do not enter own values for complex mappings. All values that you enter must be saved for the variations, either in a setting or as a property value. This also applies if the value Comparative value is shown. You still need to enter exactly the value of the setting or property that you mapped.

In complex mappings, the value of the market is always exported. Only when you map an own value, the own value that you enter is exported.

You can recognise complex mappings from the field that is shown below the name of the marketplace data field. Click on the field to show the values available for the marketplace data field.

Examples for complex 1:1 mappings are:

Categories
Brands
Shipping setting

Important: For complex mappings, do not map own values or properties of the type None.

Creating a complex 1:1:n mapping:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
Click on the PlentyONE data field for which you want to map values.
Important: Do not map own values or properties of the type None.
Your next steps depend on the PlentyONE data field you selected:
- Alternative 1: The available values for the PlentyONE data value are shown on the left.
  - Next to the value you want to select, click on the plus.
    → The value is added to the field on the right.
  - Click on Confirm.
- Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.
  - In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.
  - Click on Confirm.
- Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.
  - Select a value from the drop-down list.
  - Click on Confirm.
    → The value of the marketplace data field is exported, not the value of the PlentyONE data field.
    Exception: Only when you map an own value, the own value that you enter is exported.

Example: Delivery time in days for Otto Market

This gif shows you how to map suitable PlentyONE values to the values of the marketplace data fields Delivery time in days for Otto Market:

1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

In a 1:1 mapping with one or more fallback data fields, you map a PlentyONE data field to the marketplace data field. In addition, you specify one or more fallback data fields. This ensures that the system keeps looking if the first PlentyONE data field is missing or empty.

So this mapping specifies:

I want to fill the marketplace data field with the data from the selected PlentyONE setting.
If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.
If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

The fallback data field is used if the data field above is mapped in the catalogue but not linked to the variation.

The condition "Null" is useful when you want to map fallback data fields for the following types of PlentyONE data fields:

SKU
Barcodes
Sales prices
Properties

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Empty

The fallback data field is used if the data field above is mapped in the catalogue and linked to the variation, but is empty.

The condition "Empty" is useful when you want to map fallback data fields for the following type of PlentyONE data fields:

PlentyONE data fields that are available for variations by default

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Note: Even if you assign one or more fallback data fields, the value of only one of those fields is exported. For each variation, the mapped PlentyONE data fields are checked in the order in which you mapped them. This means that if the first data field does not provide a value for a variation, the first fallback data field is exported etc.

Creating a 1:1 mapping with fallback data fields:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
→ The fallback data field is added with the fallback condition "null".
Alternative 1: To add the fallback data field with the fallback condition "null":
1. Click on Confirm.
  → The fallback data field is exported if the data field above is not linked to the variation.
Alternative 2: To add the fallback data field with the fallback condition "empty":
1. To the left of the fallback data field, click on the cog ().
  → The window Data column settings is shown.
2. For the setting Fallback condition, select the option Empty.
3. Click on Save.
  → The fallback data field is added with the fallback condition "empty".
4. Click on Confirm.
  → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

This GIF shows you the mapping for the OTTO Market marketplace data field SKU. The PlentyONE data field SKU is mapped to this marketplace data field. The PlentyONE data field Variation ID is mapped as the fallback data field. The fallback condition "null" is applied automatically.

Result: The fallback data field Variation ID is exported if the data field SKU is not linked to the variation.

1:n mapping: 1 marketplace data field, several PlentyONE data fields

In a 1:n mapping, you map several PlentyONE data fields to the marketplace data field. You can link these data fields with a separator.

So this mapping specifies:

I want to combine these PlentyONE data fields during export so that the marketplace data field is filled with the data of these two or more PlentyONE settings.

Creating a 1:n mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.
To the right of the mapped PlentyONE data field, click on Add data field ().
→ To the left, the list of available PlentyONE data fields again are shown in groups.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
Save () the catalogue.
→ The mappings are saved.
→ During the export, the content of the PlentyONE data fields is combined and exported as one field.

Own value mapping: 1 marketplace data field, the same value for all variations

You are sure that you want to export the same value for all variations of a catalogue for a marketplace data field? Then specify an own value. This own value is then exported for all variations.

So this mapping specifies:

For this marketplace data field, I want to export the value that I entered in the field Own value for all variations of this catalogue. The value you enter is always exported. The value overwrites the market value also in complex mappings where usually the value of the market is exported. As such, make sure you enter an own value that the market accepts for this marketplace data field.

Creating an own value mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view.
Enter a value into the input field.
→ This value is exported for all variations.

Example: Diameter information

You want to export diameter information for some of your variations. The diameter is saved in centimetres for all your variations. Instead of creating a property for the unit and linking this property to the variations, you can enter the own value cm.

This is an example of how you can map an own value for the diameter unit:

Mapping with mathematical calculations: 1 Marketplace data field, the PlentyONE value is recalculated using the formula during export

Mathematical calculations allow you to change numerical values automatically during the export.

This function only works for data fields that contain numerical values.
This functionality is new and not available for all catalogue formats.

So this mapping specifies:

I want the numerical value of a PlentyONE data field to be recalculated during the export. Basic arithmetic operations are available for the formulas.

Recalculating numerical values:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.
1. Click on the icon .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

6.1.2. Activating the catalogue export

You have set up ManoMano in PlentyONE and created a catalogue for exporting your item data? Then activate the catalogues you want to export to ManoMano in the Data » Catalogues menu and continue with creating product listings.
Once you have activated the product catalogue, the ManoMano account, the product listing and the variations, the product data will be automatically exported to ManoMano once a day.

Activating the catalogue export to ManoMano:

Go to Data » Catalogues.
→ The catalogues are listed.
Scroll to the ManoMano catalogue.
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to ManoMano once a day.
Tip: Go to Data » Catalogue export status for information about the status of the export.

7. Exporting offer data

Offer data is exported to ManoMano via catalogues. Go to Data » Catalogues to create catalogues for ManoMano.

What is a catalogue?

Catalogues are used to export data from your PlentyONE system. There are two different catalogue formats:

Marketplace formats are used to export item data to markets.
Standard formats are used to export data from your PlentyONE system into a file.

Is this your first time working with catalogues? Then read up on the basic concept of catalogues first.

7.1. Creating an offer catalogue

Offer data is exported to ManoMano using catalogues. To export your offers to ManoMano, create an offer catalogue in the Data » Catalogues menu. Afterwards, link the ManoMano data fields with item data saved in PlentyONE in the catalogue.
Once you have activated the offer catalogue, the account, the listing and the variations, the offer data is automatically exported to ManoMano every 15 minutes.

Note: You need to set up a separate catalogue for each product category you want to sell on ManoMano.

Creating a catalogue:

Go to Data » Catalogues.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option ManoMano Offers.
In the drop-down list Export type, select the option Listing.
In the drop-down list Category, select ManoMano Offers.
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.

Other catalogue settings

Other catalogue settings are optional. Once you carried out the settings described on this page, your catalogue is automatically exported to ManoMano Offers. That means you can ignore the catalogue settings for Format settings, Export settings and Download settings.

7.1.1. Mapping data fields in the offer catalogue

After you have created an offer catalogue, map the channel’s data fields to item data saved in PlentyONE. This chapter describes how you map data fields and what particularities apply for item exports to ManoMano.

The market expects product data that cannot be saved in the PlentyONE item menu? Then create a property for this data. Link this property with your variations. The actual values are saved as property values for this property. Is this your first time working with properties? Then read up on the principles of properties first.

Getting to know the catalogue menu for marketplace formats

Availability	Explanation
Navigation	When you open a catalogue, the view Mapping is shown. On the very left is the navigation. Switch to other views of the catalogue. Open the catalogue settings. Use filters that limit the data that is exported. Go back to the list of catalogues. Create a new catalogue.
Toolbar	The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.
Marketplace data field	To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱). *Tip:* Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions ().
PlentyONE data fields	On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Availability

Explanation

Navigation

When you open a catalogue, the view Mapping is shown. On the very left is the navigation.

Switch to other views of the catalogue.
Open the catalogue settings.
Use filters that limit the data that is exported.
Go back to the list of catalogues.
Create a new catalogue.

Toolbar

The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.

Marketplace data field

PlentyONE data fields

On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Mapping catalogue fields:

Go to Data » Catalogues.
Click on the catalogue.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.
Map suitable PlentyONE data fields to the market data fields.
For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.
- Simple 1:1 mapping
- Simple 1:1 mapping with properties
- Complex 1:1 mapping
- 1:1 mapping with fallback data fields
- 1:n mapping
- Own value mapping
- Mapping with mathematical calculations
Save () the catalogue.
→ The mappings are saved.

Simple 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. If no suitable setting exists in PlentyONE. you can map a property instead.

As such, simple 1:1 mappings allow you to:

I want to fill this marketplace data field with the data from this PlentyONE setting.
If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.

Example: Sales price and RRP for Otto Market

This gif shows you how to map the marketplace data fields Sales price and RRP for Otto Market to PlentyONE data fields:

Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

Is this your first time working with properties? Then read up on the principles of properties first.

Creating a property:

Create a property with the necessary values.
Tip: Find out how to do that here.

Creating a simple 1:1 mapping with properties:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
Click on Confirm.
→ The property is mapped to the marketplace data field.

Complex 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

In complex mappings, the value of the market is always exported. Only when you map an own value, the own value that you enter is exported.

You can recognise complex mappings from the field that is shown below the name of the marketplace data field. Click on the field to show the values available for the marketplace data field.

Examples for complex 1:1 mappings are:

Categories
Brands
Shipping setting

Important: For complex mappings, do not map own values or properties of the type None.

Creating a complex 1:1:n mapping:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
Click on the PlentyONE data field for which you want to map values.
Important: Do not map own values or properties of the type None.
Your next steps depend on the PlentyONE data field you selected:
- Alternative 1: The available values for the PlentyONE data value are shown on the left.
  - Next to the value you want to select, click on the plus.
    → The value is added to the field on the right.
  - Click on Confirm.
- Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.
  - In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.
  - Click on Confirm.
- Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.
  - Select a value from the drop-down list.
  - Click on Confirm.
    → The value of the marketplace data field is exported, not the value of the PlentyONE data field.
    Exception: Only when you map an own value, the own value that you enter is exported.

Example: Delivery time in days for Otto Market

This gif shows you how to map suitable PlentyONE values to the values of the marketplace data fields Delivery time in days for Otto Market:

1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

So this mapping specifies:

I want to fill the marketplace data field with the data from the selected PlentyONE setting.
If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.
If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

The fallback data field is used if the data field above is mapped in the catalogue but not linked to the variation.

The condition "Null" is useful when you want to map fallback data fields for the following types of PlentyONE data fields:

SKU
Barcodes
Sales prices
Properties

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Empty

The fallback data field is used if the data field above is mapped in the catalogue and linked to the variation, but is empty.

The condition "Empty" is useful when you want to map fallback data fields for the following type of PlentyONE data fields:

PlentyONE data fields that are available for variations by default

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Creating a 1:1 mapping with fallback data fields:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
→ The fallback data field is added with the fallback condition "null".
Alternative 1: To add the fallback data field with the fallback condition "null":
1. Click on Confirm.
  → The fallback data field is exported if the data field above is not linked to the variation.
Alternative 2: To add the fallback data field with the fallback condition "empty":
1. To the left of the fallback data field, click on the cog ().
  → The window Data column settings is shown.
2. For the setting Fallback condition, select the option Empty.
3. Click on Save.
  → The fallback data field is added with the fallback condition "empty".
4. Click on Confirm.
  → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

Result: The fallback data field Variation ID is exported if the data field SKU is not linked to the variation.

1:n mapping: 1 marketplace data field, several PlentyONE data fields

In a 1:n mapping, you map several PlentyONE data fields to the marketplace data field. You can link these data fields with a separator.

So this mapping specifies:

I want to combine these PlentyONE data fields during export so that the marketplace data field is filled with the data of these two or more PlentyONE settings.

Creating a 1:n mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.
To the right of the mapped PlentyONE data field, click on Add data field ().
→ To the left, the list of available PlentyONE data fields again are shown in groups.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
Save () the catalogue.
→ The mappings are saved.
→ During the export, the content of the PlentyONE data fields is combined and exported as one field.

Own value mapping: 1 marketplace data field, the same value for all variations

You are sure that you want to export the same value for all variations of a catalogue for a marketplace data field? Then specify an own value. This own value is then exported for all variations.

So this mapping specifies:

For this marketplace data field, I want to export the value that I entered in the field Own value for all variations of this catalogue. The value you enter is always exported. The value overwrites the market value also in complex mappings where usually the value of the market is exported. As such, make sure you enter an own value that the market accepts for this marketplace data field.

Creating an own value mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view.
Enter a value into the input field.
→ This value is exported for all variations.

Example: Diameter information

This is an example of how you can map an own value for the diameter unit:

Mapping with mathematical calculations: 1 Marketplace data field, the PlentyONE value is recalculated using the formula during export

Mathematical calculations allow you to change numerical values automatically during the export.

This function only works for data fields that contain numerical values.
This functionality is new and not available for all catalogue formats.

So this mapping specifies:

I want the numerical value of a PlentyONE data field to be recalculated during the export. Basic arithmetic operations are available for the formulas.

Recalculating numerical values:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.
1. Click on the icon .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

7.1.2. Activating the catalogue export

You have set up ManoMano in PlentyONE and created a catalogue for exporting your offer data? Then activate the catalogues you want to export to ManoMano in the Data » Catalogues menu and continue with creating offer listings.
Once you have activated the offer catalogue, the ManoMano account, the offer listing and the variations, the offer data will be automatically exported to ManoMano every 15 minutes.

Activating the catalogue export to ManoMano:

Go to Data » Catalogues.
→ The catalogues are listed.
Scroll to the ManoMano catalogue.
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to ManoMano every 15 minutes.
Tip: Go to Data » Catalogue export status for information about the status of the export.

8. Managing listings

You create and manage offers for ManoMano via listings. The Sales channels » Accounts » [Open account] menu offers you an overview of your listings. Here you can create and manage product listings and offer listings. Click on the tile for ManoMano to create product listings or offer listings for ManoMano.

8.1. Offer listings

In the Offer listings menu of the account you gain an overview of your offer listings.

Tip: You can switch between specific views of offers and the listing group view via the button and .

gives you an overview of all the offer listings.
shows you the listing groups of the offer listings. Extend a listing group by clicking , to see all listings within the group.

Applying search filters

If you only want to take a look at certain offer listings, apply filters and narrow down the listings which are displayed. To do so, click on Filters () at the top of the menu.

Applying filters:

Open the Sales Channels » Accounts » [Open account] » Offer listings menu.
Click on Filters () at the top of the menu.
Select one or multiple filters.
Click Search ().
→ The selected filters are applied and the appropriate offer listings are displayed.
→ The filters that were applied are displayed at the top of the menu.

Tip: You can also reset () the selected filters. Then all offer listings will be displayed again.

Single listing view
Group view

Table 6 offers an overview of the single listing view of offer listings.

Table 6. Offer listings overview

Column

Explanation

Data sync

This column indicates whether data exchange for the offer listing is active or paused.
Tip: You can activate the data exchange in the listing’s line via » toggle_on Activate data sync .

Group ID

The ID of the listing group to which the offer listing is assigned. By clicking on the ID, you can open the listing group view.

Listing Name

Name of the offer listing.

SKU

SKU of the offer listing.
Note: You can edit the SKU. To do so, click Activate editing mode (). Make the changes and click Save () to apply them. If you want to exit the editing mode, click Deactivate editing mode ().

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Status on Channel

Displays the listing status on the sales channel, for example if the listing is already listed on the sales channel. Possible status are:

help = Unknown
progress_activity = Outstanding
progress_activity = Creation pending
cancel = Failed (before creation)
check_circle = Online
cancel = Failed (on update)
pause_circle = Paused
unpublished = Offline

Note: For platforms with multiple sales channels, the number after the status icon indicates on how many sales channels the offer listing has this status.

List on

The sales channels on which the offer listing is to be offered are displayed here.
Click on the pencil icon (edit) to add or remove sales channels.

Errors

Indicates whether the listing is incorrect. Click to open the overview of listing errors.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing.
Note: Even if the Activate data sync option is activated, the listing will not be immediately listed on the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when a listing is online.

Delete listing

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

Table 7 offers an overview of the group view of offer listings.

Table 7. Group view of the offer listings

Column

Explanation

Data sync

This column indicates whether data exchange for the listing group is active or paused.
Tip: You can activate the data exchange in the listing group’s line via » toggle_on Activate data sync.

Group name

Name of the listing group

SKU

SKU of the listing group.

Channel

The sales channel to which the listing group is exported.

Errors

The error overview.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

The date and time on which the listing group was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing group.
Note: The data sync must also be activated for the single listing to list an offer listing on a sales channel.
Even if the Activate data sync option is activated in a listing group, the listings in this group will not be immediately listed on the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when the listings are online.

Delete listing group

Delete listing group.

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

8.2. Product listings

In the Product listings menu of the account you gain an overview of your product listings.

_Tip: You can switch between specific views of product listings and the listing group view via the button.

gives you an overview of all the product listings.
shows you the listing groups of the product listings. Extend a listing group by clicking , to see all listings within the group.

Applying search filters

If you only want to take a look at certain product listings, apply filters and narrow down the listings which are displayed. To do so, click on Filters () at the top of the menu.

Applying filters:

Open the Sales Channels » Accounts » [Open accounts] » Product listings:.
Click on Filters () at the top of the menu.
Select one or multiple filters.
Click Search ().
→ The selected filters are applied and the appropriate product listings are displayed.
→ The filters that were applied are displayed at the top of the menu.

Tip: You can also reset () the selected filters. Then all product listings will be displayed again.

Single listing view
Group view

Table 8 offers an overview of the single listing view of product listings.

Table 8. Overview of product listings

Column

Explanation

Data sync

This column indicates whether data exchange for the product listing is active or paused.
Tip: You can activate the data exchange in the listing’s line via » toggle_on Activate data sync .

Listing Name

Name of the listing.

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Errors

Indicates whether the listing is incorrect. Click to open the overview of listing errors.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

Click here to display more actions.

toggle_on Activate data sync

Delete listing

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

Table 9 offers an overview of the group view of product listings.

Table 9. Group view of the product listings

Column

Explanation

Data sync

Group name

Name of the listing group

Channel

The sales channel to which the listing group is exported.

Errors

The error overview.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

The date and time on which the listing group was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing group.
Note: The data sync must be activated for the single listing to exchange product data with the sales channel.
Even if the Activate data sync option is activated for a listing group, the listing data will not be immediately exported to the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when the listings are online.

Delete listing group

Delete listing group.

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

8.3. Creating listings

Products and offers are transferred to ManoMano as listings. Carry out the following steps to create listings for ManoMano.

What are product listings and offer listings used for?

If the item you want to sell is not listed on the sales channel yet you will need to create a product listing for it first. Creating a product listing sends the product data to the sales channel and allows for the item to be listed.
In order to actually be able to sell the item on the sales channel you will need to additionally create an offer listing. The offer listing contains data related to the sale of the item, such as its price and stock. In other words, a product listing allows you to list an item on a sales channel that did not previously exist on that sales channel, but in order to sell that item on that sales channel you also need an offer listing for that item.
If the item you want to sell is already listed on the sales channel you only need to create an offer listing. Offer listings send the data related to your offer, such as the price, stock, shipping costs etc., to the sales channel.
In most cases you will only need an offer listing in order to offer a product on a sales channel. Many sales channels do not differentiate between product and offer listings. You only need to send offer listings to these kinds of sales channels.

8.3.1. Creating offer listings

Offer listings are created in three steps:

First, you enter listing details, meaning you select the platform, template, sales channel and catalogue for the listing.
Next, you select the variations from which the offer listings are created.
Lastly, check and confirm your selection and create the listings.

You can also create offer listings directly from your product listings. Here you can learn how to do that.

Step 1: Specify listing details:

Open the Sales Channels » Accounts menu.
Open the account for ManoMano.
→ The menu Channel settings opens.
Open the menu format_list_bulleted Offer listings.
Click arrow_drop_down and select Create offers.
→ The menu Create offers opens.
Select the platform ManoMano.
Select the template for the catalogue.
Tip: Only templates that are available for the platform ManoMano are displayed.
Select the sales channel on which the listing should be offered.
Select a catalogue with your mappings for offer data.
Tip: If you have no fitting catalogue yet, click on Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.
Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to ManoMano after the listing is created.
Click NEXT.
→ The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

Select the variations you want to create the offer listing for.
Tip: Use the search to filter for variations.
Note: Only variations that are linked to ManoMano in the Item » Items » [Open item] » [Open variation] menu are displayed.
Tip: If you want to create offer listings for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Offer listings can be created for a maximum of 50,000 variations at a time.
Click ADD TO SELECTED VARIATIONS.
→ The selected variations are displayed in the Selected variations section.
Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.
Click NEXT.
→ The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

Preview your settings in the Listing details section.
Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group () to see which variations are contained in the respective listing group.
If everything is set and done, click CREATE OFFER LISTINGS.
Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click CONFIRM to create the offer listings.

8.3.2. Activating offer listings

After you have created the offer listings, you have to activate the listings so that they can be transferred to ManoMano.
To do so, activate the individual listings and the listing group. The listing can only be transferred to the sales channel if both the listing and the listing group are activated.

Note: You can also activate listings immediately after creation by activating the option Automatically activate listings after creation. If you activate the option to automatically activate listings after creation, you still have to activate the data exchange for the listing group.

Activating offer listings:

Open the menu Sales Channels » Accounts » [Open ManoMano account].
→ The tab Channel settings opens.
Open the Offer listings tab.
In the line of the offer listing you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple offer listings at once, place a check mark next to the desired offer listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

Open the menu Sales Channels » Accounts » [Open ManoMano account].
→ The tab Channel settings opens.
Open the Offer listings tab.
Open the listing group view (folder).
In the line of the listing group you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing group is activated.

8.3.3. Creating product listings

Product listings are created in three steps:

First, you enter listing details, meaning you select the platform, template, sales channel and catalogue for the listing.
Next, you select the variations from which the product listings are created.
Lastly, check and confirm your selection and create the listings.

Create product listings using the group function

You can also create product listings directly in the Item menu using the variation group function. You can find more information about the variation group function here.

Step 1: Specify listing details:

Open the Sales Channels » Accounts menu.
Open the account for ManoMano.
→ The menu Channel settings opens.
Open the menu format_list_bulleted Product listings.
Click on Create products.
→ The menu Create products opens.
Select the platform ManoMano.
Select the sales channel on which the listing should be offered.
Select the template for the catalogue.
Tip: Only templates that are available for the platform ManoMano are displayed.
Select a catalogue with your mapping for item data.
Tip: If you have no fitting catalogue yet, click on Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.
Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to ManoMano after the listing is created.
Click NEXT.
→ The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

Select the variations you want to create the product listing for.
Tip: Use the search to filter for variations.
Note: Only variations that are linked to ManoMano in the Item » Items » [Open item] » [Open variation] menu are displayed.
Tip: If you want to create product listings for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Product listings can be created for a maximum of 50,000 variations at a time.
Click ADD TO SELECTED VARIATIONS.
→ The selected variations are displayed in the Selected variations section.
Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.
Click NEXT.
→ The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

Preview your settings in the Listing details section.
Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group () to see which variations are contained in the respective listing group.
If everything is set and done, click CREATE PRODUCT LISTINGS.
Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click CONFIRM to create the offer listings.

8.3.4. Activating product listings

After you have created the product listings, you have to activate the listings so that they can be transferred to ManoMano.
To do so, activate the individual listings and the listing group. The listing can only be transferred to the sales channel if both the listing and the listing group are activated.

Activating product listings:

Open the menu Sales Channels » Accounts » [Open ManoMano account].
→ The tab Channel settings opens.
Open the Product listings tab.
In the line of the product listing you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple product listings at once, place a check mark next to the desired product listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

Open the menu Sales Channels » Accounts » [Open ManoMano account].
→ The tab Channel settings opens.
Open the Product listings tab.
Open the listing group view (folder).
In the line of the listing group you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing group is activated.

8.4. Viewing listing errors

The Errors tab of the Sales Channels » Accounts » [Open account] » Offer listings / Product listings menu provides an overview of all errors that occurred in PlentyONE when exporting your product and offer listings.
Tip: The overview of listing errors is only displayed if at least one error has occurred when exporting the listings.

Here you can see:

the affected listings
error details

For each error, you can download a CSV file containing the affected listings by clicking the download button. You can correct the errors directly in the CSV file. You can then re-import the corrected CSV file.

Table 10 contains an overview of listing errors.

Table 10. Listing errors of offer listing and product listings
Column	Explanation
[Information about the error]	Information about the error is provided here. It contains the affected field of the data record, a brief description of the error and the number of listings for which this error has occurred. *Example:* "Field: gtin Error: Given data is not a string. (1)" → The error occurred in the gtin field of the data record. → The error occurred because no character string was entered as a value in the gtin field. → The error has occurred for one listing.
Download data as CSV	The CSV file with the data records is downloaded.
Listing name	The name of the listing.
Parent SKU	The parent SKU of the main variation.
SKU	The SKU of the sub-variation.
Variation ID	The ID of the variation.
Channel	The sales channel to which the listing is exported.
Export activity	Shows whether the variation is being exported. Active () = The variation is exported with the listing. Not active () = The variation is not exported with the listing.
Status	The listing’s status on the sales channel. Possible statuses are: help = Unknown progress_activity = Outstanding progress_activity = Creation pending cancel = Failed (before creation) check_circle = Online cancel = Failed (on update) pause_circle = Paused unpublished = Offline
Errors	The error overview. No entry = No errors occurred. = Errors occurred. The number indicates the number of errors.
Template	The template selected for the listing.
Catalogue	The catalogue selected for the listing.

9. Adding additional sales channels

If you already sell on ManoMano and would now like to offer your items in another country, you have to carry out the following settings:

Note: You can only sell your items on sales channels for which you have been provided Contract IDs by ManoMano.

Add the sales channel and enter its Contract ID in the ManoMano Channel settings.
Activate the matching order referrer for the new sales channel in the Setup » Orders » Order referrer menu.
In the offer catalogue for ManoMano, map the data fields for prices for the new sales channel.
Make the offer listings that you want to offer on the new sales channel available for the sales channel. To do so, open the offer listing view in the Sales Channels » Accounts » [Open account] menu and activate the new sales channel in the column List on of an offer listing. To do this, activate the editing mode via the pencil icon (edit) and make sure to save the changes.

10. Automating order processing

Create event-based flows to automatically inform ManoMano about changes to the order status. The following actions are available for ManoMano in the PlentyONE Flow Studio:

Inform ManoMano that the order was accepted. (How?)
Inform ManoMano that the order was rejected. (How?)
Inform ManoMano that the items have been shipped. (How?)
Inform ManoMano that an item was refunded. (How?)

What is PlentyONE Flow?

With PlentyONE Flow (short: "Flow"), you can automate workflows for your business processes. Flow provides you with two functions in the Automation menu:

In Flow Studio you create and configure automated workflows. Depending on the trigger type, there are three flow types: event- based, time-based or manual.
In the Flow Tracker, you can monitor running or completed workflows.

The central element in both functions is the Canvas – a graphical interface on which the workflows are visualised with Actions and Controls. In Flow Studio the canvas can be edited, in Flow Tracker it is only used for visualisation and is therefore read-only.

Is this your first time working with PlentyONE Flow? Then read up on the basic concept of Flow first.

10.1. Reporting order confirmation to ManoMano

Create an event-based flow to automatically inform ManoMano about the order confirmation.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 11.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 11.
Save () the settings.

Note: The selected statuses, controls and filters in Table 11 only serve as an example. Select the status, controls and filters for the flow which best suit your workflow.

Table 11. Event-based flow to send an order confirmation to ManoMano

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

For Order statuses, select a status between Status 1 and Status 2, for example [1.0.1] Accept order, waiting for update.
You can create a new status for this.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the other filters as condition (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the ManoMano sales channels that you want to use this flow for.

Actions

Multichannel > ManoMano

Send accept order to ManoMano

10.2. Reporting order rejection to ManoMano

Create an event-based flow to automatically inform ManoMano about the rejection of an order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 12.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 12.
Save () the settings.

Note: The selected statuses, controls and filters in Table 12 only serve as an example. Select the status, controls and filters for the flow which best suit your workflow.

Table 12. Event-based flow to send an order rejection to ManoMano

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order created

For Order types, select the type Incomplete order.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the other filters as condition (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the ManoMano sales channels that you want to use this flow for.

Actions

Multichannel > ManoMano

Send refuse order to ManoMano

10.3. Sending shipping confirmations to ManoMano

Create an event-based flow to automatically inform ManoMano when you have shipped the items of an order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 13.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 13.
Save () the settings.

Note: The selected statuses, controls and filters in Table 13 only serve as an example. Select the status, controls and filters for the flow which best suit your workflow.

Table 13. Event-based flow to send shippingconfirmations to ManoMano

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Order > Book outgoing items

Select an Order status, for example:

[7] Outgoing items booked

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the other filters as condition (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Select the order referrers for the ManoMano sales channels that you want to use this flow for.

Actions

Multichannel > ManoMano

Send fulfillment to ManoMano

10.4. Reporting refunds to ManoMano

Create an event-based flow to automatically inform ManoMano that an item was refunded. Whenever you are dealing with refunds, you need to send ManoMano a reason for the refund. The following refund reasons can be transferred to ManoMano:

No stock
Customer canceled

Note: By selecting Customer canceled as the refund reason you can inform ManoMano that an order has been cancelled by the customer and fully refunded in the same step.

To report refunds to ManoMano, a credit note must be created.

Note: ManoMano only accepts full refunds, not partial refunds. For a full refund, a credit note for all order items of the parent order must be created.

How do I create a credit note for a full refund?

Go to Orders » Orders.
Carry out the search () to display orders.
Open the order for which a credit note should be created.
At the top, click on Create orders () > Credit note.
Select the option For all order items.
Save () the settings.
→ The credit note order is created.
Carry out the appropriate flow for this order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 14.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 14.
Save () the settings.

Note: The selected statuses, controls and filters in Table 14 only serve as an example. Select the status, controls and filters for the flow which best suit your workflow.

Table 14. Event-based flow for reporting a refund to ManoMano

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order created

Select an Order type, for example:

Credit note

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the other filters as condition (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Select the order referrers for the ManoMano sales channels that you want to use this flow for.

Actions

Multichannel > ManoMano

Select the action Send refund order to ManoMano and an appropriate reason.

11. Deleting an account

In the account overview of the Sales Channels » Accounts menu, you can delete a ManoMano account. Before deleting a ManoMano account, make sure that no orders exist anymore and that the account is deactivated.

Deleting an account:

Open the Sales Channels » Accounts menu.
In the tile of the ManoMano account that should be deleted, click on Delete account ().
→ A pop-up for deleting the account opens. If you want to delete the account, confirm the pop-up by clicking on delete Delete account.
→ The account is deleted.

12. Viewing the data log

Error reports of the export are logged in the Data » Log menu. In order to view the data log and search for specific errors, proceed as follows.

Viewing the data log:

Go to Data » Log.
→ The data log overview opens.
At the top, click on Filter ().
In the Identifier field, enter the option MANOMANO to display all error reports for your ManoMano account.
Tip: Select a date if you only want to see entries for a specific day.
Optional: In the Integration field, additionally enter a path to refine the search further. E.g. the path Plenty\Modules\ManoMano\Services\Order\OrderImportServices to display only error reports for the order import.
Click Search ().
→ The error reports are shown according to the filter settings.

ManoMano

1. Becoming a seller on ManoMano

2. Frequency of data exchange

3. Setting up the data exchange

4. Workflow of an ManoMano order

5. Setting up ManoMano in PlentyONE

5.1. Creating an account

5.2. Account overview

5.3. Carrying out the channel settings for ManoMano

5.4. Modifying the account settings

5.5. Activating the account

5.6. Activating the order referrer

6. Exporting product data

6.1. Creating a product catalogue

Other catalogue settings

6.1.1. Mapping data fields in the catalogue

6.1.2. Activating the catalogue export

7. Exporting offer data

7.1. Creating an offer catalogue

Other catalogue settings

7.1.1. Mapping data fields in the offer catalogue

7.1.2. Activating the catalogue export

8. Managing listings

8.1. Offer listings

8.2. Product listings

8.3. Creating listings

8.3.1. Creating offer listings

8.3.2. Activating offer listings

8.3.3. Creating product listings

8.3.4. Activating product listings

8.4. Viewing listing errors

9. Adding additional sales channels

10. Automating order processing

10.1. Reporting order confirmation to ManoMano

10.2. Reporting order rejection to ManoMano

10.3. Sending shipping confirmations to ManoMano

10.4. Reporting refunds to ManoMano

11. Deleting an account

12. Viewing the data log

Is this page helpful?

Is this page helpful?