Required Attributes:
| Attribute name | What is expected |
|---|---|
| EAN / GTIN / ISBN / ISSN / barcode |
Not mandatory but highly recommended Some categories will reject listings without it. help.allegro.com |
| category ID / Allegro taxonomy | Must be mapped accurately. |
| name | Less 30 characters each, in polish. The title cannot be changed after the first purchase. If you need to change it, you'll have to delete your offer (and loose all historical datas) and create a new one. |
| description |
In Polish, the description section can not have more than 40,000 bytes in length. ' ' character is not allowed. h1 - title *Read further info on "description" below this table. |
| language | The language of the content you are sending to Allegro Choose the value for auto translation on Allegro. The "content_language" attribute has to be filled in to auto translate. |
| afterSalesServices.impliedWarranty.id | Warranty must exist in your Allegro backoffice. |
| safetyInformation.type | Select one of the options: - 'NO_SAFETY_INFORMATION': Use this option if the product does not have any safety information. - 'TEXT': This option will allow you to provide safety information as plain text. |
| afterSalesServices.returnPolicy.id | Return policy must exist in Allegro. |
| image | Highly recommended (URL links). Images must show: Product on different backgrounds, packaging, brand, details, certificates… Do not add store logos or text. |
| price | Must match the marketplace currency. |
| sellingMode.price.currency | Allowed values: PLN or EUR. |
| stock.available | Real-time stock preferred. |
| stock.unit | One of: UNIT, PAIR, SET. |
| delivery.handlingTime | ISO 8601 duration format. Examples: PT0S (immediately), PT24H (24 hours), P2D (2 days)... Duration can be also provided in hours, e.g. PT72H (3 days). Valid values are: PT0S, P2D, P3D, P4D, P5D, P7D, P10D, P14D, P21D, P30D, P60D, PT24H, PT48H, PT72H, PT96H, PT120H, PT168H, PT240H, PT336H, PT504H, PT720H, PT1440H Impacts visibility & buyer experience. |
| payments.invoice | Shipping rate name as set in Allegro backoffice. Recommended for B2B. help.allegro.com |
| publication.duration | Supported values: null (until all items are sold out), P3D (3 days); P5D (5 days); P7D (7 days); P10D (10 days); P20D (20 days); You can also provide the time in hours, e.g.: P72H (3 days). You cannot provide null in offers of AUCTION (auction) type and the allowed values are: P1D (1 day); P3D (3 days); P5D (5 days); P7D (7 days); P10D (10 days); However, the offers of ADVERTISEMENT (classified ad) type support the following values: null (for an indefinite time – fees are charged every 10 days); P10D (10 days); P20D (20 days); P30D (30 days). |
*description
(The following information completes those provided in the table above).
When sending a description to Allegro, the content must follow strict HTML and content rules:
HTML formatting rules
- All content must be wrapped in HTML tags, and only lowercase HTML tags are allowed.
- h1 and h2 tags cannot be further formatted (no bold, no additional styling).
- You may use bold (<b></b>), but only inside the following tags: <p></p><ul></ul><ol></ol>
- You may use paragraph tags (<p></p>) inside: <ul></ul><ol></ol>
- Photos cannot be added in the description using HTML code.
Content restrictions
Do not include the following in the description:
- Any information related to return policy, warranty, contact details, or shipping prices.
Use the dedicated Allegro attributes for these details. - Links to external websites.
- Any message suggesting that buyers should contact you before purchasing.
Make sure your description complies with all of these rules to avoid rejection by Allegro.
VAT legislation
In Lengow complete the "VAT Settings" field in the Attributes mapping.
This field is available at the Category Attributes level.
Where to find ID for values created in your allegro backoffice?
- delivery.shippingRates.id
- additionalServices.id
- afterSalesServices.impliedWarranty.id
- afterSalesServices.returnPolicy.id
- afterSalesServices.warranty.id
- contact.id
- sizeTable.id
For the above fields, allegro expect an ID.
This ID is created by allegro when you create a value in your allegro back-office.
You cannot find this ID in your allegro account.
Therefore, Lengow invites to fill in the value you want to assign to your product/s in your Lengow account (in the Attributes mapping or with a Rule). The value which you indicates has to be exactly the same as the one you created in your allegro back-office (same case, same spelling).
Lengow will then map this value to the ID retrieved from your account via the allegro API, to send the corresponding allegro ID.
How to know if the mapping has been done correctly?
If the value you've filled in in Lengow doesn't map with one of the value from your backoffice, the product will be in error. Please read the Channels report and get back to the attribute mapping to change the value if necessary.
General Product Safety Regulation (GPSR) (for merchants selling in the EU)
To comply with the General Product Safety Regulation (GPSR) applicable from December 13, 2024 in the European Union, you must provide to Allegro the following information about your products through attributes available in Lengow:
- "responsibleProducer.name": the name (or trade name) of the manufacturer,
- "responsibleProducer.countryCode": The country code of the manufacturer.
- "responsibleProducer.street": The street address of the manufacturer.
- "responsibleProducer.postalCode": The postal code of the manufacturer.
- "responsibleProducer.city": The city of the manufacturer.
- "responsibleProducer.email": The contact email of the manufacturer. (mandatory if no "formUrl" is provided)
- "responsibleProducer.phoneNumber": The phone number of the manufacturer.
- "responsibleProducer.formUrl": The contact formUrl of the manufacturer.(mandatory if no email is provided)
You must provide safety information such as: user-manual (in Polish), images of labels on product packaging, and/or warning notes.