Where every click, shelf, and checkout is the customer experience.
We built and continue to evolve Ricoh's Adobe Commerce platform across twelve stores in Latin America, one per country, including custom payment gateways for the region's complexity and a module library that keeps the whole operation moving forward.
We redesigned New Balance's Chilean storefront end to end (its own theme, listing and product pages, recommendation carousels) inside the multi-brand Adobe Commerce platform it shares with Sparta and Speedo. On that same platform we ran the upgrade to 2.4.7-p6, built split fulfillment so a single order can ship from the distribution center and the stores at once, and tune performance before every Cyber and Black Friday.
One of the largest retail groups in Latin America and the Caribbean runs 29 Adobe Commerce stores across two instances: multiple brands, multiple countries, one shared base. Adobe Analytics had been deployed without a unified measurement model or technical governance, so no two reports could be compared. We audited both instances and ordered the priorities by impact, worked performance in incremental releases that never paused the operation, and reimplemented tracking from the ground up: new tags and dashboards per brand, per country.
Stock that didn't match, pricing and checkout throwing errors, and a site that kept going down. The result was simple: it wasn't selling. We put a multidisciplinary squad on site in Mexico (architecture, backend, frontend and data managed as one team) and migrated in sections, releasing piece by piece so no single deploy could take the store with it. Login, SSO, CDN and the store locator were resolved along the way.
Where every country brings its own ERP, rules and payment gateway.
An operation inherited from another agency, with a queue of stores still to migrate and a different ERP, ruleset, integration and payment gateway in every country. We went from discovery to a 100% agency handover in one week without pausing sales, then created and migrated more than fourteen sites, brand by brand, over the next three months. Reusing a common base across sites cut development hours by 30% against what the previous agency was billing.
Where the brand owns the product but rarely owns the customer relationship.
Granado has been making soaps and botanical remedies in Brazil since 1870. Today it sells through three storefronts on one Adobe Commerce platform (B2C Brazil, a B2B operation in the United States built from scratch, and an international B2B/B2C front) with the Phebo brand running alongside. We rebuilt the checkout as a single page, integrated LS Retail so stores, stock and orders finally speak the same language, and programmed the delivery rules the business actually runs on: cut-off times per store, dark-store fulfillment, order limits per branch. Every year the whole thing gets stress-tested during Semana Granado, and every year we audit and tune the platform before it starts.
Where trust is the product and experience is the proof.
Itaú operates a marketplace where official brand stores sell alongside the catalog, and customers pay with loyalty points as readily as with a card. We've run that Adobe Commerce platform since 2024 on a monthly support cycle (more than six hundred support tickets and close to four hundred evolutions) while doing the work that never fits inside a ticket: a full upgrade to 2.4.7-p5, an attribute model rebuilt and scripted clean so sellers could publish without breaking the catalog, asynchronous processing for the sellers API, database indexing and layered-navigation tuning, and a preventive plan written after an incident so it would not happen twice.
A complete visual overhaul plus a strategic content restructure that turned the bank's digital presence into a modern, governed platform built for financial services. Twelve months from discovery to go-live on AEM as a Cloud Service, with more than 350 pages created and migrated, Target and Analytics for personalization and measurement, and the hard integrations (Drupal, Velocify and a complex branch locator) resolved inside the scope.
Where the customer experience is the only thing that isn't a commodity.
We rebuilt Brightspeed's digital platform on AEM as a Cloud Service across four stages: UX diagnosis and digital strategy, high-fidelity prototyping validated interaction by interaction, implementation of components, templates, experience and content fragments, GraphQL and geolocation, and an incremental go-live. The new site ran in parallel with the legacy one for months, so business continuity never broke.
GTD sells to residential, business and enterprise customers on Adobe Commerce Cloud, across the GTD and Telsur brands. We took the operation over in May 2026 (repository ownership, integration endpoints, environments) and kept it selling the whole way through. Since then: the upgrade to Adobe Commerce Cloud 2.4.8-p4, and a new self-service B2B channel for the SMB segment, with net-plus-VAT pricing, installation costs shown even when they are zero, legal document upload, a fifteen-minute hold on the order, and field-visit scheduling wired to TOA. Monthly support runs alongside all of it: Transbank Webpay, tax-ID validation at checkout, zonal delivery rules, promotional pricing tiers.
Where the digital experience has to match the precision of the product.
We took part in the migration of Toyota's digital platform from Adobe Experience Manager on-prem to AEM as a Cloud Service, a technical challenge held to the highest bar for architecture and security, run alongside four other AEM vendors on the same platform. UI/UX, frontend, backend and module integration in a single delivery flow. Eight years in, the relationship is still going.
We took control of Porsche's Adobe Commerce platform in July 2025 (inherited code, inherited environments) and began with the engineering basics: a code checker, deploy markers, a tightened CORS policy. Then the commerce work. Dealerships sell as sellers, so grouped products now show which dealership is behind a kit and exactly which SKUs it contains. Customers keep a garage of their own cars, so accessories match the vehicle they actually own. Carts are shared and filled straight from WhatsApp. Checkout stopped forcing a login. A year on, we still run it: monthly support, deploys, and Adobe security patches applied as they land.
Not every engagement becomes a case study, but every one of these clients trusted Improntus to deliver.
Every case study on this page started the same way: a conversation about one problem. The commerce migration that couldn't slip. The data strategy that needed to be real. The content operation that needed to scale. Whatever your version of that problem is, we'd like to hear it.
Prefer to book a call or reach out on LinkedIn? Visit our Contact page.