ChannelEngine: pricing

About this article

This article describes pricing on ChannelEngine and the main pricing attributes that are available. 

Table of contents

Introduction

Price attributes on ChannelEngine

FAQs

Introduction

Before creating a product feed, or adding products and channels on ChannelEngine, one of the first things you should consider is pricing.

While ChannelEngine offers several tools to efficiently manage prices, such as price rules and repricing (if the channel supports it), you need to think about what base price you want to use on marketplaces. ChannelEngine can advise you on this matter, but the only person who can determine the minimum price and necessary margins is you.

Bear in mind that channels, and thus also ChannelEngine, expect that the prices you submit include VAT.

Price attributes on ChannelEngine

In most scenarios, ChannelEngine expects three different prices:

• Purchase price - the price you pay your supplier for the product. This price can be useful if you use ChannelEngine's repricing but want to keep a minimum margin taken into account. This purchase price, if available, is also used to calculate a margin on ChannelEngine, which can be used in business rules.
• Price - your basic selling price, which you use when the product is sold directly on your webshop. This should include your own profit margin, but does not necessarily have to include the channel's commission or your own fees.
• Catalog price/Manufacturer's suggested retail price (MSRP) - this is not mandatory but can be very useful if you want to use from-for prices on channels that support this feature.

Of those three attributes, only the Price is mandatory. However, the other two values can be very useful – as mentioned above.

It is possible to submit multiple additional price attributes, for example, if you want to use a different base price on every Amazon EU portal. Make sure to submit these price attributes as extra attributes in your feed or API call.

FAQs

My prices are not being exported – or the wrong price attribute is exported, instead of the value from a custom attribute. What is wrong?

One of the most common causes of errors in price exports are typos in the attribute values. These can range from a comma when the attribute expects a dot, or spaces before or after the value. E.g.: "Value": "32.95 ".