We are not just a remote agency. We are an active part of the ecosystem. We believe in Open Source and contributing back to the community that powers over 40% of the web (W3Techs).
In Lyon's competitive market, site speed is your strongest SEO asset. Our Astro + Headless WP stack delivers performance that leaves competitors behind.
For businesses in Lyon serving Local SMB and Enterprise, data security is paramount. Headless architecture virtually eliminates standard WordPress attack vectors.
An online store in Lyon sits in Part-Dieu, in a Confluence startup office or in a Gerland laboratory shipping reagents across France. That is not a reason for WooCommerce to pretend it is an SAP replacement or a congress booking platform for Centre de Congrès. It is a reason for checkout, TVA logic, payment gateways and order workflows to be written the way a French legal team, an FR/EN shop manager and a compliance officer who reads GDPR and CNIL expect, not just the way a Lighthouse score expects.
WPPoland builds this WooCommerce from a senior Polish team for businesses in Lyon and Métropole de Lyon. Scope is WooCommerce development: custom checkout, Payplug and Stripe integration, Colissimo shipping, B2B wholesale, ERP sync and code review on Git. WordPress theme work, maintenance retainers and contact are separate topics, with links at the end.
Lyon is France’s second-largest economic centre after Paris, a city with a chemical and pharmaceutical tradition, biotechnology in Gerland, logistics along the Rhône and a growing digital ecosystem around Confluence and Lyon Digital Hub. This is not Paris fintech or the Côte d’Azur tourist market. Here WooCommerce often serves B2B parts catalogues, laboratory consumables, industrial equipment with quotation workflows, or D2C brands in Part-Dieu that must survive a product launch in the same week a lawyer asks about EU hosting and CNIL consent for checkout tracking pixels.
Part-Dieu is France’s second-largest business district after La Défense. Towers, Gare de Lyon-Part-Dieu, conference hotels and corporate offices create a context where WooCommerce holds product catalogues, B2B wholesale portals, demo-to-order flows and employer-branding shops for firms that just closed a funding round or prepare a cross-border campaign for the French and German markets. A gateway webhook failing on Friday evening or a TVA miscalculation on a wholesale order hurts during a Part-Dieu congress week or before an investor meeting, not in August.
Confluence is the district south of Lyon, around Musée des Confluences and a newer startup ecosystem. Lyon Digital Hub and communities such as Silicon Rhône meet in this area. WooCommerce serves SaaS add-on shops, beta product pre-orders, subscription boxes and FR/EN multilingual storefronts for firms selling across the European Union. A brief from a client here often sounds like: “we have WooCommerce with twenty plugins, checkout breaks after every update, and the CTO wants Payplug, Git and a checkout that does not lose TVA on cross-border carts”. That is a gateway, tax and delivery-process problem, not a marketplace template problem.
Gerland and the Lyonbiopôle biotechnology park are a different profile from a Part-Dieu corporation. More regulated products, more batch numbers, more forms collecting personal data under GDPR and more audit-trail requirements on who changed checkout settings. WooCommerce in this environment is a laboratory consumables shop, a reagent catalogue with SIRET-gated B2B pricing, or a spin-off D2C site that collects orders and must respect France’s Loi Informatique et Libertés and CNIL guidance on cookies and tracking.
The chemical and industrial sector in the Lyon metropolitan area generates another profile: parts catalogues with thousands of SKUs, quotation request flows that convert to orders, distributor portals with role-based pricing and FR/DE content for cross-border clients from Alsace or Switzerland. WooCommerce must survive a traffic spike after a new product line announcement at Eurexpo, not just look good on a laptop in a Part-Dieu office.
The typical project that reaches senior developers in Lyon does not sound like “make us a nice shop”. It sounds like: inherited Elementor checkout, a Gerland laboratory launching a B2B catalogue in a narrow time window, Payplug 3DS failing on mobile Safari, TVA showing incorrectly on intra-EU B2B orders with a valid VAT number, and a seasonal campaign built by duplicating last year’s coupon rules manually. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
A new WooCommerce build in Lyon starts with a decision that costs months if you get it wrong: which gateways handle which flows, how TVA displays at checkout, and what lives in a custom plugin versus the theme. That decision is written down before the first commit.
French buyers expect Carte Bancaire through a local acquirer. Payplug is the gateway many Lyon firms already use; Stripe covers international cards, Apple Pay and recurring subscriptions; Mollie appears when the firm also sells in Belgium or the Netherlands. Each gateway gets a runbook: supported flows (one-shot, recurring, refunds, partial refunds, 3DS), test card matrix, webhook endpoints, idempotency handling and reconciliation against WooCommerce order statuses.
We do not modify WooCommerce core. Customisation goes through documented action and filter hooks, plus a custom plugin and theme split where it belongs. Checkout field changes, B2B SIRET validation, conditional payment methods by customer role and custom order statuses live in the plugin. Presentation of product cards, category layouts and cart styling live in the theme. If wholesale pricing disappears after a theme change, the architecture was wrong.
Gateway integration QA on staging covers the full path: cart, checkout, payment with test cards on every active gateway, webhook receipt, order confirmation email, admin order edit, refund and partial refund, including failure paths where 3DS times out or the webhook arrives twice. A Payplug webhook that creates duplicate orders is a production incident, not a backlog ticket.
France applies TVA at standard and reduced rates depending on product type. B2B sales within the EU with a valid VAT number may qualify for reverse charge. WooCommerce tax settings copied from a US template produce wrong totals on the first real order from a distributor in Alsace or Geneva.
What we configure in the brief and the code:
We do not sell tax advice. We ensure WooCommerce configuration matches what stands in the politique de confidentialité and what the client’s fiscal counsel documented.
France applies GDPR alongside the national Loi Informatique et Libertés. The supervisory authority is the Commission Nationale de l’Informatique et des Libertés (CNIL). For a WooCommerce store in Lyon that is not an abstract legal paragraph. It is decisions in checkout fields, account creation, marketing opt-in, consent plugins, politique de confidentialité and audit logs.
What we write into the brief and the code:
CNIL publishes recommendations on cookies and tracking that affect GTM, Meta Pixel and Klaviyo on product pages. A consent banner copied from a German shop is not automatically CNIL-aligned, and no banner is not automatically legal when tracking runs. We do not sell legal opinions. We ensure tools on the store match what stands in the politique de confidentialité, and that after a GTM or consent-plugin update consent logs still record correctly.
B2B wholesale is not D2C checkout with a login form. In Lyon the pattern repeats: a chemical supplier in the Rhône-Alpes region, a Gerland laboratory selling consumables to partner clinics, a Part-Dieu firm with tiered pricing by customer role and minimum order quantities.
We implement wholesale with role-based pricing, request-for-quote workflows where the catalogue is too complex for instant checkout, and account approval gates for new B2B registrants. Product data import from ERP systems, CSV feeds or supplier APIs runs on Action Scheduler with conflict resolution, not manual CSV uploads every Monday.
A parts catalogue with ten thousand SKUs needs faceted search, cached category queries and a checkout that does not recalculate shipping on every keystroke. We audit the actual bottleneck before adding plugins: heavy theme, autoloaded options, slow meta queries, cart fragments firing on unrelated pages.
Layer comparison at kickoff:
| Layer | What lives there | Example in Lyon |
|---|---|---|
| Theme | product presentation, cart styling | Part-Dieu brand shop, category layout |
| Plugin | wholesale roles, TVA logic, ERP sync | B2B pricing, SIRET validation, inventory webhook |
| WooCommerce core | orders, products, tax engine | untouched, extended via hooks |
| Staging and Git | process, not feature | branch, review, freeze before campaign |
Shipping in France is not flat-rate everywhere. Colissimo, Chronopost, DPD and DHL appear depending on product weight, dimensions and destination. WooCommerce shipping zones must match what the warehouse actually dispatches, not what a default plugin assumes.
We configure zone-based rates, weight and dimension rules, carrier API integrations where real-time quotes matter, and tracking numbers that flow back to customer emails and ERP systems. Cross-border EU shipping from a warehouse in Vénissieux or Saint-Priest needs zones that align with TVA logic documented in the previous section.
For seasonal campaigns and Eurexpo product launches, we load-test checkout and shipping calculation before the traffic spike, not after the first hour of failed orders.
Personal data under GDPR raises the question: which jurisdiction hosts the server. OVH in France, Scaleway in Paris, AWS in Ireland (eu-west-1), Hetzner in Germany, Claranet in Lyon are different answers for a compliance officer, but all sit within the EU. Ashburn or Hillsboro is the United States and usually a veto without Standard Contractual Clauses or another transfer basis.
The question “is hosting in Lyon” comes up less often than “is it in the EU”. The operational answer is two-part. Jurisdiction: EU, order and customer data does not move overnight to a US bucket without agreement. Latency: origin in France or Ireland plus a CDN with TLS termination in the EU usually suffices for buyers in Lyon and central Europe. Residency decisions go into the runbook, not a slogan.
Multilingual FR/EN (sometimes FR/DE for Alsace or Swiss clients) requires a separate architectural decision. WPML or Polylang for traditional WooCommerce, or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. A French checkout with SIRET and TVA intracommunautaire fields and an English version without those fields are not a 1:1 copy but two templates with different validation rules.
Congress events in Part-Dieu, trade fairs at Eurexpo or product campaigns targeting the French and German markets create windows where hundreds of firms watch product landings, checkout flows and payment gateways. A store failure mid-congress week is not a “bug for the backlog”. It is lost revenue and reputation damage with partners who have a full calendar for the quarter.
The deployment runbook for clients in Lyon includes a production deploy freeze for campaign windows, usually from two weeks before an event until one week after. Critical security updates go through staging and a night window; everything else waits. That is not a developer preference. It is an operational decision agreed with the client before the season. Anyone doing a “small gateway patch” on congress Monday learns when checkout does not survive the traffic spike from attendees’ phones.
ERP and inventory sync is the most common integration point for Part-Dieu firms and chemical producers. In practice that means connecting WooCommerce to SAP Business One, Sage, EBP or a custom warehouse system, with webhook documentation, an error matrix and end-to-end testing on staging before production deployment.
For Confluence firms the second recurring integration is subscription or SaaS add-on billing: Stripe Billing, WooCommerce Subscriptions, licence key delivery after payment. Every integration gets idempotency handling so a duplicate webhook does not ship two licence keys.
For Gerland laboratories the third integration is regulated product data: batch numbers, expiry dates, restricted shipping zones. Order meta and fulfilment workflows must survive a plugin update. A laboratory that loses CNIL consent logs or order audit trails after a patch produces a compliance incident, not a UX ticket.
Every WooCommerce project in Lyon follows a structured process that minimises risk and maximises transparency:
Businesses in Lyon regularly come to us with these problems:
Core Web Vitals are a Google ranking factor and a conversion factor on a store collecting orders during a seasonal campaign or congress week in Lyon. We do not promise a specific percentage delta before audit, because improvement scale depends on the starting state of each installation. What we do systematically:
Every performance decision is data-driven. We measure before and after, document impact and include a performance baseline in project documentation so regression after the next plugin update is visible immediately, not after the fact in a congress window.
A well-built store is valuable only when your target audience in Lyon and Métropole de Lyon can find it. Our WooCommerce development projects include foundational SEO architecture from the first sketch:
SEO is not a post-launch add-on. It is part of architectural decisions from the first sketch.
Can you migrate our existing store? Yes. We handle migrations from Shopify, PrestaShop, Magento and other platforms to WooCommerce, and between hosting providers. Every migration includes URL mapping, 301 redirect implementation, product data validation and SEO monitoring for 90 days after migration, with congress or seasonal campaign calendars considered so migration does not land in a critical window.
Do you work with firms outside Lyon? Yes. We know the local context (Part-Dieu, Confluence, Gerland, Lyon Digital Hub), but we work with clients across France and abroad. Many firms in Lyon serve clients in Paris, Alsace and across the European Union without a separate page for each city.
How do you handle multilingual stores? We implement multilingual setups through WPML or Polylang for traditional WooCommerce, or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. For firms serving the French and German markets, FR/EN/DE locale configuration requires a separate architectural decision.
What does ongoing support include? After build completion the store can move to dedicated WordPress maintenance in Lyon: tested updates, backups, security and performance monitoring, and priority support with a documented runbook. Details are on the maintenance page, not in this development brief.
How does working with WPPoland differ from a local agency in Lyon? Primarily WooCommerce experience since 2007, our own technical stack on Astro and headless WordPress, and work on clear assumptions: scope, stages and responsibility are described before deployment. Pricing is individual and depends on scope, not a fixed price list.
If your firm needs WordPress development without a full ecommerce rebuild, we have a dedicated page on WordPress developer in Lyon with block themes, Gutenberg, CPT and GDPR with CNIL preparation. If the current store works and needs only ongoing care, tested updates and monitoring, see WordPress maintenance in Lyon. Both describe the same technical stack from a different angle, not a duplicate sales pitch.
The full scope of WooCommerce development work (checkout, gateways, wholesale, refactors) is described on the WooCommerce developer pillar. To discuss a brief, send a short description of your current situation through the contact form.
If you want to discuss WooCommerce development, send a short description of your current store, business goal and technical constraints. From that we review the configuration, identify risks and propose a practical action plan.
If you are planning a new build, checkout refactor or gateway migration before a Part-Dieu campaign or Eurexpo trade fair, start by writing down goals, constraints and current project state. Pricing is individual and depends on the scope of work.
We serve clients in Lyon and nearby areas.
This page features specific insights for Lyon.
An online store in Lyon sits in Part-Dieu, in a Confluence startup office or in a Gerland laboratory shipping reagents across France. That is not a reason for WooCommerce to pretend it is an SAP replacement or a congress booking platform for Centre de Congrès. It is a reason for checkout, TVA logic, payment gateways and order workflows to be written the way a French legal team, an FR/EN shop manager and a compliance officer who reads GDPR and CNIL expect, not just the way a Lighthouse score expects.
WPPoland builds this WooCommerce from a senior Polish team for businesses in Lyon and Métropole de Lyon. Scope is WooCommerce development: custom checkout, Payplug and Stripe integration, Colissimo shipping, B2B wholesale, ERP sync and code review on Git. WordPress theme work, maintenance retainers and contact are separate topics, with links at the end.
Lyon is France’s second-largest economic centre after Paris, a city with a chemical and pharmaceutical tradition, biotechnology in Gerland, logistics along the Rhône and a growing digital ecosystem around Confluence and Lyon Digital Hub. This is not Paris fintech or the Côte d’Azur tourist market. Here WooCommerce often serves B2B parts catalogues, laboratory consumables, industrial equipment with quotation workflows, or D2C brands in Part-Dieu that must survive a product launch in the same week a lawyer asks about EU hosting and CNIL consent for checkout tracking pixels.
Part-Dieu is France’s second-largest business district after La Défense. Towers, Gare de Lyon-Part-Dieu, conference hotels and corporate offices create a context where WooCommerce holds product catalogues, B2B wholesale portals, demo-to-order flows and employer-branding shops for firms that just closed a funding round or prepare a cross-border campaign for the French and German markets. A gateway webhook failing on Friday evening or a TVA miscalculation on a wholesale order hurts during a Part-Dieu congress week or before an investor meeting, not in August.
Confluence is the district south of Lyon, around Musée des Confluences and a newer startup ecosystem. Lyon Digital Hub and communities such as Silicon Rhône meet in this area. WooCommerce serves SaaS add-on shops, beta product pre-orders, subscription boxes and FR/EN multilingual storefronts for firms selling across the European Union. A brief from a client here often sounds like: “we have WooCommerce with twenty plugins, checkout breaks after every update, and the CTO wants Payplug, Git and a checkout that does not lose TVA on cross-border carts”. That is a gateway, tax and delivery-process problem, not a marketplace template problem.
Gerland and the Lyonbiopôle biotechnology park are a different profile from a Part-Dieu corporation. More regulated products, more batch numbers, more forms collecting personal data under GDPR and more audit-trail requirements on who changed checkout settings. WooCommerce in this environment is a laboratory consumables shop, a reagent catalogue with SIRET-gated B2B pricing, or a spin-off D2C site that collects orders and must respect France’s Loi Informatique et Libertés and CNIL guidance on cookies and tracking.
The chemical and industrial sector in the Lyon metropolitan area generates another profile: parts catalogues with thousands of SKUs, quotation request flows that convert to orders, distributor portals with role-based pricing and FR/DE content for cross-border clients from Alsace or Switzerland. WooCommerce must survive a traffic spike after a new product line announcement at Eurexpo, not just look good on a laptop in a Part-Dieu office.
The typical project that reaches senior developers in Lyon does not sound like “make us a nice shop”. It sounds like: inherited Elementor checkout, a Gerland laboratory launching a B2B catalogue in a narrow time window, Payplug 3DS failing on mobile Safari, TVA showing incorrectly on intra-EU B2B orders with a valid VAT number, and a seasonal campaign built by duplicating last year’s coupon rules manually. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
A new WooCommerce build in Lyon starts with a decision that costs months if you get it wrong: which gateways handle which flows, how TVA displays at checkout, and what lives in a custom plugin versus the theme. That decision is written down before the first commit.
French buyers expect Carte Bancaire through a local acquirer. Payplug is the gateway many Lyon firms already use; Stripe covers international cards, Apple Pay and recurring subscriptions; Mollie appears when the firm also sells in Belgium or the Netherlands. Each gateway gets a runbook: supported flows (one-shot, recurring, refunds, partial refunds, 3DS), test card matrix, webhook endpoints, idempotency handling and reconciliation against WooCommerce order statuses.
We do not modify WooCommerce core. Customisation goes through documented action and filter hooks, plus a custom plugin and theme split where it belongs. Checkout field changes, B2B SIRET validation, conditional payment methods by customer role and custom order statuses live in the plugin. Presentation of product cards, category layouts and cart styling live in the theme. If wholesale pricing disappears after a theme change, the architecture was wrong.
Gateway integration QA on staging covers the full path: cart, checkout, payment with test cards on every active gateway, webhook receipt, order confirmation email, admin order edit, refund and partial refund, including failure paths where 3DS times out or the webhook arrives twice. A Payplug webhook that creates duplicate orders is a production incident, not a backlog ticket.
France applies TVA at standard and reduced rates depending on product type. B2B sales within the EU with a valid VAT number may qualify for reverse charge. WooCommerce tax settings copied from a US template produce wrong totals on the first real order from a distributor in Alsace or Geneva.
What we configure in the brief and the code:
We do not sell tax advice. We ensure WooCommerce configuration matches what stands in the politique de confidentialité and what the client’s fiscal counsel documented.
France applies GDPR alongside the national Loi Informatique et Libertés. The supervisory authority is the Commission Nationale de l’Informatique et des Libertés (CNIL). For a WooCommerce store in Lyon that is not an abstract legal paragraph. It is decisions in checkout fields, account creation, marketing opt-in, consent plugins, politique de confidentialité and audit logs.
What we write into the brief and the code:
CNIL publishes recommendations on cookies and tracking that affect GTM, Meta Pixel and Klaviyo on product pages. A consent banner copied from a German shop is not automatically CNIL-aligned, and no banner is not automatically legal when tracking runs. We do not sell legal opinions. We ensure tools on the store match what stands in the politique de confidentialité, and that after a GTM or consent-plugin update consent logs still record correctly.
B2B wholesale is not D2C checkout with a login form. In Lyon the pattern repeats: a chemical supplier in the Rhône-Alpes region, a Gerland laboratory selling consumables to partner clinics, a Part-Dieu firm with tiered pricing by customer role and minimum order quantities.
We implement wholesale with role-based pricing, request-for-quote workflows where the catalogue is too complex for instant checkout, and account approval gates for new B2B registrants. Product data import from ERP systems, CSV feeds or supplier APIs runs on Action Scheduler with conflict resolution, not manual CSV uploads every Monday.
A parts catalogue with ten thousand SKUs needs faceted search, cached category queries and a checkout that does not recalculate shipping on every keystroke. We audit the actual bottleneck before adding plugins: heavy theme, autoloaded options, slow meta queries, cart fragments firing on unrelated pages.
Layer comparison at kickoff:
| Layer | What lives there | Example in Lyon |
|---|---|---|
| Theme | product presentation, cart styling | Part-Dieu brand shop, category layout |
| Plugin | wholesale roles, TVA logic, ERP sync | B2B pricing, SIRET validation, inventory webhook |
| WooCommerce core | orders, products, tax engine | untouched, extended via hooks |
| Staging and Git | process, not feature | branch, review, freeze before campaign |
Shipping in France is not flat-rate everywhere. Colissimo, Chronopost, DPD and DHL appear depending on product weight, dimensions and destination. WooCommerce shipping zones must match what the warehouse actually dispatches, not what a default plugin assumes.
We configure zone-based rates, weight and dimension rules, carrier API integrations where real-time quotes matter, and tracking numbers that flow back to customer emails and ERP systems. Cross-border EU shipping from a warehouse in Vénissieux or Saint-Priest needs zones that align with TVA logic documented in the previous section.
For seasonal campaigns and Eurexpo product launches, we load-test checkout and shipping calculation before the traffic spike, not after the first hour of failed orders.
Personal data under GDPR raises the question: which jurisdiction hosts the server. OVH in France, Scaleway in Paris, AWS in Ireland (eu-west-1), Hetzner in Germany, Claranet in Lyon are different answers for a compliance officer, but all sit within the EU. Ashburn or Hillsboro is the United States and usually a veto without Standard Contractual Clauses or another transfer basis.
The question “is hosting in Lyon” comes up less often than “is it in the EU”. The operational answer is two-part. Jurisdiction: EU, order and customer data does not move overnight to a US bucket without agreement. Latency: origin in France or Ireland plus a CDN with TLS termination in the EU usually suffices for buyers in Lyon and central Europe. Residency decisions go into the runbook, not a slogan.
Multilingual FR/EN (sometimes FR/DE for Alsace or Swiss clients) requires a separate architectural decision. WPML or Polylang for traditional WooCommerce, or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. A French checkout with SIRET and TVA intracommunautaire fields and an English version without those fields are not a 1:1 copy but two templates with different validation rules.
Congress events in Part-Dieu, trade fairs at Eurexpo or product campaigns targeting the French and German markets create windows where hundreds of firms watch product landings, checkout flows and payment gateways. A store failure mid-congress week is not a “bug for the backlog”. It is lost revenue and reputation damage with partners who have a full calendar for the quarter.
The deployment runbook for clients in Lyon includes a production deploy freeze for campaign windows, usually from two weeks before an event until one week after. Critical security updates go through staging and a night window; everything else waits. That is not a developer preference. It is an operational decision agreed with the client before the season. Anyone doing a “small gateway patch” on congress Monday learns when checkout does not survive the traffic spike from attendees’ phones.
ERP and inventory sync is the most common integration point for Part-Dieu firms and chemical producers. In practice that means connecting WooCommerce to SAP Business One, Sage, EBP or a custom warehouse system, with webhook documentation, an error matrix and end-to-end testing on staging before production deployment.
For Confluence firms the second recurring integration is subscription or SaaS add-on billing: Stripe Billing, WooCommerce Subscriptions, licence key delivery after payment. Every integration gets idempotency handling so a duplicate webhook does not ship two licence keys.
For Gerland laboratories the third integration is regulated product data: batch numbers, expiry dates, restricted shipping zones. Order meta and fulfilment workflows must survive a plugin update. A laboratory that loses CNIL consent logs or order audit trails after a patch produces a compliance incident, not a UX ticket.
Every WooCommerce project in Lyon follows a structured process that minimises risk and maximises transparency:
Businesses in Lyon regularly come to us with these problems:
Core Web Vitals are a Google ranking factor and a conversion factor on a store collecting orders during a seasonal campaign or congress week in Lyon. We do not promise a specific percentage delta before audit, because improvement scale depends on the starting state of each installation. What we do systematically:
Every performance decision is data-driven. We measure before and after, document impact and include a performance baseline in project documentation so regression after the next plugin update is visible immediately, not after the fact in a congress window.
A well-built store is valuable only when your target audience in Lyon and Métropole de Lyon can find it. Our WooCommerce development projects include foundational SEO architecture from the first sketch:
SEO is not a post-launch add-on. It is part of architectural decisions from the first sketch.
Can you migrate our existing store? Yes. We handle migrations from Shopify, PrestaShop, Magento and other platforms to WooCommerce, and between hosting providers. Every migration includes URL mapping, 301 redirect implementation, product data validation and SEO monitoring for 90 days after migration, with congress or seasonal campaign calendars considered so migration does not land in a critical window.
Do you work with firms outside Lyon? Yes. We know the local context (Part-Dieu, Confluence, Gerland, Lyon Digital Hub), but we work with clients across France and abroad. Many firms in Lyon serve clients in Paris, Alsace and across the European Union without a separate page for each city.
How do you handle multilingual stores? We implement multilingual setups through WPML or Polylang for traditional WooCommerce, or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. For firms serving the French and German markets, FR/EN/DE locale configuration requires a separate architectural decision.
What does ongoing support include? After build completion the store can move to dedicated WordPress maintenance in Lyon: tested updates, backups, security and performance monitoring, and priority support with a documented runbook. Details are on the maintenance page, not in this development brief.
How does working with WPPoland differ from a local agency in Lyon? Primarily WooCommerce experience since 2007, our own technical stack on Astro and headless WordPress, and work on clear assumptions: scope, stages and responsibility are described before deployment. Pricing is individual and depends on scope, not a fixed price list.
If your firm needs WordPress development without a full ecommerce rebuild, we have a dedicated page on WordPress developer in Lyon with block themes, Gutenberg, CPT and GDPR with CNIL preparation. If the current store works and needs only ongoing care, tested updates and monitoring, see WordPress maintenance in Lyon. Both describe the same technical stack from a different angle, not a duplicate sales pitch.
The full scope of WooCommerce development work (checkout, gateways, wholesale, refactors) is described on the WooCommerce developer pillar. To discuss a brief, send a short description of your current situation through the contact form.
If you want to discuss WooCommerce development, send a short description of your current store, business goal and technical constraints. From that we review the configuration, identify risks and propose a practical action plan.
If you are planning a new build, checkout refactor or gateway migration before a Part-Dieu campaign or Eurexpo trade fair, start by writing down goals, constraints and current project state. Pricing is individual and depends on the scope of work.
Explore selected projects supporting our clients' success.
The website project car-mechanic-huntington.co.uk was created with the aim of professionally presenting the services of a car workshop. The primary goal of t...
centrumpoludnie.pl is an information portal for a shopping centre in southern Gdansk, covering shops, promotions, news, and simple administration.
DKF.za.pl is a website created in 2010 for the Film Discussion Club “ZA”, operating as part of the Polish Federation of Film Discussion Clubs. The project wa...
How we approach AI citations, WooCommerce B2B modernization, and NIS2-aligned operational resilience on WordPress. These guides apply to every client location.
Local expertise: - Senior WooCommerce development for businesses in Lyon: custom checkout, Payplug and Stripe integration, TVA rules, Colissimo and carrier shipping, B2B wholesale and ERP sync - Local context: Part-Dieu, Confluence, Gerland biotech, Lyonbiopôle, Rhône-Alpes chemical sector, Eurexpo and Métropole de Lyon - Hook-based extensions over core edits, GDPR with French CNIL, EU hosting and FR/EN checkout built into delivery, without claiming a certification we did not earn Our team understands the Lyon market and tailors solutions to local business needs. In practice, this means a focus on Core Web Vitals, local intent, and information architecture tailored to the Lyon market.
Let's discuss how we can bring top-tier performance to your project.
Schedule free consultation in LyonStay updated with the WooCommerce Developer community
Since 26 August 2026, links in Google results go through google.com/goto instead of straight to the page. What this changes in analytics, in rank tracking tools and in WordPress, and what it does not change at all.
WP Rocket 3.23.2.1 and earlier fatal on WordPress 7.1: TypeError in Cloudflare.php line 562. GitHub report 6 July, sites down 19 August, fix 3.23.2.2 on 20 August. Update the plugin first.
Google now expands AI Overviews to a full AI Mode answer on some queries and pushes the ten blue links down. Our Search Console numbers on offer URLs at positions 2 to 4, and what we changed so the overview has a fact to cite.
Google changed its JSON-LD extraction and now applies only one pass of HTML unescaping. Double-escaped entities are no longer unrolled, so the block stops parsing and the structured data disappears. How to measure your own corpus and how to encode it correctly.
Google splits site reputation manual actions by searcher location from 30 August 2026. Outside the EEA the demotion still hits the affected portion. Inside the EEA that impact does not apply; the section may rank independently. Why parasite SEO does not return.
More articles are available on /en/blog/
The work comes mostly from Local SMB and Enterprise. The acceptance list for France runs through GDPR, NIS2 and EAA. None of that is specific to Lyon, it applies market-wide, but it is cheaper written into the scope than retrofitted after launch.
No. The store has to survive Woo updates, so customisation goes through the documented action and filter hooks, plus a custom plugin and theme split where it belongs. Core file edits are not done. The boundary between Woo core, custom plugin code and theme code is set during architecture and recorded in the runbook.
For each gateway we document supported flows (one-shot, recurring, refunds, partial refunds, 3DS), the test card matrix, the webhooks the gateway sends, and the local idempotency story. TVA display, invoice fields and cross-border EU rules are configured against the actual product catalogue and shipping zones, not copied from a generic template. End-to-end QA on staging covers cart, payment, order, email, admin edit and refund on every active gateway, including failure paths.
Strengthen your business with professional technical support in key areas of the WordPress ecosystem.
Stores, checkout flow, and sales logic.
Store outage, slow checkout, post-update chaos.
Ongoing WooCommerce care, monitoring, and uptime.
EU store checklist: VAT, accessibility, evidence pack.
White-label WordPress development for agencies.
WooCommerce sync with ERP and wholesale systems.
Google shut off the Content API for Shopping on 18 August 2026, so v2.1 calls now return 410 Gone. If your WooCommerce store feeds Merchant Center through the official plugin you are fine, but custom integrations that never moved to Merchant API are already offline.
Architecture for a WooCommerce catalog on Astro 7. What stays in wp-admin, which plugins die with the theme, Store API versus GraphQL, and why checkout stays on WooCommerce.
The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.