What are the open decisions still required before technical design (stack, data model, timeline)?

At the original requirements stage these were open: backend stack, the detailed data model, the architecture (monolith vs microservices), the timeline/MVP scope, specific regional providers, and per-scenario policy decisions. In the built platform, most are resolved: the stack is ASP.NET Core 9 / EF Core 9 / SQL Server 2022 in a modular, clean-architecture monolith, with a defined…

At the original requirements stage these were open: backend stack, the detailed data model, the architecture (monolith vs microservices), the timeline/MVP scope, specific regional providers, and per-scenario policy decisions. In the built platform, most are resolved: the stack is ASP.NET Core 9 / EF Core 9 / SQL Server 2022 in a modular, clean-architecture monolith, with a defined data model (~49 entities). What remains genuinely "configurable per deployment" are the policy decisions — return windows, cancellation fees, refund channels, the master-product toggle, which providers to use per region — which are intentionally left to configuration rather than hard-coded. So the engineering decisions are made; the per-business policies are yours to set at setup.