Supplier ingestion
CSV, XML, Excel, PDF or API is normalised into one product model.
Unclear SKUs, EANs and categories go to review.
AI infrastructure for e-commerce
ELVO builds the AI operating layer between your products, orders, marketplaces, warehouse, couriers and customers—without replacing the systems that already work.
1 real process · your data · measurable pilot
Agreed acceptance criteria, one remediation cycle and a pilot implementation fee guarantee under the terms.
ELVO · Product-to-Market
Supplier
IngestMaster product
94% readyAero Flow sneaker
Shoes › Sports
€89,00 · 31,8%
Colour
Silver white
Sizes
39–45
Material
Mesh / synthetic
Channels
AI proposes. Rules validate. You decide.
ELVO Product AI
Upload an Excel or CSV with product rows. ELVO extracts the data, adds images and descriptions, categorises it and creates a ready listing for every row. Rules hold incomplete products for human review.
01 / 05
File arrives
Incoming supplier file
supplier_catalog_august.xlsx
4 product rows · 8 columns
Raw rows only—there are no product listings yet.
ELVO is processing
Receives the file
Ready product listings
Image, title, category, price and channels for every row.
Review selected listing
94% readyAero Flow sneaker
SNK-042 · Shoes › Sports
€89,00 · 31,8%
Extracted fields
Colour
Silver white
Sizes
39–45
Material
Mesh / synthetic
Rule: Nothing is published with a missing required field or margin below the agreed threshold.
ELVO Vision AI
Photograph the shelf, the box or the shop window with your phone. ELVO recognises every product in the frame and drafts a listing with an SEO title, description and keywords—ready to review, not to write.
Incoming photo
Photo
IMG_2841.jpg · 1 frame · 6 products
Generated listings
Title, description and keywords for every detected product.Selected listing
Aero Flow sneaker
SNK-042 · Shoes › Sports · €89.00
SEO title
Aero Flow Sneakers – lightweight mesh trainers | 39–45
Meta description
Breathable trainers with a mesh upper and cushioned sole for everyday wear and sport. Fast delivery and 30-day returns.
Keywords
Rule: Copy stays a draft until a human approves it. A product with uncertain detection is flagged for review.
ELVO Pricing Autopilot
On autopilot, ELVO tracks competitor prices for the products you watch, derives a price corridor from cost and margin floor, and proposes a price with clear reasoning. Outside the corridor nothing changes without a human.
Watched products
MonitoringMarket check · every 6 hours · eMAG · Amazon · Google Shopping
Competitor prices found
AUD-204Amazon DE
€118.50
↓ 8% this week
eMAG offer
€124.99
TechZone
€139.00
€121.90
−5.5% change
29.5% margin
ELVO reasoning: Amazon cut its price by 8% this week. The recommendation sits just above the cheapest competitor without breaking the margin floor.
Guardrails: The floor protects margin, the ceiling protects conversion. ELVO never leaves the corridor and never changes a price without approval.
ELVO Try-On Studio
From a single product photo, ELVO generates a visualisation of how the garment looks on a model—for the listing, the campaign, the socials. No studio, no logistics, and every frame clearly labelled as AI.
Products to visualise
ProductGenerated frames are labelled as AI and never replace the real product photos in the order.
Product photo

Reads the cut and fabric
Casts a model and pose
Composes the frame
On-model visualisation

ELVO is generating…
ELVO Order Ops
A webhook receives the order, rules check payment, stock and risk, ERP/WMS gets the data, and Econt or Speedy returns the shipping label and tracking.
Order stream
Normal orders continue automaticallyException
#98417Signals
High value + new profile
Platform risk: HIGH · value over threshold · first order
ELVO recommendation
Hold fulfilment and request confirmation. Never reject automatically.
ELVO Returns & Support
The assistant can see the order, tracking, stock and return rules. Administration is automated; disputes, physical inspection and high risk stay human.
Chat #CS-1842
AI assistant · connects you to a person when neededCustomer · order #98201
“The headphones arrived yesterday. I want to return them—what do I do?”
Verified context
Delivery
yesterday · Speedy
Item
AUD-204 · €129
Window
within 14 days
Tools used
Prepared answer
I can create the request and return label. Reimbursement starts after the item is received and inspected.
Human boundary
The warehouse confirms what was returned and its condition before any financial action.
ELVO does not store card data and never lets text from an email or chat change system policy.
One infrastructure, more workflows
We start with the workflow that has the clearest value. Once the result is proven, the same integration layer can take on the next one.
CSV, XML, Excel, PDF or API is normalised into one product model.
Unclear SKUs, EANs and categories go to review.
Stock sync, forecasting, reorder proposals and dead-stock signals.
A large supplier PO is approved by the buyer.
Order, PSP, bank, COD and marketplace settlement are matched.
Partial refunds, chargebacks and amount mismatches stay in the Finance Queue.
Events drive lifecycle, win-back and back-in-stock workflows.
Consent, suppression and marketing strategy stay visible and controlled.
Margin, fees, stock age and price history feed verifiable rules.
Large discounts and strategy changes require approval.
Shared metrics explain changes in margin, returns and operational volume.
AI reads agreed metrics; management makes the strategic decision.
AI, with control
Every action gets a confidence, risk, estimated impact and policy. The mode follows business rules, not the model's mood.
Normalise supplier file
Automaticschema + validation
New product copy
AI + reviewdraft before publish
Stock update
Automaticevent-driven sync
Unmatched payment
AI + reviewFinance Queue
Large price change
Human onlymargin + strategy
Low-risk order
Automaticstraight-through
Medium / high fraud
Human onlymerchant review
Standard return request
AI + reviewautomatic RMA
Damaged or high-value return
Human onlyphysical inspection
AI Operations Layer
Channel adapters keep logic portable across the store, marketplaces, ERP/WMS, payments, couriers and support.
Sales and customers
Operations
Your systems remain the source of truth. ELVO orchestrates events and exceptions between them.
By default, the production environment, database, cloud and AI/API accounts belong to the client. ELVO builds, documents and hands over.
There is no mandatory ELVO subscription. Cloud, AI and third-party API costs remain transparent and are paid separately.
Before / after, not promises
Before we start, we record the baseline and acceptance criteria. Then we measure exactly what the workflow took over and where human work remains.
Illustrative model · catalogue
1,000 SKUs × 12 min = 200 hours
1,000 SKUs × 3 min review = 50 hours
150 hours of potential monthly capacity
This illustrates the method; it is not a promised result. Actual time, volume, costs and impact are measured with the client.
Start small. Prove it. Then scale.
We select the process with the fastest return potential and build it end-to-end in your store. You get proof with controlled investment and a prioritised roadmap for the next opportunities.
1 agreed process · real data · 2–4 weeks
Move to production within 30 days and the full pilot fee is credited to the project.
We write the acceptance criteria. If the workflow misses them, we complete one remediation cycle at our expense. If it still cannot deliver the agreed result, we refund the pilot implementation fee.
Third-party API, cloud and other provider costs are excluded. Full terms are set out in the proposal.
After the proven pilot, investment follows the number of systems, criticality, volume, UX and compliance requirements.
Single workflow
Production automation, monitoring and handover.
E-commerce OS
3–6 workflows and a shared integration layer.
Operations infrastructure
Multichannel, ERP/WMS, support and analytics.
The exact scope is defined after technical discovery based on the systems, volume and control points; third-party services are described separately in the individual proposal.
Straight answers
Not by default. ELVO builds adapters and workflows around the systems that already act as the source of truth. Replacement is discussed only when a specific limitation requires it.
Only inside pre-approved boundaries. A new SKU, missing required field, margin-floor breach or large discount goes to a human decision.
They provide integration interfaces, but exact scope depends on the account, contract, permissions and workflow. We verify access before the pilot.
By default, the production cloud, database, AI/API accounts and operational data are client-owned. The architecture documents access, location, retention, subprocessors and handover.
There is no mandatory ELVO subscription. Cloud, AI, messaging and API provider costs continue; ELVO monitoring and SLA are optional.
We agree written criteria, test volume and acceptance. One remediation cycle follows. If the workflow still misses the criterion, we refund the implementation fee; provider costs and agreed exclusions remain outside it.
We will map the systems, exceptions and KPI worth proving with your data.