VulCode

Marketplace integration: Erli, Empik, Amazon, Temu

Every marketplace has its own API, rules and pitfalls. We connect them to your store and warehouse directly or through a multichannel tool, so there is one stock level and orders land in one place.

Multichannel selling
An integration panel: one stock level of a thermal bottle in the store, on Allegro, Erli in Poland and Germany, on Amazon and Empik, with a buffer for slower channels and the log of stock changes, an Erli cancellation among them

Four marketplaces from the integration side

Each one connects differently, so for each we pick the surest route: directly via API or through an integrator.

CriterionErliEmpikAmazonTemu
A seller API of its ownErliyesYes, a key from the shop panelEmpikper arrangementPer arrangement with EmpikAmazonyesSelling Partner APITemuper arrangementPer Temu's partner programme
Via e-commerce systems and integratorsErliyese.g. SellasistEmpikyese.g. Magento, IdoSell, xSaleAmazonyese.g. Sellasist or BaseLinkerTemuyese.g. Sellasist
How the integration gets accessErliyesAn API key from the shop panelEmpikper arrangementDepends on the routeAmazonyesRegistering the integration and the seller's consentTemuper arrangementDepends on the route
Our most common routeErliDirectly via APIProducts by your own identifier, changes in batches, and orders with their changes in one event inbox.EmpikThrough an integratorEmpik works with e-commerce systems, and products can also be added in the Seller Panel.AmazonDirectly or through an integratorEach Amazon market has its own listings and prices, and we track request limits per operation.TemuThrough Sellasist or another integratorSellasist has a ready link with Temu, Amazon and Erli.

Erli: orders through the event inbox

Erli collects new orders and their changes in one place, the inbox.

The way of an Erli order

  1. Customer on Erlipurchase and payment
  2. Erli inboxorderorder events
  3. Integrationevents fetchedfetches, acknowledges, storesPaid: fulfilCancelled: stock does not return by itself
  4. Your warehousepaidfulfilment and shipping
  5. Erliorder updatestatus and tracking number
An integration panel: the Erli inbox with the API key, the pl and de markets, the request limit, the log of fetches and acknowledgements, and a cancelled order whose stock the integration restored

  • One event inbox

    The integration fetches new messages, acknowledges them and stores the order. The integration reads every order from it, so none goes missing.

  • The stock trap

    Erli lowers stock automatically on order but does not restore it on cancellation. The integration has to do it.

  • Two markets

    A shop can sell in the Polish and German markets. The integration names the market with every change, so translations and prices land where they belong.

Each one's pitfalls

Details that break integrations when someone treats every marketplace the same. We handle each one its own way.

  1. requests
    Erli's load grows
    Erli turns the excess away
    the queue slows down

    Erli: the limit moves with load

    The request limit varies with the service load, and Erli turns excess requests away. A queue that slows down by itself when Erli turns requests away, so no change is lost.

  2. A basket on Erli
    method 1a separate order
    method 2a separate order
    at your endone packing, if you prefer

    Erli: one basket, several orders

    Several delivery methods in one basket create separate orders. We group them in your system by buyer and time if you prefer to pack that way.

    1. Parcel lockers
    2. DPD Pickup
    3. courier
    4. Empik stores

    Empik: delivery is on your side

    The seller handles delivery, with several methods to choose from. We map Empik's methods to your couriers and pickup points.

  4. Every operationits own request limita steady pace and room for a short burst
    one counter for everything

    Amazon: a limit per operation

    Each operation has its own request limit, and the app's credentials must be replaced regularly. A separate counter for each operation and a credential replacement reminder in the panel.

  5. Your system
    • Sellasist, a ready link with Temu
    • The Temu API, per the partner programme

    Temu: access through the partner programme

    Integration access depends on the partner programme. We usually connect Temu through a multichannel tool that already has the link.

A route matched to the number of channels

We match the route to how many marketplaces you run: with one main channel we connect it directly, with several through a multichannel tool, and often we combine both.

one main oneHow many marketplaces you run at oncethree or more
another channel beside the main one
three marketplaces

Directly via API

one main channel

One marketplace drives a large share of sales. The integration should be part of your system, not one more service.

Verdict

An integration with the marketplace API in your code, with its limits and pitfalls handled directly.

Each channel its own way

some through a middleman

Amazon goes into BaseLinker, which already handles Allegro. Erli connects directly to cover two markets and the inbox.

Verdict

Some channels through a middleman, some directly, with orders and stock in one place.

Through a multichannel tool

three or more

You want one panel for orders, labels and messages. The marketplace gives you no direct API.

Verdict

BaseLinker, Apilo or Sellasist as the hub, with your system connected to it through one API.

How many marketplaces you run at once

one main one

Directly via API, one main channel

One marketplace drives a large share of sales. The integration should be part of your system, not one more service.

Verdict

An integration with the marketplace API in your code, with its limits and pitfalls handled directly.

another channel beside the main one

Each channel its own way, some through a middleman

Amazon goes into BaseLinker, which already handles Allegro. Erli connects directly to cover two markets and the inbox.

Verdict

Some channels through a middleman, some directly, with orders and stock in one place.

three marketplaces

Through a multichannel tool, three or more

You want one panel for orders, labels and messages. The marketplace gives you no direct API.

Verdict

BaseLinker, Apilo or Sellasist as the hub, with your system connected to it through one API.

three or more

Delivery from marketplaces

On Empik and Erli delivery is the seller's job, and methods must map to your couriers.

An integration panel: Empik's delivery methods assigned to the store's couriers and pickup points, Erli orders to pack, one basket with two delivery methods among them, and the statuses with tracking numbers sent back to the channels

  1. Empik's methods on your couriers

    We assign every Empik delivery method to your courier or pickup point. Delivery to Empik stores is checked for your account.

    On EmpikAt your end
    • Parcel lockersa locker, the point from the order
    • DPD Pickupthe DPD Pickup point from the order
    • courieryour courier, the address from the order
    • Empik storesper arrangement with Empik

  2. One basket, two orders

    Parcels from one basket can be packed together, and each order still gets its own label and tracking number for Erli.

    One basket on Erli
    order, method 1order, method 2
    one packing, each parcel with its own label

  3. The status and tracking number go back to the channel

    Once the parcel is dispatched, the integration sends the status and tracking number to the marketplace: to Erli directly, to Empik through the integrator.

Common questions about marketplaces

Marketplaces, stock, cancellations, delivery and orders

Which marketplaces do you want to sell on?

Tell us where you sell today and where you want to start. We will reply within an hour with an integration route and a quote.