Can you handle several Allegro accounts?

Yes. Each account is authorised separately, and orders arrive in one place in your system.

What if Allegro changes its API?

Allegro announces changes in advance. Under maintenance we adapt the integration before the old version is switched off.

Can we test without real orders?

Yes. Allegro has a separate test environment that works like the real service, with the same limits. We link a test account there and check the whole route of an order before the first real sale. We create the test listings automatically, as Allegro clears them every quarter.

Will the integration hold at peak sales?

Yes. Allegro allows one app 9000 requests a minute, shared by every linked account. A queue spreads the requests over time, and if the limit is ever exceeded we pause it instead of retrying at once, so no order is lost.

How much does an integration cost?

Integrations are quoted individually, under our API and integrations service. The figure depends on how many systems we connect, which data flows where and what should happen on an error. We give it after a short call, and the quote is free and comes back within an hour.

Will the integration code be mine?

Yes. Once the work is accepted and paid in full, the economic copyright in the code passes to you and you get the repository with run instructions. Open source libraries keep their own licences.

How do you check an integration before launch?

On the provider's test environment or on a copy of your system. We run real scenarios, including errors, cancellations and returns, and only then switch the integration on in production.

Allegro integration through the REST API

Allegro orders reach your store, wholesale system or ERP on their own, and stock and prices go back to Allegro before anyone buys something you no longer have.

Multichannel selling

An integration panel: Allegro order events fetched from the cursor, a repeated READY_FOR_PROCESSING, an out-of-order event and BUYER_CANCELLED during fulfilment with the state from the checkout form

A warehouse phone: an Allegro order cancelled during packing with a "Do not pack" notice and the shelf to put the goods back on, the orders to pack under it

Directly or through BaseLinker

We pick the route to fit how you sell: with several channels we connect through BaseLinker, and when Allegro is your main channel, directly. We run both from the data map to maintenance.

Your system
BaseLinker
Allegro and other channels

Through BaseLinker

Pick it when

Sales channels

You sell on several channels at once: Allegro, a store, other marketplaces.

What your sales run on

BaseLinker already handles your orders, labels and documents.

Features and control

What an intermediary offers is enough.

What we build

We connect your system to BaseLinker, and BaseLinker to Allegro. Less code, one place for every channel.

BaseLinker integration

Your system
The Allegro API

Directly through the Allegro API

Pick it when

Sales channels

Allegro is your main or only marketplace.

What your sales run on

The integration is part of your own system: a wholesale tool, ERP or platform.

Features and control

You need features an intermediary does not offer, or full control over events.

What we build

An app registered with Allegro, authorised by the seller, handling events and limits.

How a seller links their Allegro account to the app

The seller signs in on the Allegro site, and your app never sees their password.

How long each lasts

One-time code10 s
Access to the account12 h
Authorisation without a refresh3 months

Each mark is many times longer than the last, so 10 seconds and 3 months fit on one axis.

The password stays with Allegro
The seller signs in and consents on the Allegro site, not in your app. Only a one-time code comes back to the app, valid for 10 seconds.
Access for 12 hours
Access for 12 hours, refresh for up to 3 months. The refresh key works only once, so we store the new one at once.
After three months without a refresh
Authorisation expires and the seller must reconnect. Your panel warns about it in advance.

An integration panel: three Allegro accounts with the access token's validity, the single-use refresh token and the authorisation term, a warning about an expiring authorisation, the steps of linking an account through OAuth 2.0 and the Client ID request limit

Allegro order events

Allegro describes an order with a series of events. We start fulfilment only once the order is ready for processing.

Bought
The buyer bought but has not paid. We reserve stock, we do not ship.
Delivery details filled in
The buyer filled in the delivery form. It can repeat, e.g. after a failed payment.
Ready for processing
Paid, or cash on delivery. Only now is the final delivery address visible and fulfilment starts.
Sent
Your system updates the fulfilment status in Allegro and adds the tracking number.

Ready for processing: buyer cancellation
Cancelled by the buyer
The buyer can cancel before paying or after, so we stop fulfilment if it is running.
Delivery details filled in: no payment
Cancelled by Allegro
Allegro cancelled the order automatically. We release the reserved stock.

Allegro limits at peak sales

Allegro documents its limits openly. The integration has to fit within them at peak too.

Requests of the app per minute

One counter for the app, shared by every linked seller account.

09000

within the limitrefusal and the app blocked for a minute

Events in one fetch per request

Allegro hands over at most 1000 events at once, and we fetch the next batch from the last saved event.

01000

one batchthe next batch from the last event

How we keep the integration within the limit

A queue

A queue spreads requests over time instead of in waves.

keeps clear of the limit

Additional limits

Lower, for selected resources and per user. We check the description of every resource we use.

lowers the threshold for a resource

After going over the limit

Refusal and the app blocked for a minute. We pause the queue instead of retrying at once.

keeps clear of the block

An Allegro order in your system

The key checkout form fields and where they land.

Allegro

What we keep an eye on

Your system

Allegroorder number
→it identifies the order, so it is never saved twice
Your systemexternal order number
Allegroorder state
→fulfilment starts only once the order is ready
Your systempayment status
Allegroline items and offers
→offer linked to a product by SKU
Your systemorder lines
Allegrodelivery and pickup point
→final only once the order is ready
Your systemaddress and shipping method
Allegroinvoice details
→company tax number when the buyer wants an invoice
Your systemthe invoice buyer
Allegrofulfilment status
←goes back to Allegro after packing and dispatch
Your systemfulfilment status

Data	Direction	When
Listings	Your system → Allegro	A new product or description change: linked to a product in the Allegro catalogue.
Stock	Your system → Allegro	A sale in any channel: before someone buys a missing item.
Prices	Your system → Allegro	A price list change: every price change arrives exactly once.
Orders	Allegro → Your system	Order events.
Fulfilment status and shipment	Your system → Allegro	Packing and dispatch.
Buyer messages	Allegro ↔ Your system	A new message: when support answers from your panel.

Common questions about Allegro integration

Allegro orders, authorisation and limits

VulCode Support

Online

Click a question on the left to start a conversation

How much time does copying orders take you today?

Tell us where you sell and where you keep stock. We will reply within an hour with an integration plan and a quote.

Allegro integration through the REST API

Directly or through BaseLinker

Through BaseLinker

Directly through the Allegro API

How a seller links their Allegro account to the app

The password stays with Allegro

Access for 12 hours

After three months without a refresh

Allegro order events

Bought

Delivery details filled in

Ready for processing

Sent

Cancelled by the buyer

Cancelled by Allegro