Online Shop

How to connect Magento with easySales: a complete integration guide

How to connect Magento with easySales: a complete integration guide

Connect a Magento 1 or Magento 2 store to easySales: fill the connect form, install the module, paste the token, and know what syncs in each direction and how often.

What connecting Magento gives you

easySales reads your Magento catalogue — products, prices, stock, categories and attributes — and uses it to build and maintain offers on the marketplaces you sell through. Orders come back the other way, into one list where you invoice them and generate AWBs, without adding anything to your store.

The point is not the first import. It is that the connection keeps working afterwards: stock moves as you sell, order statuses return to Magento, and offers switch off when something runs out.

Before you start

Admin access to your Magento store

You need to reach Stores → Configuration (Magento 2) or System → Configuration (Magento 1) to paste the token.

A way to upload files to the server

SFTP, SSH or your host's file manager. Magento 2 also needs SSH to run one command; Magento 1 does not.

Unique SKUs across your catalogue

SKU is how easySales matches a Magento product to its own. Two products sharing one SKU cannot both be imported.

Stock held as a number

Products whose stock is text or blank are skipped.

Your VAT rates to hand

You set a default product VAT and a shipping VAT while connecting.

Step 1 — Add the website in easySales

Go to Integrations → Websites and press Connect a Website.

The Connect a Website form in easySales, showing Website Name, Website URL, Country, Price Vat, Shipping Vat, Language, Currency, New order custom status, Inventory source, Implicit package type and Invoice Series, above a grid of shop platform logos.
The connect form. The same fields serve every platform; the logo grid underneath is where you choose Magento.

Nothing on this form is specific to Magento — it is the same form every shop platform uses. Three of the fields cannot be changed later, so they are worth getting right the first time.

Field What it does
Website Name Your own label for the store. It appears wherever easySales has to tell your shops apart, which matters as soon as you connect a second one.
Website URL Your storefront address. Pick http:// or https:// to match what the site actually serves, and include www if the site forces it — a redirect here is a failed connection test.
Country The store's country. It decides which VAT rates the next field offers. Cannot be changed later.
Price Vat The VAT rate applied to products that arrive without one. Chosen from your country's rates, not typed.
Shipping Vat The VAT rate applied to delivery when the order does not carry one.
Language The store's language. Cannot be changed later.
Currency The currency your Magento prices are in. Cannot be changed later.
New order custom status Optional. Drops every imported order straight into one of your own statuses instead of the default.
Inventory source Where the authoritative stock number lives. See the note below the table.
Implicit package type Envelope or parcel, used as the default when generating AWBs for these orders.
Invoice Series The billing series used for orders from this store when Magento does not supply one.
What each field on the connect form does

Step 2 — Pick Magento, then your version

Below the form is a grid of platform logos. Choose Magento, and a second row appears asking which version your store runs.

The platform logo grid with the Magento tile selected and showing a green check, and below it a row headed Choose the platform version your site uses with two cards: Magento 2 and Magento 1.7 - 1.9.
One Magento tile, two versions. Both are supported.

Both versions are supported and both are actively downloadable:

Version Installed via Order Submissions Document read-back
Magento 2 Upload to app/code/, then setup:upgrade Yes, with a recent module Yes
Magento 1.7 – 1.9 Magento Connect Manager No No
The two Magento modules

Step 3 — Install the module

Selecting a version opens a three-step wizard: Download Module, Upload the Module, Configuration.

Magento 2

Download the archive, unzip it, and upload the folder to your server under app/code/. The result has to be exactly this path:

app/code/EasySales/Integrari/

Then connect over SSH and enable the module:

php bin/magento setup:upgrade

Finally clear the cache from System → Cache Management → Flush Magento Cache.

The Upload the Module step of the easySales wizard, giving the app/code/EasySales/Integrari/ path, the SSH command to enable the module, and the instruction to flush the Magento cache.
The install instructions. Note the command on this screen carries a stray exclamation mark — type it as setup:upgrade.

Magento 1

The Magento 1 module installs through Magento Connect instead. In your store admin go to System → Magento Connect → Magento Connect Manager, re-enter your login, and use Direct package file upload to upload the archive you downloaded.

Then clear the cache from System → Cache Management, and — this step is genuinely required — log out of the Magento admin and log back in. The module's menu does not appear until you do.

Step 4 — Configure the module inside Magento

Open the module's settings in your store admin. On Magento 2 they sit under Stores → Configuration, in the easySales section; on Magento 1 under System → Configuration, near the bottom.

Paste the token from the wizard's Configuration step into the Website Token field.

The Configuration step of the easySales wizard, showing where the module settings live inside Magento and the read-only website token with a copy-to-clipboard button.
The token to paste into Magento. Use the copy button rather than retyping it.
Setting What it does
Website Token Must match the token shown in the easySales wizard exactly. This is what authenticates every call between the two systems.
Store scope Which Magento store view's products and orders are exported. Defaults to the first one — set it deliberately if you run more than one.
Stock source Which Magento inventory source easySales reads quantities from.
Invoice Series The series passed to easySales with each order.
EAN / Brand / Warehouse location Which Magento product attribute holds each of these. Leave blank if you do not use them.
Weight and dimensions Which attributes hold weight and size, and in which units. Needed if your couriers price on volume.
What to fill in inside Magento

Save in Magento, then press Save in easySales. easySales calls your store to verify the token, and tells you what happened.

Step 5 — Confirm the connection

A connected store shows a card under Integrations → Websites with its platform, its token, the module version it reported, and an Active switch.

The Websites screen in easySales showing a connected Magento 2 store card with its URL, price VAT, website token, reported module version and an Active toggle, next to the Connect a Website card.
A connected store. The version in the corner is what your store reported, not what easySales assumed.

If the store did not answer, the save fails with a red Connection failed message rather than saving quietly. That almost always means one of three things: the token in Magento does not match the one in easySales, the module is not enabled, or the store is not reachable from the internet at the URL you entered.

What syncs, and how often

You do not schedule any of this, and there is no refresh-rate setting to configure.

What Direction How often
Orders Magento → easySales Every minute
Stock Magento → easySales Every 30 minutes
Prices Magento → easySales Every 30 minutes
Products Magento → easySales Every 6 hours
Categories and attributes Magento → easySales Every 6 hours
Order status, shipment, AWB easySales → Magento Every minute
Stock quantity easySales → Magento Every minute
How often each thing is checked

What flows back into Magento

Three things, and only three: order status (with shipment and AWB tracking once an order is Completed), stock quantity, and — on Magento 2 with a recent module — whole new orders.

Product names, descriptions, images, prices and categories are not written back. easySales reads them from Magento and does not overwrite them, so Magento stays the single place you edit your catalogue.

Keeping the connection healthy

Watch the module version. The card shows the version your store reported. When a newer one is released the card turns red with Update Required. On Magento 2 you install the new archive over the old one and re-run setup:upgrade; on Magento 1 you uninstall the old extension in Magento Connect Manager first, then install the new one. Settings survive either way.

Errors surface in one place. Products → Online Shops → Website errors lists everything that failed to save in either direction, with Retry and Dismiss on each row and bulk resend actions per store.

SKUs are the key, so keep them stable

easySales matches Magento products by SKU, and the match is permanent. Change a product's SKU in Magento and easySales imports it as a new product — the old one stays, with its offers attached.

If you need to find duplicates, use the Download button on Products → Online Shops → Products and check the export for repeated SKUs.

Frequently asked questions

Yes. Magento 1.7 – 1.9 is still offered in the version picker and its module is still downloadable, so an existing Magento 1 store can be connected today. It is the older path, though: Magento 1 does not get Order Submissions or invoice read-back, and its module changes far less often than the Magento 2 one. If you are planning a move to Magento 2, there is no integration reason to delay it.

Nothing. The wizard currently prints the command with a stray exclamation mark, as setup!:upgrade. The correct command is php bin/magento setup:upgrade. Type it rather than pasting from the screen.

Only about a day of history is fetched on the first connection, and a background job then backfills the previous four weeks over the following day. If your recent orders are older than that, they will not arrive on their own. Check also that the store answered the connection test — a red Connection failed message means the token or the URL is wrong.

No. Those three are locked once the website exists. Changing them means removing the connection and creating it again, which also breaks the link between your products and any marketplace offers built from them, so it is worth checking them before you save.

No. Names, descriptions, images, prices and categories are read from Magento and never written back. Only three things travel towards your store: order status with its shipment and AWB tracking, stock quantity, and — on Magento 2 with a recent module — newly created orders.

Repeated synchronisation failures disable a store automatically so a broken connection does not keep retrying. The stock, price, category and attribute jobs have low tolerances — a few consecutive failures is enough. The card greys out and offers a Restore connection button; fix the underlying cause first, then press it.

That is expected. SKU is the permanent match key, so a changed SKU reads as a new product and the old one remains with its offers. There is an Auto-archive superseded products preference that tidies the old one up once it has no stock and no active orders — it is switched off by default.

Up to 30 websites on one account. Each Magento store view you want treated separately counts as one.

Was this guide helpful?