Vorto · new e-commerce platform · MVP proposal · draft for discussion
From your requirements to a work plan
Part 1 lists every line of your Functional Requirements v1 and how we cover it. Part 2 is our technical work plan in two phases — MVP (a first working shop) and Full launch (everything needed to move vorto.se over) — with tasks, dates and prices. Click any requirement to see the tasks that deliver it, or any requirement code in the plan to jump back. Prices in EUR, excl. VAT.
Part 1
Your requirements
All 64 lines from “Vorto Functional Requirements v1 (draft)”, in your order and wording. Click a line to see where it lands in our plan.
What the statuses mean
Covered
We deliver the requirement in full, in the MVP or the Full launch. The label next to each line shows which.
Partly covered
We deliver the main part; the rest comes after launch. Open the line to see exactly what is deferred.
Next phase
Not part of this estimate — items for after the launch, not priced here.
In VortoHUB
Already handled by VortoHUB (supplier feeds, best-offer selection); the new platform connects to it.
Why some parts are deferred
Following your own markup. Your document marks these lines “MVP / Post-launch” and says which part comes later; we followed that:
.
One exception in your favour: saved delivery addresses (R40) are included in the MVP.
Our proposal, to discuss. These lines are marked “MVP / Post-launch” without saying which part comes later, so we drew the line — open each to see where:
.
Product-level reviews () were marked “to discuss”; we suggest adding them after launch.
“Finish the job”. are marked “MVP / Post-launch (to discuss)”. We propose them as the first feature after launch, once catalog and pricing run — happy to discuss moving them earlier.
All other Next phase lines are the ones your document marks as Post-launch.
Part 2
Work plan & timeline
Part 3
How we see it happening
Instead of one big launch, we get a working shop in your hands early and grow it step by step. Dates assume work starts on 1 October 2026 and that access to TecDoc, VortoHUB and the first payment provider is ready from day one.
Vorto arranges access & contracts
1 · Clickable prototype
◆
2 · First working shop (Sweden)
◆
3 · Full MVP & vorto.se switch
◆◆
Sep 2026OctNovDecJan 2027FebMarApr
Now – October 2026
0 · Preparation
While we set up the project, Vorto opens the doors we can't open ourselves.
TecDoc API access and licence terms
VortoHUB API: agree the offer and order endpoints in the first two weeks
Test account with the first payment provider (e.g. Stripe)
Customer numbers and test access with PostNord and a second carrier
End of November – December 2026
1 · Clickable prototype
Your team can click through the new shop on a test server.
TecDoc catalog: category tree, vehicle selection (make → model → engine), product pages with specifications
Prices from VortoHUB with your markups
Search and filters
Cart
End of January 2027
2 · First working shop (MVP)
Real orders in Sweden on a test domain or part of the traffic — vorto.se keeps running in parallel.
Sweden only: SEK, Swedish, Swedish VAT
One payment provider, two carriers
Orders flow to VortoHUB; order emails; staff admin
Legal minimum: terms, cookie consent, GDPR
Vehicle chosen from the list; plate and VIN lookup come next
March – April 2027
3 · Full launch & switch
Everything in the work plan above, then vorto.se moves to the new platform market by market.
Nets, Paytrail, PayPal; all four carriers; delivery dates
Norway and Finland: currencies, VAT, languages
Plate and VIN lookup
Tracking, product feeds, SEO at full scale
Migration from kvik.shop, 1:1 redirects, per-market switch with rollback
After the switch: the next phase starts with “Finish the job” and the other items marked Next phase in Part 1.
Payment & terms
Illustrative payment schedule
per month × 12 months
MVP price spread evenly. Final terms to agree: instalments, payment per work package, or a partnership component.
Paid by Vorto, not in the price
Hosting, CDN, email-sending and monitoring services
TecDoc licence and data subscriptions
Registration-plate lookup providers per market
Payment-provider and carrier fees
Klaviyo, Intercom, Trustpilot and analytics tools
Content: texts, translation review, images
Assumptions & open questions
Assumptions
kvik.shop is fully replaced; the new platform is built on Django, MariaDB, Meilisearch, htmx and Alpine.js.
VortoHUB returns the best supplier offer per TecDoc number + brand with the bare purchase price, stock and lead time; retail prices are calculated in the new platform.
Official TecDoc data via API; local caching allowed by the licence.
Developers work in parallel with AI agents writing, reviewing and testing code under their supervision.
Current vorto.se visual identity is reused; screens are agreed as AI prototypes before each package.
Launch markets: Sweden, Norway, Finland. Code, tests and documentation are owned by Vorto.
Needed from Vorto
VortoHUB API documentation, test environment and a contact person
TecDoc API credentials and licence terms
Sandbox accounts with payment providers, carriers and plate-lookup providers
kvik.shop data export: products, customers, orders, URLs
Legal texts per market; one decision-maker for acceptance
Open questions
Does VortoHUB offer a bulk export or change feed, or only per-item lookups?
Who issues invoices and credit notes: VortoHUB/ERP or the web platform?
Which plate-lookup provider per market?
Which account notifications are needed beyond order emails?
How much order history to migrate; can customer passwords move?