A replatform cannot interrupt revenue.
You need a controlled route from legacy technology to VTEX, with catalog, content, redirects, integrations, analytics and launch readiness treated as one release.
VTEX COMMERCE · ROMANIA & EUROPE
Build the commerce operation, not just the VTEX storefront.
ivi.works designs, builds, modernizes and runs VTEX commerce platforms for retailers and complex businesses. One senior team connects the business decision, customer experience, engineering, integrations and release operations.
- PLATFORM
- VTEX IO · Store Framework · APIs
- MODELS
- B2C · B2B · Marketplace
- ENGAGEMENT
- New build · Modernization · Evolution
01
THE REAL DECISION
VTEX is infrastructure. The operating model is the product.
VTEX gives you options. The work is deciding which ones become your operation.
A credible VTEX project starts before the first component and continues after go-live. We make the commercial model, information architecture, integrations, ownership and measures of success explicit, then design and engineer the clearest coherent route to production.
02
WHEN TO CALL US
Bring us in when commerce complexity starts crossing team boundaries.
The storefront no longer reflects the business.
Customer journeys, content and interface patterns have drifted while the operation evolved. We turn them into a clear, reusable experience system.
B2B rules cannot be flattened into B2C screens.
Organizations, price tables, permissions, repeat orders, credit and ERP reality need a product model designed around how buyers actually work.
Marketplace ambition needs operational clarity.
Seller onboarding, assortment, commissions, fulfillment and customer ownership must work together, not appear as disconnected platform features.
The platform is live, but the backlog is not moving.
We create an accountable evolution rhythm across product, experience, engineering, QA and release operations.
03
WHAT WE DO
One accountable system from first decision to daily operation.
Commerce direction
Business model, customer journeys, scope, platform fit, roadmap and a measurable release definition.
DISCOVERY · PRODUCT DIRECTION · ROADMAPExperience and storefront
Research, information architecture, interface design, design systems and accessible storefront implementation.
UX · UI · STORE FRAMEWORK · FASTSTORECommerce engineering
VTEX IO applications, catalog and checkout behavior, promotions, marketplace flows and custom operational tooling.
VTEX IO · APPS · CHECKOUT · MARKETPLACEIntegrations and data
ERP, PIM, CRM, payments, fulfillment and analytics connected through explicit contracts and observable flows.
APIs · ERP · PIM · OMS · ANALYTICSMigration and release
Content, data, redirects, QA, performance, SEO continuity, cutover planning and accountable go-live ownership.
MIGRATION · QA · SEO · RELEASE OPSContinuous evolution
Senior maintenance and product development after launch through an ivi Care partnership, with priorities, response times and a visible monthly rhythm.
IVI CARE · OPTIMIZATION · PRODUCT DELIVERY04
THE TEAM
You buy an outcome, not a seat count.
The roles change with the problem. Accountability does not.
We assemble the senior team the outcome needs end to end. Specialists join when the system needs them; the client does not have to coordinate a loose set of vendors.
Commerce lead
Connects commercial ambition, priorities and measures of success.
Product & experience designer
Shapes journeys, interfaces and the reusable design system.
Solution architect
Defines platform boundaries, integrations and technical decisions.
VTEX engineers
Build storefronts, applications and business-specific capabilities.
QA & release owner
Owns acceptance, continuity, performance and launch readiness.
Integration specialists
Join for ERP, PIM, CRM, payment, fulfillment or data work.
05
HOW IT MOVES
A controlled route from ambiguity to a working commerce system.
Frame
Agree on the business decision, constraints and proof of success.
Map
Make journeys, architecture, data, integrations and release risk visible.
Build
Design and engineer in one product loop with working releases.
Prove
Test real flows, content, performance and operational readiness.
Launch
Run the cutover with named owners and explicit rollback decisions.
Evolve
Keep priorities, incidents and improvements in one visible rhythm.
06
SELECTED VTEX WORK
Complex commerce, in production.
The business numbers below are our clients' own, publicly reported. What we did is described separately and precisely.
01
F64
DIRECT PARTNERSHIP
A mature VTEX IO platform, modernised for what comes next.
We redesigned the experience, improved performance and custom applications, completed unfinished capabilities and unified the wider digital system. The release went live without downtime or SEO loss.
PUBLIC CONTEXT
In 2025, F64 reported 121,000 orders in 2024, 37% web-traffic growth over three years and a renewed five-year VTEX partnership.
02
MACROMEX · BOCADO
IMPLEMENTATION CONTRIBUTION
A B2B ordering channel became core operational infrastructure.
Our team contributed to the platform work behind Macromex's VTEX B2B ecosystem, where customer-specific pricing, ERP synchronization and complex ordering flows had to behave as one service.
PUBLIC CONTEXT
VTEX's client-approved 2026 story reports €36M+ online sales, 13,000+ active customers and 100,000+ annual orders automated through ERP sync.
03
INPOST FRESH · POLAND
IMPLEMENTATION CONTRIBUTION
Marketplace growth with seller onboarding built into the operation.
Our team contributed to the VTEX marketplace implementation for InPost Fresh in Poland, working in the operational reality behind a fast-growing multi-seller catalog.
PUBLIC CONTEXT
VTEX reports that the marketplace onboarded more than 300 sellers offering more than 300,000 products after the project began in October 2022.
04
KFC ROMANIA
DELIVERED THROUGH ZITEC
A connected ordering experience across web, mobile and restaurant operations.
We worked on the VTEX implementation as Zitec's delivery partner. Zitec led the client relationship and owns the public delivery story. Our part was the commerce engineering underneath.
PUBLIC CONTEXT
KFC's 2024 release describes a nationwide pickup and delivery experience, VTEX web commerce, mobile applications and integrations with internal operational systems.
Additional VTEX contribution across Romanian retail includes work connected to Auchan, Dacris and Meli-Melo. Public detail is intentionally limited until each account is approved for publication.
07
WAYS TO START
Start with the decision you need to make, not a predetermined team size.
VTEX discovery
For a new platform, migration, B2B model or marketplace whose scope is not yet safe to estimate.
Decision map · architecture · release plan · investment rangeCommerce modernization
For a storefront, migration or operational capability that must reach production with one accountable team.
Working product · integrations · migration · controlled releasePlatform evolution
For a live VTEX operation that needs senior maintenance, improvements and product delivery after launch.
Response times · monthly priorities · releases · platform health08
USEFUL ANSWERS
Questions to settle before a VTEX project starts.
What kind of VTEX work does ivi.works handle?
Strategy and discovery, experience design, Store Framework and VTEX IO engineering, custom apps, integrations, B2B and marketplace flows, migration, QA, launch and continuous evolution.
Do we need a full replatform?
Not necessarily. We first identify the commercial constraint and the most focused coherent change. Sometimes that is a storefront modernization or custom capability; sometimes the platform boundary itself must change.
Can you modernize a live store without stopping sales?
That is how we plan critical releases: parallel preparation, explicit data and redirect mapping, end-to-end acceptance, launch ownership and a rollback decision. The exact route depends on the current VTEX architecture and integrations.
Can the team handle B2B or marketplace operations?
Yes. Our relevant work includes buyer-specific pricing, ERP-synchronized ordering, seller onboarding, marketplace catalogs and operational flows that cross commercial and technical teams.
Who owns the project?
A named senior lead remains accountable for the outcome. Product, design, engineering, integration and QA roles are assembled around the problem, not sold as disconnected seats.
What happens after go-live?
We can remain responsible for platform health, maintenance and continuous product development through a defined monthly rhythm and explicit response times.
A USEFUL FIRST CONVERSATION