SKL ERP Shipping Labels

Integration documentation for the shipping-label module of SKL ERP.

Updated: 14 September 2026. Allegro application approval and production seller authorization are pending. This page does not indicate an active connection or Allegro certification.

Purpose

The module lets authorized merchants retrieve existing Allegro shipment labels as PDF files from their SKL ERP merchant workspace. It is separate from the local HaLe Listing Assistant product-listing application.

Requested Allegro Permissions

allegro:api:profile:read: verify the identity of the connected seller using the official account API.
allegro:api:shipments:read: read existing shipment labels through the official shipment-management API.

No offer-writing, shipment-writing, payment, refund or advertising permissions are requested. The module does not create, cancel or purchase shipments.

Connection Workflow

Sign in to the SKL ERP merchant workspace and open Platform Shipping Labels, then Store Authorization.
Select the Allegro store configuration and start authorization after the dedicated application has been approved and configured.
Sign in on Allegro's own website, check the seller identity and consent to the displayed permissions.
Allegro redirects to the SKL callback. SKL validates the authorization state, exchanges the code on the server and verifies the seller identity.
Verify the connection in SKL before attempting a label download.

Label Retrieval

Use an existing Wysylam z Allegro shipment identifier. An order number or carrier tracking number is not a substitute for the shipment identifier. SKL requests the label through POST /shipment-management/label, checks the PDF response and makes it available for authorized preview and download.

The interface supports filtering label records and downloading selected files. This integration does not promise discovery of every historical shipment. Unattended synchronization is not enabled merely by connecting an account.

Data and Access Controls

Allegro passwords and two-factor codes are entered only on Allegro, not collected by this module.
Application credentials and OAuth tokens are stored encrypted on the server and are not exposed by this documentation.
Store configurations and label records are scoped to the authenticated merchant workspace. PDFs are stored outside the publicly served directory.
Label files may contain recipient information. Merchants should limit access to staff who need it for fulfillment.
Disconnecting in SKL clears locally stored connection credentials. To revoke the grant at Allegro, use Allegro's authorized-application controls as well. Disconnecting does not automatically delete previously downloaded PDFs.

Errors and Support

A pending application, missing authorization, expired credentials, wrong shipment identifier or unavailable platform label can prevent retrieval. A successful settings save is not proof of successful API authorization. Contact support through the SKL ERP merchant workspace for connection assistance.