Flowion
ProductsDevicesPricingAboutDocsSign in
© 2026 Flowion ABOrg.nr 559453-0155 · Registered for F-skatt and VAT (moms)hello@flowion.ioOCPP 1.6J · 2.0.1 · 2.1

New to OCPP

  • What a CSMS does
  • OCPP basics
  • OCPP versions
  • OCPP vocabulary

Company

  • Contact us
  • Support
  • Branding
  • Security
  • Terms of Service
  • Privacy Policy
  1. Supported devices
  2. Zaptec

Zaptec chargers on Flowion.

2 models catalogued, speaking OCPP 1.6J. These connect straight to Flowion: you set the CSMS URL on the device and it speaks OCPP to us with nothing in between.

The models below differ in how they are set up, so which Zaptec you have changes what you do next.

NOOCPP directCloud OCPPManufacturer site
2 models

OCPP direct

The charging station opens its own WebSocket to Flowion. You configure the CSMS URL on the device and it speaks OCPP to us with nothing in between.

  • Zaptec Go

    • 1.6JSupported

      AC wallbox · Vendor documented · Vendor portal

      • Choosing this path gives up Zaptec's own phase and load balancing across the installation; Flowion becomes the only thing managing power.
  • Zaptec Pro

    • 1.6JSupported

      AC wallbox · Vendor documented · Vendor portal

      • Choosing this path gives up Zaptec's own phase and load balancing across the installation.
2 models

Cloud OCPP

The station talks only to its manufacturer's cloud, which relays OCPP to us. Each vendor's relay has its own onboarding, authentication and capability rules, so every one of these needs an integration built before it works.

  • Zaptec Go

    • 1.6JPlannedNo smart charging

      AC wallbox · Vendor documented · Vendor API

      Waiting on Zaptec Cloud OCPP — OCPP 1.6J cloud-to-cloud, with stations onboarded through the Zaptec Integrations API.

      • Standard OCPP smart charging profiles are not supported on this path. Zaptec Cloud keeps power management for itself, so Flowion cannot load balance these chargers — SetChargingProfile does not reach the hardware.
      • The CSMS is limited to authentication, session management and payment.
  • Zaptec Pro

    • 1.6JPlannedNo smart charging

      AC wallbox · Vendor documented · Vendor API

      Waiting on Zaptec Cloud OCPP — OCPP 1.6J cloud-to-cloud, with stations onboarded through the Zaptec Integrations API.

      • Standard OCPP smart charging profiles are not supported on this path, so Flowion cannot load balance these chargers.
      • The CSMS is limited to authentication, session management and payment.
Provisioning

How you point Zaptec at a CSMS

Compatibility is a protocol question and it is usually the easy half. Changing the CSMS URL is the part that takes an afternoon, and it differs by manufacturer far more than the protocol does.

  • Vendor portal

    Set in the manufacturer's cloud portal. You cannot type a URL into the box; the vendor pushes the setting to it.

  • Vendor API

    Onboarded programmatically through the manufacturer's own API, usually with per-station credentials issued by them.

Provenance

Where this came from

Researched 2026-08-12 from the sources below. Vendors ship firmware faster than anyone updates a table like this, so confirm the exact SKU before you buy a pallet of them — and see how to read these labels for what each one claims.

  • docs.zaptec.com/docs/ocpp-within-zaptec
  • help.zaptec.com/hc/en-001/articles/4530001974033-Zaptec-Cloud-and-OCPP-Integration
  • monta.com/en/supported-charge-points/zaptec-go-ocpp
  • www.chargepanel.com/charge-station-vendors
  • www.zaptec.com/integrations

Connect the Zaptec you already own.

No rip and replace. Point your existing chargers at your organization's URL — and when the hardware isn't in the room, the simulator is.

Sign inRead the docs