Marketplaces

How to connect Altex with easySales: the complete integration guide

How to connect Altex with easySales: the complete integration guide

Connect the Altex marketplace to easySales, map your categories, publish offers from your existing catalogue, and read the two statuses Altex reports back.

What you can do with Altex and easySales

Altex is Romania's largest electronics and appliance retailer, and its marketplace lets other sellers list alongside its own catalogue. easySales connects to that marketplace so your offers are generated from the catalogue you already maintain, and stay current on their own: prices and stock follow your products, and offers switch off when something sells out.

That is the part worth automating. Publishing offers once is an afternoon's work; keeping them accurate as stock moves is permanent, and it is what the integration takes over.

Altex operates in Romania only. If you sell cross-border, this connection covers your Romanian channel and nothing else.

Before you connect

An Altex marketplace account

Altex approves sellers before issuing marketplace credentials. The Public and Private keys come from them, not from easySales.

Your category access confirmed

Altex grants each seller a specific set of categories. Knowing which ones you have tells you what you can actually list before you start mapping.

Products in your easySales catalogue

Offers are generated from products you already hold. Nothing publishes from an empty catalogue.

Clean, unique EANs

Altex refuses a product whose EAN is already in its catalogue. De-duplicate before a bulk publish rather than after.

The Altex courier, if you need AWBs

Added separately under Integrations → Couriers. Without it you cannot generate an AWB for an Altex order.

Connecting Altex to easySales

Go to Integrations → Marketplaces, find Altex and press Connect. The connection form opens with two tabs: Main settings and Additional settings.

The Altex connection form in easySales, showing Connection Name, Price Addition, Default shipping tax, Invoice Series, Default Tax Rate, Delivery Days and the Public and Private key fields.
The Main settings tab. Everything here becomes the default for every offer you publish.

Everything on this screen becomes the default for every offer you publish, so it is worth setting deliberately rather than accepting the blanks.

Setting What it does
Connection Name Your own label for the connection. It appears on every offer row, which matters once you run more than one channel.
New order custom status The status an imported Altex order lands in. Leave blank to use the default.
Price Addition A percentage added to the sale price on this channel only, applied to new offers. Your catalogue price is untouched.
Default shipping tax The VAT rate applied to delivery on imported orders.
Invoice Series The billing series used when easySales generates invoices for Altex orders.
Default Tax Rate The VAT rate applied to the offers you publish.
Delivery Days The handling time shown to buyers, in days.
Public key / Private key The credentials Altex issues you. They do not expire, so there is no reconnection cycle to plan for.
What each connection setting does

The second tab holds three synchronisation switches. They are the ones most often left alone, and they are what makes the integration maintain itself rather than just publish once.

The Additional settings tab of the Altex connection, showing three switches: send offer prices to marketplace, send offer stock to marketplace, and automatically enable offers when products have stock.
The three switches that keep offers current after they are published.

Mapping your categories

Offers cannot be published until the category holding them is mapped to an Altex category. Open Products → Categories and use Map categories on each category you sell from.

The Categories screen in easySales. Three categories show AltexRO in the MAPPED column; two are unmapped. Each row carries a Map categories action.
Headphones, Laptops and Keyboards, and Appliances are mapped. Furniture is not — that category has not been granted to this Altex account.

Altex organises its catalogue in two layers, and you will meet both here. Categories place the product in the shop's tree. Attribute sets define which characteristics the product must supply. A set suggests the categories it belongs to, so picking the set first usually fills the category for you.

Map only the categories you actually sell from. A complete mapping of your whole tree is not needed to start, and a smaller mapping is faster to check when something is rejected.

Adding offers

Offers are generated from products you already hold. Open Products → Products and either use Add offer on a single row, or select several and use the Add offer(s) on button above the list.

The Products screen in easySales, with an Add offer action on each product row and an Add offer(s) on button above the list for publishing several at once.
Offers are generated from products you already hold — one row at a time, or a whole batch.

If you already sell on Altex, your existing offers are imported into Marketplace → Offers on the Altex tab, unlinked. Link each one to the matching product so the two stay synchronised — an unlinked offer receives no price or stock updates.

When you publish in bulk afterwards, filter to products without offers on Altex first. That is what stops you creating a second offer for something already listed.

Reading the two statuses

Altex reviews an offer in two separate passes, and easySales shows both. This is the part sellers most often misread: an offer can be approved on one and pending on the other.

The Altex offers list in easySales showing published offers with their Altex id, linked product SKU, stock, price in RON, and both Listing status and Offer status badges reading Pending, Approved and Rejected.
Every offer carries two statuses. The rejected listing shows Altex's reason on the badge.
Status What it covers Values
Listing status The product documentation — title, description, images, characteristics Pending · Approved · Rejected
Offer status Your commercial terms — price, stock, delivery Pending · Approved · Rejected
How Altex reports on an offer

Listing status covers the product documentation — the title, description, images and characteristics that describe what the product is. Offer status covers your commercial terms: price, stock and delivery. A rejection carries Altex's reason, shown on the status badge.

Generating AWBs

Returns and credit notes

Frequently asked questions

Altex issues the Public key and Private key after approving you as a marketplace seller. Request marketplace access from Altex directly; easySales cannot generate or recover these keys for you.

No. Unlike channels that use a time-limited authorization, the Altex Public and Private keys are static credentials. Once the connection works it stays connected, and there is no periodic reconnection to plan for.

Altex grants categories per seller account, and the picker only shows the ones granted to yours. A missing category means your Altex account is not approved to sell in it. Ask Altex to extend your category access, then re-open the mapping screen.

Altex reviews an offer in two passes. Listing status covers the product documentation — title, description, images and characteristics. Offer status covers your commercial terms — price, stock and delivery. Each can be Pending, Approved or Rejected independently, so an offer can be approved on one and still waiting on the other.

Altex does not allow two products to share an EAN. If the code already exists in its catalogue the product is refused with the message "This EAN is already exists on marketplace. Altex does not allow EAN duplicates." Correct the EAN in your catalogue and resend the offer.

Yes, but only through the Altex courier, which you add separately under Integrations → Couriers. No other courier integration can produce an AWB for an Altex order.

No. Altex does not accept credit notes through the integration. easySales records the return and marks the order returned on its side, but the credit has to be settled with Altex directly.

Was this guide helpful?