Etsy integration

An Etsy seller connects their shop and Sellergoo shows what the shop actually earns: each receipt's revenue minus refunds, Etsy transaction and payment-processing fees, shipping and cost of goods — as a running profit figure per order and per SKU, next to stock levels and restock warnings. Sellers who also sell elsewhere see their Etsy shop in the same reporting as their other channels, but Etsy works on its own: a shop can connect Etsy and nothing else.

It replaces the spreadsheet a seller otherwise keeps by hand — exporting orders, guessing fees, and only learning at the end of the month which listings were actually profitable.

• transactions_r — reads the shop's own receipts and transactions. This is the profit calculation itself: sale price, quantity, shipping, refunds and dates. Without it there is no product.
• listings_r — reads active listings and their inventory quantities, so stock, restock forecasting and per-SKU margin can be computed against the seller's own cost prices.
• shops_r — resolves the seller's own shop id once, at connection time, via getMe. Every later request is scoped to that one shop.

These are read-only. A write scope (listings_w) would only ever be requested for sellers who explicitly switch on cross-channel stock synchronisation, so that a sale on another channel can decrement the Etsy quantity. That feature is off, and the scope is not requested.

• We do not create, edit or publish listings — Sellergoo is not a listing tool.
• We do not read or send messages, and we do not contact buyers.
• We do not store buyer personal data. Names, addresses and e-mail addresses in a receipt are not written to our database; we keep amounts, SKUs, quantities and dates.
• We do not scrape Etsy, and we do not collect data about shops that are not our users.
• We do not sell, share, syndicate or aggregate seller data. Nothing derived from one shop is shown to another, and no third party receives it.

Each seller authorises their own shop through Etsy's OAuth 2.0 flow with PKCE (S256). The seller consents inside their own Etsy account; we never ask for a password, and no client secret is used in the token exchange. We store the resulting refresh token and the shop id — nothing else — and the seller can revoke access at any time from their Etsy account or by disconnecting in Sellergoo, which deletes the stored authorisation.

Requests are paced below the app's rate limit and back off on 429, and the inventory stream runs on a reduced schedule so a shop's sync stays well inside the daily quota.

• 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.
• Data is retained while the connection is active and deleted on disconnect or on request, as set out in 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).