Complete apps exercised with a real business's data. Buying one means tenant onboarding — import your catalog, or for channel apps paste your own API keys into the credential vault (~30 seconds per channel) — not waiting for development.
B2B Wholesale Ordering
Your dealers order at their price, on their own
A complete wholesale channel: dealer application and approval flow, tiered wholesale price lists, and a self-service ordering screen your dealers use without calling you.
- •Dealer application → review → approval workflow with role-based access
- •Wholesale price visibility separated from retail by account type
- •Self-service bulk ordering against live stock, with order tracking
Grounding: Built end-to-end for the Volkan Oto wholesale operation on its real catalog (2,400+ SKUs) and real dealer flow.
Honest note: Ships to production with the current platform release (in final review). Onboarding a new wholesaler = importing their catalog and price tiers — no new development.
Ops Tasks & Evening Report
The team's day, assigned in the morning, reported at night
A lightweight operations task board with per-person assignment, completion tracking, and an automated evening report that tells the owner what got done and what's still open.
- •Task creation with assignee routing by role/e-mail
- •Completion tracking with who-did-what accountability
- •Automated daily report: completed work, open tasks, orders waiting for a call
Grounding: Running in production today for Volkan Oto — the evening report is generated automatically every day from the live API.
Honest note: This is a focused ops tool, not a full project-management suite — that focus is why a small team actually uses it.
Document Intake Automation
Drop a file, get a routed task
A watched intake folder that classifies incoming business files (price lists, stock exports, campaign briefs, legal docs, media) into buckets and automatically creates assigned tasks for the right person.
- •Bucket classification: products, stock, pricing, campaigns, ERP exports, marketplace, legal, media
- •Automatic task creation with assignee mapping by role
- •Nightly scan with a morning summary of everything new
Grounding: Live for Volkan Oto: a scheduled nightly scan processes the real archive intake and opens tasks for the team.
Honest note: Classification is rule-based on file type and naming today — transparent and editable, not a black-box document AI.
Counter Sales Log (POS)
Every in-store sale recorded in seconds
A fast counter-sales screen for physical stores: pick from the catalog, record the sale with customer type and payment method, cancel with an audit trail — and feed the same analytics as your online channel.
- •Catalog-backed line items with automatic totals
- •Customer-type and payment-method tracking per sale
- •Cancellations with audit trail; sales feed inventory and ROI analytics
Grounding: Built on the real Volkan Oto catalog for in-store sale recording.
Honest note: This is a sales log, not a fiscal cash-register replacement — it doesn't print legal receipts or talk to fiscal devices.
Cari Ledger (Accounts & Receivables)
Your ERP's cari export, finally readable
Imports the customer/vendor account export your ERP already produces and turns it into a living ledger: balances, classifications, and phone-matched contact records your team can act on.
- •One-file import from standard ERP cari exports
- •Automatic account classification and balance overview
- •Phone-normalised matching that links ledger accounts to CRM contacts
Grounding: Built and exercised on Volkan Oto's real ERP export and live account data.
Honest note: Read-and-act layer, not double-entry bookkeeping — your ERP stays the source of truth; this makes it usable on the floor.
CRM & Order Call Queue
No customer waits for a call twice
Order-driven customer follow-up: every new order lands in a call queue with contact status, call logs are recorded per customer, and stale uncalled orders get flagged before the customer gets angry.
- •Call queue from live orders with pending/contacted status
- •Per-customer call and interaction logs
- •Escalation flags for orders waiting too long for contact
Grounding: In daily production use for Volkan Oto — the owner's evening report reads this queue for 'orders waiting for a call'.
Honest note: Focused on order follow-up calls; it is not a full omni-channel contact center.
Multi-channel Command Center
Five sales channels, one screen
Channel clients for Trendyol, Hepsiburada, Amazon SP-API, İdefix and Meta WhatsApp with a unified readiness/test-connection layer, a server-side credential vault, and LIVE price/stock dispatch against a single catalog.
- •Server-side credential vault: paste your channel API keys once, everything uses them
- •LIVE price & stock push to Trendyol, Hepsiburada and Amazon; per-channel connection tests
- •Single-catalog governance across all connected channels
Grounding: All five channel clients, the credential vault and the live dispatch layer are built in the platform against the real Volkan Oto catalog.
Honest note: The only remaining step is yours: paste your own channel API keys (~30 seconds per channel). İdefix has no public API docs, so its write actions stay adapter-pending until a seller account confirms the contract. No live path has been soak-tested with real keys yet — the first onboarding is that test, priced accordingly.
Launch Control & Price Approval
Nothing goes live without a yes
Governance for product launches and price changes: proposal → approval → launch, with launch-pricing rules and a full decision trail — for teams where the owner wants the final word without being the bottleneck.
- •Product and price approval workflows with decision history
- •Tenant-configurable governance: approver list, discount ceiling, self-service policy via API
- •Launch control board showing what's waiting on whom
Grounding: Approval, launch-control and launch-pricing modules run in the Volkan Oto stack; governance config (approvers, thresholds) is now a tenant-editable API, not hardcoded.
Honest note: Config-driven and tenant-generic today; the defaults still mirror the first deployment until a second tenant tunes their own rules.
Brand Asset Portal
Your brand kit, always the right version
Central brand asset management for businesses with dealers and partners: upload logos, banners and product media once; partners always pull the current, approved bundle.
- •Versioned asset upload with per-tenant quota (file size, count, total storage)
- •Role-gated uploads and deletes; approved-bundle download for dealers/partners
- •Asset serving API for sites and campaigns
Grounding: Built for the Volkan Oto brand asset flow — upload, quota, role checks, delete and bundle APIs all live in the platform.
Honest note: Assets live on app-server storage, not a CDN — fine for brand-kit scale, honest to say before someone uploads their whole DAM.
Customer Portal & Seller Self-Service
Accounts that set themselves up
Self-service account layer for a commerce platform: customer signup/login and order history, plus one-call seller self-activation — a user makes themselves a seller in ~30 seconds, with an audit task logged for ops.
- •Customer signup, login and order-history portal
- •One-call seller self-activation (instant approve by policy, auditable, revocable)
- •Governance switch: auto-approve on/off per tenant via the governance API
Grounding: Customer portal APIs, the seller readiness flow and the instant self-activation endpoint are live parts of the commerce platform.
Honest note: The founder's 30-second bar is now a real endpoint, defaulting to instant approval with an ops audit trail. Flip auto-approve off and it honestly becomes 'apply and wait' again.
Category Scout Agent
A daily shortlist for your category, on schedule
A scheduled agent that runs the semsTrend engine for your category and delivers a shortlist with trend scores, evidence counts and rejected-signal transparency — a productised 'analyst that never sleeps'.
- •Per-customer subscriptions: category scope, delivery channel, monthly run quota
- •Evidence and rejected-signal counts in every report (no silent guessing)
- •WhatsApp delivery when the channel is connected; quota enforced per month
Grounding: Runs on the real semsTrend engine; the subscription store, quota metering and run-delivery API are built and running against it.
Honest note: WhatsApp delivery is real once the customer's Meta keys are in the vault; e-mail delivery is honestly not wired yet (no mail infra), so those reports land in the archive + dashboard.
WhatsApp Sales Desk
Where Turkish commerce actually happens
A WhatsApp-native sales layer: outreach campaigns to your contact base, a shared team inbox on the Meta WhatsApp Cloud API, and a bot for first-line answers — because your customers are already there.
- •Campaign outreach with per-contact delivery tracking
- •Shared inbox: whole team answers one business number, with history
- •First-line bot for catalog/price/status questions, human hand-off
Grounding: Outreach, inbox and bot modules are built in the platform; the Meta WhatsApp channel client (webhook, inbox, send-test, readiness) runs off the same credential vault as the Command Center.
Honest note: The only remaining step is the customer's own Meta Business verification + WhatsApp Cloud API token — pasted into the vault, ~2 minutes. That verification wait is Meta's, not ours.