Allegro integration

The Allegro connection is in development. This page describes exactly what it requests and does once it is available; it will be updated if that changes.

An Allegro seller connects their account and Sellergoo shows what the account actually earns: each order's revenue minus refunds, Allegro commissions and other billing entries, delivery costs, VAT and cost of goods, as a running profit figure per order, per offer and per day. Sellers who also sell on Amazon, eBay, OTTO, Kaufland or their own shop see Allegro in the same reporting, with amounts in PLN converted to their reporting currency at the ECB reference rate of the transaction day. Allegro also works on its own: an account can connect Allegro and nothing else.

• allegro:api:profile:read: identifies the seller's own account once, at connection time, so every later request is tied to that one account.
• allegro:api:orders:read: reads the seller's own orders, line items and customer returns. This is the profit calculation itself: price, quantity, delivery, refunds and dates. Without it there is no product.
• allegro:api:billing:read: reads billing entries (commissions, listing and promotion fees), so profit is shown after everything Allegro charges.
• allegro:api:payments:read: reads payment operations and refunds, so payouts and refunded amounts match the seller's bank account.
• allegro:api:sale:offers:read: reads the seller's own offers with price and available stock, so stock, restock forecasting and per-offer margin can be computed against the seller's own cost prices.
• allegro:api:sale:settings:read: reads the seller's delivery, return and warranty settings, so delivery costs and returns are attributed to the right orders.
• allegro:api:fulfillment:read: reads stock held in Allegro One Fulfillment warehouses and the seller's inbound shipments, so warehouse stock is part of stock levels and restock planning.
• allegro:api:shipments:read: reads the seller's parcels sent with Allegro delivery services, so each order carries its own shipping cost rather than a monthly total.
• allegro:api:ads: reads Allegro Ads spend per campaign and offer, so profit is shown after advertising. Allegro offers advertising access only as this one permission; Sellergoo uses it to read statistics and never creates, changes, pauses or stops a campaign.

Sellergoo only reads through all of these. One write permission, allegro:api:sale:offers:write, is used for exactly two fields of the seller's own offers: the price and the available stock. It is off by default. Sellergoo writes them only when the seller asks for it: by changing a price or a stock level in Sellergoo, by a repricing rule the seller defines, or by switching on stock synchronisation so that a sale on another channel lowers the Allegro quantity. Every change is logged in the seller's account. Nothing is written on Sellergoo's own initiative, and no other account is ever touched.

• We do not create, end or publish offers, and we never change an offer's title, description, photos, parameters or any other content. Price and stock, at the seller's request, are the only fields we write.
• We do not create, change, pause or stop Allegro Ads campaigns or their budgets.
• We do not read or send messages, and we do not contact buyers.
• We do not store buyer personal data. Names, addresses, phone numbers and e-mail addresses in an order are not written to our database; we keep amounts, offer ids, SKUs, quantities and dates.
• We do not scrape Allegro, and we do not collect data about accounts that are not our users.
• We do not sell, share, syndicate or aggregate seller data. Nothing derived from one account is shown to another, and no third party receives it.

Each seller authorises their own account through Allegro's OAuth 2.0 authorization code flow. The seller signs in and consents on Allegro's own page; we never ask for a password. We store the resulting refresh token and the account id, nothing else, and the seller can revoke access at any time from their Allegro account or by disconnecting in Sellergoo, which deletes the stored authorisation.

Orders, billing and refunds refresh every 30 minutes; requests are paced below Allegro's rate limits and back off when Allegro asks them to.

• Hosted on our own server in Frankfurt, Germany (EU). Data is not transferred outside the EU for processing.
• Every customer has a physically separate database file. Isolation is not a query filter that could be forgotten; it is a different file per tenant.
• OAuth tokens are encrypted at rest with AES-256-GCM; the key lives in the server environment, never in the database or the source tree.
• Disconnecting stops all access at once and deletes the stored authorisation. Allegro data already synced is kept only to show the seller their own history, and is deleted on request ([email protected]) or when the account is closed: immediately from the live system, and from encrypted backups within 30 days. See the privacy policy.

Support and API questions: [email protected] · support page. See also the privacy policy, terms of service and Impressum (the operator's full legal identity under German law).