Reseller Portal¶

The reseller portal (Händler-Portal) is the workspace for DiKAS specialist resellers (POS specialist retailers, IT system houses): you create a running DiKAS instance for your own customers yourself, set it up together with them and activate it as soon as it is ready. Until activation, the entire customer relationship is with you — DiKAS does not get in touch. From activation, DiKAS takes over invoicing your customer directly (they get their own customer portal and activate their SEPA mandate there themselves), and you receive a monthly commission for it (see Activating and Understanding Prices).

ℹ️ Who is this page for? It is aimed at specialist resellers with a DiKAS partner account that has been enabled with the reseller permission. If you are also registered with DiKAS as a tax advisor firm, additionally read Tax Advisor & Firm — that is a separate portal area with its own login.

Login¶

Login is at konto.dikas.de/haendler/login with email and password — with the same partner account that you also use for any firm or agent access at DiKAS. It is not a separate "reseller account"; it is your normal DiKAS partner account with an additionally enabled permission.

If two-factor authentication is set up for your account, the login asks in a second step for an additional 6-digit code from your authenticator app — or, if the device is not available, one of your recovery codes (format xxxx-xxxx, each usable only once).

If an account without the reseller permission logs in to this portal, a generic error message appears — for security reasons DiKAS does not confirm whether an account exists at all.

If your account additionally carries the firm permission, the switcher "Switch to firm" (Zur Kanzlei wechseln) appears at the top right. Firm and reseller areas deliberately keep separate sessions — the switcher therefore does not automatically log you in there as well, but leads to the firm login if no active session is running there yet.

Creating a Customer¶

Via "Create customer" (Kunde anlegen) in the customer list, the creation form (/haendler/kunden/neu) opens. The button is locked as long as your quota is exhausted or the quota status could not be loaded — more on this in the section Quota.

1. Company & Contact¶

Field	Mandatory?
Company	yes
Street, postal code, city, country	no
Contact email, phone	no
Tax / VAT no.	no

This information is master data for later invoicing and reporting purposes — not an access or login record. Your customer does not get their own DiKAS access through it (see What Your Customer Gets — and What Not).

2. Online Name¶

The online name determines the address of the new instance: <online-name>.dikas.de. While you type, the form checks live whether the name is still free (short delay, then "Available." or "This online name is already taken or invalid."). Without an available name, the creation cannot be submitted.

3. Package, Add-on Modules, Devices, TSE¶

Package (mandatory) — selection from the complete DiKAS catalog.
Add-on modules — the form offers only modules that fit the selected package: modules that the package already includes and modules whose prerequisite the package does not meet (e.g. Online ordering under Gastro) are hidden. Which modules exist, what they cost and what they require is in the module overview. A link above the selection leads straight there.
Devices — number of POS workstations, at least 1.
TSE — default is "None (can be retrofitted later)"; a cloud TSE can be ordered here directly, this is not blocked for reseller customers.

Changing modules later

Until activation you can change modules freely at any time (see Setup phase). After activation the portal no longer offers module changes — if your customer later needs another module, DiKAS handles it. This also applies to "Self-Service (QR ordering)": so plan it in before activation if your customer wants to offer ordering by QR code at the table.

4. Price¶

As soon as package, number of devices or add-on modules are selected, the form shows a price preview with two lines — more on this under Understanding Prices.

5. Initial Password¶

You assign the initial password of the instance yourself (at least 8 characters, with confirmation field). This is intentional: DiKAS does not store it in plain text and shows it not a single time after submission — not even on its own completion page. So note it down in a safe place before submitting, otherwise you will have to set a new one later (see Sending Credentials & Setting a New Password).

After Submitting¶

"Create customer" starts the instance immediately, but "In setup" (In Einrichtung): your customer can work at the POS right away, but DiKAS does not yet invoice them, sends no email and does not yet set up a cloud TSE. Only your own step Activate (Freischalten, see below) starts billing. The completion page shows:

the instance address (with copy button),
the user name,
the notice that the password is not displayed because you have just assigned it yourself.

From there you go either directly to the customer overview of this customer or — via "Create another customer" — to a completely empty form for the next customer; master data is deliberately not carried over, every customer is a business of its own.

If creation fails because your quota is exhausted or your account is not yet fully set up for reseller operation, a corresponding message appears asking you to contact DiKAS.

Modules¶

A DiKAS customer consists of a package and optional add-on modules. Each package already includes a number of modules; you book further ones as add-on modules. Prices are monthly net customer prices; for modules with a unit they apply per installation or per machine.

Current prices

Before submitting, the form always shows the currently valid prices and your commission. The tables here serve as orientation and do not replace the price display in the portal.

What Each Package Already Includes¶

Package	Included modules
Basic	Time tracking, Kitchen display
Workshop (Werkstatt)	Time tracking, Customer account, Workshop, Kitchen display
Gastro	Time tracking, Customer account, Tables, Finance, Kitchen display
Delivery & Pickup (Liefer & Abhol)	Delivery service, Time tracking, Customer account, Tables, Finance, Kitchen display
Club	Disco, Time tracking, Customer account, Tables, Finance, Kitchen display
dikas Faktura (Free / Invoice / Pro)	Invoicing; Invoice and Pro additionally Finance

A module that your package already includes does not appear again as an add-on module.

Add-on Modules¶

Add-on module	Price / month (net)	Prerequisite	Unit	More
Invoicing (Faktura)	€9	—	flat	Invoices
Finance	€19	—	flat	Banking & Payment Reconciliation
Customer account (credit/bonus)	€9	—	flat	Customers
Inventory & stock management	€29	—	flat	Inventory
HACCP documentation	€19	—	flat	HACCP
Shift schedule	€29	—	flat	Staff Schedule
Reservations & appointments	€29	—	flat	Table Reservations
Ticketing	€19	—	flat	Ticketing
Workshop	€20	—	flat	Workshop
Cash machine	€19	—	flat	Payments
Draught system connection	€15	—	per installation	Tables
Online ordering	€49	Package Delivery & Pickup	flat	Online Shop
Self-Service (QR ordering)	€49	Package Gastro, Delivery & Pickup or Club	flat, includes one machine	QR Ordering & Self-Service
Additional self-service machine	€39	as Self-Service	per machine (up to 10)	QR Ordering & Self-Service

Flow: When You Can Change Modules¶

Phase	What you can do in the portal
At creation	Select package and add-on modules. The form hides what does not fit the package or is already included there.
In setup (until activation)	On the customer detail page in the "Configuration" block, change package, modules, devices and machines as often as you like. Nothing is billed. Every change takes effect immediately in the instance.
On activation	The valid state is frozen for the first invoice.
After activation	Add or reduce devices and self-service machines, cancel. No module change via the portal — DiKAS handles that.

If the selection is rejected

The check whether a module fits the package is done by DiKAS on saving. If you select a module in the configuration that the package does not allow or already includes, DiKAS rejects saving with an explanatory message. Change the selection and save again.

Setup Phase: Configure While Nothing Is Billed Yet¶

As long as a customer is "In setup" (status on the detail page, see Your Customer List), you change package, add-on modules, number of devices and machines freely and as often as you like — every change takes effect immediately in your customer's instance but triggers no invoice. Only on activation is the state valid at that time frozen for the first invoice. Use this phase to finish setting up the instance together with your customer before you trigger billing.

Activating¶

On the detail page of a customer "In setup" you see the notice "This customer is still in setup. Nothing is billed, and they hear nothing from DiKAS. After 30 days without activation the instance is shut down." and the button "Activate customer" (Kunde freischalten).

30-day period

If you do not activate the customer within 30 days of creation, DiKAS automatically shuts down the instance (locked, not deleted) — after 21 days without activation you as the reseller receive a reminder email in advance. If a Swissbit TSE has already been delivered by the time of shutdown, DiKAS invoices this hardware to you as the reseller — the customer themselves is never charged for it as long as they have not been activated.

The confirmation dialog says it explicitly: "Activate now? Billing starts, the customer gets their first invoice and an invitation to the customer account." With the confirmation, the following happens in one go:

Billing starts on today's date; the configuration state valid at activation (package, modules, devices, machines) is frozen for the first invoice.
The first invoice is generated.
A Swissbit TSE that has already been delivered is — if not yet done — billed as well; an ordered cloud TSE is provisioned now.
Your customer gets an invitation to the DiKAS customer portal (konto.dikas.de) — from here on they have their own DiKAS access for the first time.

A second click on "Activate" — for example after a timeout or by mistake — triggers neither a second invoice nor a second invitation; the portal merely reports that the customer has already been activated.

If the cloud TSE setup of all things fails, the customer nevertheless remains activated and billed — the portal points this out with a separate message telling you to try again later. If the invitation to the customer account fails, the portal explicitly points out that your customer cannot activate a SEPA mandate without it — follow up manually in this case.

What Your Customer Gets — and What Not¶

Your customer gets	Your customer does not get
An immediately running, live usable DiKAS instance (already before activation)	Before activation: an invoice, an email from DiKAS, a cloud TSE
After activation: their own invoice from DiKAS and their own DiKAS customer portal access (`konto.dikas.de`)	—

Until activation, DiKAS never addresses your customer itself — the contact data you enter at creation is pure master data until then. Setup until activation is entirely with you. From activation this changes fundamentally: DiKAS invoices your customer directly like any other end customer — including dunning and blocking in case of late payment — and your customer sets up their SEPA direct debit mandate themselves in their new customer portal under "SEPA mandates" (or until then keeps paying the individual invoices by bank transfer). As the reseller, you have nothing more to do with your customer's actual payment transactions from here.

Quota¶

In the header and on the customer list you see your quota status, e.g. "7 of 10 customers". DiKAS sets the maximum number according to your agreement — you cannot change it yourself; once it is reached, contact DiKAS to have it extended.

Every customer instance assigned to you that is not deleted and whose term has not yet ended is counted. Two points can easily be surprising:

A scheduled cancellation keeps counting until it actually takes effect — i.e. until the end of the current month (see Cancelling) — the customer is, after all, still managed and billed until then.
A failed creation attempt counts permanently. The status "failed" (see Your Customer List) therefore does not automatically release a place in the quota. In this case, do not simply create the same customer a second time — that consumes another place — but contact DiKAS.

As long as the quota status could not be determined (e.g. during a connection disturbance), "Create customer" also stays locked — even if there would actually still be room. This is intentional: a creation should not be risked as long as it is not certain that quota is still free.

Your Customer List¶

Under "Customers" (/haendler/kunden) you see all customers you created with company, online name, package, number of devices, status and creation date. A click on the company leads to the detail page.

Status	Meaning
In setup	Instance is running, but DiKAS is not yet billing. You configure freely and activate when setup is finished (see Activating). Without activation within 30 days the instance is shut down automatically.
live	Activated, DiKAS invoices the customer directly. Instance runs normally.
being set up	Creation is still in progress (briefly after submitting).
failed	Setup failed technically. Still counts against your quota (see above) — do not simply create the customer again, but contact DiKAS.
locked	The instance was locked — either by DiKAS, or because neither an activation within 30 days nor (after activation) a paid invoice from the customer was on record. Contact DiKAS, unlocking is not possible via this portal.

Changing the Contract¶

On the detail page of a customer (/haendler/kunde/:id) you see their master data, package, modules and number of devices and can change the running contract. Every action with a financial effect shows a confirmation dialog before confirming with the monthly amount (net) and, if due, a pro-rata amount for the current period — these are pure price statements; see Understanding Prices for how this is billed.

Devices¶

Add devices — possible at any time, with price confirmation before confirming.
Reduce devices — clickable only as long as more than 1 device is booked. A reduction does not take effect immediately, but only on the first of the following month; until then the current number of devices remains.
Undo — takes back a scheduled reduction at any time free of charge as long as it has not yet taken effect. The button is always clickable; if no reduction is scheduled at all, the portal simply reports this as information, not as an error.

Self-Service Machines¶

The same three actions (add / reduce / take back) exist for self-service machines — the section appears on the detail page only if the customer has licensed the module "Self-Service (QR ordering)". This module already includes one machine; so from the outside it seems like "from the first machine on", but visibility actually depends on the module, not on a quantity. If the module is missing, there is no way here to add it later — you select the module at creation or in the setup phase; after activation DiKAS handles that (see Modules). If the module is present, adding, reducing and undoing an additional machine work as with devices.

Changing the Package¶

Only for customers in the pure factura tariff without a POS module. If your customer has one of the POS packages (e.g. Basic or Gastro — the normal packages for most of your customers), the portal offers no package change: the operation is rejected, with the note that the license is not in the factura tariff. For these customers a package change goes through DiKAS.

Only as long as your customer is still in the factura tariff without a POS module does the change work as described: you select a target package from the catalog and have the price displayed (list price and your purchase price, as at creation). The selection list shows the entire catalog, without restricting to suitable targets in advance — only an upgrade is offered. A target that does not fit is rejected by DiKAS on confirming with an explanatory message instead of being applied silently.

Cancelling¶

Ends this customer's subscription at the end of the current month — not immediately. Until then the instance continues to run normally, and a booked cloud TSE also stays active until the end of the month; only afterwards is it switched off and archived. The confirmation explicitly points out that this step cannot be undone. The customer keeps counting against your quota until it takes effect (see Quota).

Sending Credentials & Setting a New Password¶

On the same detail page you find two separate actions with which you can supply your customer afterwards:

Send credentials — you enter any recipient address (your own or your customer's) and send an email with instance address and user name. A password is never in it — the mail explicitly states that the credentials come from the reseller. As protection against misuse, at most 10 such emails per minute are possible per reseller account; if exceeded, a short waiting notice appears.

Set new password — you assign a new password for this customer's instance (at least 6 characters). It is set for exactly the user who was created at creation — the same user name that the "Send credentials" mail also names. The old password is thereby invalid; the next login at the POS works only with the new one. It may be that the POS accepts the old password for a few more seconds — it remembers login data briefly. This concerns only the POS itself, not a DiKAS customer portal — the customer does not have one anyway at this point.

If your customer has locked themselves out (after five failed attempts the POS locks access for 15 minutes), the new password lifts this lock as well — they do not have to wait out the time.

As with the initial password: afterwards it is not displayed, logged or sent anywhere — remember it before you submit. The log only shows the fact that a new password was set.

Two messages can appear instead of a success confirmation; in both cases nothing was changed and the old password remains valid:

"There is no instance access for this customer yet whose password could be set." — this customer's setup has not progressed far enough (status failed or being set up, see Your Customer List).
"The instance is currently not reachable." — a temporary disturbance; try again later.

Brand¶

Under "Brand" (Marke, /haendler/marke) you maintain the ONE brand that reaches your end customers. Without a brand saved so far, the page shows an empty default — not an error, simply the starting state before the first maintenance.

The following can be maintained:

Brand name and name (mandatory) — name is the internal designation of the brand, brand name the externally visible one.
Claim — a short subtitle/slogan.
Theme — only "DiKAS" and "DiKAS Light" (DiKAS Hell) are available for selection. The other themes in the system are the house colors of named existing customers including their own logo; the selection is restricted server-side to the two neutral themes, not just hidden in the form.
Primary and accent color — each via a color picker, resettable to the theme value.
Fonts (interface/headings) — optional, only effective where the respective portal loads its own font styles.
Logo — upload (up to 512 KB) or remove; without your own logo the theme logo applies, or ultimately the DiKAS logo.

A live preview next to the form shows immediately how brand and colors look — it colors only this preview area, not the portal around it.

Save asks for confirmation and names the number of affected businesses. Only the confirmation writes and distributes: the brand is attached to all your so far brandless licenses and distributed immediately to all your own businesses (fan-out, best effort — the feedback says "distributed to N of M"). Customers who already carry a different brand set by DiKAS remain unaffected. A change therefore takes effect not only at the next contact with the customer, but immediately on saving.

White label stays with DiKAS. Whether platform documents (e.g. system emails) also carry your brand instead of the DiKAS brand is not something you determine here — DiKAS decides that.

Log¶

Under "Log" (Protokoll, /haendler/protokoll) you see, read-only, all your own actions, newest first: time, action, affected customer (linked to the detail page) and details.

A brand change appears there as its own row "Brand changed" — without a customer column, but with a "—": a brand belongs to no single customer, but to you as the reseller.

For customers of the old model (see Understanding Prices), this log is still the only basis from which DiKAS traces actions with a financial effect such as adding devices or a package upgrade and invoices them to you. For activated customers of the new model, billing runs automatically (invoice to the customer, commission to you) — the log serves there only for traceability.

Understanding Prices¶

At every place with a price — creation form, package change, adding devices/machines — the portal shows two amounts side by side:

List price (end customer) — what your customer is actually invoiced by DiKAS.
Your commission — your share of this invoice, in percent.

Your commission rate depends on your agreement with DiKAS — either an individually negotiated special condition, or otherwise a scale that rises with the number of your active customers. You see the percentage currently applicable to you live at every price display.

DiKAS bills the customer directly — your commission follows the payment

Since direct billing, DiKAS issues the running subscription invoices to your customer — not you. Billing only starts with the activation of this customer. For every paid subscription invoice of an activated customer you then automatically receive a commission, at the rate that was frozen at the activation of this customer (if your general rate changes later, the already activated customer stays at their own rate). An unpaid, dunned or cancelled invoice triggers no commission. Payout takes place in the monthly commission run.

For customers of the old model (created by you before activation existed), the following still applies: DiKAS issues no invoice to the end customer, you are invoiced by DiKAS as before and settle with your customer yourself.

Your Commission in the Portal¶

In the tab "Commission" (Provision) you see per billing period which paid customer invoices triggered commission and what amount results — the same calculation DiKAS uses for the payout, restricted to your customers. The commission run runs daily automatically over the current and the previous period; a payment booked only after month end is caught up.

The payout is made as a credit note from DiKAS with its own document number, transferred by bulk transfer; the payment reference contains document number and period.

What triggers no commission

An invoice closed without payment received — write-off after non-payment, insolvency, flat closing of old items — triggers no commission. Partial payments and late payments are taken into account normally.

Small business

If, as a small business, you do not show VAT, tell DiKAS: your credit notes are then issued without tax. As a rule, the credit note includes the tax statement.

Reseller and Firm in One Hand¶

If you are also connected to DiKAS as a tax advisor firm, a customer created by you is linked to your firm immediately and without confirmation by the customer — so you also see them in the firm area. If you abort the setup or the 30-day period expires, this automatic link ends again; a link confirmed by the customer themselves remains.

Keyboard Operation¶

The portal can be operated without a mouse: with Tab you jump from control to control, with Enter or the space bar you trigger it — this also applies to the cards in the subscription list and to "Manage mandate" on the subscription detail page. The element currently focused gets a visible frame; with mouse operation it does not appear. Dialogs are closed via their Cancel button.

What Is Not Yet Possible in This Version¶

Not yet possible

No package downgrade — only an upgrade is possible via the portal. A downgrade goes through DiKAS.
Package change only in the factura tariff without a POS module — as soon as a customer has one of the POS packages (Basic, Gastro, Delivery & Pickup, Club), the portal offers no package change at all for them. Every further adjustment goes through DiKAS.
No module change in the portal after activation — you select add-on modules at creation or in the setup phase (see Modules); afterwards DiKAS takes over the change.
No deleting a customer — cancelling ends the subscription, actual deletion of the instance remains reserved for DiKAS.
No own domain — all customer instances run under *.dikas.de.
The interface is available only in German.

Frequently Asked Questions¶

Can I delete a created customer again? No, not via the portal. "Cancel" ends the subscription at the end of the current month; actual deletion of the instance is done by DiKAS on request.

I see "failed" for a customer — what should I do? Do not simply create the same customer again, that consumes another place in your quota. Contact DiKAS so that the creation attempt can be reviewed.

I forgot my customer's password — can I look it up? No, DiKAS does not display or store any password in plain text. Instead, set a new one under Set new password; the old one is thereby invalid (the POS may still accept it for a few seconds, it remembers login data briefly). An existing 15-minute lock after failed attempts is lifted in the process.

"Create customer" is locked although my quota should not actually be full yet — why? Probably the quota status could not be loaded just now; reload the page. If it stays that way, contact DiKAS.

I have additionally connected a tax advisor firm at DiKAS — does one login suffice for both? It is the same account, but two separate sessions. The switcher "Switch to firm" leads to the firm area; if no session of its own is active there, log in there once separately.

"Change package" rejects every attempt although my customer has a normal POS package — is that a bug? No, that is the current state: a package change via the portal works only as long as the customer is still in the pure factura tariff without a POS module. For customers with a POS package (Basic, Gastro, Delivery & Pickup, Club) the portal offers no package change — that goes through DiKAS.

I forgot the self-service module (or another module) — can I book it afterwards? As long as the customer is still "In setup": yes. On the customer detail page in the "Configuration" block, tick the module and save, without invoice. After activation the portal no longer offers this; contact DiKAS then. Details: Modules.

A module is rejected on saving — why? Either the package does not meet the prerequisite (e.g. Online ordering exists only with the package "Delivery & Pickup", Self-Service only with Gastro, Delivery & Pickup or Club), or the package already includes the module. The tables under Modules show what belongs to which package.

What happens if I do not activate a customer within 30 days? The instance is shut down automatically (locked, not deleted) — after 21 days without activation you receive a reminder email in advance. A Swissbit TSE that has already been delivered is then invoiced to you as the reseller. If you still activate the customer later, setup continues normally — the shutdown is lifted in the process.

Can I activate a customer twice or undo the activation? A second click on "Activate" does nothing further — no second invoice, no second invitation. There is no going back to the state "In setup": activation is final.

Why do I get no commission for an activated customer? Commission arises exclusively on paid subscription invoices. If an invoice is open, dunned or cancelled, the commission for this invoice does not apply — but it can arise again with the next paid period.

Can a customer use dikas Faktura together with a POS package? Yes. A license with invoicing and POS (or Gastro tables) remains a full POS operation: normal/expert mode, inventory, QR and self-service and the other operating modules stay visible, the invoicing functions are added.

Do I have to take care of the SEPA mandate of my activated customer? No. As soon as the customer is activated, they are responsible for it themselves — they grant it in their own customer portal under "SEPA mandates". Until then they pay individual invoices by bank transfer.