About Service Plugins

A service plugin is custom backend logic that Wix calls during one of its own flows, such as checkout or booking. In Studio Two you add one from the Code tab through the Wix Extension Builder, and the plugin is part of the site project.

Studio Two uses the SDK service plugins that the Wix Extension Builder offers. Wix Studio and Wix Editor sites use Velo service plugins, and that set is smaller. For the full list and for what each plugin's handler must return, see Available Service Plugins.

Anatomy of a service plugin

A service plugin in a Studio Two project is a configuration file and a handler:

  • The handler is the code Wix calls. It receives the current cart, booking, or other host state, and returns a response in the shape that plugin requires.
  • The configuration file declares the plugin's ID, name, and path to the handler. For the fields, see Service Plugin Extension Files and Code.

You generate the files first, then edit the handler. For that workflow, see Build a Service Plugin in Studio Two.

How service plugins are used

  • You add the plugin from the Code tab through the Wix Extension Builder, which puts its files in your site project and registers it.
  • You pick the plugin type from a fixed list, such as Ecom Additional Fees or Booking Policy Provider.
  • Wix calls the handler when the matching flow runs on the site. Calling the underlying API yourself doesn't reach the handler.

See also

Last updated: 2 November 2026

Did this help?