Skip to content

Installation and setup

  • CS-Cart and Multi-Vendor 4.17.2 or later (4.21.x supported).
  • Administrator access to the store’s admin panel.
  • An Allegro seller account and your own Allegro application (client ID and client secret) registered in the Allegro developer console (apps.developer.allegro.pl; the sandbox has its own console and its own accounts).
  • In the Allegro seller settings: a delivery price list, a return policy and an implied warranty (their IDs are entered on the Connection page; offers cannot be published without them).
  • Products with a valid EAN (GTIN) as the barcode and images that are reachable from the internet (Allegro downloads them).
  • A public https address for your store if you use the browser sign-in (the redirect address must be registered with your application).
  • A cron job on your server (see step 6).
  1. Download the kv_allegro-<version>.zip package from your Kavio Labs or CS-Cart Marketplace account.
  2. In the admin panel, open Add-ons > Manage add-ons.
  3. Click the gear button and choose Manual installation, then upload the archive.
  4. Find Allegro Marketplace Connector in the list and make sure its status is Active.
  5. Enter your license key under Settings > License (Kavio Labs downloads) and click Check now.
  1. In the Allegro developer console register an application. For the device code sign-in choose an application type that allows the device flow; for the browser sign-in register the redirect address shown on the Connection page. Copy the client ID and client secret.
  2. Open Orders > Allegro channel and the Connection tab. Enter the client ID and client secret for the mode you want (Test = sandbox, Live = allegro.pl), choose the marketplace, enter the delivery price list ID, return policy ID, implied warranty ID, your city and post code. Save.
  3. Press Connect to Allegro. Allegro shows a code: open the shown address, sign in as the seller and enter the code, then press I have entered the code. (The Connect with browser sign-in button does the same with a redirect.) The add-on stores the tokens encrypted and tests the connection at once: the green message names the authorized Allegro user.
  4. Switch to Live mode only after the whole flow worked in the sandbox.
  5. Set up categories, parameters and rules (see Usage).
  6. Add the cron job from the settings page (Cron section), every minute is fine. Overlapping runs are prevented.

The Allegro sandbox is a separate site (allegro.pl.allegrosandbox.pl) with separate accounts, applications and data: register in the sandbox, create a sandbox application at apps.developer.allegro.pl.allegrosandbox.pl and a seller account there, and create the delivery price list, return policy and implied warranty in the sandbox. Sandbox data is not copied to production.

By default the marketplace owner connects one Allegro account for all vendors (Marketplace owner mode on). Switch it off to let each vendor connect their own Allegro application and account in the vendor panel (Connection tab); each vendor then maps, lists and ships on their own.

  1. Upload the new package the same way. Your settings, credentials, authorization and data are kept.
  2. The add-on adds missing tables and settings by itself on the first request after the update.

See CHANGELOG for what changed in each version.

Open Add-ons > Manage add-ons, click the add-on’s gear button and choose Uninstall. This removes the add-on’s settings, language variables and database tables, including the stored credentials, tokens and mappings. Offers already on Allegro stay there.