How to capture, publish and file your data on fahrschuldaten.de

One published price stand feeds the website widget, partner API and register file. Capture completely, then publish, then file.

1. 1

   Create an account and confirm your email address.

2. 2

   Complete setup: operators, plan, locations, classes, prices, opening hours, review.

3. 3

   Maintain locations in the location hub (master data, classes, contact, hours).

4. 4

   Capture prices as a draft — each cell needs an amount or a status, never 0 €.

5. 5

   Review and publish the price board. Only then do widget, API and register change.

6. 6

   Under Register submissions, review the location list and prepare the submission.

7. 7

   Submit to the authority, download the register file, and document the run as submitted.

Changes after a publication always go through a new draft and a new version — the live board stays unchanged until the next publish.

After registration you land in setup. The rest of the cockpit (locations, register, import) opens only when you complete setup. Support and settings stay reachable.

1. 1

   Account and school

   Register, confirm your email and create your driving school. Without a confirmed email you cannot later publish or create API keys.

2. 2

   Operators

   Create at least one operating company (permit holder). Complete status needs name, legal form and address. Every location must later be assigned to an operator — otherwise register filing is blocked.

3. 3

   Plan

   Choose a package. How many locations you can publish depends on the plan. Without a booked package, publishing and register filing may be blocked.

4. 4

   Locations

   Add branches by address (street, postcode, city) — one by one or from a file. Assign an operating company to each location. Coordinates are usually resolved automatically.

5. 5

   Classes

   Set the licence classes you offer (car, motorcycle, truck, …). During setup they apply to all locations first. Per-location differences come later in the location hub.

6. 6

   Prices

   Capture the price board once — it initially applies to all locations. Every cell needs an amount or a status (Not offered, Free of charge, Included in basic fee). Enter or Tab saves and moves on.

7. 7

   Opening hours

   Hours are optional but useful for the public board. They can apply to all locations and later be adjusted per branch.

8. 8

   Review and finish

   The last page shows what is complete and what is still missing. Required fields must be filled before “Complete setup” works. Draft locations then become active and you land on the dashboard.

After completion you can still change classes, prices and hours per location. Setup disappears from the account menu; day-to-day care runs through Locations.

Under Locations you see every branch with lifecycle, price stand and register status. Open a location to work in the hub — that is the home for master data, classes, prices and filings.

3.1Location hub

Every location has the same areas. The header keeps lifecycle, public visibility and register status separate — do not mix them.

3.2Location states

• Draft — not active yet, typical during setup.

• Active — the branch is operating and can be published and filed.

• Closed — hidden from widget and API lists; a previously filed branch is prepared as a deactivation. Delete only unused drafts.

• Superseded — after a merge the old record stays readable, with a link to the target location.

Many locations at once: use Import & Export for Excel, CSV or JSON. Review conflicts and duplicates before applying. A location matrix helps align classes and prices across branches.

Each location has at most one live board and optionally a draft. The draft is internal only; partners, widget and register see the published stand exclusively.

• Edits create or update the draft. The public board changes only when you review and publish.

• Price rows autosave while you edit — no extra save step.

• Every cell needs an amount or a status: Not offered, Free of charge, or Included in basic fee.

• 0 € is not a valid amount. Use the matching status or clear the value.

• The board lists driving-school charges. TÜV, DEKRA and authority fees are external and shown separately, not as school prices.

4.1Board structure

1. 1

   Basic prices — basic fee, theory retake, learning materials

2. 2

   Lessons & instruction — driving lesson, vehicle instruction, simulator; variants such as automatic, evening, weekend

3. 3

   Special training drives — where the class requires them

4. 4

   Exam presentations — theory and practical at TÜV/DEKRA

5. 5

   Surcharges — school fees and extras

6. 6

   Packages & courses — fixed-price packages, intensive courses

7. 7

   Promotions & discounts — not in the standard comparison

8. 8

   External & official fees — display only (TÜV, authority)

After setup, maintain prices in the location hub under Price board. For many branches with the same prices, use the price matrix. Position labels are fixed so boards stay comparable.

Publishing means: check the draft against required rules, inspect the diff versus the live board, and freeze the price stand. That version then becomes read-only.

1. 1

   In the location hub under Price board, open the draft and fill missing required prices.

2. 2

   Choose “Review” / “Review and publish”.

3. 3

   Go through data checks, price checks and preview. Blockers (missing required prices, missing operator, empty classes) must be resolved.

4. 4

   Check the effects: new public board, widget and API pick up the new stand, a register filing is prepared.

5. 5

   Confirm publication. The draft becomes the live version; further changes need a new draft.

After a successful publish:

• The public price board shows the new version.

• The website widget can be enabled and stays in sync with the board.

• The partner API returns this published stand only — never drafts.

• The location appears under Register submissions as ready to review and file, once no open draft remains.

Several locations at once: use bulk publish. Plan limits, missing payment or incomplete operator data can block publishing — fix billing or operators first.

Register submissions are the control centre before filing with the authority. Review first, then prepare — not the other way around.

1. 1

   Open Register submissions. The overview shows which locations are ready, which drafts are still open, and whether blockers exist.

2. 2

   Choose “Review before filing”. You see first filings, changes and deactivations with version and price diff.

3. 3

   Check the list. Locations with open price drafts are held back from this run — publish them first.

4. 4

   “Prepare register submission” creates a run with every currently register-ready location. Only one open submission can exist at a time.

6.1What holds a location back

• Open price draft — review and publish first.

• Missing or incomplete permit holder on the location.

• No published price board yet.

• An open submission already exists — finish or discard it first.

In the submission run you file the reviewed locations, download the register file and document that filing happened. Versions and references stay auditable.

1. 1

   In the run, choose “Submit to register”. Each location gets a filing ID.

2. 2

   After submission, download the register file (schema fahrschuldaten.register-batch.v1). That file is for the authority — not the same format as widget or partner API.

3. 3

   “Document run as submitted”. That closes the run; versions and references stay in the protocol.

4. 4

   Optionally download the full register file: it contains the last filed stand of every location, not just the latest run.

The register file contains operator, location address, classes, offers and canonical price rows. Widget and partner API use fahrschuldaten.public-prices.v1, not this batch file.

{
  "schema":: "fahrschuldaten.register-batch.v1",
  "batchReference":: "2027-01-15-001",
  "batchTransactionReference":: "VORG-20270115-1234567890-001",
  "locationCount":: 1,
  "workspace":: {
    "publicId":: "wsp_musterfahrschule",
    "customerNumber":: "123-456-7890",
    "name":: "Musterfahrschule"
  },
  "permitHolder":: {
    "publicId":: "ph_muster",
    "legalName":: "Musterfahrschule GmbH"
  },
  "locations":: [
    {
      "locationId":: "loc_muster_1",
      "name":: "Hauptstandort",
      "street":: "Musterstraße 12",
      "postalCode":: "10115",
      "city":: "Berlin",
      "submissionType":: "INITIAL",
      "versionNumber":: 1,
      "submissionReference":: "MELD-20270115-1234567890-001-01",
      "payload":: {
        "licenseClasses":: [
          {
            "code":: "B"
          }
        ],
        "validFrom":: "2027-01-01",
        "prices":: [
          {
            "label":: "Grundbetrag",
            "amountGrossCents":: 39900,
            "billingUnit":: "ONE_TIME"
          },
          {
            "label":: "Begleitung zur praktischen Prüfung",
            "amountGrossCents":: 19900,
            "billingUnit":: "PER_EXAM"
          },
          {
            "label":: "Vorstellung theoretische Prüfung",
            "amountGrossCents":: 7900,
            "billingUnit":: "PER_EXAM"
          }
        ]
      }
    }
  ]
}

If you close a previously filed location, the next run includes a deactivation (DEACTIVATE). Merged locations are superseded; the source is deactivated and the target keeps the stable identity.

• Public pages, widget, API and register see published stands only — never drafts.

• Each publish creates an auditable version. The live board is read-only.

• Confirm your email before you publish or create API keys.

• Plan, location limit and payment method must be in order, or publish and filing stay blocked.

• Manage members and roles under Team. Integrations (widget, partner API) live under Integrations.