Log in
Have an Account?
Log in to check out faster.
The IFG eCommerce Protocol is the method I use, Francesco Guiducci, to analyse and design Shopify stores by connecting theme structure, data, usability, performance and maintenance. It starts from a simple principle: before adding code, apps or a redesign, we need to understand which problem we are trying to solve and how we will verify the result.
The method is designed for Shopify stores on Basic, Grow and Advanced. It does not promise a store that will never have bugs or automatic sales results: it is used to reduce unnecessary complexity, make the architecture clearer and build a foundation that can be tested and improved over time.
Design and technical work are not separate activities. Effective visual hierarchy must coexist with maintainable components, consistent data, verified responsive behaviour and an understandable buying journey.
Overlapping apps, scripts left behind by old installations, duplicated components and undocumented customizations can make a store harder to maintain and, in some cases, affect performance or stability.
In the Protocol I treat this set of dependencies as technical debt. This does not mean that every app or line of code is a problem: first I identify its function and dependencies, then I decide what to keep, simplify or remove. The goal is to reduce complexity without losing useful functionality.
When a feature can be managed well by the theme or Shopify, I prefer a native solution before introducing a new dependency. Liquid, Online Store 2.0 sections, Metaobjects and Metafields make it possible to build components and data that merchants can manage without automatically relying on an app.
Performance is not defined with adjectives: I measure the available metrics on the real store and check for regressions after changes. Even a clean architecture can be affected by images, content, external services and apps added later.
Speed, stability and usability can influence the buying experience, but there is no formula that automatically turns milliseconds into revenue. The Protocol helps distinguish measurable technical problems from commercial hypotheses and define a sequence of interventions that can be verified.
Errors, duplication and unnecessary dependencies come first; optimizations come afterwards. When the outcome also depends on traffic, product, pricing or market, I state that explicitly instead of attributing to the theme an effect that cannot be demonstrated.
I analyse assets, apps, scripts and theme code to identify bottlenecks that can be changed. The result is verified using the available metrics; I do not promise to make a store the fastest in its niche or to achieve identical values across different devices, pages and conditions.
Hierarchy, navigation, product pages and calls to action are designed to reduce friction and make the buying journey understandable. Design decisions are linked to observable problems rather than universal psychological formulas.
Design should communicate the value of the brand and product consistently. It can contribute to perceived quality, but prices, margins and conversions depend on multiple factors and are not presented as an automatic consequence of visual style.
The IFG eCommerce Protocol brings together procedures, criteria and checks I use in Shopify work: technical debt, theme structure, data, performance, apps, maintenance and development decisions.
It is designed for merchants who want to understand how to assess their store and make technical decisions more independently. It is not a growth formula or a promise about the future value of a business: it is an operational tool to adapt to the real context.
A store evolves continuously: new apps, campaigns, products and theme changes can alter how the site behaves. The Protocol is used to maintain a clear baseline, understand what changed and verify that a local improvement does not introduce a regression elsewhere.
The priority is not to add more technology, but to use what is necessary and keep the system understandable over time.
It is the method I use to connect analysis, design, development and verification on Shopify. It considers theme, data, dependencies, usability and performance together to decide what to change, what to leave unchanged and how to check the result.
No. During the Audit, I first check the state of the store and try to preserve what works. I propose a complete redesign only when the theme, structure or technical problems justify it; otherwise, I identify targeted interventions. I define and quote custom solutions after this analysis.
The goal is to keep everything that can be managed safely by the merchant inside the Theme Editor and Shopify admin. Customizations that require code remain technical work, but I avoid creating unnecessary dependencies or components that are difficult to understand and maintain.
No. It can help identify technical inefficiencies, overlap and friction that can be changed, but sales, margins and costs also depend on product, traffic, market, pricing and operational processes. Technical benefits are verified within the scope that was actually changed.
Yes, when it helps avoid unnecessary complexity from the start. On a small project the best solution can be simpler: few dependencies, clear structure and features suited to real needs. Complexity is added only when the business requires it.
View my profile and the reviews published in the official Shopify Partner Directory. View now
Read the reviews published on my Google Business profile. View now
Read the reviews published on Trustpilot for IFG eCommerce. View now
