Call Brief · Internal — Tradebyte kickoff

Tradebyte · Breuninger integration

25-minute technical kickoff at 1 pm CEST with Steffen Scholand (Integrationsteam). Felix is on the call. Status update first, then architecture questions, then what we need from them to scope the build. Goal: walk out with a clear picture of the Breuninger channel requirements so the integration can be sized this week.

How to frame this at the top

"Our Shopify shop went live on 25 April. The past two weeks were bug-fixing and stabilisation — the platform is stable now: 1,331 active products, full stock and order sync with Intex, no outstanding regressions. Xano sits between Shopify and Intex as our point of truth. We're ready to start the Breuninger integration this week, and I'd like to scope the work once I have your attribute spec and feed requirements."

What we already know (don't re-ask these)

Channel: Breuninger only (channel id 5150 in TB.One — ticket "initial-gössl-gwand-gmbh-5150-breuningerde").
Project was paused Apr 27 (Theresa) because of the Shopify launch; you reactivated it May 2.
Steffen Scholand took over from Theresa as the technical integration lead.
TB.One staging access is already live for sj@asksj.com (Apr 29 staging outage notice was sent directly).
Felix's TB.One creds are stashed — login felix.goessl@goessl.com (used to reach Community + integration panel).
Platform tooling: TB.One now has Smart Mapping (AI) + Article Error Hub (new, replacing Solution Center by 31 May).
Shipping decision already made: SendCloud for DPD (own shop) + DHL (Breuninger), Felix approved 9 Apr. Each store as a sender address.

Where Gössl is right now

Shopify Plus, live since 25 Apr 2026 · 1,331 active products · stable.
Xano is the middleware / point of truth · workspace 1 · holds product master, variants, stock, image library, customers.
Intex remains the ERP · read-only for product / stock / customers · writable for orders / customer returns.
Cloudflare Workers are where new compute is going · contact form, cron jobs, reconcilers, sale-tag manager, build-recommendations, curator hub all already live there.
Direction of travel: feeds + webhooks for new integrations land on CF Workers, read Xano, post to Intex via the existing order pipeline.

The questions — in this order

Question 1 · the scope driver

"How does Tradebyte want to receive our product feed — pull from a URL, or do we push to your SFTP?"

HTTPS pull (Tradebyte fetches an XML feed from a URL we host). Best fit for our stack — Cloudflare Worker generates the XML, caches at edge, Tradebyte pulls on their schedule.

SFTP push (we drop XML files in a Tradebyte SFTP bucket on schedule). Adds complexity — worker-to-SFTP bridge or schedule on Xano. Push if required.

REST API (we POST products to a Tradebyte endpoint per change). Real-time delta updates after an initial bulk load. Ask whether bulk-then-delta is the pattern.

Their answer + notes

Question 2

"What's the Breuninger attribute spec — where do I find the required vs. optional fields and the valid values?"

Get the URL or a downloadable file. Determines how much we map from our existing Shopify metafields and Xano fields. Ideally a JSON schema or annotated XML. Ask whether Smart Mapping suggestions are reliable for the Trachten/Bekleidung category.

Their answer + notes

Question 3

"How are stock updates expected to flow — real-time webhook on our side, or batch sync on a schedule?"

Batch on schedule (e.g. every 15–30 min). Easy to schedule via CF Worker cron, decoupled from existing pipelines.

Real-time POST per change. Hook into existing Shopify stock webhook path; replay events to Tradebyte alongside.

Their answer + notes

Question 4

"How do orders come back to us — webhook to a URL we host, or do we poll Tradebyte?"

Strong preference for webhook. CF Worker receives, translates, posts into Intex via the existing fn46-equivalent path. Ask about retry semantics if our endpoint is briefly unavailable.

Their answer + notes

Question 5

"What authentication do you require — for the feed URL, the order webhook, and any sandbox endpoints?"

Bearer token, IP allow-list, HMAC signature on payload? Determines how we lock down the CF Worker endpoints. Ask whether token rotation is on a schedule.

Their answer + notes

Question 6

"Can I use the existing TB.One staging environment to validate the feed before we go live with Breuninger?"

Confirms the integration loop. Also ask: is there a Breuninger sandbox marketplace, or only TB.One staging?

Their answer + notes

Question 7

"What's the typical onboarding length from kickoff to first live order on Breuninger?"

Want their estimate before quoting Felix. Hedge: "I want to scope after seeing the attribute spec — but my expectation is days-to-weeks rather than months given Xano has the data ready."

Their answer + notes

Question 8 · shipping

"For Breuninger orders we'll ship DHL via SendCloud. Does Tradebyte handle label generation, or do we generate the label on our side and push the tracking number back to you?"

Already decided: SendCloud for both DPD + DHL. Confirm where the tracking number originates and how it gets back to Breuninger. Ask about Breuninger's specific shipping SLAs / returns handling.

Their answer + notes

Architecture sketch (reference if asked)

Xano (DB only — point of truth) │ read ▼ goessl-tradebyte.asksj.workers.dev (Cloudflare Worker) ├── GET /feed/breuninger.xml (cached at edge, ~15 min TTL) ├── POST /webhook/tradebyte/order (receives order from TB) ├── POST /webhook/tradebyte/shipped (shipment ack back) └── cron: stock-delta push (15–30 min) Tradebyte ←HTTPS→ goessl-tradebyte Tradebyte ←TB.One→ Breuninger Order webhook → existing Intex InsertOrder path (fn46-equivalent) Tracking → SendCloud → push back to Tradebyte → Breuninger

Credentials & reference URLs

TB.One staging sj@asksj.com (already provisioned) Integration ticket community.tradebyte.com/s/integration/a0NJz00000ARWywMAH/ initial-gössl-gwand-gmbh-5150-breuningerde Felix's TB.One felix.goessl@goessl.com Meet link meet.google.com/gsz-mssg-vfp PIN (dial-in) 416183065

What we want to walk away with (tap to tick off)

Decision on feed transport (HTTPS pull preferred, SFTP as fallback)
The Breuninger attribute spec document or URL
Decision on stock cadence (real-time vs. batch)
Order webhook URL pattern + auth method
TB.One staging confirmed as the validation environment
Steffen's onboarding-length estimate
Shipping-label question resolved (Tradebyte-generated vs. SendCloud + push-back)
Next call scheduled if needed

Things to flag for SJ after the call

Any answer that pushes us toward SFTP push — that changes the worker scope.
Any field in the Breuninger spec that we don't currently store in Xano or Shopify (size charts, country-of-origin, GTIN, model measurements, sustainability labels).
Whether Tradebyte's order webhook can be configured to retry with backoff.
Any compliance / data residency requirements Breuninger imposes.
Whether pricing parity (Breuninger vs. own shop) is enforced or flexible.
Whether returns come back through Tradebyte or directly from the customer to Gössl.

Other notes & live questions

Anything that came up that doesn't fit above

How to close the call

"Thanks Steffen. I'll review the Breuninger spec, scope the work this week, and come back with a build plan and timeline. If anything in the spec is ambiguous I'll raise it through the Community ticket. Felix and I will coordinate from there."

Tap "Send summary" after the call. Goes to Slack (#claude-code).