WordPress developer in Turin

WordPress development for companies in Turin by a Polish freelancer who works remotely and in English. Italian site notices under D.Lgs. 70/2003, Garante cookie rules, the 2025 accessibility duties and SdI invoicing explained.

WordPress developer

My place in the WordPress community

  • I have had a wordpress.org account since 2006.
  • I contributed to WordPress core for versions 7.0 and 7.1.
  • I maintain 30 plugins on wordpress.org.
  • I organise and speak at WordCamps.
  • I have attended every WordCamp Europe from 2017 to 2026.
  • Local WordPress meetup: WordPress Torino Meetup

My WordPress.org profile

My name is Mariusz Szatkowski. I build and extend WordPress sites from Gdynia, on the Polish coast, and have worked with WordPress since 2006. If you searched for an Italian freelance WordPress developer, you should know up front that I am not Italian. I am a Polish freelancer, I work remotely, and with companies in Turin I write in English. This page explains what that arrangement covers, which Italian rules a WordPress site in Turin has to follow, and what you send me to get a written estimate.

#A Polish developer for a Turin site: how the language split works

The work divides cleanly. I handle the WordPress side: theme or block implementation from your layout, custom post types and fields, forms, integrations, the consent setup, multilingual structure, speed and the move to your hosting. You or the people you already trust handle the words: Italian page copy, the privacy policy, the cookie policy, terms of sale and any English or French versions. I do not write legal texts and I do not translate into Italian. I put the approved texts in the right place and make the site behave the way they describe.

Graphic design is not part of what I deliver either. The layout comes from you, from your designer or as a filled-in spreadsheet where you mark which elements go on which view. I turn that into a working, responsive WordPress site.

All communication is written: the brief, my questions, the scope, the staging review, the acceptance list. That suits a remote arrangement across two languages, because every decision has a record that a translator or a colleague in your office can read later.

#What the Italian e-commerce decree asks a website to show

Italy implemented the EU e-commerce directive with Decreto Legislativo 9 aprile 2003, n. 70. Its article 7 obliges the provider of an online service to make certain information easy, direct and permanent to reach. On a WordPress site that turns into a short list I check before launch:

  • Name or company name (ragione sociale), exactly as registered.
  • Registered office (sede legale).
  • Contact details that allow fast contact, including an email address.
  • REA or company register number, from the Camera di commercio.
  • VAT number (partita IVA) or an equivalent identifier.
  • Supervisory authority details, if the activity needs a licence or authorisation.
  • Regulated professions: the professional body, registration number and title, if this applies to you.
  • Prices and fees stated clearly, saying whether tax and delivery are included.

“Permanent” is the word that matters for a build. A company number tucked into one About page does not meet it. I place these details in the site footer, which WordPress renders on every template, and repeat them on a legal notice page. In a block theme the footer is a template part, so one edit updates every view and a later redesign cannot quietly drop it.

#Cookies under the Garante guidelines of 10 June 2021

The Italian data protection authority, the Garante per la protezione dei dati personali, adopted its cookie and tracking guidelines on 10 June 2021. Several points translate directly into how the consent banner on a WordPress site has to work:

  • The banner carries an X, usually in the top right corner. Closing it that way keeps the default settings, which means no cookies beyond technical ones.
  • Scrolling, by itself, never counts as consent.
  • A cookie wall, where access depends on accepting cookies, is treated as unlawful, unless the site offers an equivalent content or service without consent, judged case by case.
  • Once a visitor refuses, the choice is recorded and the banner should not ask again until at least six months have passed, unless the conditions change materially, for example a new third party.
  • Analytics cookies can be treated like technical ones, without prior consent, only under conditions: no direct identification of the visitor (masking at least the fourth part of the IPv4 address is one way), use limited to aggregate statistics for one site, and no combining of the data by the provider with other processing.

In practice I set up a consent plugin so that marketing tags, embedded videos and third-party fonts stay blocked until the visitor agrees, and I test that on staging with the browser’s network panel open. Which tools you use and how you word the banner is your decision, ideally with your privacy consultant. My part is a site that keeps its promise.

#Accessibility: D.Lgs. 82/2022 and what AgID supervises

Italy transposed the European Accessibility Act, Directive (EU) 2019/882, with Decreto Legislativo 27 maggio 2022, n. 82. Article 1 makes it apply to products and services placed on the market from 28 June 2025, and the list of services in article 1, paragraph 3 includes e-commerce services (letter f). Paragraph 5 leaves out some older content: pre-recorded audio and video and office files published before 28 June 2025, and archived content not updated after that date.

The AgID FAQ adds the practical points:

  • AgID, the Agenzia per l’Italia Digitale, is the supervisory authority for the services in article 1, paragraph 3. The Ministry of Enterprises and Made in Italy covers products.
  • The decree does not apply to microenterprises that provide services, defined as fewer than ten employees and annual turnover or balance sheet total of no more than two million euros.
  • Breaches of the accessibility requirements carry a fine of five thousand to forty thousand euros.

For a Turin company that sells online and is above the microenterprise size, accessibility belongs in the build from the first template. When I implement a layout I keep the parts that decide whether a visitor can use the shop without a mouse: real headings, labelled form fields, visible keyboard focus, menus that open with the keyboard, images with text alternatives, and a checkout that reports errors in words. If the layout itself causes a problem, such as light grey text on white, I point it out in writing before I build it, because the visual design stays yours.

#E-invoicing through the SdI: where WordPress stops

The Agenzia delle Entrate states in its electronic invoicing FAQ that invoices issued to VAT-registered businesses (B2B) must be electronic via the Sistema di Interscambio, and that the SdI delivers each invoice to the address it carries: a PEC address or a recipient code (codice destinatario).

WordPress is not an invoicing system, and I do not try to make it one. What a WooCommerce shop for Italian business buyers needs is the right data at checkout: company name, partita IVA, codice fiscale where relevant, and the PEC or codice destinatario. I add those fields, validate their format, and pass the order to the invoicing software or accountant you already use. The details of shop builds are on the WooCommerce developer page for Turin.

Two payment plugins come up often for Italian shops, both on wordpress.org: Satispay for WooCommerce, published by Satispay, and Nexi XPay, published by Nexi Payments, which needs the bcmath PHP extension on the server. Whether either fits depends on your contract with the provider, so I ask before I install anything.

#Turin as a place to do business online

Politecnico di Torino

Photo: Gabridelca, CC BY-SA 3.0, Wikimedia Commons.

Four local institutions are worth knowing if your website is part of a wider digital plan. None of them is a reason to hire me; they are places where a Turin company can get support that a WordPress developer does not give.

  • I3P, the incubator of Politecnico di Torino, supports high-tech start-ups with consultancy, training and networking, and runs an open innovation service for established companies. A start-up coming out of I3P often needs a site that can change every few weeks without a developer, which argues for editable blocks over a fixed template.
  • Fondazione Piemonte Innova, formerly Torino Wireless, is a public-private partnership set up in 2002. It manages the ICT innovation cluster that Regione Piemonte activated in 2009, linking small firms, large companies and research bodies.
  • Torino City Lab, promoted by the City of Turin and launched under that name in October 2018, lets companies test solutions in real urban conditions around smart living, mobility and climate neutrality.
  • The Camera di commercio di Torino runs a Punto Impresa Digitale with digital services named Selfi 4.0 and Zoom 4.0, mentoring, cybersecurity, digital marketing and e-commerce, by appointment. The same chamber keeps the company register, which is where your REA number for the site footer comes from.

#How a WordPress project with me runs

  1. You send a brief. Two paragraphs are enough: what the site must do, by when, what runs today and who supplies the Italian content.
  2. I reply with questions. Usually about integrations, the number of templates, languages, who owns the hosting, and which legal texts already exist.
  3. I write the scope. What I build, what I do not, the assumptions, and what you approve. If something new comes up later, it gets its own written estimate.
  4. I build on staging. A password-protected copy where you click through real pages filled with your content.
  5. You accept against a list. The list comes from the scope. Corrections go in writing, I fix them and mark each one done.
  6. Launch. A backup first, then the move to your hosting, then a check of forms, consent and the footer details on the live address.
  7. After launch. Updates and monitoring can continue as WordPress maintenance for Turin, or your own team takes over with the notes I leave.

For speed I work to Google’s published thresholds: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1, as described on web.dev. I measure the live site against them after launch rather than promising a score in advance.

#A pre-launch checklist for an Italian WordPress site

Use this with any developer, including me.

CheckWhere to look
Company name, sede legale, email, REA and partita IVA visible on every pageSite footer, then a legal notice page
Prices say whether VAT and delivery are includedProduct and cart pages
Cookie banner has an X that closes it without acceptingFront page in a private window
No marketing tags load before consentBrowser network panel, before clicking anything
Refusal is remembered and not asked again at onceReload after refusing
Analytics either consented or configured with masked IP and aggregate useAnalytics settings
Shop pages and checkout usable with keyboard onlyTab through a full order
B2B checkout collects PEC or codice destinatarioCheckout form with a company buyer
Italian copy and legal texts approved by you, not by the developerYour own sign-off

#Questions from Turin companies

#Are you an Italian WordPress developer?

No. I am Polish, based in Gdynia, and I work remotely for clients abroad. With Turin companies I write in English. Italian page copy, privacy texts and translations come from you, your translator or your consultant, and I put them into WordPress.

#Which company details must an Italian site show?

Article 7 of D.Lgs. 70/2003 lists them: name or company name, registered office, contact details including email, the REA or company register number, the VAT number, and prices that state whether tax and delivery are included. I place them in the footer and on a legal page so they appear on every view.

No. Under the Garante guidelines of 10 June 2021 the banner needs an X that closes it and keeps only technical cookies, scrolling never counts as consent, and a cookie wall is unlawful unless the visitor gets an equivalent alternative without consenting.

#Does the accessibility law apply to my company website?

D.Lgs. 82/2022 covers e-commerce services placed on the market from 28 June 2025. According to AgID, which supervises services, it does not apply to microenterprises that provide services: fewer than ten employees and annual turnover or balance sheet total of no more than two million euros. A brochure site that sells nothing online is outside the e-commerce category.

#Can WordPress send invoices through the SdI?

Not by itself. Invoices between VAT-registered businesses in Italy are electronic and travel through the Sistema di Interscambio to the PEC address or recipient code on the invoice. A shop usually passes order data to the invoicing software you already use, and that software talks to the SdI.

#What do you need from me to start?

The address of the current site if there is one, the goal, the deadline, the layout for each view, the Italian content, and access to hosting and the domain. With that I can write a scope.

#Send me your project

If an English-speaking developer in Poland works for you, write to me through the contact page. Tell me the site address or that there is none yet, what the site should achieve, your deadline, and what it runs on today. I read every message myself, reply in writing with my questions, and then send a written estimate with scope and assumptions. That first estimate costs you nothing. More about how I approach WordPress builds in general is on the WordPress developer page.

See also in Italy

Need this service: WordPress developer in Turin?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Latest WordPress developer articles

Sep 14, 2017

WordPress history, from 4.9 to the Gutenberg era

WordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?