How to connect Gomag with easySales: a complete integration guide

Connect your Gomag store with easySales in three steps — activate the easySales app inside your Gomag admin, set up the website in easySales, and paste the generated token back into Gomag. Centralize orders, sync stock, and re-list the same products on every marketplace you sell on.

Why connect Gomag with easySales

Sell on Gomag and want one place to manage orders, generate invoices, push AWBs to couriers, and re-list the same products as offers on eMAG, Altex, Allegro, or any other marketplace? easySales handles all of it.

Once connected, easySales pulls products and variants from your Gomag store and centralizes incoming orders. From there, you generate invoices, create AWBs with any supported courier, and turn the same catalog into marketplace offers. Order status changes you make in easySales push back to Gomag through a mapping you define, and stock changes propagate to Gomag continuously.

The setup takes three steps: activate the easySales app inside Gomag, fill in the website form in easySales, and paste the token back into Gomag to complete the connection.

Interactive tour

Don't feel like reading? Take the interactive tour.

Interactive walkthrough — connect Gomag with easySales

Prerequisites — what to prepare before you start

Get your Gomag catalog ready before you start. A few requirements prevent products from being skipped at import time.

Unique SKU per product

Two products with the same SKU collide — only one is imported. Audit and de-duplicate before connecting.

Gomag admin access

You need admin permissions to activate the easySales app and paste the website token in Gomag.

Clear catalog data

Products without a name, price, or stock value are skipped at import. Fill them in before connecting.

A few things worth knowing upfront:

  • Each product must have a unique SKU. If two products share the same SKU, only one is imported.
  • easySales tracks products by SKU. Renaming a SKU in Gomag creates a fresh product in easySales — to find duplicates, use the export button in Online Shops → Products.
  • You need admin access to your Gomag store to activate the easySales app and paste credentials.

Step 1 — Activate the easySales app in Gomag

easySales connects to Gomag through a first-party app already published in the Gomag App Store. Nothing to install — you only activate it.

1.1 Open the easySales app

In your Gomag admin, open Apps → Sales Channels → easySales.

Gomag admin Apps section showing the Sales Channels group with the easySales tile
In Gomag admin, open Apps → Sales Channels and click the easySales tile.

1.2 Activate the app

Click the activation button. Gomag opens the app's settings panel with an empty Website token field. Leave this tab open — you'll come back to it in Step 3 after generating the token in easySales.

Step 2 — Connect Gomag in easySales

In your easySales account, go to Integrations → Online Shops → Connect Website and fill in the form. The fields below explain what to enter and which choices apply to most Gomag sellers.

Website name and URL

  • Website name — a label you choose. It's only visible inside easySales.
  • Website URL — your Gomag storefront, exactly as it appears in your browser address bar. Pick http or https to match your store, and add www only if your domain redirects to it.
easySales Integrations page with Gomag selected as the platform and the generated website token shown in the Configuration step
In easySales, select Gomag as the platform — the website token is generated for you and shown on the Configuration step.

VAT and VAT for shipping

If you're a VAT payer, enter the rate that applies to your products and a separate rate for shipping (e.g. 21 for the standard Romanian rate). Leave blank if you're not a VAT payer.

Language and currency

Pick the storefront language and currency. These act as defaults for products imported from this store and as a fallback when an incoming Gomag order doesn't carry an explicit currency. They never override individual orders — each order keeps the currency Gomag reported.

Product stock source

The most important decision on the form. It tells easySales where the authoritative stock value lives:

  • Website — Gomag is the source of truth. easySales reads stock from Gomag and never overwrites it.
  • easySales — easySales is the source of truth. Stock changes inside easySales (sales, manual edits, marketplace deductions) are pushed to Gomag.
  • Connected integration — your stock lives in a third-party system already wired to easySales (billing software like SmartBill, Oblio, or FacturisOnline; an ERP such as NexusERP or Sedona; a fulfilment partner like Fulfillro or Huboxx). easySales reads stock from that integration and pushes it to Gomag. Connect the integration and declare its warehouse first — you can't pick this option otherwise.

Running a multi-warehouse operation? Switch the form to Advanced warehouse mode. Instead of binding the store to one stock source, you pick one or more easySales warehouses and define how their stock is aggregated, prioritized, or split per channel.

Default package type

Used at AWB generation when the order doesn't specify a package. Pick the type that matches most of your orders.

Sync products status

Decide whether existing products in easySales should be marked as active in Gomag once the connection is saved. Most sellers leave this No for the first connection and switch it on later, after auditing the catalog inside easySales.

Platform

Select Gomag from the platform list. easySales doesn't need any other credential at this stage — it generates the website token for you once you save.

Click Save. easySales creates the website, generates the website token, and shows it on the Configuration tab.

Step 3 — Paste the easySales token back in Gomag

Copy the website token from easySales. Go back to the Gomag tab you left open in Step 1 (Gomag Apps → Sales Channels → easySales) and paste the token into the Website token field. Save.

Gomag easySales app settings panel with the Website token field filled in and the Save button visible
Paste the website token from easySales into the easySales app settings in Gomag, then save.

The connection is now live. easySales begins the initial import — your product catalog and recent orders start flowing in within minutes.

What happens automatically after you connect

easySales handles live sync and the initial import for you.

  1. Live sync covers orders, products, and stock. New Gomag orders reach easySales within seconds. Product and stock changes follow the same path.
  2. Your product catalog is imported — products and variants appear in Online Shops → Products, where you can browse, edit, and turn them into offers for marketplaces.
  3. Incoming Gomag orders appear in your Orders screen, where you generate invoices, AWBs, and run automation flows.
  4. Stock syncs according to the source you picked. If you chose easySales, stock pushes run continuously and your Gomag storefront reflects centralized inventory.
From Gomag → easySales From easySales → Gomag
Orders (create, update, cancel, paid) Stock updates
Products and variants Order status changes (per your mapping)
Stock levels Product field updates (unless Block product updates is on)
Product prices
Categories
Customer details and addresses
Bilateral sync covers orders inbound and stock + status outbound.

Fine-tuning your Gomag connection

Open the Gomag website's Preferences tab to adjust how easySales handles your store.

easySales Preferences tab for the Gomag website, grouped into Gomag Settings, Order Behavior, and Synchronization sections
Preferences for a Gomag website — Gomag Settings, Order Behavior, and Synchronization.

Fetch variant options as product properties

Turn this on if your Gomag products use variant options (size, colour, material) that you want to import as easySales product properties. Without it, variants come in as separate SKUs without their option labels.

Order status mapping

Map each Gomag order status to its easySales equivalent. This is the bridge that decides what easySales does when a Gomag order moves from one status to another, and what status update easySales pushes back to Gomag when you change an order locally. Map every status you actively use — unmapped statuses are ignored.

Block product updates

Turn this on if you manage your catalog primarily in Gomag and want easySales to stop pushing product changes back. Stock pushes are unaffected — only catalog fields (name, description, price) stop flowing from easySales to Gomag.

Default discount tax rate

Gomag doesn't always report a VAT percentage on discount lines. Set a fallback rate here (e.g. 21) and easySales applies it to every imported discount, so order totals match what Gomag shows.

Click Save at the bottom of the page to apply your changes.

You're connected — what's next

Once orders start arriving, the next steps are about automation. Set up flows to auto-generate invoices, auto-create AWBs, and auto-send tracking notifications. If you also sell on marketplaces (eMAG, Altex, Allegro, Trendyol, and others), turn your Gomag catalog into offers and let easySales push them out.

No card required
14 days free
You can cancel anytime

Connect your Gomag store in minutes

Try easySales free for 14 days. No credit card and no module to install.

Frequently asked questions

The most common cause is the Product stock source you picked at connection time. If you chose Website, Gomag is the master and easySales reads its values — any edit you make inside easySales won't be pushed. If you chose easySales, the master is easySales and the value in Gomag should match — if it doesn't, check Online Shops → Errors for failed stock pushes (usually a missing SKU on the Gomag side). For multi-warehouse setups, also confirm the warehouse priority you defined in Advanced warehouse mode.

Products without a unique SKU, without a name, or without a price are skipped at import. So are products marked inactive in Gomag at the time of fetch. Open Online Shops → Errors in easySales — the import logs every skipped product with the exact reason. Fix the field on the Gomag side and trigger a fresh fetch from the website's Configuration tab.

Open the Gomag website's Preferences tab in easySales and use the Order status mapping section. Each row pairs a Gomag status with an easySales status. The mapping runs in both directions: when a Gomag order moves to a mapped status, easySales applies the matching local status; when you change the easySales status, the corresponding Gomag status is pushed back. Map every status you actively use — unmapped statuses are ignored by the sync.

easySales fetches roughly the last 6 hours of orders by default once the connection is live. That's enough to catch in-flight orders during the switchover. If you need a deeper backfill — a few days, a week, or a full month — contact support with the website ID and the date range, and we'll trigger an extended fetch on your behalf.

Turn on Block product updates in the Gomag website's Preferences tab. From that point, easySales stops pushing product field changes (name, description, price) to Gomag. Stock pushes keep running — Block product updates only affects catalog fields. Use this when Gomag is your catalog master and easySales is there for orders, invoices, and AWBs.

The usual culprit is the VAT applied to discount lines. Gomag doesn't always report a VAT percentage on a discount, so easySales falls back to whatever you set under Default discount tax rate in the Gomag website's Preferences tab. If the fallback doesn't match your Gomag tax setup, totals drift by a few cents. Set the rate that matches your products (e.g. 21% in Romania) and re-import the affected orders.

First, confirm the website URL you entered matches the storefront URL exactly — the scheme (http vs https) and the www prefix have to match. Next, make sure you activated the easySales app inside Gomag and pasted the website token back. If both are correct and the error persists, regenerate the token from the website's Configuration tab in easySales, paste the new value into Gomag, and save again. If it still fails, contact support with the website ID — we have logs that pinpoint which side rejected the connection.

Was this guide helpful?