Get started
Live in an afternoon. Compounding for years.
No code required to start. A developer is optional, not a dependency. Here is exactly what happens after you click the button.
1. Register
Brand name, website, vertical. Wiinta verifies the storefront so your product URLs always belong to you. The ops team reviews and approves - usually the same day.
2. Sync
CSV in the portal, or the API with your minted key. Rows are validated against the ontology: price, images, sizes, colours, categories. Fixes are suggested in place.
3. Meet demand
Approved products stage in the catalogue mirror and start answering asks. The demand card, the gap report and the insights turn on with your data in them.
What do I need before I register?
A website or storefront you control (your product URLs must live on your own domain), and a sense of your vertical: fashion or beauty to start. Everything else is supplied in the flow.
How long does approval take?
The ops team reviews same day in most cases. You can stage your whole catalog while you wait, and it publishes the moment the store is approved.
What if my data is messy?
That is the normal case, and exactly what the ontology validation is for. Rows that fail are never published; the portal shows the exact field that failed and the fix. Clean data is a side effect of syncing.
Do I need a developer?
No. CSV covers everything the API covers. A developer becomes useful when you want your stock system to sync automatically instead of on upload days.