What we do
Tools
Industries
Department
How we workLet's talk →
Home/Wix/Velo by Wix
Wix developer platform

Velo by Wix: Where Your Site's Own Business Rules Can Live

Velo is the coding layer inside Wix: JavaScript on the page, and JavaScript on Wix's servers that your visitors never see. Wix's developer docs now file it under building websites, next to a newer JavaScript SDK, but the pieces most businesses need haven't changed. A few backend files decide whether an order gets checked against your own rules, whether another system can push data in, and whether a nightly job runs without anyone opening a laptop.

Velo in one screen

It's JavaScript, front and back. Page code talks to elements on the page. Backend code runs on Wix's servers, holds your secrets and calls other systems.

Where you write it: the Code panel in the Wix Editor or Wix Studio, the Wix IDE in Studio, or your own editor on your computer.

What it adds: data collections you query from code, backend functions the page can call, HTTP endpoints other systems can call, hooks on your data and scheduled jobs.

What it costs: nothing extra to switch on. Paid APIs your code calls still bill you themselves.

The backend files a real Velo build is made of

Most Velo work that matters to a business sits in the backend folder. These are the files you'll meet, in the order a typical integration needs them.

  1. 1

    A web module the page can call

    backend orders.web.js

    Files ending in .web.js export functions wrapped in webMethod(). Page code imports them and calls them like any async function, while the logic and any keys stay on the server. Each one carries a permission: Anyone, Site Member or Admin.

    Watch for: older sites use .jsw files. Wix has deprecated that format, though existing .jsw modules keep working, so there's no need to rewrite them in a panic.

  2. 2

    Secrets kept out of the code

    API keys for QuickBooks, a CRM or a carrier go in Wix's Secrets Manager and are read by backend code at run time, so they never sit in a file someone might copy.

  3. 3

    wix-fetch for calls going out

    Backend code uses wix-fetch to send an HTTP request to any outside API. That's the route from a Wix order to an invoice, a shipment or a CRM record, with no separate server in between.

    Watch for: calling a third-party API from page code instead runs into browser CORS limits and exposes your key. Wix's own guidance is to make those calls from a web module.

  4. 4

    http-functions.js for calls coming in

    backend http-functions.js

    Each exported function's prefix sets the method it answers: get_, post_, put_, delete_, or use_ for several at once. A function called post_shipmentUpdate is reached at your site's /_functions/shipmentUpdate address, which is where a carrier or accounting system sends its webhook.

    Watch for: a request with the wrong method gets a not-found error, not a helpful message. If a sender only does POST, a get_ function won't catch it.

  5. 5

    Hooks and events on your own data

    backend data.js

    Data hooks run before or after an item is saved to a collection, which is where you stop a bad record or fill in a field. The events file reacts to things happening on the site, such as a new order or a form submission.

  6. 6

    A scheduled job for the quiet hours

    backend jobs.config

    The jobs config tells Wix to run a backend function on a timetable: a nightly stock pull, a weekly cleanup of abandoned records, a morning export to the warehouse.

Logic inside Velo, or on a server of its own?

Keep it in Wix

Velo's own backend

  • The rule is about this site: its orders, forms, members or collections.
  • It reacts to Wix events directly, with no polling from outside.
  • One less service to host, patch and pay for.
  • Logs from web methods appear in the Developer Console while you preview, not in the browser on the live site, so plan your own logging for production.
Run it elsewhere

A separate service

  • The same logic has to serve Wix and other channels, such as a second store or a wholesale portal.
  • The job is long or heavy, such as reconciling a month of transactions.
  • Several systems need to agree, and one of them isn't Wix.
  • You want the integration to survive a future move off Wix.

Plenty of builds use both: Velo catches the Wix event and makes one small call, and the heavier work happens on a service that owns the other systems' logins.

Velo work that pays for itself on a Wix store

The App Market covers common, single-purpose connections well, and it's worth trying first. Velo earns its keep when your process has a condition no connector was written for: an order over a set value waits for a manager, tax treatment changes by customer type, or stock is counted in a system Wix has never heard of.

n-frames writes that backend code for Wix sites: web modules with tight permissions, HTTP functions that accept updates from carriers and accounting software, and scheduled jobs that keep collections in step. Each outside call is logged, so a failed sync shows up the same day instead of in a customer complaint.

Now and then a Wix setting has no API behind it at all, only a dashboard panel. For that narrow case we automate the dashboard screen itself with a headless browser, and keep it to that one job.

Questions people ask

Is Velo by Wix free to use?

Switching it on costs nothing extra; it comes with Wix's editors. You do need a plan that suits what you're building, such as one that takes payments if the code touches orders, and any outside service your code calls charges for its own API.

Do I need to hire a developer to use Velo?

Not for small page tweaks, which Wix's tutorials cover well. For business logic with real consequences, like holding orders, syncing with another system or recovering when an outside API fails, treat it as development work. n-frames writes that part: the web modules, HTTP functions and error handling.

What programming language does Velo by Wix use?

JavaScript everywhere: page code and backend code alike. Wix adds its own modules on top, such as wix-data for collections, wix-fetch for outside requests and wix-web-module for backend functions.

Can Velo connect to systems outside Wix?

In both directions. Backend code calls outside APIs with wix-fetch, and HTTP functions give other systems an address under /_functions/ to send data to, so a carrier or a CRM can update your site as well as hear from it.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.