Integration with Baselinker (base.com)
- View all variations as list
| CODE | Payment method | Price | ||
|---|---|---|---|---|
|
|
407
ss_baselinker
2026-11-13
1.1.5.9
|
1375.00 PLN
(Price without tax) |
||
|
|
589
ss_baselinker_sub_1Y
2026-11-13
1.1.5.9
|
550.00 PLN
/year
(Price without tax) |
||
|
|
588
ss_baselinker_sub_1M
2026-11-13
1.1.5.9
|
55.00 PLN
/month
(Price without tax) |
- — 12 months guarantee for all our add-ons
- — add-ons sold to entire world
- — stable, flexible, high-quality products
- — competitive prices, attractive discounts
- — quick and competent technical support
- — installation in 24 hours
- — personalized solutions - we'll write any add-on for you
Extension for Store Builder and Multi-Vendor that connects your store with BaseLinker (Base.com), so that the catalogue, stock, prices and orders from every sales channel are managed in one place. A store that sells on its own site and on marketplaces at the same time keeps the same goods and the same orders in two systems, and copying data between them by hand costs time and invites mistakes. Our add-on turns the store into a full data source for BaseLinker: the platform pulls products with variations, prices and stock, collects the orders placed in the store, and sends back stock and price changes, marketplace orders, statuses and tracking numbers with a tracking link. Synchronisation needs only a data exchange address and a password, with no API token and no cron jobs. An API token comes into play only with the optional API operations, which let the store tidy up the catalogue on the BaseLinker side.
See how it works
Key Features
- A connection through the BaseLinker integration file, protected by a communication password, with the catalogue, prices and stock served in pages of a thousand products, even for very large stores.
- A family of variations keeps its ID in BaseLinker even when the store changes its main product, so offers and stock never lose their links.
- Marketplace orders created in the store with the right status and without duplicates, while tracking numbers, statuses and stock return from BaseLinker to the store.
- A pickup point map at the delivery step, with the chosen point passed to BaseLinker and shown on the order.
- Optional API operations: deleting products from the BaseLinker catalogue in a queue, with confirmation before deletion and within the request limit.
- In Multi-Vendor, a separate BaseLinker account for every vendor, operator consent for data exchange and locking of chosen settings.
First, the direction of the connection, because everything else depends on it. BaseLinker connects to the store, not the other way round: it pulls the catalogue, prices, stock and orders, then sends back whatever has changed on its side. In everyday synchronisation the store never sends anything on its own, which is why it needs neither an API token nor a task schedule for it:

Screenshot 1
Setup begins in the General section. Here you set the communication password and copy the data exchange file address with a single button, then paste both values into the BaseLinker panel. Next to them you will find a link for registering a BaseLinker account and a weight converter, useful when the store measures weight in a different unit than the platform:

Screenshot 2
Only what you choose reaches the marketplaces. You select the statuses of exported products, for example active and hidden, the way variations are passed on, the promotional price for products on promotion, and the language and currency of the offer. Separate switches decide whether BaseLinker receives names and descriptions written especially for it:

Screenshot 3
Marketplaces and warehouse software expect correct codes. EAN, SKU and brand can come from the product code or from chosen features, and when the catalogue calls for it, you build the SKU from several features using your own pattern, with a separate rule for variations:

Screenshot 4
The store decides when an order is ready for BaseLinker. You choose the order statuses to send, the statuses that mean paid and the cash on delivery payments, while an order discount travels as a separate line with its own SKU and EAN, clear for accounting and invoicing software:

Screenshot 5
Marketplace orders arrive in the store as regular orders, with a default shipping and payment method, and paid ones receive the chosen status straight away. Three separate switches decide whether the customer, the orders department and the vendor are emailed about such an order. This matters when the marketplace notifies the buyer itself and a second message from the store would only confuse them:

Screenshot 6
The catalogue can also flow the other way. Products created in BaseLinker arrive in the store with a set status, tax rate, category and EAN, and when importing features you decide whether to add only features that already exist in the store and whether a re-import keeps the current values:

Screenshot 7
Invoice details need no manual completion. You point to the customer profile fields where the store keeps the tax ID, the company name and the invoice request, and the add-on carries them into the right fields of the BaseLinker order:

Screenshot 8
The API section opens a second, optional direction of communication. The integration file lets BaseLinker read and write store data, but it gives the store no way to remove anything on the BaseLinker side, and this is exactly what API operations are for. They are disabled by default, and until you tick Enable API operations the add-on sends not a single request to BaseLinker. Next to it you enter the API token and the limit of requests per minute, 100 by default, which is what BaseLinker allows; once the limit is reached, the operation waits for a minute. Below is a ready crontab line that keeps the queue running in the background, with a hint for stores running behind Cloudflare:

Screenshot 9
A marketplace listing often needs a different title than the product page in the store. In the product's Baselinker tab you enter a separate name and description that only BaseLinker receives, while the content your store customers see stays unchanged:

Screenshot 10
The pickup point map is enabled for a chosen shipping method. You tick the carriers whose points should appear, such as InPost, DPD, Pocztex or ORLEN Paczka, and the type of points. A separate field holds the Furgonetka map API key, without which the map shows no points:

Screenshot 11
This is what the buyer sees. With delivery to a pickup point, the Select point button opens the Furgonetka map at checkout, centred on the customer's address. The filters show only the carriers chosen in the shipping settings, and the list beside the map suggests the nearest points:

Screenshot 12
Once a point is clicked, the map closes and its number, name and address appear under the shipping method. Choosing a point is required, so no order reaches the store without a pickup location:

Screenshot 13
The order details show the number under which the order is known in BaseLinker and the point chosen by the customer: its name with address, point code, type and country. The same point reaches BaseLinker, so the label is issued for the right parcel locker from the start:

Screenshot 14
When a shipment is created in BaseLinker, its number comes back to the store. The add-on creates a shipment on the order with the tracking number and records the carrier service name and the parcel tracking link in its comment, so the store team does not have to look for this information in another system:

Screenshot 15
Stores with several warehouses decide where the stock for BaseLinker comes from. For each location you choose the storefronts for which the warehouse is included in synchronisation, and you mark the warehouse that receives the stock sent back by BaseLinker:

Screenshot 16
In Multi-Vendor every vendor can connect their own BaseLinker account. In the vendor profile the operator grants consent for data exchange, and the vendor receives their own communication password and their own data exchange address, under which BaseLinker sees only that vendor's products and orders:

Screenshot 17
A vendor who wants to use API operations saves their own token in the profile, in the Baselinker token field at the end of the integration settings. The panel shows it only in masked form. Operations performed for the vendor use this token alone, never the store owner's token, so every vendor tidies up only their own catalogue in BaseLinker:

Screenshot 18
BaseLinker access can also become part of what you offer vendors. Tick it in a chosen plan and every vendor on that plan receives it, with no need to grant consent in each profile separately:

Screenshot 19
The operator keeps control over what vendors may change. On the restrictions list they lock chosen integration settings for all vendors or for a single one, for example the currency of exported products or the payment method assigned to BaseLinker orders:

Screenshot 20
The same list lets the operator decide on access to the BaseLinker API. A rule with API as the locked field closes the whole section, token field included, either for all vendors or for one vendor chosen from the list. Consent for data exchange is granted and withdrawn by the administrator alone, and the server enforces this even when someone tries to bypass the form:

Screenshot 21
This is the vendor's point of view. In their own panel the vendor copies their data exchange address and configures the integration, but no longer sees the fields locked by the operator, nor the access consent itself:

Screenshot 22
Data beyond the standard fields can reach BaseLinker too. You choose a BaseLinker order field, for example the comments, and compose its content from order field tags, such as the delivery phone number. The table below the form lists the available tags:

Screenshot 23
Custom product data travels the same way. You point to a column in the store database, for example the return period, and to the extra product field in BaseLinker where it should go:

Screenshot 24
The testing dashboard shows what the store will answer BaseLinker before the first synchronisation starts. You choose a storefront, a vendor and a method, and the test result explains how the add-on recognised the context of the request. The test runs on the store side, without any call to BaseLinker:

Screenshot 25
API operations have a page of their own. You choose the storefront and the vendor the operation is meant for, and the add-on shows the masked token it will use. Deletion covers either the whole catalogue fetched from BaseLinker or a pasted list of product IDs. The Prepare the list to delete button only collects the items and removes nothing yet, while the task table below shows the stage and progress of every operation:

Screenshot 26
Before anything disappears, the task stops and waits for confirmation. You see how many products are to be deleted and a sample of the first items with their BaseLinker ID, code and name, while a highlighted box reminds you that the products will go together with their variations and that BaseLinker has no trash, so the operation cannot be undone. Deletion starts only after you click the confirmation button, and the browser asks once more whether you are sure:

Screenshot 27
Once confirmed, the task works through the queue and shows how many products have been deleted so far and how many operations failed. The red ERROR_MAX_QUERIES_LIMIT message is not a failure. It is the answer BaseLinker gives once the request limit is used up, and the add-on responds with a deliberate pause: the task waits the indicated number of seconds and then resumes where it stopped. The queue is processed by a scheduled task on the server or, when the store has no cron, by an open panel tab with the Process in this tab button. The Cancel task button stops the operation at any moment:

Screenshot 28
Families of variations need protection of their own. BaseLinker recognises a family by the ID of the main product it saw on the first import, yet CS-Cart can switch the main product by itself, for instance when the current main variation sells out. The add-on remembers a key for every family and always sends the family under it, while the new main product reaches BaseLinker as an ordinary variation under its own ID. Offers, stock and prices of the family therefore keep updating, without manual product linking and without import errors:

Screenshot 29
Mismatches that arose before the add-on was updated are fixed on the Variation family keys page. The counters show how many keys were saved on the first synchronisation, how many were added later and how many were set by hand. Paste the IDs of the products BaseLinker cannot find and click Set as family keys. The result table confirms which family each product belongs to and which previous keys were removed, and the next synchronisation sends the family under the chosen ID, with no change to the products themselves:

Screenshot 30
In Store Builder the integration settings are saved separately for each storefront, and the data exchange address carries the storefront identifier. Each storefront can therefore connect to its own BaseLinker account and serve its own catalogue:

Screenshot 31
Configuration on the BaseLinker side
The other half of the connection is set up in the BaseLinker panel. A store connected through the add-on appears on the integrations list as a Multi-Vendor/CS-Cart shop, and this is where you open its settings:

Screenshot 32
In the Connection tab you paste the communication password and the data exchange file address copied from the store. The connection test button confirms at once that BaseLinker reaches the store:

Screenshot 33
The Products tab defines how BaseLinker uses the store's offer. You set the product link pattern, the name and description filters, and the import into the Base.com catalogue:

Screenshot 34
In the Stock tab you choose which system is the master, the target warehouse and the synchronisation frequency. When Base.com is the master, stock goes to the store warehouse marked earlier as the one receiving stock from BaseLinker:

Screenshot 35
Prices follow the same principles: synchronisation direction, price group, rounding and update frequency:

Screenshot 36
The Orders tab controls the exchange of orders in both directions. You decide how often BaseLinker downloads orders from the store, which status they receive and whether marketplace orders should be added to the store:

Screenshot 37
The BaseLinker Integration add-on brings order to multichannel selling: stock, prices and orders stay consistent between the store and BaseLinker, and orders from every channel are handled in one tool. In Store Builder each storefront has its own configuration, and in Multi-Vendor each vendor runs their own integration while the operator decides on access and on the range of available settings. Families of variations keep their IDs in BaseLinker, and when the BaseLinker catalogue needs tidying up, the API operations handle it with confirmation and within the request limit.
Full walkthrough: Store Builder, 7 minutes
Full walkthrough: Multi-Vendor, 7 minutes
Feel free to contact us and purchase the add-on!
Choose the most convenient form of payment for the add-on. You can pay once and use the add-on. Choosing a subscription payment (monthly or annual) means that you pay for the add-on at regular intervals and have access to the latest versions of the addon and technical support.
- Store Bulider
- Multi-Vendor
- 4.21.x
- 4.20.x
- 4.18.x
- 4.17.x
- 4.16.x
- 4.15.x
- 4.14.x
- 4.13.x
- 4.12.x
- 4.11.x
- 4.10.x
- 4.9.x
- 4.8.x
- 4.7.x
- 4.6.x
- 4.5.x
- 4.4.x
- 4.3.x
- 4.2.x
- 4.1.x
- 4.0.x




