Channel Manager

The hard part of selling across channels is not publishing the catalogue: it is keeping stock identical everywhere. When a unit sells in store it has to stop being available on the marketplace; and when an online order comes in, it has to appear with its customer and carrier ready to pick. Everything else is secondary to never selling the same unit twice.

Each channel has its own rules: pricing rules per category, per product or per band, because the margin a marketplace absorbs is not the one your own shop does; each platform's categories mapped against your families; and dropshipping for the catalogue that never passes through your warehouse.

The sync and error log is the part you appreciate when something breaks: it tells you why a product was not published, instead of letting you find out through the sales that never came.

One single stock

The problem is not publishing the catalogue

Uploading products to a marketplace is something almost any tool can do. The hard part, and the one that costs money when it fails, is keeping stock identical across every channel at the same time.

Synchronisation runs both ways and continuously: when a unit sells at the shop's POS, it stops being available on the marketplace; when an online order comes in, it appears in the system with its customer, its lines and its carrier, ready to pick like any other.

Selling the same unit twice costs more than a cancelled shipment: on most platforms it damages your seller rating, and that is paid for in visibility for months.

Each channel, its rules

The same product is not worth the same everywhere

A marketplace takes a commission your own shop does not, so publishing the same price on every channel means selling at very different margins without having decided to.

Pricing rules solve that without maintaining parallel lists: you define the adjustment per channel, per category, per specific product or per price band, and the published price is calculated from yours.

And what each platform demands

Each marketplace's own categories, mapped against your families and subfamilies, because no platform accepts your classification as it is.
Carriers linked to each channel so the order ships with the right service.
Dropshipping for the catalogue that never passes through your warehouse and is shipped by the supplier.

When something breaks

Knowing why a product was not published

Marketplace integrations fail for mundane reasons: an empty required field, an image below the minimum size, a category the platform has changed, a duplicate barcode. None is serious; what is serious is not finding out.

The sync log stores what was sent, when, and what each channel replied, with errors described and grouped. Products that never made it to publication appear in a list with their reason, instead of being discovered weeks later while wondering why that item sells nothing.

That is the boring part of a channel manager and the one that separates an integration that maintains itself from one somebody has to review by hand every Monday.

See the channel manager in a demo

Clearing things up

Frequently asked questions

Answers to what we get asked most.

Which platforms does it sync with?

With PrestaShop, WooCommerce, Amazon, Miravia, Zalando and other marketplaces, in both directions: products, stock, prices, orders and customers. Online orders enter the system with their customer, lines and carrier, ready to pick like any other.

Can I avoid selling the same unit twice?

That is exactly the point. When a unit sells at the shop's POS, it stops being available on the marketplace. Overselling costs more than a cancelled shipment: on most platforms it damages your seller rating, and that is paid for in visibility for months.

Can I set different prices per channel?

Yes, with pricing rules per channel, category, specific product or price band. The published price is calculated from yours, so there are no parallel lists to maintain: a marketplace takes a commission your shop does not, and that should be a decision rather than an accident.

How do I know if a product failed to publish?

The sync log stores what was sent, when and what each channel replied, with the errors described: an empty required field, an image below minimum size, a changed category or a duplicate barcode. They appear in a list with their reason instead of being discovered through sales that never come.

POS, retail and loyalty

A point-of-sale terminal compliant with Spanish anti-fraud law and Verifactu, promotions and campaigns, marketplace synchronisation and the full purchasing and sales cycle.

POS · Point of Sale Terminal

A point of sale terminal that is fast at the counter and compliant with Spanish anti-fraud law and Verifactu, with discounts, vouchers, gift receipts, returns and cash-up.

View module