Sales hub

BaseLinker integration
for Medusa

Medusa and BaseLinker both ways: product cards, stock and prices, store orders sent exactly once, and orders from Allegro, Amazon and other channels imported into Medusa.

See it in the demo admin
BaseLinker: The integration page in the Medusa admin, demo mode with sample data.
The integration page in the Medusa admin, demo mode with sample data.

What exactly
this integration does

  • Cards linked by SKU and EAN

    Cards of the BaseLinker catalog link to variants by SKU, then by EAN. Duplicates show up at once and nobody guesses them.

  • The catalog where you keep it

    Keep the catalog in Medusa and missing cards are created in BaseLinker. Or keep it in BaseLinker and the products come into Medusa.

  • Stock and prices in your direction

    The BaseLinker warehouse feeds Medusa, or Medusa feeds a BaseLinker warehouse. Prices go to a price group. Everything planned first.

  • Store orders exactly once

    A Medusa order reaches BaseLinker once, with lines, address, invoice data and cash on delivery. Every send is preceded by a lookup.

  • Marketplace orders

    Orders from Allegro, Amazon, eBay or Erli, from the sources you pick, come into Medusa as regular orders, each one once.

  • Statuses, parcels and returns

    Status, parcel number and tracking link come back to the order, returns from the return manager show on the order, and the Fakturownia invoice number lands in the BaseLinker order.

How it guards
your data

  • Seven writes, all off

    Catalog import, cards, stock both ways, prices, order import and invoice numbers ship off. A person turns them on, in the options and in the admin.

  • A barrier on API methods

    Reads always pass, and every writing method passes only with the permit of its writer. Nothing gets written by accident.

  • Quarantine and retries

    An item that fails three runs in a row waits for a person. Only transient errors are retried, with growing pauses.

Setup
in three steps

The full list of options, events and API routes is in the package README on GitHub.

Paste it into Claude Code, Cursor or another AI assistant in your Medusa project: it installs and configures the integration, with writes off.

  1. 1
    Install the package from npm.
    npm install @koda-plus/medusa-plugin-baselinker
  2. 2
    Add the plugin to medusa-config.ts.
                            plugins: [
      {
        resolve: "@koda-plus/medusa-plugin-baselinker",
        options: {
          apiToken: process.env.BASELINKER_API_TOKEN,
          inventoryId: process.env.BASELINKER_INVENTORY_ID,
          warehouseId: process.env.BASELINKER_WAREHOUSE_ID, // bl_12345
          orderStatusId: process.env.BASELINKER_ORDER_STATUS_ID,
          // stockSource: "baselinker", // or "medusa"
          // orderImportSources: ["allegro", "amazon:7245"],
          // demo: true,
        },
      },
    ]
                          
  3. 3
    Run the migrations and open the integration in the Medusa admin.
    npx medusa db:migrate

Running for our clients

See our portfolio
  • soon
Free 15-minute call

Tell us about your project,
we'll tailor the rest to you

A 15-minute call is enough for us to know whether we are a fit for your project.
We start from what you need, not from an off-the-shelf solution.

See our demo

Contact us

Remigiusz in a navy shirt and glasses
I use iMessage I use WhatsApp
Adrian in a grey turtleneck and glasses
I use iMessage I use WhatsApp