kafeOS pricing and pilot scope

How is pricing determined for kafeOS?

We do not publish a public fixed price list for kafeOS. The setup needs of a single cafe differ from the operating model of a multi-branch restaurant. This page explains what we discuss before preparing a proposal and how we separate cost items. Once your scope is clear, setup, services, and any external provider costs are listed in a written proposal. This information is not a specific price or a contract.

Branches, users, and daily workflows

We learn how many branches you plan to start with, who will manage them centrally, and which screens staff will use. You may want to start with loyalty and ordering, then add other operations later. Or you may want to consider checkout, kitchen, and TV menu screens together. We define scope by who handles each workflow from start to finish, not just by a feature list. We also discuss each branch's device and connectivity conditions.

• Branch count for the pilot and next phase
• Staff roles and checkout and kitchen needs
• Existing devices, internet, and operating conditions

Branding, menu, and initial setup

Your business name, logo, colors, menu, products, and initial rules are part of setup. If existing customer or product data needs to be imported, we separately assess its source, format, and transfer authorization. If an app store submission is planned, account ownership, submission content, and publishing responsibilities are also included in the written scope. Preparation time depends on the status of these inputs and external approvals.

• Who will provide brand and menu information
• Whether data needs to be imported
• Responsibility for app stores and third-party accounts

Training, support, and updates

We define training so staff can handle enrollment, points, rewards, or orders within their roles. The proposal covers the support channel, working hours, how requests are logged, and which updates are included. New feature development, day-to-day usage support, and an external provider outage are different service items. Clarifying this up front helps the business know who to contact in each situation.

Payments, POS, and other external services

The checkout workflow within kafeOS, an external POS connection, and bank card processing are separate things. Online card payments require a provider account, commercial terms, and production activation; online card payments are not enabled in the current production setup. External services such as e-Archive also require separate verification of the provider and business account. Integration requirements and any provider fees are listed separately in your proposal.

• Compatibility review for an external POS or tab system
• Payment provider and production activation requirements
• External service fees and business account requirements

How is a pilot planned after the demo?

First, we demonstrate a few of your most important workflows using sample data. If it looks suitable, we can plan an approximately 6–8 week pilot at one or two branches; timing, starting conditions, and fees are finalized in the written proposal. We define which transactions should be completed successfully and how training will work. At the end of the pilot, we review usage and transaction results, then decide separately whether to roll out to other branches. The pilot does not guarantee increased sales.

What should I include in a proposal request?

Tell us your business type, current and planned number of branches, checkout or tab system, and the first issue you want to solve. Let us know whether loyalty, ordering, or staff and management workflows are the priority; this helps us prepare the right demo. You can also share your target start period. You do not need to include passwords or customer records in your initial request.

• Your business and branch setup
• Existing software and required connections
• Top priority and target start period

Frequently asked questions