Available for selected B2B collaborations

I help teams build and improve eCommerce projects on VTEX.

Technical project manager with hands-on VTEX experience since 2018. I work across platform architecture, Admin, APIs, integrations, requirements, QA and releases.

Discuss a project See where I can help
Eugen Predescu
VTEX LegacyVTEX IOArchitecture & AdminAPIs & integrationsQA & UATeCommerce delivery

01 / What I do

VTEX experience plus practical project delivery.

I can help with a new implementation, a migration, an integration or a project that simply needs clearer ownership and follow-through.

01

Technical project coordination

I clarify the scope, organize priorities, follow dependencies and keep business and technical teams working on the same problem.

  • Roadmaps
  • Delivery
  • Risk management
02

VTEX architecture, Admin & APIs

Experience with VTEX Legacy and VTEX IO, platform architecture, Admin/back office, commerce flows, APIs and integrations with external systems.

  • VTEX
  • APIs
  • Migrations
03

Requirements, QA & launch

I turn business needs into workable requirements, check edge cases, coordinate testing and stay involved through release.

  • Discovery
  • QA / UAT
  • Go-live
04

AI for commerce & customer support

I also work on practical AI products for product assistance and customer support, including automation, human handoff and operational tools.

  • AI assistants
  • RAG
  • Support operations

02 / Experience

I’ve worked with VTEX since 2018 — from F64’s two major platform migrations to ongoing delivery and releases across multiple iviteb client accounts.

I came to eCommerce from customer support and operations, then moved into business analysis and technical project work. That mix helps me understand both how a platform should work and what teams need to run it every day.

2023 — present

Oigan Tech

Founder · Technical Project Manager, B2B

Through Oigan Tech I work mainly with iviteb solutions across 12 VTEX client accounts, contributing to client projects, new implementations and ongoing releases. My role covers requirements and architecture, implementation coordination, integrations and testing.

2011 — 2023

F64 Studio

Technical Support → Customer Care Coordinator → Project Manager / eCommerce Analyst

At F64 I contributed to the 2018 migration from Magento to VTEX Legacy, followed by the 2020 migration from VTEX Legacy to VTEX IO. I worked with the platform from both business and technical sides: architecture, Admin/back office, APIs, integrations, testing and daily operations.

2007 — 2011

eMAG · Flanco

Technical Support & Retail Sales

I started in technical support and retail sales. It gave me a practical understanding of customers, products and the operational side of commerce.

15+

years working where customer needs, operations and technology meet.

03 / How I work

I stay close to the actual work.

I clarify requirements, talk to the right people, follow implementation, test the important flows and stay involved through launch.

01 / 07

Conversation

A first call about the problem, not the backlog. What is broken, who feels it, and what would count as fixed.

02 / 07

Discovery

Current flows, systems and constraints, mapped out. Most of the expensive surprises live in this step.

03 / 07

Requirements & acceptance

Business needs turned into requirements a developer can actually implement, with acceptance criteria agreed before anyone writes code.

04 / 07

Architecture

How it fits VTEX and everything around it — Admin, APIs, integrations and the data that has to stay consistent between them.

05 / 07

Implementation

Coordinating developers, operations and stakeholders — unblocking work and raising issues while there is still time to fix them cheaply.

06 / 07

QA & UAT

The important flows, the data and the edge cases. When something fails here it is cheap; the point of this step is to make sure it fails here.

07 / 07

Go-live & monitoring

Release, then watch what actually happens. The plan is a hypothesis until real orders and real data move through it.

04 / Migration risk

What actually breaks during a platform migration.

Not a scare list. The dangerous risks are not the severe ones — they are the severe ones nobody finds until real traffic and real orders are running.

Found too late to be cheap

Found earlyFound after launch

Impact

  1. Content, banners, landing pages

    Rarely dangerous. It is visible immediately, everyone notices, and it gets fixed the same day.

    How I handle itInventory it early so it never competes for attention with the things that actually hurt.

  2. Payment gateway re-certification

    Severe but loud. The gateway either certifies or it does not, and you find out well before launch.

    How I handle itStart certification before it sits on the critical path, because the timeline belongs to the provider, not to us.

  3. Price tables and promotions

    Promotion rules rarely map one to one between platforms. The mismatch shows up as a wrong total in a specific basket combination.

    How I handle itRebuild the rules deliberately rather than migrating them, then test the awkward baskets — not the simple ones.

  4. ERP and WMS synchronisation

    Stock and order sync usually works in testing, where volume is low and nothing arrives at once. It fails on the first real peak.

    How I handle itTest with production-shaped volume and deliberately break the connection to see how it recovers.

  5. Customer accounts and passwords

    Accounts migrate, but credentials often cannot. Customers discover this one at a time, at the worst moment — checkout.

    How I handle itDecide the credential strategy in discovery and prepare the communication before launch, not after the first complaint.

  6. Catalog structure and specifications

    The tree and specifications look fine in the Admin, then filters return nothing and search misses products. It surfaces once customers browse the way customers actually browse.

    How I handle itValidate against real category and filter journeys during UAT, not against a sample of well-behaved SKUs.

  7. Orders in flight at cutover

    Orders placed on the old platform still need returns, refunds and support after the switch. The gap appears days later, in customer service.

    How I handle itAgree who owns those orders, and for how long, before the cutover date is set.

  8. URLs and the redirect map

    The most expensive one, and the quietest. Nothing looks broken on launch day. Rankings and traffic decline over the following weeks, when the cause is already hard to trace.

    How I handle itBuild the redirect map from real crawl and analytics data before launch, then verify it after — the one task worth doing twice.

“I’m comfortable discussing both the business problem and how the platform behaves.”

Business contextI keep the reason behind a request visible throughout delivery.

VTEX knowledgeI understand enough of the platform to discuss options and spot weak assumptions.

Practical experienceI have worked with customers, operations and technical teams, not only project plans.

05 / Contact

Need help with a VTEX or eCommerce project?

Send me a short description of the project and where you need help. I’ll tell you directly if it fits my experience.

[email protected]
LinkedIn ↗ Bucharest · Romania