Frequently asked questions

We work with VTEX (IO and Legacy), Shopify (Liquid and Hydrogen), deco.cx and Nuvemshop. Each project is individually evaluated to recommend the platform that best fits the operation.

VTEX IO is VTEX's modern framework for building storefronts with React and Node.js. It offers automated deployment, an app system and serverless infrastructure, which speeds up development and simplifies maintenance.

Yes. deco.cx uses Fresh (Deno) and Preact to deliver stores with extreme performance and edge rendering. It is an excellent option for operations that prioritize speed and Core Web Vitals.

It is an architecture where the front-end (the store the customer sees) is separated from the back-end (catalog, checkout, payments). This allows more design freedom, better performance and integration with any CMS or external system.

It depends on the size of the operation, order volume, integrations and budget. VTEX handles robust operations, Shopify is ideal for agility, deco.cx for maximum performance and Nuvemshop for those starting to scale.

Yes. We take care of the entire process: catalog mapping, 301 redirects, content migration, ERP and payment gateway integration. The goal is zero organic traffic loss and operational continuity.

Yes. We build institutional websites with the same technical rigor as stores: optimized performance, advanced SEO, accessibility and responsive design. We use Next.js or whichever stack makes the most sense for the project.

Implementation means building the store from scratch. Evolution means developing new features and continuous improvements. Support means keeping the store stable day-to-day: bug fixes, monitoring and technical support with SLA.

Yes. After each delivery, we run training sessions so your team can operate the admin panel, edit content and understand the publishing workflow. Everything is documented and recorded.

Yes. All implementations are built so that texts, images and banners can be updated through the platform's admin panel or CMS, without depending on a developer.

We work with monthly hour packages dedicated to improvements, new features and optimizations. We define priorities together at each sprint and you follow everything in real time.

Yes. Technical SEO and performance are part of every delivery. We optimize Core Web Vitals, URL structure, meta tags, structured data, lazy loading and asset compression in every project.

It depends on the scope. A standard store takes 6 to 12 weeks. More complex projects with ERP integration, custom checkout and multiple channels can take 3 to 5 months. We define a realistic timeline during the diagnosis.

We follow four stages: diagnosis (technical audit), plan (scope and priorities), execution (sprints with frequent deliveries) and follow-up (monitoring and routine meetings). Everything with direct communication.

After launch, we enter follow-up mode: we monitor metrics, fix bugs that appear in production and prioritize improvements based on real usage and conversion data.

We use business metrics (conversion rate, average ticket, revenue) and technical metrics (Core Web Vitals, uptime, load time). We share dashboards and review them together in routine meetings.

Yes. Deliveries happen in short 1 to 2 week cycles. Each sprint has a defined scope, code review and production deployment. You follow progress in real time through the repository.

Direct communication, no middlemen. We use Slack or WhatsApp for day-to-day and weekly meetings for alignment. You talk directly to the person writing the code.

Each project is individually quoted. The cost depends on the platform, integration complexity, visual customizations and specific features. We send a detailed proposal after the diagnosis.

Implementations are priced per project with a fixed scope. Evolution and support work with monthly hour packages. In both cases, you know exactly what you will receive and for how much.

The platform has its own cost (VTEX license, Shopify plan, etc). Our support service is contracted separately with an hour package and defined SLA. There are no surprise charges.

They are Google metrics that evaluate user experience: LCP (loading speed), INP (interactivity) and CLS (visual stability). Stores with good scores rank higher and convert more.

The SLA defines response and resolution times by severity. Critical issues (store down) get a response within 1 hour. Minor bugs within 24 hours. Terms are agreed upon in the support contract.

Yes. We integrate with ERPs (Bling, Tiny, SAP), payment gateways, logistics platforms, CRMs and marketing tools. We use REST APIs, webhooks and middleware when necessary.

All code goes through code review, follows linting standards (ESLint, Prettier), uses TypeScript for typing and has automated tests when applicable. Nothing goes to production without review.

Yes. We set up GA4, GTM, e-commerce dataLayer, conversion events and integration with Google Ads and Meta Ads. Tracking is validated before go-live to ensure accurate data from day one.

The platforms we use (VTEX, Shopify) already offer secure infrastructure with SSL, CDN and DDoS protection. On the code side, we follow security best practices: input sanitization, protection headers and continuous monitoring.