TB Business Systems not responding to price endpoint proposal. Without resolution: no addon monetization, tier-only billing, ARPU model broken. Frame as REMOVING complexity from TB, not adding it. Revenue arguments > technical arguments.
Nobody has validated how much work the NEO fork actually requires and what works out of the box. Flagged by PM. Could blow up the timeline if assumptions are wrong.
Stresstest identified hosting agents learning e-commerce need 8-10 weeks. Without L1.5 bridge (2-3 Shoptet specialists), escalation will overwhelm HQ.
Scenario B baseline 60%. COD constitutionally protected in HU. ShoptetPay take-rate ARPU model depends on card share growing.
Not a "fix later" item — missing slevová logika blocks entire B2C merchant category from day 1.
No single person responsible for config layer decisions across countries. Risk: inconsistent decisions as markets multiply.
Manual partner-side toggle vs. webhook/API — not decided. Affects partner integration and add-on UX.
IP+timestamp logging for consents, pre-checked box ban, HU surname-first convention. Not validated with Laura yet (session 25.3.).
Zero agencies identified or engaged. Kateřina's workstream has no outputs beyond the kickoff task (done 24.3.). What does the HU implementation partner ecosystem actually look like?
"Shoptet Ready" and "One by Shoptet" both on the table. Previous "ONE" rejection wasn't final — just doubts. No decision framework. Jarda prefers aspirational over descriptive.
Logistics aggregator as D-layer for scalability. Not shared with anyone yet. Sendcloud doesn't cover HU carriers. ShippyPro better for IT. Per-country carrier integrations don't scale (5 countries = 15-20 integrations).
Competitive analysis done (Shoprenter/UNAS comparison strong). But zero pre-launch demand validation — no waitlist, no LOIs, no merchant interviews. Is the "only functional solution at this price" thesis real?